Omeka S is a powerful and flexible tool for creating and managing digital collections, but its terminology might be confusing for those who are starting to work with it. Hereunder, some of the key terms you need to know in order to better understand how this platform works are synthesized.
1. Class
A kind of resource, as defined by a vocabulary. Often, vocabularies specify what properties can be used with particular classes. For example, a foaf:Person type of resource could have properties like foaf:familyName, but it would not be expected to have a dcterms:publisher property.
Omeka Classic analogy: Item type.
2. File
A file is data uploaded to an Omeka S installation which is associated directly with an item. Any type of data can be files, from images to text or audio files.
Omeka Classic analogy: File (although the analogy is weak).
3. Global Admin
This is the administrator who has total control over the Omeka S installation. Usually, it is who creates the installation and manages the global setting.
Omeka Classic analogy: Superuser.
4. Installation
An Omeka S installation is a software specific instance, which can be managed by a central IT department of an institution. The installation allows creating and managing several sites within the same instance.
Omeka Classic analogy: it does not have a direct Omeka Classic analogy.
5. Item
An item or token is a register used to create a site in Omeka S. Items can be shared between sites within the same installation, unless unless otherwise specified
Omeka Classic analogy: Item
6. Item Set
An Item set o a token set is a group of items. Items can belong to multiple token sets.
Omeka Classic analogy: Collection.
7. Media
Media are representations or descriptions of a item, which go beyond metadata. This can include files (images, documents, videos) or external sources like YouTube videos.
Omeka Classic analogy: File (although the analogy is weak).
8. Modules
A module is a plug-in which can be added to Omeka S in order to expand its funcionalities. Modules allow adding new data entry options or new funcionalities to sites.
Omeka Classic analogy: Plugin.
9. Property
A property is a type of metadata which can be used to describe a new resource. A common example is dcterms:title, which can be used to describe the title of a element. Properties values can be literals (text), internal resources or external URIs.
Omeka Classic analogy: Element.
10. Resource template
A resource template is a predefined porperties se, and optionally a class, which is used to create items. Templates guide items creation specifying the properties which must be completed.
Omeka Classic analogy: Item type (although the analogy is weak).
11. Site admin
The site admin is in charge of managing a single site within an Omeka S installation.
Omeka Classic analogy: Superuser role.
12. Value
A value is real information which completes the Resource-Property-Value triple. For example, if the property is dcterms:title, a value could be "Heart of darkness". Values can be literals (text) or URIs to external data.
Omeka Classic analogy: Element text.
13. Vocabulary
A vocabulary is a RDF metadata properties and class collection used for describing resources. These vocabularies are created externally to Omeka and can be imported for use within the Omeka S installation.
Omeka Classic analogy: Element set.
Mastering these basic terminology is the first step for working efficiently with Omeka. You are invited to keep exploring the platform's funtionalities and applying what you have learnt about creating and managing your collections.
