uhlibraries-digital / bcdams-map

Metadata Application Profile for the Bayou City DAMS
MIT License
6 stars 5 forks source link

Update Identifier guidelines #42

Closed metaweidner closed 7 years ago

metaweidner commented 7 years ago

https://uhlibraries-digital.github.io/bcdams-map/guidelines/identifier

librarycard commented 7 years ago

can we put OCLC number here?

metaweidner commented 7 years ago

@librarycard That seems reasonable. Do you anticipate any other types that we should include in the guidelines?

librarycard commented 7 years ago

@metaweidner i think that should cover it -- i can't think of any others at the moment.

amgaynor commented 7 years ago

@metaweidner @librarycard is this also where we would put the accession number? If so, would we follow the format "1970-001, Box 5, Folder 20"? If we did this, however, this particular identifier wouldn't be unique.

metaweidner commented 7 years ago

@amgaynor Uniqueness is not required. The accession number should be sufficient to make that construction useful as an identifier.

amgaynor commented 7 years ago

@metaweidner Ok sounds good. I think we talked about the possibility of Brays generating this field value based on the filename. Does that sound right?

metaweidner commented 7 years ago

Let's use a table for the identifier examples instead of a bulleted list, something like:

Type Example
Call Number [call number example]
OCLC Number [oclc number example]
Archival Location [archival location example]
ARK [ark example]
amgaynor commented 7 years ago

I didn't have an example of a real digital object ARK, so I put a fake one in the documentation. I'll update that once we have some real digital object ARKs.

librarycard commented 7 years ago

add to preservation input guidelines: preservation package ark goes here