UCSCLibrary / dams_project_mgmt

DAMS purpose is to provide access to digitized and born-digital UCSC Special Collections content. This repository is used for project planning. It holds the task tickets and roadmap for the different projects under DAMS.
2 stars 0 forks source link

RMB-PJ complex image sets: not all child works showing on parent work landing pages #458

Open rmjaffe opened 3 years ago

rmjaffe commented 3 years ago

Descriptive Summary

Not all child works are appearing within RMB-PJ complex image sets. In a couple cases (see Background), images that display as the representative images for the set do not appear in the listing of child images on the parent work page. This issue require investigation as Special Collections staff need to be able to access metadata records for all the child images in order to retrieve master filenames and fulfill patron requests.

Background

In response to a patron request, Luisa was wanting to locate the master filename for the image that appears as the representative image for this group of RMB-PJ-Black Panthers images: Black Panther Free Breakfast for Children Program, St. Augustine's Episcopal Church [merged with Trinity Church 1975]. Commissioned by Swedish magazine, Vi (https://digitalcollections.library.ucsc.edu/records/8k71nk74w). However, this image does not appear among the child images belonging to this set. She observed a similar issue with another object set: George Gaines "Baby D" and his men at the Manzanita Center, Marin City (https://digitalcollections.library.ucsc.edu/records/p5547t610).

No sure what the issue is here, but I suspect it may have something to do with the metadata re-ingest and image grouping work we did. At the point at which we decided to group the RMB-PJ images, they were already in the DAMS, and it was decided that instead of removing the collection from the DAMS and re-ingesting it with the structured metadata, that Ned would only reload the metadata. If we had removed and reloaded the URIs on the images would have changed, which is something Sue and Ned wanted to avoid.

Following the reloading of the metadata, Ned had to do a lot of work to clean up the assignment of child images and their metadata to the correct parent metadata records. I have no idea what form that work took, why some of the children are not showing, but clearly it's something we overlooked during QA of the collection.

Acceptance Criteria

This is what done looks like

Expected Behavior

All child works belonging to a image group appear in the child works listing on the parent work landing page.

Actual Behavior

Some child works appear to be missing from the list.

Related Work

Possibly, Add parent records for the MS20 Collection UCSCLibrary/dams_project_mgmt#92 or other tickets that were created as a result of Create more tickets for the republication of MS20 RMB-PJ Collection UCSCLibrary/dams_project_mgmt#82

rmjaffe commented 3 years ago

Here is another example in which the representative image does not appear again within the list of child works: https://digitalcollections.library.ucsc.edu/concern/works/4b29b810w

crisr15 commented 2 years ago

This is the only collection that currently has the complex image set. This should be corrected for future ingests as well so that it does not occur again.

rschwab commented 2 years ago

@bkiahstroud Could we use this ticket as part of the bulkrax handoff process: use resloving it to train ucsc staff?

bkiahstroud commented 2 years ago

Moving to Sandbox QA to determine if it's still an issue or not

rschwab commented 2 years ago

@rmjaffe Can you confirm whether this issue still exists on Sandbox? I think we'll need to fix this with a future Bulkrax round-trip, but wanted to double-check.

rschwab commented 2 years ago

Actually this problem doesn't exist on Sandbox because this collection doesn't exist on Sandbox. I'm moving back to "Ready for Development" because the issue exists on production.

rschwab commented 2 years ago

Probably will be resolved by UCSCLibrary/ucsc-library-digital-collections#412

rmjaffe commented 2 years ago

As this issue is noted and will be resolved once we implement our interim complex image objects display strategy (either UCSCLibrary/ucsc-library-digital-collections#412 or #395), I'm retiring this card.