Closed mikeapp closed 2 years ago
It sends the visibility to MC. MC will set published appropriately with this information.
Yale only digital object in test Aspace: https://puitestarchivesspace.library.yale.edu/repositories/11/archival_objects/3411293 https://puitestarchivesspace.library.yale.edu/repositories/11/archival_objects/3411294
Public: https://puitestarchivesspace.library.yale.edu/repositories/11/archival_objects/699963 (There may be some old ones in test aspace that are Yale Only which were created before this update.)
Looks good on test. Was there a MC update and if so, do they need to be promoted together?
Story
DCS will write digital object information to ASpace through Metadata Cloud. There is an issue with Yale Community Only assets - these will only be viewable to ASpace users if they are on campus. We should set publish=False for the IIIF digital objects and only have the link to DCS in ASpace.
This will require updates to Metadata Cloud as well.
Acceptance When a DCS item has YCO permissions:
publish=False
for the IIIF manifest file versionpublish=False
for the Thumbnail file version