Arks with unregistered naans not parsed correctly
@datadavev is already working on this.
Since Aug 2, 2024.
Assessment
This issue has not been assessed yet.
Description
The introspection response for an unregistered ARK prefix presents incorrectly parsed identifier properties.
For example a request with the (currently) unregistered prefix of "99167" like https://arks.org/.info/ark:/99167/foo returns:
{
"pid": "ark:/99167/foo",
"scheme": "ark",
"content": "99167/foo",
"prefix": "",
"value": "foo",
"suffix": "9167/foo",
"target": "/.info/ark:/99167/foo",
"canonical": "ark://foo",
"status_code": 302,
"properties": {
"what": "ark",
"name": "Archival Resource Key"
},
...
with the parsed prefix and suffix portions incorrect.
The response is correct with registered prefixes.
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- Avg merge
- 21h 56m
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from CDLUC3/resolver
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
Support legacy inflection behaviorMay be free again @datadavev claimed this 394 days ago, and no pull request is open. Openbug
-
Service status availabilityMay be free again @datadavev claimed this 650 days ago, and no pull request is open. Openenhancement
-
Check availability of targets.May be free again @datadavev claimed this 650 days ago, and no pull request is open. Openenhancement
Similar issues
-
integration: media_player
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
home-assistant/core#193344 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
daniel-ospina/tortoise#13607 ·
Maintainers usually reply within 1 day
-
documentation priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day