Hi!
I do not know why I can’t find it on the web but I really can’t find the URI, namespace, prefix and file for “CRM” - can someone help me?
Thanks a lot!!!
Best,
//Staffan
sorry, wrong name, the name is “curation:”
Customer relationship management (CRM) is a set of integrated, data-driven software solutions that help manage, track, and store information related to your company’s current and potential customers.
Hi Staffan,
I’m a noob concerning CIDOC-CRM but this link can help:
https://cidoc-crm.org/
Cheers,
Hans Ruedisueli
1 Like
If you talk about the “curation” ontology that i added in some of my modules (Access, Block Plus, Bulk Import, Shortcode, etc.), it is not a standard one, but a simple way of managing common values that researchers and documentalists need. In fact, this ontology has three purposes, all related to the uses of documentalists/librarians/archivists/curators, so it was called curation.
First, it is a response to the real needs of documentalists and researchers. For example, they need a way to store the access rights to a resource, with start and end embargo dates, or to mark some items reserved or selected. Or they want to define a status, a rank, a number or to track various data about a resource, or to make a private note in some records. Or to keep the publication city separate from the publisher, but that’s not possible simply in Dublin Core or in bibo, so there is location for that. Or to store coordinates separate from the place set in Dublin Core “spatial”. Or they require a type that is different from the Dublin Core “type”.
Secondly, the ontology makes it possible to classify a resource in several properties, when the user does not want to mix them all up in Dublin Core “subject”, so there are category, collection, set, subject, tag, and theme. The meanings of these terms are close together, and deliberately broad, which is good for librarians because they can choose the ones they want. Of course, this is bad for a real ontology, but it can be a temporary way to store values until they find more accurate ontologies.
A third purpose exists: to facilitate the migration from Omeka Classic, therefore it explains the presence of the terms tag, new and featured, which are common in many tools or cms, but not standard in Omeka S.
So this ontology is a way to group all above common terms in a single ontology, thus avoiding to create an ontology for each module or each project. Note that all terms are marked “experimental”: ideally, the user should use better established ontologies where possible. Nevertheless, the curation ontology is sufficiently stable. But indeed, it should be normalised and published somewhere.
1 Like
This topic was automatically closed 360 days after the last reply. New replies are no longer allowed.