Look up DOIs after normalisation
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
When looking up by DOI, which differs from the DOI stored in Dataverse in upper/lowercase of ASCII characters, e.g. https://data.fz-juelich.de/dataset.xhtml?persistentId=doi:10.26165/juelich-data/ywb5p1, the dataset is not found. Instead, I expect seeing the same output as with https://data.fz-juelich.de/dataset.xhtml?persistentId=doi:10.26165/JUELICH-DATA/YWB5P1.
Note that case-insensitiveness affects only ASCII letters. Non-ASCII letters like “Ü”, while allowed in principle, must not be normalised.
We use Dataverse 4.20.
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
Trace the Dataverse DOI or persistentId lookup path responsible for the two example URLs. Reproduce the mismatch using the lowercase and uppercase DOI forms, then verify that ASCII letters compare case-insensitively while non-ASCII letters such as “Ü” are preserved and the two URLs produce the same dataset result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100