IQSS / IQSS/dataverse-frontend
Support ORCID links
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 31
- Forks
- 26
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 4
Description
Overview of the Feature Request
Support ORCID links (and other currently supported ids) on the frontend, making these identifiers clickable and navigable to the corresponding landing pages.
In the current Dataverse UI, this logic is handled in the frontend side (JSF), so it is not straightforward to return these links via API (See: https://github.com/IQSS/dataverse/pull/7979). It is necessary to rethink the existing solution and find the optimal balance between frontend and backend logic to support this functionality.
This issue will potentially split into more spike issues.
What kind of user is the feature intended for?
SPA user
What inspired the request
What existing behavior do you want changed?
- ORCID author ids as links
Any brand new behavior do you want to add to Dataverse?
N/A
Any open or closed issues related to this feature request?
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 with the related dataverse-frontend issue #115 and the linked Dataverse PR #7979, then trace how identifier links are currently handled in the JSF frontend. Define the frontend/backend split for ORCID and other supported identifiers; done means SPA users can click author identifiers and reach the corresponding landing pages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100