Manifest regeneration enhancements [placeholder]

[eporter23]

Story

As a Library Staff Depositor, I want to reduce the frequency of automatic manifest regenerations that may occur, so that this resource-intensive process is not triggered unless explicitly called

Acceptance Criteria

Use one or more of the following options to provide acceptance criteria.

Notes

The original manifest generation process was built several years ago, and includes a behavior that will automatically generate or re-generate a manifest if 1) a cached manifest does not exist or 2) if certain changes are made to a work's metadata, visibility, or FileSets. In production, we anticipate that not all works will have a cached manifest, because we had been ingesting material prior to developing our most recent caching strategy.

We later did work to try to optimize this behavior and resolve a bug where the manifest generation job would execute multiple times for the same work as a result of viewing a work before its completed manifest was cached. This bug still occasionally recurs, however, and is particularly problematic for large book objects, where the manifest generation can take anywhere from 20 minutes or longer to complete. This behavior is also problematic when we are attempting to re-index works for full text searching, because the addition of a new fileset will result in a manifest being generated, even though the Fulltext file being attached is not immediately utilized in the manifest. Additionally, we may want to add the Fulltext Data file as a download option in the UV, and editing the work to make that change will result in a second manifest regeneration process.

Links to Additional Information

Add links here

Possible Tasks

• Identify works that do yet not have a cached manifest in production
• Manually generate manifests for the above works
• Disable automatic generation and re-generation of manifests in Curate and Lux for specific conditions (TBD)
• Determine what a user should see if they happen to encounter a work without a manifest
• Implement any needed changes related to the above
• Update training and support documentation to assist Curate users related to any changes

Given/When/Then

• Given (some context) and (some other optional context)
• When (some action is carried out)
• Then (a set of observable consequences should occur)