Fix OCR Catalog Search

[ShanaLMoore]

Summary

Is full or all text getting indexed? etc...

Acceptance Criteria

• When a user performs a catalog search for OCR, the parent should return. ref: https://gitlab.com/notch8/louisville-hyku/-/merge_requests/137#a79adb1024bf4a71a325bf3ac94b212477013dae

Screenshots or Video

Testing Instructions

Deploy i87-ocr-search to hyku-iiif (hyku branch) ✅ visit: demo.hyku-iiif.notch8.cloud/

1. Create a work. Upload an image that has text. OCR should run. Confirm that json coordinates are created as its derivatives. Confirm that a user can search for the text in the UV, and find a match.
2. Create a work. Attach a child. Confirm that a user can visit the parent's UV, search for the child's metadata and find a match.
3. A user should able be able to catalog search the child metadata and have its parent return
4. A user should be able to catalog search the child's ocr term and have its parent return

Notes

The commits in Louisville that worked towards this are:

• notch8/louisville-hyku@128a9ef — i149 - fix timing issue that cause child ocr search bug Shana Moore, (2022-09-21)
• notch8/louisville-hyku@50489ac — 90-ocr-highlighting Alisha Evans, (2022-05-12)
• notch8/louisville-hyku@211e888 — i19 - pull in uv configs from nnp to enable ocr search Shana, (2022-01-26)

maybe helpful refs:

1. https://gitlab.com/notch8/louisville-hyku/-/merge_requests?scope=all&state=merged&search=ocr

If things aren't working, try...

ActiveFedora::Base.reindex_everything

[ShanaLMoore]

to get this working, we needed to add and set advanced_parse to false, in the catalog controller.

For now we will note this in the readme, and decide if and how iiifprint should generate this in the future.

[laritakr]

@ShanaLMoore I don't see that the referenced branch is ready to deploy or has been deployed. Should this be moved back to "deploy to staging"?

[ShanaLMoore]

Yes, the deploy failed. I will move this back to deploy to staging.

[DeonFranklin]

This ticket passes Soft Serv QA