Expose file set annotations as=iiif #345
Open
+162
−57
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
fixes https://github.com/nulib/repodev_planning_and_docs/issues/5779
Works with many files sets with transcriptions are causing performance issues. Refactor so that transcriptions are referenced by the IIIF manifest and served as separate route.
Specific Changes in this PR
file-sets/<id>/annotations?as=iiifthat serves a file set's annotations (right now that's just a single transcription)manifest.jsso that the transcript is referenced at the annotations routegetWorkFileSetsfunction to take a sort parameter so file sets can be sorted by rankHow to Test