identify orphaned digital objects and re-link them as appropriate

[regineheberlein]

In the course of pulling a digital objects report, we identified multiple orphaned digital objects in repository 3. They seem to cluster around collection MC180, but their existence makes me think that we need to do a sweep for any and all orphaned digital objects in our ASpace instance. Questions and tasks include:

• orphaned digital objects epic: identify any and all orphaned digital objects #604
• orphaned digital objects epic: identify the collection and archival object they should be associated with #605
• For the 584 figgy objects whose do id's match a do id in aspace, check which of the corresponding ao's can be (re-)linked #614
• Counter-check dao count/cid/links in EAD serialization #615
• orphaned digital objects epic: identify whether a duplicate object exists that is linked to the target ao #606
• orphaned digital objects epic: either link or delete the digital object, as appropriate #607