Update schema to allow vocab level overrides of retrieval params#58
Draft
Update schema to allow vocab level overrides of retrieval params#58
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.
There is community interest in allowing two different services to be used on the same fields, e.g. for ORCID and ROR to allow person or org entries, or multiple vocabulary services for a keyword/subject field, etc.
While this is ~possible today in that a script can be written to support multiple services, the schema for the :CVocConf setting and the backend Dataverse repository currently have no way to detect/manage multiple types of PID in a given field.
To support that, this PR changes the schema to allow retrieval-filtering to be defined per vocabulary. (Top-level entries are still allowed for backward compatibility.) With related changes to Dataverse, this should allow filtering to detect which PID type is being used and then filter appropriately.
This PR is draft until the related Dataverse PR is in place. See #9828 for some discussion