CollectionObjects with CatalogNumber DataAttribute without Identifier::Local::CatalogNumber

[mjy]

Perhaps candidates for script.

/tasks/collection_objects/filter?per=50&local_identifiers=false&data_attribute_predicate_id[]=485&extend[]=dwc_occurrence&extend[]=repository&extend[]=current_repository&extend[]=collecting_event&extend[]=taxon_determinations&extend[]=identifiers&exclude[]=object_labels&page=1

[tmcelrath]

I think a script could work where there are no identifier overlap issues, but I'm not sure how many are there. So far, 2/3 I've checked were complicated cases where someone used the wrong namespace, so a script would get too complicated too quick. Is there a way to run a script to check how many would fail if you just took the catalog number and namespace from the DataAttribute and tried to add it to the CO?

[tmcelrath]

Example:
https://sfg.taxonworks.org/collection_objects/224986 has data attributes of: Prefix: "Insect Collection" and CatalogNumber: "17031", but that is occupied by: https://sfg.taxonworks.org/tasks/collection_objects/browse?collection_object_id=24315 which ACTUALLY is INHS PLECOPTERA 17031 but that one ALSO exists here: https://sfg.taxonworks.org/tasks/collection_objects/browse?collection_object_id=488034.

So this one would need a Unify with the bottom two objects, keeping the correct catalog number of INHS Plecoptera 17031, deleting the incorrect INHS Insect Collection 17031, then adding that to the first one.

I can do all that manually, but dang it's annoying to do 2000+ of those.