Provide a public view of the data model for the access team #589
Conversation
This file contains hidden or 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
This ensures that no items, collections or files with dark access are in the public representation. It also adds a link to the parent virtual object if any.
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.
Why was this change made? 🤔
This is a refinement to the purl-fetcher API. This ensures that no items, collections or files with dark access are in the public representation. It also adds a link to the parent virtual object if any.
This moves the data about virtual objects in the XML into the data passed to the access team: https://github.com/sul-dlss/dor-services-app/blob/main/app/services/published_relationships_filter.rb#L36-L42
Details at https://docs.google.com/document/d/1GQY8QLwLNbSrw6RErFpj7HEpgvODqH81M0YOlPsVIY0/edit#
How was this change tested? 🤨
not tested yet.