Main Page
Welcome to this wikibase implementation of the Records in Contexts Conceptual Model (RiC-CM v1.0).
Implementation notes
1. Implementation of RiC-CM entities
RiC-CM entities are implemented as Items.
2. Implementation of RiC-CM attributes
RiC-CM defines attributes of entities. In this wikibase, attributes are implemented as Properties, with some exceptions:
a. attributes shared by all entities
RiC-CM defines three basic attributes that are shared by all classes: identifier, name, and general Description.
Since they correspond to features pre-defined by the wikibase data model, they have not been implemented separately in this wikibase.
They map onto wikibase as follows:
| RiC-CM | wikibase |
|---|---|
| RiC-A22 Identifier | Item id (assigned at creation) |
| RiC-A28 Name | label |
| RiC-A43 General Description | description |
b. entity attributes by item type
Attributes on entities are implemented as properties, with a String datatype for notes and other discursive fields and an Item datatype for controlled values. Two attributes, RiC-A13 Date Qualifier and RiC-A19 Expressed Date, are implemented as statement qualifiers rather than properties on entities. They add to the four qualifiers already defined by RiC-CM (certainty, date, description, and identifier).
3. Implementation of RiC-CM relations
In this implementation, RiC-CM relations are implemented as Properties.
4. Implementation of controlled vocabularies
In this implementation, controlled vocabularies are implemented as entities (not strings). The following vocabularies have been loaded:
| Vocabulary | Source | Vocabulary | use with |
|---|---|---|---|
| record set type | Library of Congress | EAD 2002 schema / @level | P230 |
| content type | Library of Congress | MARC Code List for Content Types | P219 |
| state / diplomatics | Library of Congress | Generation terms | P232 |
| language | Library of Congress | MARC Code List for Languages | |
| occupation | Folger Library | Terms for Occupations in Archival and Manuscript Collections | |
| demographic group | Library of Congress | Demographic Group Terms | |
| UNDER DEVELOPMENT: | |||
| carrier type | Library of Congress | ||
| event type | Library of Congress | ||
| method of production | Library of Congress | ||
| recording medium | Library of Congress | ||
| genre | Library of Congress | ||
| paper | RBMS |
5. Constraints
Constraints are implemented as Wikidata constraint properties. For example, an attribute that takes an entity as its value is implemented as a property with `property constraint` set to `allowed entity types constraint` qualified by the statement `item of property constraint` : `Wikibase entity`.
Note that the functionality of those properties, and data validation in general, on wiki.cloud is limited to the services provided by Wikimedia and not configurable.
6. Extensions
This implementation relies on certain ontological concepts and extensions to the RiC-CM data model. Among them are general-purpose Wikidata properties such as "same as", "instance of", and "subclass of" as well as constraint properties and qualifiers, and new classes and properties for concepts like controlled vocabulary, language, or abbreviation, among others.