Closed seth-shaw-unlv closed 5 years ago
Title (Goal) | Record Born-digital File's Original Name |
---|---|
Primary Actor | Repository Manager |
Scope | |
Story | As a repository manager I want to record a file's original path as a PREMIS "originalName" property. |
Some of our repository materials are born-digital items where we want to record the original full path of the file. E.g. 2016-2018 photographs/neo000093-013.TIF
. I propose we add a field to the various Media entities to record this.
I agree with this proposal. However, we haven't discussed what approach to take to replace 7.x's Islandora PREMIS, but as part of the Islandora Riprap module, I started work (didn't get far) on providing PREMIS fixity event data at https://github.com/mjordan/islandora_riprap/issues/5.
This is probably related to our meta issue on auditing (https://github.com/Islandora-CLAW/CLAW/issues/927).
We also need to pick which version of PREMIS we are using. Fedora 5 uses a PREMIS 1 namespace built-in (http://www.loc.gov/premis/rdf/v1#
); the module @mjordan cites appears to serialize PREMIS 2 XML; but LOC appears to only recognize PREMIS 3 as an RDF ontology (the page for 2.2 says they have an OWL ontology, but the linked page only refers to v 3).
PREMIS 3 is the one to go with.
So, for this usecase we can use http://www.loc.gov/premis/rdf/v3/originalName
which we can shorten to premis3:originalName
.
Hey, sorry if I missed the discussion elsewhere, but why is the field storage in islandora instead of islandora defaults?
I don't recall the original reason, but the pattern of placing the field storage configs for media fields in core feature and the field definitions in islandora_defaults was established by @dannylamb a while ago.
You can see the existing field storage configs @ https://github.com/Islandora/islandora/tree/8.x-1.x/modules/islandora_core_feature/config/install. Now that I think about this, I seem to recall it has something to do with setting up views we can keep in core regardless of the field definition...
^^ That plus things like making a field multi-valued are locked down by the core feature and don't change unless we explicitly do so and then provide an update hook for.