🦄 Spike: Processing previously loaded content

[ShanaLMoore]

Updated Ticket 2023-04-18

Story

We are trying to answer how can we ensure that previously loaded content in the digital library gets processed by the viewer? Considering SDAPI ingest and derivative Rodeo work

3. [This work](https://adl.s2.adventistdigitallibrary.org/concern/published_works/20215986_the_great_advent_movement?locale=en) originally uploaded on 1-30-23; the PDF did not reupload with the import, so the viewer didn't process the book. The TXT and thumbnail did reupload on 3/18. How can we ensure that previously loaded content in the digital library gets processed by the viewer?" 

Acceptance Criteria

• [ ] Follow up tickets for how can we ensure that previously loaded content in the digital library gets processed by the viewer are created

---

Old ticket

### Story Per Katharine, "I see some discrepancies in child works. Can you look at these examples and see if the issues are due to an error or due to the works still processing?" - [ ] 1. UV not rendering - [ ] 2. UV doesn't display human readable titles in the content panel - [ ] 3. Spike: How can we ensure that previously loaded content in the digital library gets processed by the viewer? Considering SDAPI ingest and derivative Rodeo work ### Acceptance Criteria 1. child works should render in the UV 2. UV should display human readable title in the content panel 3. TBD ### Screenshots / Video

1. [This work](https://adl.s2.adventistdigitallibrary.org/concern/published_works/20213922_evidence_from_scripture_and_history_of_the_second_coming_of_christ?locale=en) has an upload date of 3/14; child works show in the Items list, but nothing loads in the viewer. The child works show duplicates of pages such as page 002 and 011.  

2. [This work](https://adl.s2.adventistdigitallibrary.org/concern/published_works/20217998_christian_stewardship?locale=en) uploaded 3/20. The viewer shows the thumbnail and 15 page PDF, but in the viewer each page shows with a string of numbers and letters as the "title," rather than a human readable name which I expect to see. Will this resolve? Or can we fix the titles to show as they do in the Items list? 

3. [This work](https://adl.s2.adventistdigitallibrary.org/concern/published_works/20215986_the_great_advent_movement?locale=en) originally uploaded on 1-30-23; the PDF did not reupload with the import, so the viewer didn't process the book. The TXT and thumbnail did reupload on 3/18. How can we ensure that previously loaded content in the digital library gets processed by the viewer?" 

### Testing Instructions and Sample Files - TBD ### Notes Consider breaking these into separate tickets.

[jillpe]

Focus on criteria 2 for this ticket

[jillpe]

Point 1 and 2 has been resolved - Point 3 can be deferred until after SDAPI ingest

[ShanaLMoore]

Noting that we discussed the possibility of pushing this to the next phase of work or maintenance contract. This work doesn't relate to SDAPI and the deadline for ADL ingest isn't until November. cc @jillpe

[jillpe]

possibly helpful: https://assaydepot.slack.com/archives/C0313NJV9PE/p1689611025243569?thread_ts=1688740330.826599&cid=C0313NJV9PE

[jillpe]

related to

• scientist-softserv/adventist_knapsack#401

Possible to merge into one ticket?

[jillpe]

Potentially related to https://assaydepot.slack.com/archives/C0313NJV9PE/p1698254306742289

[KatharineV]

Team, today I noticed that some works have dropped out of the OAI feed for the adl:issue set. The works were present almost two years ago when my predecessor ran the first Bulkrax OAI importers. As a result, the periodical issue works have ingested and are present in the digital library repository, and the associated files are attached to the metadata, but the files (of course) don't render in the UV because they were imported looooong before the print gem.

I want you to be aware that these works have dropped from the OAI feed so that the solution for reindexing and/or rendering in the viewer does not require the works to be erased and rewritten in a manner that would be impossible now, thanks to the way the feed has changed. Our team is unable to repair the feed to reinstate the works, and I'm also sadly not able to identify why they were present in the feed and now gone.

So that you can understand what I'm saying, here are two examples.

Works are present on ADL prod:

1. https://adl.b2.adventistdigitallibrary.org/concern/published_works/22252037_western_midnight_cry?locale=en
2. https://adl.b2.adventistdigitallibrary.org/concern/published_works/22252165_vermont_telegraph?locale=en

Empty OAI_ADL query for each work's ID:

1. http://oai.adventistdigitallibrary.org/OAI-script?verb=GetRecord&metadataPrefix=oai_adl&identifier=22252037
2. http://oai.adventistdigitallibrary.org/OAI-script?verb=GetRecord&metadataPrefix=oai_adl&identifier=22252165