Feature Request: Improve CVOC Retrieval filtering mechanism for Local Contexts

[qqmyers]

Overview of the Feature Request
Local Contexts Integration leverages the external vocabulary mechanism. The relevant JavaScript leverages Dataverse as an authenticating proxy to access the Local Contexts v2 api. (see #11294).

One limitation of this related to retrieval-filtering. The proxy API added requires knowing both the Dataverse dataset id and the Local Contexts project id (a security measure to avoid Dataverse being usable as a way to get information about arbitrary Local Contexts projects - the api will only return useful content for projects associated with the specified dataset). Unfortunately, the current retrieval filtering mechanism, while allowing some parameterization of the retrieval-url, does not allow inserting the id of the dataset when trying to retrieve content.

For retrieval filtering to work with Local Contexts v2 api, we either need a way to specify adding a dataset id in the grammar for the retrieval-url field of the external vocabulary configuration, or a new API call in Dataverse, possibly restricted to localhost-only, allowing lookup of a project without knowing the dataset id, or some other relevant change.

For now, the Local Context configuration examples still use the v1 API (which is limited in terms of which fields are returned and presumably will go away at some point), so moving to support the v2 API is more of a feature-request/next-step than an immediate issue/bug in using the Local Contexts Integration.

Are you thinking about creating a pull request for this feature?
TBD - depending on the scope of the ongoing Local Contexts projects