As someone working with collection management systems for many years, I wanted to ask if there is any news/update/infos, regarding auto-incrementing custom identifiers?
Since Omeka is actually amazing for becoming the main input source for collection management, it also becomes the entity assigning the IDs.
See related, but ending threads from 2021:
If nothing exists: Would anyone be interested in writing a paid module?
How are other archival institutions using Omeka handling this?
Hi, maybe an unconventional way to achieve this without writing a module: create a database trigger which would update the value column of the value table after a new row is inserted with the property_id set to the id corresponding to the dcterms:identifier (found it in the property table).
Ok, I said it was not conventional
That said, I think that a simple increment may not be relevant as a safe identifier. DC says:
Recommended practice is to identify the resource by means of a string conforming to an identification system. Examples include International Standard Book Number (ISBN), Digital Object Identifier (DOI), and Uniform Resource Name (URN). Persistent identifiers should be provided as HTTP URIs.
Anyway, the trigger can perform a more complex calculation than adding 1
Thanks for the DC quote. However, I’m very much familiar with all sorts of identifiers - yet I’m simply looking for “the classic, conventional way” of using regular, in-house identifiers, as all GLAM institutions I’ve been working in-and-with have.
Something like “prefix-index[-subindex]”.
And the fact that Omeka doesn’t provide such mechanism, means that it seems to be unintended for the use of generating IDs, rather than having IDs generated by (and external?) cataloging system and then imported?
I can’t be the first, nor only one intending to assign “classic” identifiers?
How is everyone else doing it?
I mean IDs like:
V-00815
WF-DOC-0001
e07-00815_01
The stuff that things on the shelf in museums have on their stickers
