Concept Search
Showing 2710 results:
Acquisition Information
Comment:
According to the International Guidelines for Museum Object Information: The CIDOC Information Categories, acquisition information supports Security and Accountability. It is needed to provide evidence of the legal status of the object as part of the museum's collections and should record the following information categories:
- Acquisition method
- Acquisition date
- Acquisition source
Frequently acquisition of objects is confused with legal acquisition. In this graph we describe only legal acquisition of objects. Physical acquisition is dealt with in the Collection Information graph.
Type: Functional Overview
Appellation Information
Comment:
Appellation, i.e. names, titles and identifiers are relative to a group of people using these names for some thing. Therefore the CIDOC CRM models and recommends to register the history and use of appellations in order to trace the identity of objects throughout their history, rather than relying on possible unique identifiers.
Type: Functional Overview
Attribute Assignment
Comment:
Motivation of this unit is expert knowledge about assigning attributes to items, as well as interpretation of characteristic database schema elements from relevant collection management systems.
Type: Functional Overview
Changing Thing
Comment:
Motivation for this unit is expert knowledge about transformation and modification activities, as well as interpretation of characteristic database schema elements from relevant collection management systems.
Type: Functional Overview
CIDOC CRM Class Hierarchy
Type: Functional Overview
CLP104 subject to
Quantification: one to many, dependent (0,n:1,1)
Scope note:
This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of E30 Right, which applies to all exemplars of that publication, as long as they are recognised as exemplars of that publication.
The rights covered by this property may include: acquisition or access authorisation; terms of availability; access restrictions on the Manifestation Product Type; etc.
Examples:
The publication entitled ‘Recent poems’ by the author named ‘Stephen Spender’, released by the publisher named ‘Anvil Press Poetry’ in 1978 and identified by ISBN ‘0856460516’ (F3) CLP104 subject to availability restricted to Anvil Press Poetry subscribers (E30) [P3 has note ‘This edition […] is available only to Anvil Press Poetry subscribers’ (E62)]
Type: Property
CLP105 right held by
Quantification: many to many (0,n:0,n)
Scope note:
This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of E39 Actor, who holds an instance of E30 Right on all exemplars of that publication, as long as they are recognised as exemplars of that publication.
Examples:
The publication entitled ‘Recent poems’ by the author named ‘Stephen Spender’, released by the publisher named ‘Anvil Press Poetry’ in 1978 and identified by ISBN ‘0856460516’ (F3) CLP105 right held by Anvil Press Poetry (F11)
Type: Property
CLP2 should have type
Quantification: many to many (0,n:0,n)
Scope note:
This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of E55 Type, which all exemplars of that publication should belong to, as long as they are recognised as exemplars of that publication. Typically, this property is observed on one exemplar of a publication, and extrapolated to all other exemplars of the same publication. This logical inference is an induction along the path that can be modelled as: F3 Manifestation Product Type R7i has example F5 Item P41i was classified by E17 Type Assignment P42 assigned E55 Type.
It can happen that a given exemplar, or subset of exemplars, originally produced, or intended to be produced, with that characteristic, accidentally lacks it. This fact should be recorded as a property of F5 Item, and not of F3 Manifestation Product Type.
Examples:
The sound recording entitled ‘The Glory (????) of the human voice’, identified by label and label number ‘RCA Victor Gold Seal GD61175’, containing recordings of musical works performed by Florence Foster Jenkins (F3) CLP2 should have type sound recording (E55)
The sound recording entitled ‘The Glory (????) of the human voice’, identified by label and label number ‘RCA Victor Gold Seal GD61175’, containing recordings of musical works performed by Florence Foster Jenkins (F3) CLP2 should have type kind of sound: monaural (E55)
Type: Property
CLP43 should have dimension
Quantification: one to many, necessary, dependent (1,n:1,1)
Scope note:
This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of E54 Dimension, which all exemplars of that publication should have, as long as they are recognised as exemplars of that publication. Typically, this property is observed on one exemplar of a publication, and extrapolated to all other exemplars of the same publication. This logical inference is an induction along the path that can be modelled as: F3 Manifestation Product Type R7i has example F5 Item P39i was measured by E16 Measurement P40 observed dimension E54 Dimension.
It can happen that a given exemplar, or subset of exemplars, originally produced, or intended to be produced, with that characteristic, accidentally lacks it. This fact should be recorded as a property of F5 Item, and not of F3 Manifestation Product Type.
Examples:
The publication entitled ‘Functional Requirements for Bibliographic Records: final report’, published by K. G. Saur in 1998, identified by ISBN ‘3-598-11382-X’ (F3) CLP43 should have dimension height of the individual copy of ‘Functional Requirements for Bibliographic Records: final report’ that I have at hand and that I observed while describing it (E54) P3 has note ‘24 cm’ (E62) [or, alternatively: P90 has value ‘24’ (E60) and P91 has unit ‘cm’ (E58)]
The jigsaw puzzle entitled ‘Map of the New York city subway system’, designed by Stephen J. Voorhies and released around 1954 by the Union Dimes Savings Bank (F3) CLP43 should have dimension length and height of the exemplar held and catalogued by the Library of Congress (E54) P3 has note ‘46 x 29 cm’ (E62)
Type: Property
CLP45 should consist of
Quantification: many to many (0,n:0,n)
Scope note:
This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of E57 Material, which all exemplars of that publication should consist of, as long as they are recognised as exemplars of that publication. Typically, this property is observed on one exemplar of a publication, and extrapolated to all other exemplars of the same publication. This logical inference is an induction along the path that can be modelled as: F3 Manifestation Product Type R7i has example F5 Item P41i was classified by E17 Type Assignment P42 assigned E57 Material.
It can happen that a given exemplar, or subset of exemplars, originally produced, or intended to be produced, with that characteristic, accidentally lacks it. This fact should be recorded as a property of F5 Item, and not of F3 Manifestation Product Type.
Examples:
The jigsaw puzzle entitled ‘Map of the New York city subway system’, designed by Stephen J. Voorhies and released around 1954 by the Union Dimes Savings Bank (F3) CLP45 should consist of cardboard (E57)
Type: Property
CLP46 should be composed of
Quantification: many to many (0,n:0,n)
Scope note:
This property associates an instance of F3 Manifestation Product Type which prescribes that all its Items will contain as parts an Item of another instance of F3 Manifestation Product Type with that instance of F3 Manifestation Product Type.
Examples:
The publication product identified by ISBN ‘0618260587’ and consisting of a 3-volume edition of J.R.R. Tolkien’s ‘The Lord of the rings’ (F3) CLP46 should be composed of the publication product identified by ISBN ‘0618260595’ and consisting of an edition of J.R.R Tolkien’s ‘The two towers’ (F3)
The publication product issued by Deutsche Grammophon in 1998 and consisting of a recording of Richard Wagner’s ‘Der fliegende Holländer’ as performed in 1991 by Plácido Domingo, Cheryl Studer et al., and conducted by Giuseppe Sinopoli (F3) CLP46 should be composed of the publication product consisting of printed programme notes and libretto with French and English translations (F3)
Type: Property
CLP57 should have number of parts
Quantification: many to one, necessary (1,1:0,n)
Scope note:
This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of E60 Number, which denotes the number of physical units all exemplars of that publication should consist of, as long as they are recognised as complete exemplars of that publication. Typically, this property is observed on one exemplar of a publication, and extrapolated to all other exemplars of the same publication. This logical inference is an induction along the path that can be modelled as: F3 Manifestation Product Type R7i has example F5 Item P57 has number of parts E60 Number.
It can happen that a given exemplar, or subset of exemplars, originally produced, or intended to be produced, with that characteristic, accidentally lacks it. This fact should be recorded as a property of F5 Item, and not of F3 Manifestation Product Type.
Examples:
The jigsaw puzzle entitled ‘Map of the New York city subway system’, designed by Stephen J. Voorhies and released around 1954 by the Union Dimes Savings Bank (F3) CLP57 should have number of parts 76 (E60) [Number of physical units of the exemplar held by the Library of Congress, as observed by a cataloguer from the Library of Congress when he/she catalogued that particular exemplar and recorded the statement: ‘1 jigsaw puzzle (ca. 76 pieces)’]
The publication entitled ‘History of costume: in slides, notes, and commentaries’ by Jeanne Button, Patricia Quinn Stuart, and Stephen Sbarge, released by Slide Presentations (New York) ca. 1975 (F3) CLP57 should have number of parts 1,491 (E60) [Number of physical units of the exemplar held by the Gelman Library of the George Washington University, as observed by a cataloguer from the Gelman Library of the George Washington University when he/she catalogued that particular exemplar and recorded the statement: ‘1,491 slides in 14 slide trays + 6 ring binders in cases (30 x 29 cm.)’]
Type: Property
CLR6 should carry
Quantification: many to one, necessary (1,1:0,n)
Scope note:
This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of F24 Publication Expression, which all exemplars of that publication should carry, as long as they are recognised as complete exemplars of that publication. Typically, this property is observed on one exemplar of a publication, and extrapolated to all other exemplars of the same publication. This logical inference is an induction along the path that can be modelled as: F3 Manifestation Product Type R7i has example F5 Item R6 carries F24 Publication Expression.
It can happen that a given exemplar, or a subset of exemplars, originally produced, or intended to be produced with that characteristic, accidentally lacks part of the publication expression. This fact should be recorded as a property of F5 Item, and not of F3 Manifestation Product Type.
Examples:
The publication, dated 1972, entitled ‘The complete poems of Stephen Crane, edited with an introduction by Joseph Katz’ (ISBN ‘0-8014-9130-4’) (F3) CLR6 should carry the overall content of the book identified by ISBN ‘0-8014-9130-4’, i.e.: the text of Stephen Crane’s complete poems as edited by Joseph Katz, the numbering system introduced by Joseph Katz in order to identify each individual poem by Stephen Crane, page numbers, the text of Joseph Katz’s dedication, preface, acknowledgements, and introduction, the table of contents, the index of first lines, the statements found on title page, back of title page (including CIP bibliographic record), cover front, back front, and spine, and the layout of the publication, and the occasional statement ‘[NO STANZA BREAK]’ (F24)
Type: Property
Collection Information
Comment:
Motivation for this unit has been expert knowledge about museum collections, as well as interpretation of characteristic database schema elements from relevant collection management systems.
Type: Functional Overview
Condition Information
Comment:
Motivation for this unit has been the Condition Information Group of the International Guidelines for Museum Object Information: The CIDOC Information Categories and other domain expert knowledge about the condition of things, as well as interpretation of characteristic database schema elements from relevant collection management systems.
According to the International Guidelines for Museum Object Information: The CIDOC Information Categories, condition information supports Accountability. It helps ensure the physical protection of the object and also supports the identification of objects. Condition information also helps provide physical protection and should record the following information categories:
- Condition
- Condition summary
- Condition date
Type: Functional Overview
De-accession and Disposal Information
Comment:
Motivation for this unithas been the Deaccession and Disposal Information Group of the International Guidelines for Museum Object Information: The CIDOC Information Categories and other domain expert knowledge about the deaccession and disposal activities of museums, as well as interpretation of characteristic database schema elements from relevant collection management systems.
According to the International Guidelines for Museum Object Information: The CIDOC Information Categories, deaccession and disposal information supports Security, Accountability, and Access. Without this information it is not possible to tell whether an object is missing or whether it has been actively deaccessioned. For deaccession and disposal the following information categories should be recorded:
- Deaccession date
- Disposal date
- Disposal method
- Disposal recipient
Type: Functional Overview
Description Information
Comment:
Motivation for this graph has been the DescriptionInformation Group of the International Guidelines for Museum Object Information: The CIDOC Information Categories and other domain expert knowledge, as well as interpretation of characteristic database schema elements from relevant collection management systems.
According to the International Guidelines for Museum Object Information: The CIDOC Information Categories, this information supports Security, Accountability, Access, and an Historic archive. In the absence of an image it provides a detailed description of an object and a retrieval facility which would not be available using an image alone. Description information can be used for a variety of purposes, including research, handlists, exhibitions, and publications and should record the following information categories:
- Physical description
- Specimen status
Type: Functional Overview
Documentation and References
Comment:
Motivation for this unit has been expert knowledge about documentation and relationships of references, as well as interpretation of characteristic database schema elements from relevant collection management systems.
Type: Functional Overview
E1 CRM Entity
Scope note:
This class comprises all things in the universe of discourse of the CIDOC Conceptual Reference Model. It is an abstract concept providing for three general properties:
1. Identification by name or appellation, and in particular by a preferred identifier
2. Classification by type, allowing further refinement of the specific subclass an instance belongs to
3. Attachment of free text for the expression of anything not captured by formal properties.
With the exception of E59 Primitive Value, all other classes within the CRM are directly or indirectly specialisations of E1 CRM Entity.
Examples:
- the earthquake in Lisbon 1755 (E5)
Type: Entity
Belongs to version: Version 5.1.2
E1 CRM Entity
Scope note:
This class comprises all things in the universe of discourse of the CIDOC Conceptual Reference Model. It is an abstract concept providing for three general properties:
1. Identification by name or appellation, and in particular by a preferred identifier
2. Classification by type, allowing further refinement of the specific subclass an instance belongs to
3. Attachment of free text for the expression of anything not captured by formal properties.
With the exception of E59 Primitive Value, all other classes within the CRM are directly or indirectly specialisations of E1 CRM Entity.
Examples:
- the earthquake in Lisbon 1755 (E5)
Type: Entity
Belongs to version: Version 6.2.1
E1 CRM Entity
Scope note:
This class comprises all things in the universe of discourse of the CIDOC Conceptual Reference Model.
It is an abstract concept providing for three general properties:
Identification by name or appellation
Classification by type, allowing further refinement of the specific subclass an instance belongs to
Attachment of free text for the expression of anything not captured by formal properties
With the exception of E59 Primitive Value, all other classes within the CRM are directly or indirectly specialisations of E1 CRM Entity.
Examples:
- the earthquake in Lisbon 1755 (E5)
Type: Entity
Belongs to version: Version 4.1
E1 CRM Entity
Scope note:
This class comprises all things in the universe of discourse of the CIDOC Conceptual Reference Model.
It is an abstract concept providing for three general properties:
Identification by name or appellation, and in particular by a preferred identifier
Classification by type, allowing further refinement of the specific subclass an instance belongs to
Attachment of free text and other unstructured data for the expression of anything not captured by formal properties
All other classes within the CIDOC CRM are directly or indirectly specialisations of E1 CRM Entity.
Examples:
- the earthquake in Lisbon 1755 (E5) (Chester, 2001)
Type: Entity
Belongs to version: version 7.1.1
E1 CRM Entity
Scope note:
This class comprises all things in the universe of discourse of the CIDOC Conceptual Reference Model. It is an abstract concept providing for three general properties:
1. Identification by name or appellation, and in particular by a preferred identifier
2. Classification by type, allowing further refinement of the specific subclass an instance belongs to
3. Attachment of free text for the expression of anything not captured by formal properties.
With the exception of E59 Primitive Value, all other classes within the CRM are directly or indirectly specialisations of E1 CRM Entity.
Examples:
- the earthquake in Lisbon 1755 (E5)
Type: Entity
Belongs to version: Version 6.1
E1 CRM Entity
Scope note:
This class comprises all things in the universe of discourse of the CIDOC Conceptual Reference Model.
It is an abstract concept providing for three general properties:
Identification by name or appellation, and in particular by a preferred identifier
Classification by type, allowing further refinement of the specific subclass an instance belongs to
Attachment of free text for the expression of anything not captured by formal properties
With the exception of E59 Primitive Value, all other classes within the CRM are directly or indirectly specialisations of E1 CRM Entity.
Examples:
- the earthquake in Lisbon 1755 (E5)
Type: Entity
Belongs to version: Version 5.0.2
E1 CRM Entity
Scope note:
This class comprises all things in the universe of discourse of the CIDOC Conceptual Reference Model. It is an abstract concept providing for three general properties:
1. Identification by name or appellation, and in particular by a preferred identifier
2. Classification by type, allowing further refinement of the specific subclass an instance belongs to
3. Attachment of free text for the expression of anything not captured by formal properties.
With the exception of E59 Primitive Value, all other classes within the CRM are directly or indirectly specialisations of E1 CRM Entity.
Examples:
- the earthquake in Lisbon 1755 (E5)
Type: Entity
Belongs to version: Version 6.2.2
E1 CRM Entity
Scope note:
This class comprises all things in the universe of discourse of the CIDOC Conceptual Reference Model. It is an abstract concept providing for three general properties:
1. Identification by name or appellation, and in particular by a preferred identifier
2. Classification by type, allowing further refinement of the specific subclass an instance belongs to
3. Attachment of free text for the expression of anything not captured by formal properties.
With the exception of E59 Primitive Value, all other classes within the CRM are directly or indirectly specialisations of E1 CRM Entity.
Examples:
- the earthquake in Lisbon 1755 (E5)
Type: Entity
Belongs to version: Version 6.0
E1 CRM Entity
Scope note:
This class comprises all things in the universe of discourse of the CIDOC Conceptual Reference Model.
It is an abstract concept providing for three general properties:
• Identification by name or appellation, and in particular by a preferred identifier
• Classification by type, allowing further refinement of the specific subclass an instance belongs to
• Attachment of free text and other unstructured data for the expression of anything not captured by formal properties
It is an abstract concept providing for three general properties:
• Identification by name or appellation, and in particular by a preferred identifier
• Classification by type, allowing further refinement of the specific subclass an instance belongs to
• Attachment of free text and other unstructured data for the expression of anything not captured by formal properties
All other classes within the CIDOC CRM are directly or indirectly specialisations of E1 CRM Entity.
Examples:
- the earthquake in Lisbon 1755 (E5) (Chester,2001)
Type: Entity
Belongs to version: version 7.1
E1 CRM Entity
Scope note:
This class comprises all things in the universe of discourse of the CIDOC Conceptual Reference Model. It is an abstract concept providing for three general properties:
1. Identification by name or appellation, and in particular by a preferred identifier
2. Classification by type, allowing further refinement of the specific subclass an instance belongs to
3. Attachment of free text for the expression of anything not captured by formal properties.
With the exception of E59 Primitive Value, all other classes within the CRM are directly or indirectly specialisations of E1 CRM Entity.
Examples:
- the earthquake in Lisbon 1755 (E5)
Type: Entity
Belongs to version: Version 6.2
E1 CRM Entity
Scope note:
This class comprises all things in the universe of discourse of the CIDOC Conceptual Reference Model.
It is an abstract concept providing for three general properties:
Identification by name or appellation, and in particular by a preferred identifier
Classification by type, allowing further refinement of the specific subclass an instance belongs to
Attachment of free text for the expression of anything not captured by formal properties
With the exception of E59 Primitive Value, all other classes within the CRM are directly or indirectly specialisations of E1 CRM Entity.
Examples:
- the earthquake in Lisbon 1755 (E5)
Type: Entity
Belongs to version: Version 5.0.1
E10 Transfer of Custody
Scope note:
This class comprises transfers of physical custody of objects between instances of E39 Actor.
The recording of the donor and/or recipient is optional. It is possible that in an instance of E10 Transfer of Custody there is either no donor or no recipient. Depending on the circumstances it may describe:
1. the beginning of custody
The recording of the donor and/or recipient is optional. It is possible that in an instance of E10 Transfer of Custody there is either no donor or no recipient. Depending on the circumstances it may describe:
1. the beginning of custody
2. the end of custody
3. the transfer of custody
4. the receipt of custody from an unknown source
5. the declared loss of an object
The distinction between the legal responsibility for custody and the actual physical possession of the object should be expressed using the property P2 has type (is type of). A specific case of transfer of custody is theft.
The interpretation of the museum notion of "accession" differs between institutions. The CRM therefore models legal ownership and physical custody separately. Institutions will then model their specific notions of accession and deaccession as combinations of these.
The distinction between the legal responsibility for custody and the actual physical possession of the object should be expressed using the property P2 has type (is type of). A specific case of transfer of custody is theft.
The interpretation of the museum notion of "accession" differs between institutions. The CRM therefore models legal ownership and physical custody separately. Institutions will then model their specific notions of accession and deaccession as combinations of these.
Examples:
- the delivery of the paintings by Secure Deliveries Inc. to the National Gallery
- the return of Picasso’s “Guernica” to Madrid’s Prado in 1981
Type: Entity
Belongs to version: Version 6.2.1
E10 Transfer of Custody
Scope note:
This class comprises transfers of physical custody of objects between instances of E39 Actor.
The recording of the donor and/or recipient is optional. It is possible that in an instance of E10 Transfer of Custody there is either no donor or no recipient. Depending on the circumstances it may describe:
the beginning of custody
the end of custody
the transfer of custody
the receipt of custody from an unknown source
the declared loss of an object
The distinction between the legal responsibility for custody and the actual physical possession of the object should be expressed using the property P2 has type (is type of). A specific case of transfer of custody is theft.
The interpretation of the museum notion of accession differs between institutions. The CRM therefore models legal ownership and physical custody separately. Institutions will then model their specific notions of accession and deaccession as combinations of these.
Examples:
- the delivery of the paintings by Secure Deliveries Inc. to the National Gallery
- the return of Picasso’s “Guernica” to Madrid’s Prado in 1981
Type: Entity
Belongs to version: Version 4.1
E10 Transfer of Custody
Scope note:
This class comprises transfers of the physical custody or the legal responsibility for the physical custody of objects. The recording of the donor or recipient is optional. It is possible that in an instance of E10 Transfer of Custody there is either no donor or no recipient.
Depending on the circumstances, it may describe:
the beginning of custody (there is no previous custodian)
the end of custody (there is no subsequent custodian)
the transfer of custody (transfer from one custodian to the next)
the receipt of custody from an unknown source (the previous custodian is unknown)
the declared loss of an object (the current or subsequent custodian is unknown)
In the event that only a single kind of transfer of custody occurs, either the legal responsibility for the custody or the actual physical possession of the object but not both, this difference should be expressed using the property P2 has type (is type of).
The sense of physical possession requires that the object of custody be in the hands of the keeper at least with a part representative for the whole. The way, in which a representative part is defined, should ensure that it is unambiguous who keeps a part and who the whole and should be consistent with the identity criteria of the kept instance of E18 Physical Thing.
The interpretation of the museum notion of accession differs between institutions. The CIDOC CRM therefore models legal ownership and physical custody separately. Institutions will then model their specific notions of accession and deaccession as combinations of these.
Theft is a specific case of illegal transfer of custody.
Examples:
- the delivery of the paintings by Secure Deliveries Inc. to the National Gallery
- the return of Picasso’s “Guernica” to Madrid’s Prado in 1981 (Chipp, 1988)
Type: Entity
Belongs to version: version 7.1.1
E10 Transfer of Custody
Scope note:
This class comprises transfers of physical custody of objects between instances of E39 Actor.
The recording of the donor and/or recipient is optional. It is possible that in an instance of E10 Transfer of Custody there is either no donor or no recipient. Depending on the circumstances it may describe:
1. the beginning of custody
The recording of the donor and/or recipient is optional. It is possible that in an instance of E10 Transfer of Custody there is either no donor or no recipient. Depending on the circumstances it may describe:
1. the beginning of custody
2. the end of custody
3. the transfer of custody
4. the receipt of custody from an unknown source
5. the declared loss of an object
The distinction between the legal responsibility for custody and the actual physical possession of the object should be expressed using the property P2 has type (is type of). A specific case of transfer of custody is theft.
The interpretation of the museum notion of "accession" differs between institutions. The CRM therefore models legal ownership and physical custody separately. Institutions will then model their specific notions of accession and deaccession as combinations of these.
The distinction between the legal responsibility for custody and the actual physical possession of the object should be expressed using the property P2 has type (is type of). A specific case of transfer of custody is theft.
The interpretation of the museum notion of "accession" differs between institutions. The CRM therefore models legal ownership and physical custody separately. Institutions will then model their specific notions of accession and deaccession as combinations of these.
Examples:
- the delivery of the paintings by Secure Deliveries Inc. to the National Gallery
- the return of Picasso’s “Guernica” to Madrid’s Prado in 1981
Type: Entity
Belongs to version: Version 6.1
E10 Transfer of Custody
Scope note:
This class comprises transfers of physical custody of objects between instances of E39 Actor.
The recording of the donor and/or recipient is optional. It is possible that in an instance of E10 Transfer of Custody there is either no donor or no recipient. Depending on the circumstances it may describe:
1. the beginning of custody
The recording of the donor and/or recipient is optional. It is possible that in an instance of E10 Transfer of Custody there is either no donor or no recipient. Depending on the circumstances it may describe:
1. the beginning of custody
2. the end of custody
3. the transfer of custody
4. the receipt of custody from an unknown source
5. the declared loss of an object
The distinction between the legal responsibility for custody and the actual physical possession of the object should be expressed using the property P2 has type (is type of). A specific case of transfer of custody is theft.
The interpretation of the museum notion of "accession" differs between institutions. The CRM therefore models legal ownership and physical custody separately. Institutions will then model their specific notions of accession and deaccession as combinations of these.
The distinction between the legal responsibility for custody and the actual physical possession of the object should be expressed using the property P2 has type (is type of). A specific case of transfer of custody is theft.
The interpretation of the museum notion of "accession" differs between institutions. The CRM therefore models legal ownership and physical custody separately. Institutions will then model their specific notions of accession and deaccession as combinations of these.
Examples:
- the delivery of the paintings by Secure Deliveries Inc. to the National Gallery
- the return of Picasso’s “Guernica” to Madrid’s Prado in 1981
Type: Entity
Belongs to version: Version 5.1.2
E10 Transfer of Custody
Scope note:
This class comprises transfers of physical custody of objects between instances of E39 Actor.
The recording of the donor and/or recipient is optional. It is possible that in an instance of E10 Transfer of Custody there is either no donor or no recipient. Depending on the circumstances it may describe:
the beginning of custody
the end of custody
the transfer of custody
the receipt of custody from an unknown source
the declared loss of an object
The distinction between the legal responsibility for custody and the actual physical possession of the object should be expressed using the property P2 has type (is type of). A specific case of transfer of custody is theft.
The interpretation of the museum notion of accession differs between institutions. The CRM therefore models legal ownership and physical custody separately. Institutions will then model their specific notions of accession and deaccession as combinations of these.
Examples:
- the delivery of the paintings by Secure Deliveries Inc. to the National Gallery
- the return of Picasso’s “Guernica” to Madrid’s Prado in 1981
Type: Entity
Belongs to version: Version 5.0.2
E10 Transfer of Custody
Scope note:
This class comprises transfers of physical custody of objects between instances of E39 Actor.
The recording of the donor and/or recipient is optional. It is possible that in an instance of E10 Transfer of Custody there is either no donor or no recipient. Depending on the circumstances it may describe:
1. the beginning of custody
2. the end of custody
3. the transfer of custody
4. the receipt of custody from an unknown source
5. the declared loss of an object
The distinction between the legal responsibility for custody and the actual physical possession of the object should be expressed using the property P2 has type (is type of). A specific case of transfer of custody is theft. The sense of physical possession requires that the object of custody is in the hands of the keeper at least with a part representative for the whole. The way, in which a representative part is defined, should ensure that it is unambiguous who keeps a part and who the whole and should be consistent with the identity criteria of the kept instance of E18 Physical Thing. For instance, in the case of a set of cutlery we may require the majority of pieces having been in the hands of the actor regardless which individual pieces are kept over time.
The interpretation of the museum notion of "accession" differs between institutions. The CRM therefore models legal ownership and physical custody separately. Institutions will then model their specific notions of accession and deaccession as combinations of these.
Examples:
- the delivery of the paintings by Secure Deliveries Inc. to the National Gallery
- the return of Picasso’s “Guernica” to Madrid’s Prado in 1981
Type: Entity
Belongs to version: Version 6.2.2
E10 Transfer of Custody
Scope note:
This class comprises transfers of physical custody of objects between instances of E39 Actor.
The recording of the donor and/or recipient is optional. It is possible that in an instance of E10 Transfer of Custody there is either no donor or no recipient. Depending on the circumstances it may describe:
1. the beginning of custody
The recording of the donor and/or recipient is optional. It is possible that in an instance of E10 Transfer of Custody there is either no donor or no recipient. Depending on the circumstances it may describe:
1. the beginning of custody
2. the end of custody
3. the transfer of custody
4. the receipt of custody from an unknown source
5. the declared loss of an object
The distinction between the legal responsibility for custody and the actual physical possession of the object should be expressed using the property P2 has type (is type of). A specific case of transfer of custody is theft.
The interpretation of the museum notion of "accession" differs between institutions. The CRM therefore models legal ownership and physical custody separately. Institutions will then model their specific notions of accession and deaccession as combinations of these.
The distinction between the legal responsibility for custody and the actual physical possession of the object should be expressed using the property P2 has type (is type of). A specific case of transfer of custody is theft.
The interpretation of the museum notion of "accession" differs between institutions. The CRM therefore models legal ownership and physical custody separately. Institutions will then model their specific notions of accession and deaccession as combinations of these.
Examples:
- the delivery of the paintings by Secure Deliveries Inc. to the National Gallery
- the return of Picasso’s “Guernica” to Madrid’s Prado in 1981
Type: Entity
Belongs to version: Version 6.0
E10 Transfer of Custody
Scope note:
This class comprises transfers of the physical custody or the legal responsibility for the physical custody of objects. The recording of the donor or recipient is optional. It is possible that in an instance of E10 Transfer of Custody there is either no donor or no recipient.
Depending on the circumstances, it may describe:
1. the beginning of custody (there is no previous custodian)
2. the end of custody (there is no subsequent custodian)
3. the transfer of custody (transfer from one custodian to the next)
4. the receipt of custody from an unknown source (the previous custodian is unknown)
5. the declared loss of an object (the current or subsequent custodian is unknown)
In the event that only a single kind of transfer of custody occurs, either the legal responsibility for the custody or the actual physical possession of the object but not both, this difference should be expressed using the property P2 has type (is type of).
The sense of physical possession requires that the object of custody be in the hands of the keeper at least with a part representative for the whole. The way, in which a representative part is defined, should ensure that it is unambiguous who keeps a part and who the whole and should be consistent with the identity criteria of the kept instance of E18 Physical Thing.
The interpretation of the museum notion of "accession" differs between institutions. The CIDOC CRM therefore models legal ownership and physical custody separately. Institutions will then model their specific notions of accession and deaccession as combinations of these.
Theft is a specific case of illegal transfer of custody.
Examples:
- the delivery of the paintings by Secure Deliveries Inc. to the National Gallery
- the return of Picasso’s “Guernica” to Madrid’s Prado in 1981 (Chipp, 1988)
Type: Entity
Belongs to version: version 7.1
E10 Transfer of Custody
Scope note:
This class comprises transfers of physical custody of objects between instances of E39 Actor.
The recording of the donor and/or recipient is optional. It is possible that in an instance of E10 Transfer of Custody there is either no donor or no recipient. Depending on the circumstances it may describe:
1. the beginning of custody
The recording of the donor and/or recipient is optional. It is possible that in an instance of E10 Transfer of Custody there is either no donor or no recipient. Depending on the circumstances it may describe:
1. the beginning of custody
2. the end of custody
3. the transfer of custody
4. the receipt of custody from an unknown source
5. the declared loss of an object
The distinction between the legal responsibility for custody and the actual physical possession of the object should be expressed using the property P2 has type (is type of). A specific case of transfer of custody is theft.
The interpretation of the museum notion of "accession" differs between institutions. The CRM therefore models legal ownership and physical custody separately. Institutions will then model their specific notions of accession and deaccession as combinations of these.
The distinction between the legal responsibility for custody and the actual physical possession of the object should be expressed using the property P2 has type (is type of). A specific case of transfer of custody is theft.
The interpretation of the museum notion of "accession" differs between institutions. The CRM therefore models legal ownership and physical custody separately. Institutions will then model their specific notions of accession and deaccession as combinations of these.
Examples:
- the delivery of the paintings by Secure Deliveries Inc. to the National Gallery
- the return of Picasso’s “Guernica” to Madrid’s Prado in 1981
Type: Entity
Belongs to version: Version 6.2
E10 Transfer of Custody
Scope note:
This class comprises transfers of physical custody of objects between instances of E39 Actor.
The recording of the donor and/or recipient is optional. It is possible that in an instance of E10 Transfer of Custody there is either no donor or no recipient. Depending on the circumstances it may describe:
the beginning of custody
the end of custody
the transfer of custody
the receipt of custody from an unknown source
the declared loss of an object
The distinction between the legal responsibility for custody and the actual physical possession of the object should be expressed using the property P2 has type (is type of). A specific case of transfer of custody is theft.
The interpretation of the museum notion of accession differs between institutions. The CRM therefore models legal ownership and physical custody separately. Institutions will then model their specific notions of accession and deaccession as combinations of these.
Examples:
- the delivery of the paintings by Secure Deliveries Inc. to the National Gallery
- the return of Picasso’s “Guernica” to Madrid’s Prado in 1981
Type: Entity
Belongs to version: Version 5.0.1
E100 Activity Plan
Scope note:
This class comprises plans for specific predefined activities or kinds of activities to happen. They consist of descriptions of specific constraints, patterns or types of activities that could be realized. They may also foresee that the planned activities are realized at times explicitly foreseen by the actor intending the application of the plan, for instance, to organize a conference, in which case we may talk about “active plans”. Alternatively, times of realization may be foreseen in reaction to external kind of events foreseen by the plan, for instance a rescue action in case of earthquake according to a rescue plan, or a penal action in case of criminal activity according to a law, in which case we may talk about “reactive plans”. An instance of Activity Plan does not imply the intention of any Actor to apply it. It may be created together, before or without the will to apply it. For instance, laws are created before they are passed in the parliament. Any Activity Plan may require specific conditions for it to be applicable. For example a plan to excavate a river bank may require that the river is flooded. Or my plan to lime plaster my stone wall requires that it is winter (i.e. wet and cold).
Examples:
- The disaster plan of Tate Archives in case of the Thames flooding.
- The proposal for conservation work for MS Greek 418 at the Saint Catherine library.
Type: Entity
Belongs to version: Version 6.2.2
E101 Intention to Apply
Scope note:
This class comprises the mental state of intention or wanting to apply a particular instance of Activity Plan by a particular E39 Actor. This can be understood as the period of time that an individual or a group holds a particular will. It binds the activity plan to the actor. The intention to apply may be abandoned before the realization of the plan. When the plan is realized, the intention to apply must still exist. Characteristically, the passing of a law initiates the intention of a parliament to apply a law. In many cases, the creation of the plan initiates the intention to apply it, and in case of “active plans” the realization ends the intention. Often, the existence of the intention to apply cannot be determined other by the realization of the plan.
Subclass of: S16 State
Examples:
- The intention of Nicholas Pickwoad to undertake conservation work on MS Greek 418 at the Saint Catherine's Library.
Type: Entity
Belongs to version: Version 6.2.2
E102 Expression of Intention
Scope note:
This class comprises the externalisation, the expression of the Intention to Apply in the form of identifiable immaterial objects, such as texts, that make propositions about these intentions. These are kind of formal texts, legal documents, proceedings, minutes etc. that document the will, the intentions of the actor.
Type: Entity
Belongs to version: Version 6.2.2
E11 Modification
Scope note:
This class comprises all instances of E7 Activity that create, alter or change E24 Physical Man-Made Thing.
This class includes the production of an item from raw materials, and other so far undocumented objects, and the preventive treatment or restoration of an object for conservation.
Since the distinction between modification and production is not always clear, modification is regarded as the more generally applicable concept. This implies that some items may be consumed or destroyed in a Modification, and that others may be produced as a result of it. An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities.
If the instance of the E29 Design or Procedure utilised for the modification prescribes the use of specific materials, they should be documented using properties of the design or procedure, rather than via P126 employed (was employed in): E57 Material.
Examples:
- the construction of the SS Great Britain (E12)
- the impregnation of the Vasa warship in Stockholm for preservation after 1956
- the transformation of the Enola Gay into a museum exhibit by the National Air and Space Museum in Washington DC between 1993 and 1995 (E12, E81)
- the last renewal of the gold coating of the Toshogu shrine in Nikko, Japan
Type: Entity
Belongs to version: Version 5.0.1
E11 Modification
Scope note:
This class comprises all instances of E7 Activity that create, alter or change E24 Physical Man-Made Thing.
This class includes the production of an item from raw materials, and other so far undocumented objects, and the preventive treatment or restoration of an object for conservation.
Since the distinction between modification and production is not always clear, modification is regarded as the more generally applicable concept. This implies that some items may be consumed or destroyed in a Modification, and that others may be produced as a result of it. An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities.
If the instance of the E29 Design or Procedure utilized for the modification prescribes the use of specific materials, they should be documented using property P68 foresees use of (use foreseen by): E57 Material of E29 Design or Procedure, rather than via P126 employed (was employed in): E57 Material.
Examples:
- the construction of the SS Great Britain (E12)
- the impregnation of the Vasa warship in Stockholm for preservation after 1956
- the transformation of the Enola Gay into a museum exhibit by the National Air and Space Museum in Washington DC between 1993 and 1995 (E12, E81)
- the last renewal of the gold coating of the Toshogu shrine in Nikko, Japan
Type: Entity
Belongs to version: Version 6.2.1
E11 Modification
Scope note:
This class comprises instances of E7 Activity that are undertaken to create, alter or change instances of E24 Physical Human-Made Thing.
This class includes the production of an item from raw materials and other so far undocumented objects. It also includes the conservation treatment of an object.
Since the distinction between modification and production is not always clear, modification is regarded as the more generally applicable concept. This implies that some items may be consumed or destroyed in an instance of E11 Modification, and that others may be produced as a result of it. An event should also be documented using an instance of E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities.
An activity undertaken on an object which was designed to alter it, but which, in fact, it did not in any seemingly significant way (such as the application of a solvent during conservation which failed to dissolve any part of the object), is still considered as an instance of E11 Modification. Typically, any such activity will leave at least forensic traces of evidence on the object.
If the instance of E29 Design or Procedure utilized for the modification prescribes the use of specific materials, they should be documented using property P68 foresees use of (use foreseen by): E57 Material of E29 Design or Procedure, rather than via P126 employed (was employed in): E57 Material.
Examples:
- the construction of the SS Great Britain (E12) (Gregor, 1971)
- the impregnation of the Vasa warship in Stockholm for preservation after 1956 (Håfors, 2010)
- the transformation of the Enola Gay into a museum exhibit by the National Air and Space Museum in Washington DC between 1993 and 1995 (E12, E81) (Yakel, 2000)
- the last renewal of the gold coating of the Toshogu shrine in Nikko, Japan (Cali and Dougil, 2012)
Type: Entity
Belongs to version: version 7.1.1
E11 Modification
Scope note:
This class comprises all instances of E7 Activity that create, alter or change E24 Physical Man-Made Thing.
This class includes the production of an item from raw materials, and other so far undocumented objects, and the preventive treatment or restoration of an object for conservation.
Since the distinction between modification and production is not always clear, modification is regarded as the more generally applicable concept. This implies that some items may be consumed or destroyed in a Modification, and that others may be produced as a result of it. An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities.
If the instance of the E29 Design or Procedure utilized for the modification prescribes the use of specific materials, they should be documented using property P68 foresees use of (use foreseen by): E57 Material of E29 Design or Procedure, rather than via P126 employed (was employed in): E57 Material.
Examples:
- the construction of the SS Great Britain (E12)
- the impregnation of the Vasa warship in Stockholm for preservation after 1956
- the transformation of the Enola Gay into a museum exhibit by the National Air and Space Museum in Washington DC between 1993 and 1995 (E12, E81)
- the last renewal of the gold coating of the Toshogu shrine in Nikko, Japan
Type: Entity
Belongs to version: Version 6.1
E11 Modification
Scope note:
This class comprises all instances of E7 Activity that create, alter or change E24 Physical Man-Made Thing.
This class includes the production of an item from raw materials, and other so far undocumented objects, and the preventive treatment or restoration of an object for conservation.
Since the distinction between modification and production is not always clear, modification is regarded as the more generally applicable concept. This implies that some items may be consumed or destroyed in a Modification, and that others may be produced as a result of it. An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities.
If the instance of the E29 Design or Procedure utilized for the modification prescribes the use of specific materials, they should be documented using property P68 foresees use of (use foreseen by): E57 Material of E29 Design or Procedure, rather than via P126 employed (was employed in): E57 Material.
Examples:
- the construction of the SS Great Britain (E12)
- the impregnation of the Vasa warship in Stockholm for preservation after 1956
- the transformation of the Enola Gay into a museum exhibit by the National Air and Space Museum in Washington DC between 1993 and 1995 (E12, E81)
- the last renewal of the gold coating of the Toshogu shrine in Nikko, Japan
Type: Entity
Belongs to version: Version 5.1.2
E11 Modification
Scope note:
This class comprises all instances of E7 Activity that create, alter or change E24 Physical Man-Made Thing.
This class includes the production of an item from raw materials, and other so far undocumented objects, and the preventive treatment or restoration of an object for conservation.
Since the distinction between modification and production is not always clear, modification is regarded as the more generally applicable concept. This implies that some items may be consumed or destroyed in a Modification, and that others may be produced as a result of it. An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities.
If the instance of the E29 Design or Procedure utilised for the modification prescribes the use of specific materials, they should be documented using properties of the design or procedure, rather than via P126 employed (was employed in): E57 Material.
Examples:
- the construction of the SS Great Britain (E12)
- the impregnation of the Vasa warship in Stockholm for preservation after 1956
- the transformation of the Enola Gay into a museum exhibit by the National Air and Space Museum in Washington DC between 1993 and 1995 (E12, E81)
- the last renewal of the gold coating of the Toshogu shrine in Nikko, Japan
Type: Entity
Belongs to version: Version 5.0.2
E11 Modification
Scope note:
This class comprises all instances of E7 Activity that create, alter or change E24 Physical Man-Made Thing.
This class includes the production of an item from raw materials, and other so far undocumented objects, and the preventive treatment or restoration of an object for conservation.
Since the distinction between modification and production is not always clear, modification is regarded as the more generally applicable concept. This implies that some items may be consumed or destroyed in a Modification, and that others may be produced as a result of it. An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities.
If the instance of the E29 Design or Procedure utilized for the modification prescribes the use of specific materials, they should be documented using property P68 foresees use of (use foreseen by): E57 Material of E29 Design or Procedure, rather than via P126 employed (was employed in): E57 Material.
Examples:
- the construction of the SS Great Britain (E12)
- the impregnation of the Vasa warship in Stockholm for preservation after 1956
- the transformation of the Enola Gay into a museum exhibit by the National Air and Space Museum in Washington DC between 1993 and 1995 (E12, E81)
- the last renewal of the gold coating of the Toshogu shrine in Nikko, Japan
Type: Entity
Belongs to version: Version 6.2.2
E11 Modification
Scope note:
This class comprises all instances of E7 Activity that create, alter or change E24 Physical Man-Made Thing.
This class includes the production of an item from raw materials, and other so far undocumented objects, and the preventive treatment or restoration of an object for conservation.
Since the distinction between modification and production is not always clear, modification is regarded as the more generally applicable concept. This implies that some items may be consumed or destroyed in a Modification, and that others may be produced as a result of it. An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities.
If the instance of the E29 Design or Procedure utilized for the modification prescribes the use of specific materials, they should be documented using property P68 foresees use of (use foreseen by): E57 Material of E29 Design or Procedure, rather than via P126 employed (was employed in): E57 Material.
Examples:
- the construction of the SS Great Britain (E12)
- the impregnation of the Vasa warship in Stockholm for preservation after 1956
- the transformation of the Enola Gay into a museum exhibit by the National Air and Space Museum in Washington DC between 1993 and 1995 (E12, E81)
- the last renewal of the gold coating of the Toshogu shrine in Nikko, Japan
Type: Entity
Belongs to version: Version 6.0
E11 Modification
Scope note:
This class comprises instances of E7 Activity that are undertaken to create, alter or change instances of E24 Physical Human-Made Thing.
This class includes the production of an item from raw materials and other so far undocumented objects. It also includes the conservation treatment of an object.
Since the distinction between modification and production is not always clear, modification is regarded as the more generally applicable concept. This implies that some items may be consumed or destroyed in an instance of E11 Modification, and that others may be produced as a result of it. An event should also be documented using an instance of E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities.
An activity undertaken on an object which was designed to alter it, but which, in fact, it did not in any seemingly significant way (such as the application of a solvent during conservation which failed to dissolve any part of the object), is still considered as an instance of E11 Modification. Typically, any such activity will leave at least forensic traces of evidence on the object.
If the instance of E29 Design or Procedure utilized for the modification prescribes the use of specific materials, they should be documented using property P68 foresees use of (use foreseen by): E57 Material of E29 Design or Procedure, rather than via P126 employed (was employed in): E57 Material.
Examples:
- the construction of the SS Great Britain (E12) (Gregor, 1971)
- the impregnation of the Vasa warship in Stockholm for preservation after 1956 (Håfors, 2010)
- the transformation of the Enola Gay into a museum exhibit by the National Air and Space Museum in Washington DC between 1993 and 1995 (E12, E81) (Yakel, 2000)
- the last renewal of the gold coating of the Toshogu shrine in Nikko, Japan (Cali and Dougil, 2012)
Type: Entity
Belongs to version: version 7.1
E11 Modification
Scope note:
This class comprises all instances of E7 Activity that create, alter or change E24 Physical Man-Made Thing.
This class includes the production of an item from raw materials, and other so far undocumented objects, and the preventive treatment or restoration of an object for conservation.
Since the distinction between modification and production is not always clear, modification is regarded as the more generally applicable concept. This implies that some items may be consumed or destroyed in a Modification, and that others may be produced as a result of it. An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities.
If the instance of the E29 Design or Procedure utilized for the modification prescribes the use of specific materials, they should be documented using property P68 foresees use of (use foreseen by): E57 Material of E29 Design or Procedure, rather than via P126 employed (was employed in): E57 Material.
Examples:
- the construction of the SS Great Britain (E12)
- the impregnation of the Vasa warship in Stockholm for preservation after 1956
- the transformation of the Enola Gay into a museum exhibit by the National Air and Space Museum in Washington DC between 1993 and 1995 (E12, E81)
- the last renewal of the gold coating of the Toshogu shrine in Nikko, Japan
Type: Entity
Belongs to version: Version 6.2
E11 Modification Event
Scope note:
This class comprises all instances of E7 Activity that create, alter or change E24 Physical Man-Made Stuff.
This class includes the production of an item from raw materials, and other so far undocumented objects, and the preventive treatment or restoration of an object for conservation.
Since the distinction between modification and production is not always clear, modification is regarded as the more generally applicable concept. This implies that some items may be consumed or destroyed in a modification event, and that others may be produced as a result of it. An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities.
If the instance of the E29 Design or Procedure utilised for the modification prescribes the use of specific materials, they should be documented using properties of the design or procedure, rather than via P126 employed (was employed in): E57 Material.
Examples:
- the construction of the SS Great Britain (E12)
- the impregnation of the Vasa warship in Stockholm for preservation after 1956
- the transformation of the Enola Gay into a museum exhibit by the National Air and Space Museum in Washington DC between 1993 and 1995 (E12, E81)
- the last renewal of the gold coating of the Toshogu shrine in Nikko, Japan
Type: Entity
Belongs to version: Version 4.1
E12 Production
Scope note:
This class comprises activities that are designed to, and succeed in, creating one or more new items.
It specializes the notion of modification into production. The decision as to whether or not an object is regarded as new is context sensitive. Normally, items are considered “new” if there is no obvious overall similarity between them and the consumed items and material used in their production. In other cases, an item is considered “new” because it becomes relevant to documentation by a modification. For example, the scribbling of a name on a potsherd may make it a voting token. The original potsherd may not be worth documenting, in contrast to the inscribed one.
This entity can be collective: the printing of a thousand books, for example, would normally be considered a single event.
An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities and matter is preserved, but identity is not.
Examples:
- the construction of the SS Great Britain
- the recasting of the Little Mermaid at the harbour of Copenhagen
- the seventh edition of Rembrandt’s etching “Woman sitting half dressed beside a stove”, 1658, Bartsch Number 197
Type: Entity
Belongs to version: Version 5.0.1
E12 Production
Scope note:
This class comprises activities that are designed to, and succeed in, creating one or more new items.
It specializes the notion of modification into production. The decision as to whether or not an object is regarded as new is context sensitive. Normally, items are considered “new” if there is no obvious overall similarity between them and the consumed items and material used in their production. In other cases, an item is considered “new” because it becomes relevant to documentation by a modification. For example, the scribbling of a name on a potsherd may make it a voting token. The original potsherd may not be worth documenting, in contrast to the inscribed one.
This entity can be collective: the printing of a thousand books, for example, would normally be considered a single event.
An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities and matter is preserved, but identity is not.
Examples:
- the construction of the SS Great Britain
- the first casting of the Little Mermaid from the harbour of Copenhagen
- Rembrandt’s creating of the seventh state of his etching “Woman sitting half dressed beside a stove”, 1658, identified by Bartsch Number 197 (E12,E65,E81)
Type: Entity
Belongs to version: Version 6.2.1
E12 Production
Scope note:
This class comprises activities that are designed to, and succeed in, creating one or more new items.
It specializes the notion of modification into production. The decision as to whether or not an object is regarded as new is context sensitive. Normally, items are considered “new” if there is no obvious overall similarity between them and the consumed items and material used in their production. In other cases, an item is considered “new” because it becomes relevant to documentation by a modification. For example, the scribbling of a name on a potsherd may make it a voting token. The original potsherd may not be worth documenting, in contrast to the inscribed one.
This entity can be collective: the printing of a thousand books, for example, would normally be considered a single event.
An event should also be documented using an instance of E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities and matter is preserved, but identity is not.
Examples:
- the construction of the SS Great Britain (Gregor, 1971)
- the first casting of the Little Mermaid from the harbour of Copenhagen (Dewey, 2003)
- Rembrandt’s creating of the seventh state of his etching “Woman sitting half dressed beside a stove”, 1658, identified by Bartsch Number 197 (E12, E65, E81) (Hind, 1923)
Type: Entity
Belongs to version: version 7.1.1
E12 Production
Scope note:
This class comprises activities that are designed to, and succeed in, creating one or more new items.
It specializes the notion of modification into production. The decision as to whether or not an object is regarded as new is context sensitive. Normally, items are considered “new” if there is no obvious overall similarity between them and the consumed items and material used in their production. In other cases, an item is considered “new” because it becomes relevant to documentation by a modification. For example, the scribbling of a name on a potsherd may make it a voting token. The original potsherd may not be worth documenting, in contrast to the inscribed one.
This entity can be collective: the printing of a thousand books, for example, would normally be considered a single event.
An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities and matter is preserved, but identity is not.
Examples:
- the construction of the SS Great Britain
- the first casting of the Little Mermaid from the harbour of Copenhagen
- Rembrandt’s creating of the seventh state of his etching “Woman sitting half dressed beside a stove”, 1658, identified by Bartsch Number 197 (E12,E65,E81)
Type: Entity
Belongs to version: Version 6.1
E12 Production
Scope note:
This class comprises activities that are designed to, and succeed in, creating one or more new items.
It specializes the notion of modification into production. The decision as to whether or not an object is regarded as new is context sensitive. Normally, items are considered “new” if there is no obvious overall similarity between them and the consumed items and material used in their production. In other cases, an item is considered “new” because it becomes relevant to documentation by a modification. For example, the scribbling of a name on a potsherd may make it a voting token. The original potsherd may not be worth documenting, in contrast to the inscribed one.
This entity can be collective: the printing of a thousand books, for example, would normally be considered a single event.
An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities and matter is preserved, but identity is not.
Examples:
- the construction of the SS Great Britain
- the first casting of the Little Mermaid from the harbour of Copenhagen
- Rembrandt’s creating of the seventh state of his etching “Woman sitting half dressed beside a stove”, 1658, identified by Bartsch Number 197 (E12,E65,E81)
Type: Entity
Belongs to version: Version 5.1.2
E12 Production
Scope note:
This class comprises activities that are designed to, and succeed in, creating one or more new items.
It specializes the notion of modification into production. The decision as to whether or not an object is regarded as new is context sensitive. Normally, items are considered “new” if there is no obvious overall similarity between them and the consumed items and material used in their production. In other cases, an item is considered “new” because it becomes relevant to documentation by a modification. For example, the scribbling of a name on a potsherd may make it a voting token. The original potsherd may not be worth documenting, in contrast to the inscribed one.
This entity can be collective: the printing of a thousand books, for example, would normally be considered a single event.
An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities and matter is preserved, but identity is not.
Examples:
- the construction of the SS Great Britain
- the first casting of the Little Mermaid from the harbour of Copenhagen
- Rembrandt’s creating of the seventh state of his etching “Woman sitting half dressed beside a stove”, 1658, identified by Bartsch Number 197 (E12,E65,E81)
Type: Entity
Belongs to version: Version 5.0.2
E12 Production
Scope note:
This class comprises activities that are designed to, and succeed in, creating one or more new items.
It specializes the notion of modification into production. The decision as to whether or not an object is regarded as new is context sensitive. Normally, items are considered “new” if there is no obvious overall similarity between them and the consumed items and material used in their production. In other cases, an item is considered “new” because it becomes relevant to documentation by a modification. For example, the scribbling of a name on a potsherd may make it a voting token. The original potsherd may not be worth documenting, in contrast to the inscribed one.
This entity can be collective: the printing of a thousand books, for example, would normally be considered a single event.
An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities and matter is preserved, but identity is not.
Examples:
- the construction of the SS Great Britain
- the first casting of the Little Mermaid from the harbour of Copenhagen
- Rembrandt’s creating of the seventh state of his etching “Woman sitting half dressed beside a stove”, 1658, identified by Bartsch Number 197 (E12,E65,E81)
Type: Entity
Belongs to version: Version 6.2.2
E12 Production
Scope note:
This class comprises activities that are designed to, and succeed in, creating one or more new items.
It specializes the notion of modification into production. The decision as to whether or not an object is regarded as new is context sensitive. Normally, items are considered “new” if there is no obvious overall similarity between them and the consumed items and material used in their production. In other cases, an item is considered “new” because it becomes relevant to documentation by a modification. For example, the scribbling of a name on a potsherd may make it a voting token. The original potsherd may not be worth documenting, in contrast to the inscribed one.
This entity can be collective: the printing of a thousand books, for example, would normally be considered a single event.
An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities and matter is preserved, but identity is not.
Examples:
- the construction of the SS Great Britain
- the first casting of the Little Mermaid from the harbour of Copenhagen
- Rembrandt’s creating of the seventh state of his etching “Woman sitting half dressed beside a stove”, 1658, identified by Bartsch Number 197 (E12,E65,E81)
Type: Entity
Belongs to version: Version 6.0
E12 Production
Scope note:
This class comprises activities that are designed to, and succeed in, creating one or more new items.
It specializes the notion of modification into production. The decision as to whether or not an object is regarded as new is context sensitive. Normally, items are considered “new” if there is no obvious overall similarity between them and the consumed items and material used in their production. In other cases, an item is considered “new” because it becomes relevant to documentation by a modification. For example, the scribbling of a name on a potsherd may make it a voting token. The original potsherd may not be worth documenting, in contrast to the inscribed one.
This entity can be collective: the printing of a thousand books, for example, would normally be considered a single event.
An event should also be documented using an instance of E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities and matter is preserved, but identity is not.
Examples:
- the construction of the SS Great Britain (Gregor, 1971)
- the first casting of the Little Mermaid from the harbour of Copenhagen (Dewey, 2003)
- Rembrandt’s creating of the seventh state of his etching “Woman sitting half dressed beside a stove”, 1658, identified by Bartsch Number 197 (E12, E65, E81) (Hind, 1923)
Type: Entity
Belongs to version: version 7.1
E12 Production
Scope note:
This class comprises activities that are designed to, and succeed in, creating one or more new items.
It specializes the notion of modification into production. The decision as to whether or not an object is regarded as new is context sensitive. Normally, items are considered “new” if there is no obvious overall similarity between them and the consumed items and material used in their production. In other cases, an item is considered “new” because it becomes relevant to documentation by a modification. For example, the scribbling of a name on a potsherd may make it a voting token. The original potsherd may not be worth documenting, in contrast to the inscribed one.
This entity can be collective: the printing of a thousand books, for example, would normally be considered a single event.
An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities and matter is preserved, but identity is not.
Examples:
- the construction of the SS Great Britain
- the first casting of the Little Mermaid from the harbour of Copenhagen
- Rembrandt’s creating of the seventh state of his etching “Woman sitting half dressed beside a stove”, 1658, identified by Bartsch Number 197 (E12,E65,E81)
Type: Entity
Belongs to version: Version 6.2
E12 Production Event
Scope note:
This class comprises activities that are designed to, and succeed in, creating one or more new items.
It specializes the notion of modification into production. The decision as to whether or not an object is regarded as new is context sensitive. Normally, items are considered “new” if there is no obvious overall similarity between them and the consumed items and material used in their production. In other cases, an item is considered “new” because it becomes relevant to documentation by a modification. For example, the scribbling of a name on a potsherd may make it a voting token. The original potsherd may not be worth documenting, in contrast to the inscribed one.
This entity can be collective: the printing of a thousand books, for example, would normally be considered a single event.
An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities and matter is preserved, but identity is not.
Examples:
- the construction of the SS Great Britain
- the recasting of the Little Mermaid at the harbour of Copenhagen
- the seventh edition of Rembrandt’s etching “Woman sitting half dressed beside a stove”, 1658, Bartsch Number 197
Type: Entity
Belongs to version: Version 4.1
E13 Attribute Assignment
Scope note:
This class comprises the actions of making assertions about properties of an object or any relation between two items or concepts.
This class allows the documentation of how the respective assignment came about, and whose opinion it was. All the attributes or properties assigned in such an action can also be seen as directly attached to the respective item or concept, possibly as a collection of contradictory values. All cases of properties in this model that are also described indirectly through an action are characterised as short cuts of this action. This redundant modelling of two alternative views is preferred because many implementations may have good reasons to model either the action or the short cut, and the relation between both alternatives can be captured by simple rules.
In particular, the class describes the actions of people making propositions and statements during certain museum procedures, e.g. the person and date when a condition statement was made, an identifier was assigned, the museum object was measured, etc. Which kinds of such assignments and statements need to be documented explicitly in structures of a schema rather than free text, depends on if this information should be accessible by structured queries.
Examples:
- the assessment of the current ownership of Martin Doerr’s silver cup in February 1997
Type: Entity
Belongs to version: Version 5.0.1
E13 Attribute Assignment
Scope note:
This class comprises the actions of making assertions about properties of an object or any relation between two items or concepts.
This class allows the documentation of how the respective assignment came about, and whose opinion it was. All the attributes or properties assigned in such an action can also be seen as directly attached to the respective item or concept, possibly as a collection of contradictory values. All cases of properties in this model that are also described indirectly through an action are characterised as "short cuts" of this action. This redundant modelling of two alternative views is preferred because many implementations may have good reasons to model either the action or the short cut, and the relation between both alternatives can be captured by simple rules.
In particular, the class describes the actions of people making propositions and statements during certain museum procedures, e.g. the person and date when a condition statement was made, an identifier was assigned, the museum object was measured, etc. Which kinds of such assignments and statements need to be documented explicitly in structures of a schema rather than free text, depends on if this information should be accessible by structured queries.
Examples:
- the assessment of the current ownership of Martin Doerr’s silver cup in February 1997
Type: Entity
Belongs to version: Version 6.2.1
E13 Attribute Assignment
Scope note:
This class comprises the actions of making assertions about properties of an object or any relation between two items or concepts.
This class allows the documentation of how the respective assignment came about, and whose opinion it was. All the attributes or properties assigned in such an action can also be seen as directly attached to the respective item or concept, possibly as a collection of contradictory values. All cases of properties in this model that are also described indirectly through an action are characterised as short cuts of this action. This redundant modelling of two alternative views is preferred because many implementations may have good reasons to model either the action or the short cut, and the relation between both alternatives can be captured by simple rules.
In particular, the class describes the actions of people making propositions and statements during certain museum procedures, e.g. the person and date when a condition statement was made, an identifier was assigned, the museum object was measured, etc. Which kinds of such assignments and statements need to be documented explicitly in structures of a schema rather than free text, depends on if this information should be accessible by structured queries.
Examples:
- the assessment of the current ownership of Martin Doerr’s silver cup in February 1997
Type: Entity
Belongs to version: Version 4.1
E13 Attribute Assignment
Scope note:
This class comprises the actions of making assertions about one property of an object or any single relation between two items or concepts. The type of the property asserted to hold between two items or concepts can be described by the property P177 assigned property type: E55 Type.
For example, the class describes the actions of people making propositions and statements during certain scientific/scholarly procedures, e.g., the person and date when a condition statement was made, an identifier was assigned, the museum object was measured, etc. Which kinds of such assignments and statements need to be documented explicitly in structures of a schema rather than free text, depends on whether this information should be accessible by structured queries.
This class allows for the documentation of how the respective assignment came about, and whose opinion it was. Note that all instances of properties described in a knowledge base are the opinion of someone. Per default, they are the opinion of the team maintaining the knowledge base. This fact must not individually be registered for all instances of properties provided by the maintaining team, because it would result in an endless recursion of whose opinion was the description of an opinion. Therefore, the use of instances of E13 Attribute Assignment marks the fact, that the maintaining team is in general neutral to the validity of the respective assertion, but registers someone else’s opinion and how it came about.
All properties assigned in such an action can also be seen as directly relating the respective pair of items or concepts. Multiple use of instances of E13 Attribute Assignment may possibly lead to a collection of contradictory values.
All cases of properties in this model that are also described indirectly through a subclass of E13 Attribute Assignment are characterised as short cuts of a path via this subclass. This redundant modelling of two alternative views is preferred because many implementations may have good reasons to model either the action of assertion or the short cut, and the relation between both alternatives can be captured by simple rules.
Examples:
- the examination of MS Sinai Greek 418 by Nicholas Pickwoad in November 2003 (Honey & Pickwoad , 2010)
- the assessment of the current ownership of Martin Doerr’s silver cup in February 1997 (fictitious)
Type: Entity
Belongs to version: version 7.1.1
E13 Attribute Assignment
Scope note:
This class comprises the actions of making assertions about properties of an object or any relation between two items or concepts.
This class allows the documentation of how the respective assignment came about, and whose opinion it was. All the attributes or properties assigned in such an action can also be seen as directly attached to the respective item or concept, possibly as a collection of contradictory values. All cases of properties in this model that are also described indirectly through an action are characterised as "short cuts" of this action. This redundant modelling of two alternative views is preferred because many implementations may have good reasons to model either the action or the short cut, and the relation between both alternatives can be captured by simple rules.
In particular, the class describes the actions of people making propositions and statements during certain museum procedures, e.g. the person and date when a condition statement was made, an identifier was assigned, the museum object was measured, etc. Which kinds of such assignments and statements need to be documented explicitly in structures of a schema rather than free text, depends on if this information should be accessible by structured queries.
Examples:
- the assessment of the current ownership of Martin Doerr’s silver cup in February 1997
Type: Entity
Belongs to version: Version 6.1
E13 Attribute Assignment
Scope note:
This class comprises the actions of making assertions about properties of an object or any relation between two items or concepts.
This class allows the documentation of how the respective assignment came about, and whose opinion it was. All the attributes or properties assigned in such an action can also be seen as directly attached to the respective item or concept, possibly as a collection of contradictory values. All cases of properties in this model that are also described indirectly through an action are characterised as "short cuts" of this action. This redundant modelling of two alternative views is preferred because many implementations may have good reasons to model either the action or the short cut, and the relation between both alternatives can be captured by simple rules.
In particular, the class describes the actions of people making propositions and statements during certain museum procedures, e.g. the person and date when a condition statement was made, an identifier was assigned, the museum object was measured, etc. Which kinds of such assignments and statements need to be documented explicitly in structures of a schema rather than free text, depends on if this information should be accessible by structured queries.
Examples:
- the assessment of the current ownership of Martin Doerr’s silver cup in February 1997
Type: Entity
Belongs to version: Version 5.1.2
E13 Attribute Assignment
Scope note:
This class comprises the actions of making assertions about properties of an object or any relation between two items or concepts.
This class allows the documentation of how the respective assignment came about, and whose opinion it was. All the attributes or properties assigned in such an action can also be seen as directly attached to the respective item or concept, possibly as a collection of contradictory values. All cases of properties in this model that are also described indirectly through an action are characterised as short cuts of this action. This redundant modelling of two alternative views is preferred because many implementations may have good reasons to model either the action or the short cut, and the relation between both alternatives can be captured by simple rules.
In particular, the class describes the actions of people making propositions and statements during certain museum procedures, e.g. the person and date when a condition statement was made, an identifier was assigned, the museum object was measured, etc. Which kinds of such assignments and statements need to be documented explicitly in structures of a schema rather than free text, depends on if this information should be accessible by structured queries.
Examples:
- the assessment of the current ownership of Martin Doerr’s silver cup in February 1997
Type: Entity
Belongs to version: Version 5.0.2
E13 Attribute Assignment
Scope note:
This class comprises the actions of making assertions about properties of an object or any relation between two items or concepts.
This class allows the documentation of how the respective assignment came about, and whose opinion it was. All the attributes or properties assigned in such an action can also be seen as directly attached to the respective item or concept, possibly as a collection of contradictory values. All cases of properties in this model that are also described indirectly through an action are characterised as "short cuts" of this action. This redundant modelling of two alternative views is preferred because many implementations may have good reasons to model either the action or the short cut, and the relation between both alternatives can be captured by simple rules.
In particular, the class describes the actions of people making propositions and statements during certain museum procedures, e.g. the person and date when a condition statement was made, an identifier was assigned, the museum object was measured, etc. Which kinds of such assignments and statements need to be documented explicitly in structures of a schema rather than free text, depends on if this information should be accessible by structured queries.
Examples:
- the assessment of the current ownership of Martin Doerr’s silver cup in February 1997
Type: Entity
Belongs to version: Version 6.2.2
E13 Attribute Assignment
Scope note:
This class comprises the actions of making assertions about properties of an object or any relation between two items or concepts.
This class allows the documentation of how the respective assignment came about, and whose opinion it was. All the attributes or properties assigned in such an action can also be seen as directly attached to the respective item or concept, possibly as a collection of contradictory values. All cases of properties in this model that are also described indirectly through an action are characterised as "short cuts" of this action. This redundant modelling of two alternative views is preferred because many implementations may have good reasons to model either the action or the short cut, and the relation between both alternatives can be captured by simple rules.
In particular, the class describes the actions of people making propositions and statements during certain museum procedures, e.g. the person and date when a condition statement was made, an identifier was assigned, the museum object was measured, etc. Which kinds of such assignments and statements need to be documented explicitly in structures of a schema rather than free text, depends on if this information should be accessible by structured queries.
Examples:
- the assessment of the current ownership of Martin Doerr’s silver cup in February 1997
Type: Entity
Belongs to version: Version 6.0
E13 Attribute Assignment
Scope note:
This class comprises the actions of making assertions about one property of an object or any single relation between two items or concepts. The type of the property asserted to hold between two items or concepts can be described by the property P177 assigned property type: E55 Type.
For example, the class describes the actions of people making propositions and statements during certain scientific/scholarly procedures, e.g., the person and date when a condition statement was made, an identifier was assigned, the museum object was measured, etc. Which kinds of such assignments and statements need to be documented explicitly in structures of a schema rather than free text, depends on whether this information should be accessible by structured queries.
This class allows for the documentation of how the respective assignment came about, and whose opinion it was. Note that all instances of properties described in a knowledge base are the opinion of someone. Per default, they are the opinion of the team maintaining the knowledge base. This fact must not individually be registered for all instances of properties provided by the maintaining team, because it would result in an endless recursion of whose opinion was the description of an opinion. Therefore, the use of instances of E13 Attribute Assignment marks the fact, that the maintaining team is in general neutral to the validity of the respective assertion, but registers someone else’s opinion and how it came about.
All properties assigned in such an action can also be seen as directly relating the respective pair of items or concepts. Multiple use of instances of E13 Attribute Assignment may possibly lead to a collection of contradictory values.
All cases of properties in this model that are also described indirectly through a subclass of E13 Attribute Assignment are characterised as "short cuts" of a path via this subclass. This redundant modelling of two alternative views is preferred because many implementations may have good reasons to model either the action of assertion or the short cut, and the relation between both alternatives can be captured by simple rules.
Examples:
- the examination of MS Sinai Greek 418 by Nicholas Pickwoad in November 2003 (E13) (Honey and Pickwoad, 2010)
- the assessment of the current ownership of Martin Doerr’s silver cup in February 1997 (fictitious)
Type: Entity
Belongs to version: version 7.1
E13 Attribute Assignment
Scope note:
This class comprises the actions of making assertions about properties of an object or any relation between two items or concepts.
This class allows the documentation of how the respective assignment came about, and whose opinion it was. All the attributes or properties assigned in such an action can also be seen as directly attached to the respective item or concept, possibly as a collection of contradictory values. All cases of properties in this model that are also described indirectly through an action are characterised as "short cuts" of this action. This redundant modelling of two alternative views is preferred because many implementations may have good reasons to model either the action or the short cut, and the relation between both alternatives can be captured by simple rules.
In particular, the class describes the actions of people making propositions and statements during certain museum procedures, e.g. the person and date when a condition statement was made, an identifier was assigned, the museum object was measured, etc. Which kinds of such assignments and statements need to be documented explicitly in structures of a schema rather than free text, depends on if this information should be accessible by structured queries.
Examples:
- the assessment of the current ownership of Martin Doerr’s silver cup in February 1997
Type: Entity
Belongs to version: Version 6.2
E14 Condition Assessment
Scope note:
This class describes the act of assessing the state of preservation of an object during a particular period.
The condition assessment may be carried out by inspection, measurement or through historical research. This class is used to document circumstances of the respective assessment that may be relevant to interpret its quality at a later stage, or to continue research on related documents.
Examples:
- last year’s inspection of humidity damage to the frescos in the St. George chapel in our village
Type: Entity
Belongs to version: Version 5.0.1
E14 Condition Assessment
Scope note:
This class describes the act of assessing the state of preservation of an object during a particular period.
The condition assessment may be carried out by inspection, measurement or through historical research. This class is used to document circumstances of the respective assessment that may be relevant to interpret its quality at a later stage, or to continue research on related documents.
Examples:
- last year’s inspection of humidity damage to the frescos in the St. George chapel in our village
Type: Entity
Belongs to version: Version 6.2.1
E14 Condition Assessment
Scope note:
This class describes the act of assessing the state of preservation of an object during a particular period.
The condition assessment may be carried out by inspection, measurement or through historical research. This class is used to document circumstances of the respective assessment that may be relevant to interpret its quality at a later stage, or to continue research on related documents.
Examples:
- last year’s inspection of humidity damage to the frescos in the St. George chapel in our village
Type: Entity
Belongs to version: Version 4.1
E14 Condition Assessment
Scope note:
This class describes the act of assessing the state of preservation of an object during a particular period.
The condition assessment may be carried out by inspection, measurement or through historical research. This class is used to document circumstances of the respective assessment that may be relevant to interpret its quality at a later stage, or to continue research on related documents.
Examples:
- last year’s inspection of humidity damage to the frescos in the St. George chapel in our village (fictitious)
- the condition assessment of the endband cores of MS Sinai Greek 418 by Nicholas Pickwoad in November 2003 (Honey & Pickwoad, 2010)
- the condition assessment of the cover of MS Sinai Greek 418 by Nicholas Pickwoad in November 2003 (Honey & Pickwoad, 2010)
Type: Entity
Belongs to version: version 7.1.1
E14 Condition Assessment
Scope note:
This class describes the act of assessing the state of preservation of an object during a particular period.
The condition assessment may be carried out by inspection, measurement or through historical research. This class is used to document circumstances of the respective assessment that may be relevant to interpret its quality at a later stage, or to continue research on related documents.
Examples:
- last year’s inspection of humidity damage to the frescos in the St. George chapel in our village
Type: Entity
Belongs to version: Version 6.1
E14 Condition Assessment
Scope note:
This class describes the act of assessing the state of preservation of an object during a particular period.
The condition assessment may be carried out by inspection, measurement or through historical research. This class is used to document circumstances of the respective assessment that may be relevant to interpret its quality at a later stage, or to continue research on related documents.
Examples:
- last year’s inspection of humidity damage to the frescos in the St. George chapel in our village
Type: Entity
Belongs to version: Version 5.1.2
E14 Condition Assessment
Scope note:
This class describes the act of assessing the state of preservation of an object during a particular period.
The condition assessment may be carried out by inspection, measurement or through historical research. This class is used to document circumstances of the respective assessment that may be relevant to interpret its quality at a later stage, or to continue research on related documents.
Examples:
- last year’s inspection of humidity damage to the frescos in the St. George chapel in our village
Type: Entity
Belongs to version: Version 5.0.2
E14 Condition Assessment
Scope note:
This class describes the act of assessing the state of preservation of an object during a particular period.
The condition assessment may be carried out by inspection, measurement or through historical research. This class is used to document circumstances of the respective assessment that may be relevant to interpret its quality at a later stage, or to continue research on related documents.
Examples:
- last year’s inspection of humidity damage to the frescos in the St. George chapel in our village
Type: Entity
Belongs to version: Version 6.2.2
E14 Condition Assessment
Scope note:
This class describes the act of assessing the state of preservation of an object during a particular period.
The condition assessment may be carried out by inspection, measurement or through historical research. This class is used to document circumstances of the respective assessment that may be relevant to interpret its quality at a later stage, or to continue research on related documents.
Examples:
- last year’s inspection of humidity damage to the frescos in the St. George chapel in our village
Type: Entity
Belongs to version: Version 6.0
E14 Condition Assessment
Scope note:
This class describes the act of assessing the state of preservation of an object during a particular period.
The condition assessment may be carried out by inspection, measurement or through historical research. This class is used to document circumstances of the respective assessment that may be relevant to interpret its quality at a later stage, or to continue research on related documents.
Examples:
- last year’s inspection of humidity damage to the frescos in the St. George chapel in our village (fictitious)
- the condition assessment of the endband cores of MS Sinai Greek 418 by Nicholas Pickwoad in November 2003 (E14) (Honey and Pickwoad, 2010)
- the condition assessment of the cover of MS Sinai Greek 418 by Nicholas Pickwoad in November 2003 (E14) (Honey and Pickwoad, 2010)
Type: Entity
Belongs to version: version 7.1
E14 Condition Assessment
Scope note:
This class describes the act of assessing the state of preservation of an object during a particular period.
The condition assessment may be carried out by inspection, measurement or through historical research. This class is used to document circumstances of the respective assessment that may be relevant to interpret its quality at a later stage, or to continue research on related documents.
Examples:
- last year’s inspection of humidity damage to the frescos in the St. George chapel in our village
Type: Entity
Belongs to version: Version 6.2
E15 Identifier Assignment
Scope note:
This class comprises activities that result in the allocation of an identifier to an instance of E1 CRM Entity. An E15 Identifier Assignment may include the creation of the identifier from multiple constituents, which themselves may be instances of E41 Appellation. The syntax and kinds of constituents to be used may be declared in a rule constituting an instance of E29 Design or Procedure.
Examples:
- of such identifiers include Find Numbers, Inventory Numbers, uniform titles in the sense of librarianship and Digital Object Identifiers (DOI). Documenting the act of identifier assignment and deassignment is especially useful when objects change custody or the identification system of an organization is changed. In order to keep track of the identity of things in such cases, it is important to document by whom, when and for what purpose an identifier is assigned to an item.
- The fact that an identifier is a preferred one for an organisation can be expressed by using the property E1 CRM Entity. P48 has preferred identifier (is preferred identifier of): E42 Identifier. It can better be expressed in a context independent form by assigning a suitable E55 Type, such as “preferred identifier assignment”, to the respective instance of E15 Identifier Assignment via the P2 has type property.
- Examples:
- Replacement of the inventory number TA959a by GE34604 for a 17th century lament cloth at the Museum Benaki, Athens
- Assigning the author-uniform title heading “Goethe, Johann Wolfgang von, 1749-1832. Faust. 1. Theil.” for a work (E28)
- On June 1, 2001 assigning the personal name heading “Guillaume, de Machaut, ca. 1300-1377” (E42,E82) to Guillaume de Machaut (E21)
Type: Entity
Belongs to version: Version 5.0.1
E15 Identifier Assignment
Scope note:
This class comprises activities that result in the allocation of an identifier to an instance of E1 CRM Entity. An E15 Identifier Assignment may include the creation of the identifier from multiple constituents, which themselves may be instances of E41 Appellation. The syntax and kinds of constituents to be used may be declared in a rule constituting an instance of E29 Design or Procedure.
Examples of such identifiers include Find Numbers, Inventory Numbers, uniform titles in the sense of librarianship and Digital Object Identifiers (DOI). Documenting the act of identifier assignment and deassignment is especially useful when objects change custody or the identification system of an organization is changed. In order to keep track of the identity of things in such cases, it is important to document by whom, when and for what purpose an identifier is assigned to an item.
The fact that an identifier is a preferred one for an organisation can be expressed by using the property E1 CRM Entity. P48 has preferred identifier (is preferred identifier of): E42 Identifier. It can better be expressed in a context independent form by assigning a suitable E55 Type, such as “preferred identifier assignment”, to the respective instance of E15 Identifier Assignment via the P2 has type property.
Examples:
- Replacement of the inventory number TA959a by GE34604 for a 17th century lament cloth at the Museum Benaki, Athens
- Assigning the author-uniform title heading “Goethe, Johann Wolfgang von, 1749-1832. Faust. 1. Theil.” for a work (E28)
- On June 1, 2001 assigning the personal name heading “Guillaume, de Machaut, ca. 1300-1377” (E42,E82) to Guillaume de Machaut (E21)
Type: Entity
Belongs to version: Version 6.2.1
E15 Identifier Assignment
Scope note:
This class comprises actions assigning or deassigning object identifiers.
Examples:
- of such identifiers include Find Numbers and Inventory Numbers. Documenting the act of identifier assignment and deassignment is especially useful when objects change custody or the identification system of an organization is changed. In order to keep track of the identity of an object in such cases, it is important to document by whom, when and for what purpose an identifier is assigned to an object.
- Examples:
- replacement of the inventory number TA959a by GE34604 for a 17th century lament cloth at the Museum Benaki, Athens
Type: Entity
Belongs to version: Version 4.1
E15 Identifier Assignment
Scope note:
This class comprises activities that result in the allocation of an identifier to an instance of E1 CRM Entity. Instances of E15 Identifier Assignment may include the creation of the identifier from multiple constituents, which themselves may be instances of E41 Appellation. The syntax and kinds of constituents to be used may be declared in a rule constituting an instance of E29 Design or Procedure.
Examples of such identifiers include Find Numbers, Inventory Numbers, uniform titles in the sense of librarianship and Digital Object Identifiers (DOI). Documenting the act of identifier assignment and deassignment is especially useful when objects change custody or the identification system of an organization is changed. In order to keep track of the identity of things in such cases, it is important to document by whom, when and for what purpose an identifier is assigned to an item.
The fact that an identifier is a preferred one for an organisation can be expressed by using the property E1 CRM Entity. P48 has preferred identifier (is preferred identifier of): E42 Identifier. It can better be expressed in a context independent form by assigning a suitable E55 Type, such as “preferred identifier assignment”, to the respective instance of E15 Identifier Assignment via the P2 has type property.
Examples:
- replacement of the inventory number TA959a by GE34604 for a 17th century lament cloth at the Museum Benaki, Athens
- assigning the author-uniform title heading “Goethe, Johann Wolfgang von, 1749-1832. Faust. 1. Theil.” for the respective work
- on June 1, 2001 assigning the personal name heading “Guillaume, de Machaut, ca. 1300-1377” to Guillaume de Machaut (Kelly, 2014)
Type: Entity
Belongs to version: version 7.1.1
E15 Identifier Assignment
Scope note:
This class comprises activities that result in the allocation of an identifier to an instance of E1 CRM Entity. An E15 Identifier Assignment may include the creation of the identifier from multiple constituents, which themselves may be instances of E41 Appellation. The syntax and kinds of constituents to be used may be declared in a rule constituting an instance of E29 Design or Procedure.
Examples of such identifiers include Find Numbers, Inventory Numbers, uniform titles in the sense of librarianship and Digital Object Identifiers (DOI). Documenting the act of identifier assignment and deassignment is especially useful when objects change custody or the identification system of an organization is changed. In order to keep track of the identity of things in such cases, it is important to document by whom, when and for what purpose an identifier is assigned to an item.
The fact that an identifier is a preferred one for an organisation can be expressed by using the property E1 CRM Entity. P48 has preferred identifier (is preferred identifier of): E42 Identifier. It can better be expressed in a context independent form by assigning a suitable E55 Type, such as “preferred identifier assignment”, to the respective instance of E15 Identifier Assignment via the P2 has type property.
Examples:
- Replacement of the inventory number TA959a by GE34604 for a 17th century lament cloth at the Museum Benaki, Athens
- Assigning the author-uniform title heading “Goethe, Johann Wolfgang von, 1749-1832. Faust. 1. Theil.” for a work (E28)
- On June 1, 2001 assigning the personal name heading “Guillaume, de Machaut, ca. 1300-1377” (E42,E82) to Guillaume de Machaut (E21)
Type: Entity
Belongs to version: Version 6.1
E15 Identifier Assignment
Scope note:
This class comprises activities that result in the allocation of an identifier to an instance of E1 CRM Entity. An E15 Identifier Assignment may include the creation of the identifier from multiple constituents, which themselves may be instances of E41 Appellation. The syntax and kinds of constituents to be used may be declared in a rule constituting an instance of E29 Design or Procedure.
Examples of such identifiers include Find Numbers, Inventory Numbers, uniform titles in the sense of librarianship and Digital Object Identifiers (DOI). Documenting the act of identifier assignment and deassignment is especially useful when objects change custody or the identification system of an organization is changed. In order to keep track of the identity of things in such cases, it is important to document by whom, when and for what purpose an identifier is assigned to an item.
The fact that an identifier is a preferred one for an organisation can be expressed by using the property E1 CRM Entity. P48 has preferred identifier (is preferred identifier of): E42 Identifier. It can better be expressed in a context independent form by assigning a suitable E55 Type, such as “preferred identifier assignment”, to the respective instance of E15 Identifier Assignment via the P2 has type property.
Examples:
- Replacement of the inventory number TA959a by GE34604 for a 17th century lament cloth at the Museum Benaki, Athens
- Assigning the author-uniform title heading “Goethe, Johann Wolfgang von, 1749-1832. Faust. 1. Theil.” for a work (E28)
- On June 1, 2001 assigning the personal name heading “Guillaume, de Machaut, ca. 1300-1377” (E42,E82) to Guillaume de Machaut (E21)
Type: Entity
Belongs to version: Version 5.1.2
E15 Identifier Assignment
Scope note:
This class comprises activities that result in the allocation of an identifier to an instance of E1 CRM Entity. An E15 Identifier Assignment may include the creation of the identifier from multiple constituents, which themselves may be instances of E41 Appellation. The syntax and kinds of constituents to be used may be declared in a rule constituting an instance of E29 Design or Procedure.
Examples:
- of such identifiers include Find Numbers, Inventory Numbers, uniform titles in the sense of librarianship and Digital Object Identifiers (DOI). Documenting the act of identifier assignment and deassignment is especially useful when objects change custody or the identification system of an organization is changed. In order to keep track of the identity of things in such cases, it is important to document by whom, when and for what purpose an identifier is assigned to an item.
- The fact that an identifier is a preferred one for an organisation can be expressed by using the property E1 CRM Entity. P48 has preferred identifier (is preferred identifier of): E42 Identifier. It can better be expressed in a context independent form by assigning a suitable E55 Type, such as “preferred identifier assignment”, to the respective instance of E15 Identifier Assignment via the P2 has type property.
- Examples:
- Replacement of the inventory number TA959a by GE34604 for a 17th century lament cloth at the Museum Benaki, Athens
- Assigning the author-uniform title heading “Goethe, Johann Wolfgang von, 1749-1832. Faust. 1. Theil.” for a work (E28)
- On June 1, 2001 assigning the personal name heading “Guillaume, de Machaut, ca. 1300-1377” (E42,E82) to Guillaume de Machaut (E21)
Type: Entity
Belongs to version: Version 5.0.2
E15 Identifier Assignment
Scope note:
This class comprises activities that result in the allocation of an identifier to an instance of E1 CRM Entity. An E15 Identifier Assignment may include the creation of the identifier from multiple constituents, which themselves may be instances of E41 Appellation. The syntax and kinds of constituents to be used may be declared in a rule constituting an instance of E29 Design or Procedure.
Examples of such identifiers include Find Numbers, Inventory Numbers, uniform titles in the sense of librarianship and Digital Object Identifiers (DOI). Documenting the act of identifier assignment and deassignment is especially useful when objects change custody or the identification system of an organization is changed. In order to keep track of the identity of things in such cases, it is important to document by whom, when and for what purpose an identifier is assigned to an item.
The fact that an identifier is a preferred one for an organisation can be expressed by using the property E1 CRM Entity. P48 has preferred identifier (is preferred identifier of): E42 Identifier. It can better be expressed in a context independent form by assigning a suitable E55 Type, such as “preferred identifier assignment”, to the respective instance of E15 Identifier Assignment via the P2 has type property.
Examples:
- Replacement of the inventory number TA959a by GE34604 for a 17th century lament cloth at the Museum Benaki, Athens
- Assigning the author-uniform title heading “Goethe, Johann Wolfgang von, 1749-1832. Faust. 1. Theil.” for a work (E28)
- On June 1, 2001 assigning the personal name heading “Guillaume, de Machaut, ca. 1300-1377” (E42,E82) to Guillaume de Machaut (E21)
Type: Entity
Belongs to version: Version 6.2.2
E15 Identifier Assignment
Scope note:
This class comprises activities that result in the allocation of an identifier to an instance of E1 CRM Entity. An E15 Identifier Assignment may include the creation of the identifier from multiple constituents, which themselves may be instances of E41 Appellation. The syntax and kinds of constituents to be used may be declared in a rule constituting an instance of E29 Design or Procedure.
Examples of such identifiers include Find Numbers, Inventory Numbers, uniform titles in the sense of librarianship and Digital Object Identifiers (DOI). Documenting the act of identifier assignment and deassignment is especially useful when objects change custody or the identification system of an organization is changed. In order to keep track of the identity of things in such cases, it is important to document by whom, when and for what purpose an identifier is assigned to an item.
The fact that an identifier is a preferred one for an organisation can be expressed by using the property E1 CRM Entity. P48 has preferred identifier (is preferred identifier of): E42 Identifier. It can better be expressed in a context independent form by assigning a suitable E55 Type, such as “preferred identifier assignment”, to the respective instance of E15 Identifier Assignment via the P2 has type property.
Examples:
- Replacement of the inventory number TA959a by GE34604 for a 17th century lament cloth at the Museum Benaki, Athens
- Assigning the author-uniform title heading “Goethe, Johann Wolfgang von, 1749-1832. Faust. 1. Theil.” for a work (E28)
- On June 1, 2001 assigning the personal name heading “Guillaume, de Machaut, ca. 1300-1377” (E42,E82) to Guillaume de Machaut (E21)
Type: Entity
Belongs to version: Version 6.0
E15 Identifier Assignment
Scope note:
This class comprises activities that result in the allocation of an identifier to an instance of E1 CRM Entity. Instances of E15 Identifier Assignment may include the creation of the identifier from multiple constituents, which themselves may be instances of E41 Appellation. The syntax and kinds of constituents to be used may be declared in a rule constituting an instance of E29 Design or Procedure.
Examples of such identifiers include Find Numbers, Inventory Numbers, uniform titles in the sense of librarianship and Digital Object Identifiers (DOI). Documenting the act of identifier assignment and deassignment is especially useful when objects change custody or the identification system of an organization is changed. In order to keep track of the identity of things in such cases, it is important to document by whom, when and for what purpose an identifier is assigned to an item.
The fact that an identifier is a preferred one for an organisation can be expressed by using the property E1 CRM Entity. P48 has preferred identifier (is preferred identifier of): E42 Identifier. It can better be expressed in a context independent form by assigning a suitable E55 Type, such as “preferred identifier assignment”, to the respective instance of E15 Identifier Assignment via the P2 has type property.
Examples:
- Replacement of the inventory number TA959a by GE34604 for a 17th century lament cloth at the Museum Benaki, Athens
- Assigning the author-uniform title heading “Goethe, Johann Wolfgang von, 1749-1832. Faust. 1. Theil.” for the respective work (E28)
- On June 1, 2001 assigning the personal name heading “Guillaume, de Machaut, ca. 1300-1377” (E42,E82) to Guillaume de Machaut (E21)
Type: Entity
Belongs to version: version 7.1
E15 Identifier Assignment
Scope note:
This class comprises activities that result in the allocation of an identifier to an instance of E1 CRM Entity. An E15 Identifier Assignment may include the creation of the identifier from multiple constituents, which themselves may be instances of E41 Appellation. The syntax and kinds of constituents to be used may be declared in a rule constituting an instance of E29 Design or Procedure.
Examples of such identifiers include Find Numbers, Inventory Numbers, uniform titles in the sense of librarianship and Digital Object Identifiers (DOI). Documenting the act of identifier assignment and deassignment is especially useful when objects change custody or the identification system of an organization is changed. In order to keep track of the identity of things in such cases, it is important to document by whom, when and for what purpose an identifier is assigned to an item.
The fact that an identifier is a preferred one for an organisation can be expressed by using the property E1 CRM Entity. P48 has preferred identifier (is preferred identifier of): E42 Identifier. It can better be expressed in a context independent form by assigning a suitable E55 Type, such as “preferred identifier assignment”, to the respective instance of E15 Identifier Assignment via the P2 has type property.
Examples:
- Replacement of the inventory number TA959a by GE34604 for a 17th century lament cloth at the Museum Benaki, Athens
- Assigning the author-uniform title heading “Goethe, Johann Wolfgang von, 1749-1832. Faust. 1. Theil.” for a work (E28)
- On June 1, 2001 assigning the personal name heading “Guillaume, de Machaut, ca. 1300-1377” (E42,E82) to Guillaume de Machaut (E21)
Type: Entity
Belongs to version: Version 6.2
E16 Measurement
Scope note:
This class comprises actions measuring physical properties and other values that can be determined by a systematic procedure.
Examples:
- include measuring the monetary value of a collection of coins or the running time of a specific video cassette.
- The E16 Measurement may use simple counting or tools, such as yardsticks or radiation detection devices. The interest is in the method and care applied, so that the reliability of the result may be judged at a later stage, or research continued on the associated documents. The date of the event is important for dimensions, which may change value over time, such as the length of an object subject to shrinkage. Details of methods and devices are best handled as free text, whereas basic techniques such as carbon 14 dating should be encoded using P2 has type (is type of:) E55 Type.
- Examples:
- measurement of height of silver cup 232 on the 31st August 1997
- the carbon 14 dating of the “Schoeninger Speer II” in 1996 [an about 400.000 years old Palaeolithic complete wooden spear found in Schoeningen, Niedersachsen, Germany in 1995]
Type: Entity
Belongs to version: Version 5.0.1
E16 Measurement
Scope note:
This class comprises actions measuring physical properties and other values that can be determined by a systematic procedure.
Examples include measuring the monetary value of a collection of coins or the running time of a specific video cassette.
The E16 Measurement may use simple counting or tools, such as yardsticks or radiation detection devices. The interest is in the method and care applied, so that the reliability of the result may be judged at a later stage, or research continued on the associated documents. The date of the event is important for dimensions, which may change value over time, such as the length of an object subject to shrinkage. Details of methods and devices are best handled as free text, whereas basic techniques such as "carbon 14 dating" should be encoded using P2 has type (is type of:) E55 Type.
Examples:
- measurement of height of silver cup 232 on the 31st August 1997
- the carbon 14 dating of the “Schoeninger Speer II” in 1996 [an about 400.000 years old Palaeolithic complete wooden spear found in Schoeningen, Niedersachsen, Germany in 1995]
Type: Entity
Belongs to version: Version 6.2.1