Default record view

Label
Notes for modeling EMLO in CRM
Comment

Notes for modeling EMLO in CRM

About this Annalist collection

This collection is an exploration of using linked data, CIDOC CRM and Annalist to model the contents of the EMLO database.

Annalist links

Main classes used to model EMLO content:

Letter

Describes a letter from the EMLO dataset.

Declared as a subtype of both F1_Work and F2_Expression. This might turn out to be an ontological over-commitment, in which case treat as an F2_Expression.

This in turn is a subtype of various other CIDOC CRM classes, including E70_Thing and E77_Persistent_Item.

E39_Actor

This is a CIDOC CRM class used to describe actors in events. It is used in the EMLO data representation to describe the sender and recipient of a letter (which in the EMLO data may be a person or an organization). Correspondents who are natural persons may be described as instances of E21_Person, which is a subclass of E39_Actor, and will allow for additional information such as birth and death to be included in their description.

Creation activity

Represents the creation (conception and authoring) of a letter.

EMLO represents this by fields stored with data about the letter itself. The CRM (and PROV) approach is to separate activities from artifacts so that more detailed information about the specific provenance and history of an artifact can be captured.

This is represented by the CRM class crm:E65_Creation, which is a subclass of crm:E7_Activity.

Transmission activity

Represents the transmission of a letter to its recipient.

EMLO represents this by fields stored with data about the letter itself. The CRM (and PROV) approach is to separate activities from artifacts so that more detailed information about the specific provenance and history of an artifact can be captured.

This is represented by a new class emlo:Transmission, which itself is a subclass of crm:E7_Activity.

Note that a letter, as modeled, is a conceptual entity (F1_Work and F2_Expression) rather than a physical object. Thus, the specific CRM class E10_Transfer_of_Custody would not be applicable here.

@@etc...

Main database entry types

Per Mat, the main entry types are:

  • work; e.g. this letter from Sir Isaac Newton
  • person (a person entity can also represent an organisation); e.g. Sir Isaac Newton
  • location; e.g. London, England
  • manifestation @@example?
    • Appears to be information appearing as "Repositories and Versions" in the description of a letter (work)?
  • resource @@example?
    • Appears to be any/all data-derived links appearing in the item page
  • comment @@example?
  • institution; e.g. Bodleian Library, University of Oxford (there seems to be a problem with this link - it returns search results rather than info about the institution)
    • Is there some confusion or overlap between "institution" and "repository"? Are they the same tyhing in EMLO?
  • role @@example?
  • subject @@example?

There also appear to be:

work

This seems to be the type of entry used for describing letters. The term "work" appeals to the FRBR notion (modelled in CIDOC CRM/FRBRoo as F1_Work, but I wonder if a FRBR expression (modeled as F2_Expression) wouldn't be closer.

See also: FRBR Work and Expression.

person (a person entity can also represent an organisation)

Looks to me like a CRM E39_Actor.

CRM provides separate subtypes for individual people (E21_Person) and groups including organizations (E74_Group).

location

manifestation

The examples seen so far seem to be loosely related to FRBR manifestation, but also covering things like catalogue entries as well as realizations of the letter expression.

FRBRoo modeling is a bit confusing in this area, providing both F3_Manifestation_Product_Type and F4_Manifestation_Singleton types. (There is also a separate F5_Item type.)

This is a manifestation (of the letter) in the FRBR sense, but in some cases, the image provided is not; e.g. may be an image of a cataloguing card.

resource

Looks like web references - could map these to Annalist journal resources?

comment

institution

role

Relates to person (E55_Type?)

subject

??

Example to prove modeling

http://emlo.bodleian.ox.ac.uk/profile/work/2aac1eaa-3d1e-46b4-9a81-500f5bca3666

 
Choose view

Default record view

Default view applied when no view is specified when creating a record.

This view defines a minimal set of fields that are generally presumed to be present in all records: a record Id, a record type, a short label and a comment that can be used to provide an extended description. For site data, the comment is used to populate interactive help information.

This view can also be used to change the type of a record.

Fields:

Id: Entity identifier

Type: Reference to type of this record.

Label: short label used to describe this record.

Comment: longer text description of this record. Uses Markdown for formatting, with value substitutions for links, etc.