Investigate Aspace digital object issues

sshetenhelm commented 5 months ago

Story When some objects have either (a) been reassociated with ArchivesSpace or (b) newly ingested with Aspace information, they have not been displaying in Archives at Yale. We would like to have an investigation into whether or not there is a “quick fix” that could be made in Metadata Cloud, or if this is a larger Aspace issue.

The purpose of this ticket is just to undertake a quick investigation; if the issue seems more complicated than an hour or two of work can discover and fix, we can wait until we have more staff time/support (AKA when staff come back from leave or get hired).

Examples OID 16538107

After being reassociated with Aspace uri, the UV and link appeared in ArchivesSpace digital object record, but Archives at Yale retained a manually-created digital object record/link.
UV and link did not appear in Archives at Yale until the object was made Private, and then made Public again

OID 16538108

After being reassociated with Aspace uri, the UV and link appeared in ArchivesSpace digital object record, but Archives at Yale retained a manually-created digital object record/link.
This object has NOT been made Private and then Public again, so as to illustrate the error.
Object information is available in Metadata Cloud digital object queue with timestamp of 2024-02-23, which matches date of reassociation
Archives at Yale record is retaining legacy link

Acceptance

[ ] Investigate issue with UV and links not appearing in ArchivesSpace
[ ] Make ticket for low-hanging fruit fix OR Make placeholder ticket for future work (may be related to on hold ticket #2526?)

martinlovell commented 5 months ago

It might be something related to how MC writes updates.

MC does not bother changing the ArchiveObject if it already has an instance that's pointing to the DigitalObject it is updating. So the ArchivalObject doesn't get modified. So, it seems possible that the page for the ArchivalObject doesn't get refreshed in the PUI even though the DigitalObject is updated. Maybe that's more of an ArchivesSpace issue.

laurenb33 commented 4 months ago

I asked Trip about this; he said he would investigate what was happening and get back to us. He mentioned that Stephen in DSCA reported an Aspace-DCS issue too and they may be related. When I have an update from Trip, I will report back.

DraxIndustries79 commented 4 months ago

Waiting for Trip's investigation

sshetenhelm commented 3 months ago

@laurenb33 anything from Trip? If not I suggest we pull this back to backlog.

laurenb33 commented 3 months ago

Not yet - he was out last week. I think it's a good idea to move it to the backlog.

yalelibrary / YUL-DC

Investigate Aspace digital object issues #2757