Works failed to import with "Frozen Error"

[KatharineV]

We have to run lots of large jobs through Bulkrax to slot thousands of periodicals into their collections in the ADL tenant. I ran the first importer to do this work on 12/10 (with 4,500 works it is still running today, 12/11) and some of the works are failing with the message "Frozen Error." We have so many importers to create and run that it's impractical and disheartening to have to circle back and rerun errored entries if the errors can be avoided. Is there any chance the Frozen Error is related to a cutover bug and can/will be fixed in the new year?

https://adl.b2.adventistdigitallibrary.org/importers/523?locale=en

[KatharineV]

@laritakr I'm dropping a note here to ask if you folks will keep an eye on this current import that caused issues due to valkyrie/fedora. There's some weird stuff going wrong that I've never seen with an import before. For example, these new works aren't registering in the catalog search details as I'd expect. The count of total items in the repo hasn't increased. The import is almost done with 4,477 works, but the total work count is still close to 116,000, which is where it started.

[laritakr]

Hmmm I know that some of the works existed previously, but I would expect that the ones which completed normally hadn't imported before and should increase the count. This is definitely something to check into as well. Thanks for pointing it out.

[KatharineV]

I may be inflating the number of works that were new. This may be my mistake. I will double-check my numbers, but thanks for keeping an eye out just in case.

[KatharineV]

Another weird behavior from this importer that is affected by the valkyrie/fedora migration. This morning, like two hours ago, there were 17,000+ jobs queued in GoodJobs. I just checked and the jobs are at zero. The CSV that was running had ~4,500 works in it, and all should be slotted into various collections. The parent collection is here and it should contain all ~4,500 some periodical issues. It only has about 1,300 right now. The child collections, which should contain periodical issues by volume year, appear to be empty (I spot-checked four of the 100+ subcollections).

I know we may be able to rerun this import after the Valkyrie/Fedora move is complete and things will be fixed, but I'm marking all issues just in case. It is critical that the importer be able to move existing works and new works into existing collections and new subcollections, because this collection architecture is required for our hundreds of thousands of works to be browsable. Running the collection jobs by Bulkrax import is also the solution that Jeremy scoped for us when we had to break the collection links to make the OAI feed work to migrate from Islandora.

Just want to mark this as a critical fix, if completed migration doesn't solve things. Thank you so much, team.