Feature Request/Idea: Data Access Place add URI to support linkages
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Overview of the Feature Request
Currently the Data Access Place field is under the 'Terms' metadata and it doesn't support adding a URI or identifier for the access place , we've imported metadata using the DDI Import API and structured our links like this:
<setAvail>
<accsPlac><a href="http://odesi.scholarsportal.info/documentation/NHS/2011/NHS-2011-Profile.html"> Access data here </a></accsPlac>
</setAvail>
Would be better if it was like this:
<setAvail>
<accsPlac URI="http://odesi.scholarsportal.info/documentation/NHS/2011/NHS-2011-Profile.html">Data Access text</accsPlac>
</setAvail>
To support proper identification of those URI/locations.
What kind of user is the feature intended for?
Curator, Depositor, Guest,
Would support use of the DDI standard and provide structured metadata for data access place where datasets live outside of Dataverse, but with metadata only in Dataverse.
What inspired the request?
We use this field in our ODESI data repository (https://odesi.ca) and the field is integrated with our search to enable users to go directly to the data access place housed outside of Dataverse, but where Dataverse metadata is the searchable metadata source.
What existing behavior do you want changed?
We would like to add a URI accompanying field to support these linkages
Any brand new behavior do you want to add to Dataverse?
Yes more identifiers for these kind of fields.
Any related open or closed issues to this feature request?
Yes we would also like to revisit this in the context of this issue:
- #8191
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the DDI Import API handling of the accsPlac element and the related issue #8191. The request is complete when a Data Access Place can retain its display text while accepting a structured URI or identifier for external data access locations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- xml
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100