port app/services/hyrax/manifest_builder_service_decorator to the iiif_print gem

[kirkkwang]

Summary

File now exists, but needs to be made functional. Specifically for IIIF manifest 2 and 3

ref: https://github.com/scientist-softserv/iiif_print/blob/main/lib/generators/iiif_print/templates/manifest_builder_service_decorator.rb

Indiana is open to upgrading their manifest.

Heads Up: Indiana has a configuration to pull in the metadata into the manifest. This will need some work, and we also may need to consider how it will work with AllinsonFlex.

The end goal is for the UV to display the way that LV has it.

---

Acceptance Criteria

• When looking at the works show page, works with metadata should display their metadata in the Universal Viewer right side panel

Screenshots or Video

Testing Instructions

https://demo.hyku-iiif.notch8.cloud/

• Create a work with some metadata properties
• Navigate to its show page
• Open the right side panel and confirm the metadata shows up

Notes

• AllinsonFlex handling will need to be apart of a different ticket #298
• Essi uses this implementation where it seems there is select metadata to be displayed
• Essi's implementation does not support facetable links fro the UV metadata panel
• Essi uses IIIF Presentation Manifest V2 which is the Hyrax 2x default, while UTK (on Hyrax 3x) uses IIIF Presentation Manifest V3

[ShanaLMoore]

QA RESULTS:

On staging, when creating a manual work, we can see the file in the UV. However, when you add a child manually, the parent's UV no longer displays anything. When you click into the child, we can see its file in the UV.

[ShanaLMoore]

This passes QA:

On staging, I manually created a parent and child work. I can see the child work and its metadata, from the parent's UV. Created manually...

Additional examples: https://demo.hyku-iiif.notch8.cloud/concern/images/725b2026-7804-4338-a776-27436b3299b9?locale=en

However, I will create a separate spin-off ticket to handle the following edge case cc @kirkkwang A UV should still render if the parent doesn't have a fileset. Scenario was created by importing sample csv: relationship-example.zip