Support IIIF canvas labels and metadata from node #1072
Merged
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.
What does this Pull Request do?
This PR allows us to use content fields to populate canvas labels and metadata for the IIIF Manifest views style plugin.
E.g. currently when we use Mirador the media's name is used for the canvas label in viewer. However, our child nodes have title metadata, even if it is simply as "Cover", "Page 1", etc. or "Recto" and "Verso" which this PR allows us to configure. Also, Mirador can display metadata with each canvas (see IIIF Presentation API section on metadata and "Metadata on any Resource" from the cookbook), which we didn't support. This PR allows us to add fields to the view and include them in metadata display.
What's new?
How should this be tested?
Documentation Status
Additional Notes:
`views.view.iiif_manifest.yml` for testing canvas metadata
Interested parties
@Islandora/committers, esp @alxp and @joecorall