Skip to content

explicit identifier for fin import #251

Open
@qjhart

Description

@qjhart

The current methodology for the fin import cli is;

  • when an object has no identifier, and is a ArchivalGroup, then look to the schema:identifier and choose and ark: if it exists. For example the following would use ark:/87287/d7002v as the identifier
{
  "@context":  "http://schema.library.ucdavis.edu/context/dams.json",
  "@id": "",
  "@type": [ "fedora:ArchivalGroup", "CreativeWork", "Menu" ],
  "identifier": [ "ark:/87287/d7002v" ]
}

However, in practice, this would actually add the data as if it were explicitly set with the `"@id": "info:fedora/item/ark:/87287/d7002v"'.

If you have two identifiers that are arks: eg.

{
  "@context:": {
     "@context":  "http://schema.library.ucdavis.edu/context/dams.json",
     "shelfmark":"ark:/87287/d7r94j/"
  },
  "@id": "",
  "@type": [ "fedora:ArchivalGroup", "CreativeWork", "Menu"],
  "identifier": [ "ark:/87287/d7002v", "shelfmark:D-060/box:60+folder:112"]
}

Then it's unclear where to upload this data. The current plan is you can specifically add the @id parameter, and disambiguate this setup. This has two problems. One, we have to remember to add the info:fedora/item prefix, and second, in reality it's actually now ok in fedora 6 to have two @ids with valid LDP urls like:

{
  "@context:": {
     "@context":  "http://schema.library.ucdavis.edu/context/dams.json",
     "shelfmark":"ark:/87287/d7r94j/"
  },
 "@graph":[ {
  "@id": "info:fedora/ark:/87287/d7002v",
  "@type": [ "fedora:ArchivalGroup", "CreativeWork", "Menu"],
  "identifier": [ "ark:/87287/d7002v", "shelfmark:D-060/box:60+folder:112"]
  },
  {
    "@id":"info:fedora/ark:/9999/9999",
   "desc": "random info"
  }]
}

We are already using metadata with multiple @ids.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions