orphaned digital objects epic: identify the collection and archival object they should be associated with

[regineheberlein]

54,114 digital object records in ArchivesSpace exist with one or more of the following being true:

• the do is not associated with a resource or component/archival object record
• the do is not associated with a file_uri (i.e. link to image)
• the do is not associated with an instance record

Figgy has 57,346 objects with source ArchivesSpace. Comparing against the 54,114 suspected orphans, I can match 755 that we will be able to re-link unless they are duplicates.

That leaves 53,359 confirmed orphans.

NB: The total number of figgy objects is higher than the number of active figgy objects because figgy doesn't delete objects. As such, the logic figgy objects-aspace do's = number of aspace orphan do's does not work.

[regineheberlein]

I was able to identify (a paltry) 29 do's that may be candidates for re-linking; mss is looking into them.