Change the Universal Viewer to be embedded from a configurable source #304
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This changes the way that the Universal Viewer is initialized into a view. Instead of a local installation, it pulls a remote viewer from a content provider into an inline frame element.
The source of the viewer is configurable in the runtime environment as:
If those values are absent, then the path to the viewer (and the UV configuration) will be a URL relative to the running application. In that case it would expect a local installation.
Also, there is a temporary measure put in place to suppress the initialization of the viewer if the link that it gets from an EAD DAO does not match a known pattern. This is a pretty opinionated piece of code; it is literally looking for our institutional PURL patterns that represent a IIIF manifest. This is to provide flexibility during final legacy migration and can be taken back out when not needed.