max-mapper / max-mapper/handle-protocol
HS_ALIAS
Open
Nobody has claimed this yet.
help wanted
- Dominant language
- JavaScript
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
I currently ignore HS_ALIAS values during resolution
test dois (first one aliases to second):
10.1016/s0009-9260(01)90959-6
10.1053/crad.2001.0959
Contributor guide
No contributing guide indexed for this repository
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 locating the handle-resolution entry point and reproduce the issue with the two DOI values in the report, where the first aliases to the second. Trace how HS_ALIAS values are handled and verify that resolving 10.1016/s0009-9260(01)90959-6 follows the alias to 10.1053/crad.2001.0959.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100