Skip to content

Arks with unregistered naans not parsed correctly #26

Description

@datadavev

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.

Metadata

Metadata

Assignees

Labels

Priority LowA bug but not a bad onebugSomething isn't working

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions