External Controlled Vocabularies: Support vocab specific retrieval filtering#12331
Open
qqmyers wants to merge 6 commits intoIQSS:developfrom
Open
External Controlled Vocabularies: Support vocab specific retrieval filtering#12331qqmyers wants to merge 6 commits intoIQSS:developfrom
qqmyers wants to merge 6 commits intoIQSS:developfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 this PR does / why we need it: To support use of multiple services on one field, i.e. to allow selecting a Person (ORCID) or organization (ROR), it is important for Dataverse to be able to retrieve and cache information about either PID type (i.e. so that names, etc. can be used in exports). To do that, the External Vocabulary mechanism (specifically the CVocConf schema) is being extended to support including retrieval-filtering and other elements per vocabulary (versus one for the whole field). That is in gdcc/dataverse-external-vocab-support#58 . This PR makes the associated changes to Dataverse's code to use those per-vocab entries.
Which issue(s) this PR closes:
Special notes for your reviewer:
Suggestions on how to test this: Using the person-or-org script in the external vocab repo is probably the easiest way to see it in action.
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
Is there a release notes update needed for this change?:
Additional documentation: