Migrate AMEEL Collection (PID 59)

[sshetenhelm]

Story
We need to migrate approx. 1,524 parents from the AMEEL collection (PID 59) from FindIt to DCS. This is a hierarchical collection in FindIt, which means there are many unneeded OIDs.

Parents to migrate: AMEEL_parentOIDs.csv

Acceptance

• Export image files from Fedora
• Import image files into the DCS pairtree
• Generate list of Parent OIDs (use list above)
• Import the objects into DCS UAT into the SML admin set as Public
• Audit images
• Reassociate with catalog
• Get approval from stakeholder
• Migrate into Production
• Update handles

[sshetenhelm]

As per Maggie, downloading of images is in progress.

[MaggieZhaoYale]

@sshetenhelm This is the handle file: ameel_handle.csv

[sshetenhelm]

1524 parents in UAT MGMT
4 in Blacklight

Update Visibility to Public for all, then will report back.

[sshetenhelm]

Up to 474 in Blacklight, still working.

[sshetenhelm]

Up to 628 in Blacklight, still working.

[sshetenhelm]

Up to 1512 in Blacklight. Currently investigating the following 12 OIDs:
15976796 -image 351 broken
15976797 - no images; uploaded incorrectly in LB
15696840 - deleted; hierarchical
15976488 - image 9 broken in LB
15976864 - no images in DCS; looks fine in LB?
15976865 - no images; uploaded incorrectly in LB
15976866 - no images; uploaded incorrectly in LB
15976869 - no images; "you have requested a record that does not exist" in FindIt
15976871 - no images; all images broken in LB
15976872 - no images; uploaded incorrectly in LB
15976874 - no images; uploaded incorrectly in LB
15976875 - no images; uploaded incorrectly in LB

[sshetenhelm]

Made #2982 to address 11 objects with missing images. Will move forward with migration of other objects. Currently working on reassociation, as that is necessary for the metadata for these objects to "make sense" in DCS.