Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version. Compare with Current  |   View Page History

Notes from May-Jul 2013


Lec: (Our mapping) is same as Dominic's manual (to best of our understanding)
Vlado: Does it comply with BM's latest changes to modeling Association codes (esp re Acquisition, Production)? BM Association Mapping v2. Dominic's document probably reflects this, but these are recent changes and I haven't checked.

YCBA uses the following systems:

  • BededWork = calendaring
  • TMS = art collections
  • Drupal = website, exhibitions etc
  • Orbis = books etc

Getting Yale On-board

Lec: If there is something else you need to get this to work with Research Space please let me know
Vlado: Once it's compliant, we should:

  • try loading the data
  • load your thesauri. Complete Getty or only the subset used by your objects? How about Broader terms?
  • implement Image Annotation over your DeepZoom images (we also use IIP Image for RKD images, so shouldn't be too hard)
  • coreference some of your terms to enable cross-collection search
  • create RForms for your objects

See RS Plan 3.7#Get Yale on-board with ResearchSpace for details. As of 08-Jul-2013, this iteration is under planning and the exact scope and start is not clear. I think we can get Yale on board before mid-Sep (the Getty meeting), but it depends on the exact scope.

It appears that Yale is not the bottleneck: starting the RS3.7 iteration is. So please let's not rush this review process!


Please don't use color or strikethrough, use the following symbols for easier tracking (easiest to edit them in Wiki Markup mode):

  • open issue
  • resolved issue
  • issue under discussion


Lec: I am reviewing for any typos, missing types...

  • Have you tried Eyeball? See here: RDF Validation and Conversion#Eyeball
    Lec: We tried Eyeball, no luck have to contact dev community as we were not able to install it after number of tries. TBD..



  • GREY Pubby prefixes are not setup: shows "?:..."
    Lec: low priority, at first glance did not see where the config has this, will need to return to it after we are done with everything or in spare time. 
  • STRONGLY Suggest to have 1 URI per object, not 3 sameAs URIs
    GREY Lec: BM has multiple, followed their lead - we still need to figure this out (don't want to publish two data sets one for RS and one for the world) - not pressing low priority
    Vlado: RS currently cannot work with these sameAs (eg would return results in triplicate). BM puts sameAs in separate files that we don't load
  •  don't emit prefixes you don't need: lccn, oclc, ycba_aat, etc etc
  • crm:PX_* (e.g. crm:PX_display_wrap) is wrong, should be bmo:PX_*
    Lec: fixed with
    Vlado: Please use bmo:PX_* and not ycba:PX_*: don't create a second property with the same purpose.
  • Same holds about classes: use bmo:EX_Association not ycba:EX_Association: don't define your own class for the same purpose.

Connected Resources

TODO Vlado: write down appropriate representations

It's best to list all URLs closely related to each object, eg
"Mrs. Abington as Miss Prue in Love for Love by William Congreve":


Whole Getty or Parts


Currently you emit thesaurus data together with the object, and only the terms used in the object:

  • This way you miss Broader terms, so eg a search for "Animal" or "Mammal" won't find FR Transitivity
    • Lec: regarding Places, why don't we use Geographic Coordinates (included by Yale) and search by a bounding box?
    • Vlado: RS currently doesn't have bounding box search, because BM Places thesaurus doesn't include Geographic Coordinates.
      RS has place name search, that uses the place hierarchy.
  • This way you repeat data about the same term in many objects
  • If you start emitting objects in separate graphs like BM does (to be able to easily replace/delete), the term data will be duplicated in each of these object graphs
    As you can see already happens about YCBA itself:
    <> a crm:E74_Group , skos:Concept ;
      skos:prefLabel "Yale Center for British Art" ;
      skos:inScheme <> ;
      a crm:E74_Group , skos:Concept ;
      skos:prefLabel "Yale Center for British Art" ;
      skos:inScheme <> .
  • In several cases these in-object ad-hoc terms don't satisfy Thesaurus Requirements (see next section)

My strong recommendation is to export the complete Getty thesauri

  • we shouldn't wait for Getty to do an official mapping, since it'll take a few months for TGN and ULAN, and it won't satisfy the requirement to publish as CRM (see next section)
  • I can do this mapping. I'll also be involved in the Getty's mapping, so that's a good synergy
  • Getty's committed to publish as LOD, so hopefully they won't object, as soon as we mark our export as Unofficial
  • use a separate thesaurus export config, like BM does

Lec: I export terms within objects because they are present in the LIDO XML.
But to export the complete tehsauri, I would need to get someone to export from RDBMS, and we cannot do this right now


  • For the time being we'll stay without Broader terms
  • Dominic and Vlado to try to expedite the Getty export by Getty

Thesaurus Requirements

You must comply with BMX Issues#Thesaurus requirements
Each term should be both a CRM entity of appropriate type, and skos:Concept.

  • You have this for some (eg Agents) but not others (eg Title Type).


Each thesaurus (ConceptScheme) used by Yale should be described in Meta-Thesaurus and FR Names#YCBA Thesauri (this section will be merged to the rest of the table)

  • This applies to both Getty and YCBA local thesauri.
  • GREY extend RS to handle AAT as one ConceptScheme that includes a number of facets (hierarchies) for object type, material, technique, etc
  • For now: Yale will export AAT terms in different concept schemes, eg:
    aat:123456 skos:inScheme aat_object:    . # painting
    aat:678901 skos:inScheme aat_material:  . # canvas
    aat:234567 skos:inScheme aat_technique: . # oil
    aat:890123 skos:inScheme aat_subject: .   # horse
  • TODO Vlado: use actual AAT identifiers above, and use the AAT Facets (top-levels) as concept schemes

Emmanuelle: It would be helpful to briefly go over the definitions for searchable and tagable.

  • Searchable is a thesaurus that can be used in FR search. The list of FRs is Meta-Thesaurus and FR Names#FR Names Table and the detailed definitions are FR Implementation. Examples:
    • BM Object is searchable using FR2_has_type "is/has/about" because it's mapped to P2_has_type of the object
    • BM Ware and BM Currency are searchable using the same FR because they are sub-properties of P2_has_type
    • BM Aspect is not searchable because it's P2_has_type of E55_Type of a E25 Man-Made Feature on the object (side of coin)
    • If IPTC code is similar to "subject", it should be searchable
    • BM Unit and BM Dimension are not searchable because they are attributes of a Dimension of the object, and there's no FR defined for dimensions
    • BM Place is searchable, even in a hierarchical way
    • BM Place Type (town, village) and BM Place Name Type (modern, archaic) are not searchable because FRs don't reach into the properties of a place
  • Taggable: whether the thesaurus is "interesting enough" to be used as a source of tags. Tags are general categories to be used for categorization of research questions and comments. See Tags Spec

Term Distribution

  • Yale: 99% of Yale terms come from TGN, AAT, and ULAN.
    1% of terms come from ODNB, IconClass, YCBA Local terms (Frames, ...)
    • Vlado: AAT surely has Frames?
  • Yale: example of a lesser known person (Elihu Yale) who's found in ODNB, VIAF, DBPedia but not ULAN:
    • Vlado: such "local heros" are a typical pattern for any museum. BM People also has "local heros" that are not found in ULAN.
  • Lec: will it be helpful if we make connections to ODNB, VIAF, DBPedia?
    • Vlado: yes, assuming you can easily export such term data according to Thesaurus Requirements. If you source it from these external sources, you'd need to make the same SKOS & CRM mapping as for the rest, and register in the Meta-Thesaurus.
      If these are indeed less than 1%, I'd source them from a single thesaurus YCBA Local.

There will be a meeting at Getty in September 2013, with 1/2 day discussion on Vocabularies


  • remove crm:E55_Type: a Group is not a Type
    <thesauri/nationality/British> a crm:E55_Type , crm:E74_Group , skos:Concept ;
  • SKOS says one prefLabel (per language). If you don't have a flag in TMS, call the first one prefLabel and the rest altLabel
    <person-institution/142> a crm:E21_Person , skos:Concept ;
    	skos:inScheme ycba:person-institution ;
    	skos:prefLabel "Robert Smirke I" , "Robert Smirke R. A." , "Robert Smirk" , "Robert I Smirke" , "Robert Smirke" ;
  • you don't have any date (P82_at_some_time_within) for <person-institution/142/birth/date>. This makes all the following statements useless, so kill them.
    	crm:P92i_was_brought_into_existence_by <person-institution/142/birth> ;
    <person-institution/142/birth> a crm:E63_Beginning_of_Existence ;
    	crm:P4_has_time-span <person-institution/142/birth/date>
    • Same for death
  • If you know whether it's a person or institution then use the respective specific subprop & subclass instead of the generic P92i, E63:
    Person: P98i_was_born, E67_Birth
    Group: P95i_was_formed_by, E66_Formation

Lec: we have more variety in Person dates.

Thesaurus URIs

  • Use more logical URIs that reflect the nature of the resource or type, and don't reflect their genesis in existing systems:
    <thesauri/event/exhibition_history> -> <thesauri/event/exhibition> (an exhibition is NOT "exhibition history")
    <event/some-exhibition/TMS/exhibition_history> -> <event/some-exhibition/identifier> (an identifier is NOT "exhibition history")
    <thesauri/identifier/TMS/exhibition_history> -> <thesauri/identifier/exhibition> (doesn't matter your system is called TMS)

    Lec: this may need further discussion, we may have other types of events with IDs from other systems, however made changes per suggestion
    Vlado: you have a point. If you have 2 exhibition IDs then you need to add the system acronym

Exhibition URIs

  • We need to make decision on URI for exhibition, originally we had a short identifier, BM suggested title, this does not always work well, eg see: ObjectID 34
  • Vlado: Yes, pretty long titles in
    Exhibition :: An American's Passion for British Art - Paul Mellon's Legacy, 2007-2008
    Exhibition :: Great British Paintings from American Collections: Holbein to Hockney, Thursday, September 27, 2001 - Sunday, December 30, 2001
    Exhibition :: J. M. W. Turner - A Selection of Paintings from the Collection of Mr. and Mrs. Paul Mellon, 1968-1969
  • RS doesn't care what the URI is

Getty URIs



  • Why do you need these duplicate types?
    crm:P2_has_type <thesaurus/title/Alternate-title> , <thesaurus/title/alternate> .
  • I'm not sure what "Repository title" is. But if it means Preferred, then this is also unnecessary duplication:
    crm:P2_has_type <thesaurus/title/Repository-title> , <thesaurus/title/preferred> .

    Emmanuelle to clarify.
    EDG: the capitalized title types (Repository, Alternate, Verso,...) talk about the purpose of the titles, not their ranking.  The 2 other title attributes (alternate and preferred) talk about the ranking/preference of the titles.
    Can an object have different Repository title and Preferred title?
    EDG: no, all Repository titles are always the preferred ones.  But all alternate titles are not of the type Alternate.  Here are all the types possible: Alternate title, Collective title, Creator's title, Exhibited title, Foreign language title, Former title, Inscribed title, Repository, Verso title.

  • these two titles are duplicated. Keep just one of them: I suggest <title/1> for uniformity with the alternate title(s)
    <object/19850/title/1> a crm:E35_Title ;
      rdfs:label "Malvolio Dancing" ;
      crm:P2_has_type <thesaurus/title/Repository-title> , <thesaurus/title/preferred> .
    <object/19850/title/primary> a crm:E35_Title ;
      rdfs:label "Malvolio Dancing" ;
      crm:P2_has_type <thesaurus/title/Repository-title> , <thesaurus/title/preferred> .
  • (optional) Indicate the title language:
    <object/19850/title/1> a crm:E35_Title ;
      rdfs:label "Malvolio Dancing"@en ;
      P72_has_language <thesaurus/language/english>.

    Emmanuelle: we indicate the language of the titles only if they are in foreign language <thesaurus/title/ForeignLanguage-title>, and probably not consistently.  All the other titles are understood as being in American English, the official language of the YCBA.


  • The YCBA director does not want to publish which person gave up the object.
    Maybe if the person has passed, that can be exported. Emmanuelle to clarify.

Emmanuelle''s answer:  Right now, we absolutely cannot publish who were the previous owners of our objects, no matter if they have passed or not.  

<object/19850/acquisition> a crm:E10_Transfer_of_Custody , crm:E8_Acquisition ;
  crm:P22_transferred_title_to <thesauri/ULAN/500303557> ;
  crm:P29_custody_received_by <thesauri/ULAN/500303557> ;
  rdfs:label "Yale Center for British Art, Paul Mellon Collection" .
  • format the label as "Transferred to ..." (now it reads as an Agent, not as a Transfer)
  • If YCBA is incorporated, use E40_Legal_Body instead of the more generic E74_Group:
     <thesauri/ULAN/500303557> a crm:E74_Group , skos:Concept ; skos:prefLabel "Yale Center for British Art" . 
  • The acquisition label (and the Credit Line facet here) show that there are several sub-agents (or sub-colletions) under it: Paul Mellon Collection, Paul Mellon Fund, Gift of Mr. and Mrs. J. Richardson Dilworth, B.A. 1938.
    If it's important to preserve this information in RDF, you could create sub-agents under YCBA, eg like this:
    <person-institution/ycba_mellon_collection> a E74_Group, skos:Concept;
      skos:inScheme <person-institution/>; rdfs:label "Yale Center for British Art, Paul Mellon Collection" ;
      skos:broader ulan:500303557; P107i_is_current_or_former_member_of ulan:500303557 .
    <person-institution/ycba_dilworth_gift> a E74_Group, skos:Concept;
      skos:inScheme <person-institution/>; rdfs:label "Yale Center for British Art, Gift of Mr. and Mrs. J. Richardson Dilworth, B.A. 1938" ;
      skos:broader ulan:500303557; P107i_is_current_or_former_member_of ulan:500303557 .


  • this was wrong, see image_objects_carriers@crmg
    <object/7> P62_depicts <object/7/image/1>

    The correct one is:

    <object/7> P65_shows_visual_item <object/7/image/1>

    Explanation: an E24_Physical_Man-Made_Thing P128_carries an E73_Information_Object. In the particular case of E38_Image, we say E24_Physical_Man-Made_Thing P65_shows_visual_item E38_Image

  • this is wrong
    <object/7/image/1> P108i_was_produced_by <object/7/image/1/creation>.   # images are conceptual, so use P94i_was_created_by
    <object/7/image/1/creation> P14_carried_out_by <object/thesauri/actor>; # by WHOM?! If you have no info, don't output Creation
      rdf:type crm:E12_Production.                                          # E12_Produciton is for material objects
    • Emmanuelle: I was trying to express the fact that the image is supplied/was made by YCBA, hence P108i_was_produced_by.
    • Vladimir: ok, but use the correct type and properties for Image (a conceptual object), and YCBA's URL:
      <object/7/image/1> P94i_was_created_by <object/7/image/1/creation>.
      <object/7/image/1/creation> P14_carried_out_by <thesauri/ULAN/500303557>;
        rdf:type crm:E65_Creation.

      Emmanuelle to Vladimir:  I had originally used P94i in my original modeling but then changed it because we are talking about a physical/digital image. So ok, good to go with P94i.

Image Views

RKD has the following image views (in separate thesauri):

  • area captured: overall, detail, from left, from bottom...
  • side captured: front, back
  • object status: before treatment, during treatment, after treatment
  • documentation type: X-ray film, action photograph, black and white detail photograph, black and white photograph, color transparency etc

(BM doesn't have such notions.)

Yale has similar notions. Our lovely Miss Prue has 8 images:

  • cropped to image, recto, unframed
  • recto, unframed
  • framed, recto
  • framed, verso
  • detail, recto
  • detail, recto
  • Composite X-radiograph
  • cropped to image, recto, unframed

Yale needs to represent this. For now I think it's enough to lump them in one thesaurus, eg:

  PX_has_main_representation <>.
  P2_has_type <yale/thes/image/kind/cropped_to_image>, <yale/thes/image/kind/recto>, <yale/thes/image/kind/unframed>.

All Image Sizes

format/1: thimbnail (for result list)
format/2: large (for lightbox)
format/3: full screen (1920)
format/6: for publication (3000)
format/7: deep zoom JPEG2000 (eg 4492)

Deep Zoom images

TODO Vlado

Image Rights

  • This says nothing (has no fields)
    <object/7/image/1> P104_is_subject_to
  • this has the following problems:
    <object/7/image/1> P70i_is_documented_in <object/7/image/1/terms_of_use>.  # 1. should be P104_is_subject_to
    <object/7/image/1/terms_of_use>                     # 2. it's not specific to this image, so don't use per-image node
      rdfs:label ""; # 3. should be URI not string, 4. this redirects, so just use the final destination
      rdf:type crm:E62_String.                          # 5. means nothing. So-called "CRM Primitive types" should not be used
    • so simply use this:
      <object/7/image/1> P104_is_subject_to <>. # 6
      <object/5054/image/1> P104_is_subject_to <>. # 7
      <>    a E30_Right; rdfs:label "Public Domain".
      <> a E30_Right; rdfs:label "Under Copyright: © Estate of the Artist".
    • 8. better yet, use CreativeCommons URIs, since CC is a stronger authority about rights than YCBA.
      But this is optional: if YCBA has defined 15 different rights, it won't be easy to match them to CC URIs.


  • Emmanuelle: I have some contextual information regarding my modeling for image rights that might help, since we are doing things a bit differently from the BM on this I believe.
    • Vladimir: indeed, BM claims rights (eg images\assets_0.trig):
        crm:P138i_has_representation <>.
        crm:P105_right_held_by thesIdentifier:the-british-museum.
  • Emmanuelle: YCBA does not claim rights over images, just points to image use page, hence P70i_is_documented_in rather than P104_is_subject_to. YCBA does not say who owns the image rights.
    • Vladimir: My example above (6) says the image P104_is_subject_to a Rights object, which allows unrestricted usage. See the scope note to be convinced this is the right class to use: "This class comprises legal privileges concerning material and immaterial things". It doesn't say YCBA holds any rights.
    • For (7) it would be nice to compute the actual holder of rights and state P105_right_held_by but that's not easy
  • Emmanuelle: OK, i see that P104_is_subject_to is good even when no image restrictions apply.  Then let's use P104_is_subject_to 

Object Rights


  • P30_transferred_custody_of is wrong direction
    Lec: Replaced with P30i_custody_transferred_through


  • useless intermediate node
    • just use
      <object/20049> P129_is_about <>,
                 <>. # etc
  • if you can't find a term during mapping, report an error, don't export it as "-1"
    Lec: Emmanuelle, please have some students go through TMS, I exclude now anything that has -1
  • Lec: Emmanuelle there are cases where subjects are TGN where conceptID = 0, I will try to ignore. Example ObjectID = 34


When and why to use <obj/production/M/association> a ycba:EX_Association
That's defined by the specific sections in BM Association Mapping v2. The Intro section describes 3 patterns: code in Event, code in Subevent, code in Association, and the specific sections say which to use for which part of your data

  • No point using BOTH Subevents (parts) and EX_Association

Produced By Specific Process

What do I do for the following crm:P14_carried_out_by association codes? Do they become types or labels?
These are all types of Production sub-events, because they pertain to the nature of the production process. See BM Association Mapping v2#Produced By Specific Process for the pattern:

  • AR-Artist
  • AU-author
  • FB-finished by
  • M-maker
  • R-printer (printed by)
  • PM-printmaker (print made by)
  • Z-publisher (published by)
  • TU-touched up by (print)

BTW: if you have just 1 code, it would be nice to optimize and not create sub-events, but BM doesn't do that

Unknown Artist

Some records say "production performed by Unknown Artist".

  • Lec: removed unknown artists, this will need to be communicated with Emmanuelle, she has some reservations about it. In effort to get our data to work with RS I made the change.
  • Vladimir's considerations:
    • RS is agnostic about this
    • CONS: If you say 10 paintings are made by Unknown Artist and use the same term, that's false because they may have been made by different people.
    • CONS: The sem web way of expressing that some info is missing is simply NOT to say anything.
    • PRO: if you want to search in RS for "paintings with Unknown creator", you can do it when mapped to an Unknown person or Unknown group. But you cannot currently search for "paintings that don't have creator info"
  • Ken: Interesting conundrum about "Unknown" but it seems to be exactly as we know the world in traditional data. If one searches simply for Unknown, one does get everything Unknown, and we realize the works are not all by the same maker and that isn't a problem because we understand that Unknown is a class not an individual.
  • Dominic: I am not sure that a person URI should refer to a generic 'unknown' which would be the same unknown person. Generally, if something is unknown it shouldn't have a triple. The absence of a triple means that it is not known. Producing triples that state a null doesn't seem useful. Is there a particular reason for specifically stating that an artist is unknown? A query for an object created in the 18th century, in the french style and that was produced by the technique of sculpting would return the result in the example. Further, if the person was unknown then you couldn't assume that s/he was French. In other words if there is a way to query to get the result required without a null then this seems preferable.
  • Emmanuelle: I agree with Ken. 'Unknown creator' for an art historian carries meaningful information. It is not synonym with a null value (of course since all works of art have creators). Rather it means that the attribution research has not come up with conclusive information for now, and that situation can last for many years even centuries.
  • Ken: Such a search however is usually combined with limiting qualifiers like "Unknown French 18th-century sculptor." Being unable to search in that fashion seems to me the much more limited option.
  • Vladimir: You can express "French" and "Sculptor". Here's how the BM thesauri are modeled:
      a crm:E21_Person, skos:Concept;
      skos:inScheme id:person-institution;
      skos:prefLabel "Alfonso Ruspagiari";
      bmo:PX_gender <>;
      bmo:PX_nationality <>;
      bmo:PX_profession <>.

    Nationality and Profession are modeled as Groups (Gender is not, it's merely a Type):

      bmo:PX_gender rdfs:subPropertyOf crm:P2_has_type .
      bmo:PX_nationality rdfs:subPropertyOf crm:P107i_is_current_or_former_member_of .
      bmo:PX_profession rdfs:subPropertyOf crm:P107i_is_current_or_former_member_of .

    In RS the search relation (FR) "created by" is transitive over P107i_is_current_or_former_member_of.
    So if you search by "French" or "scupltor" you'll find objects created by the respective nationality or profession.
    If the artist is unknown, you can still say that the E74_Group "French" and the E74_Group "scupltor" P14i_performed the Production, and the same searches will work.

  • Vladimir: As for "18th century": RS cannot currently search by dates of the creator (life and flourit), but it can search by creation dates, which I think is "close enough".

Closely Related Group

  • Emmanuelle: I think it would make sense to model 'unknown artist' as a group because it is a denomination that actually contains many different entities (all unknown artists are not the same), and also because traditionally when we speak we create a short cut but we actually cannot be sure that 'unknown artist' is only one artist for a work of art.
    • The National Gallery has grappled with this as well and models 'Unknown Artist' as a sub-group of E74:
      The production of a particular painting (E84) was carried out by an Unknown Artist (E21) who was known to be part of the EN41.Artist_Sub_Group of a known/individually defined Master (E21)
    • I have represented this logic in the attached graph. On the model of the NG I have also moved Circle of, Studio of and Workshop of to be Production association codes for E74_Group.
      YCBA Production2 unknown creator.pdf
      viewpdf: The viewfile macro is unable to locate the attachment "YCBA Production2 unknown creator.pdf" on this page
  • Vlado: this closely follows BM Association Mapping v2#Production by Closely Related Group, and it's more faithful modeling than before. But it has implications for Search that need to be discussed with BM.
    Need to track the discussion at BM Association Mapping Problems#Closely Related Group.
  • Vlado: not all these codes are the same, and they map to different CRM constructs. I would group the NG codes as follows:
  • Some of these are subject to debate. Eg BM mapped two codes that sound similar to me onto different patterms:
    AJ: Circle/School of: BM Association Mapping v2#Production by Closely Related Group
    S: School of/style of BM Association Mapping v2#Influenced By
  • Ken: Interesting conundrum about "Unknown" but it seems to be exactly as we know the world in traditional data. If one searches simply for Unknown, one does get everything Unknown, and we realize the works are not all by the same maker and that isn't a problem because we understand that Unknown is a class not an individual.
    • Vlado: That's ok for this search case, as used by a person. But still there's a falsehood in the RDF, that all these paintings are by the same person. If you want to e.g. investigate painting similarity, this will trip you up. IMHO to avoid spurious unification, an Unknown should not be a known term or URI. Could be a blank (URI-less) node, which is by definition unique.
  • Emmanuelle: traditionally when we speak we create a short cut but we actually cannot be sure that 'unknown artist' is only one artist for a work of art.
    • Vlado: Exactly!
  • Vlado: seems to me there are different degrees of unknown that may need different modeling, e.g.:
    1. has 2 records:
        <object/7/production/1> crm:P14_carried_out_by <id/person-institution/1180> . # Production by :: Formerly attributed to Benjamin Williams Leader
        <object/7/production/3> crm:P14_carried_out_by <unknown> .

      This says there were 2 painters, one is B.W.Leader and the other Unknown: which does not reflect the actual situation (there is 1 painter!)
      Note: We should qualify production/1 with an EX_Association having type "unlikely/formerly-attributed-to" (this is described well at the page BM Association Mapping v2

    2. In another case there may be actual evidence of 2 producers (e.g. Rembrandt and someone unknown from his Workshop).
  • Vlado: The simplest solution could be to just mark with a flag "there's significant unknown info about the producer".

Curatorial Comment

  • Yale: PX_curatorial_comment needs date and author added to the data model
  • Vlado: this is clearly a case of EX_Association. It's is a subclass of E13_Attribute_Assignment, so see attribute_assignment@crmg and recorder@crmg:
      <obj> bmo:PX_curatorial_comment "comment".
      <obj/comment/1> a bmo:EX_Association;
        P140_assigned_attribute_to <obj>; P141_assigned "comment"; bmo:PX_property bmo:PX_curatorial_comment;
        P14_carried_out_by <researcher>;
        P4_has_time-span <obj/comment/1/date>.
      <obj/comment/1/date> P82_at_some_time_within "2013-07-06"^^xsd:gYear.
    • you could alternatively use P3_has_note instead of PX_curatorial_comment, to accommodate apps that know CRM and EX_Association but not PX_curatorial_comment. But I still think using the subproperty is better


I haven't seen any Inscription info in TTL. And in LIDO I see only empty XML tags for teh following types but without data:

Are there any objects with inscriptions for me to check?

Object Type and Genre

Object Type and Genre (lido:objectWorkType) are missing, eg

  • There is a term for the 1st but it's not connected to the object.
  • You try to make a term for the 3rd but seems look it up in the wrong thesaurus (it's local not AAT):
    <> a crm:E55_Type , skos:Concept ;
    	skos:inScheme <> ;
    	skos:prefLabel "architectural subject" .

I'd represent the first 2 as "type" and the last one as "subject":

  P2_has_type <>, # painting
    <>;           # landscape
  P62_depicts <>. # architectural subject

Note: BM has defined some subprops of P2_has_type: PX_object_type, PX_ware (for pottery), PX_escapement (for clocks). But so far I don't see a need to do this for Yale.

Current Owner, Keeper

This is probably wrong, it should describe the specific sub-organization (department):

  crm:P50_has_current_keeper <> ;

If you don't have departments in YCBA, just don't say anything about departments.

Current Location

You currently use per-object place representations. Such places are not searchable, and

<> a crm:E53_Place ;
	rdfs:label "Bay25" . # UnitType
<> a crm:E53_Place ;
	rdfs:label "401" .   # SubSite
<> a crm:E53_Place ;
	rdfs:label "Yale Center for British Art" . # Site
<> a crm:E53_Place ;
	rdfs:label "New Haven" .  # Geo location


  • it probably doesn't make sense to put location/1 and location/2 in a thesaurus, so they are correctly per-object. But add something to the label to explain what they mean. If there's a hierarchy between them and the coding won't get too complicated, something like this could be best:
      rdfs:label "Storage unit: Bay25, shelf: 401"
  • location/3: YCBA is an organization. Here you mean "the place of that org", which is a known conundrum. Since you already say "YCBA is current owner/keeper", just skip
  • location/4: A city is a well-known place, so just use the respective TGN URI


You state object dimensions (including their properties):

	crm:P43_has_dimension <> ;
	crm:P43_has_dimension <> ;

But you omit lido:extentMeasurements, i.e. don't state what was measured:

If you have data with lido:qualifierMeasurements, we should also consider it

You can add it like this:

  P39i_was_measured_by <>.
<> a E16_Measurement ;
  P40_observed_dimension <> ,
    <> ;
  rdfs:label "12 1/16 x 16 inches (30.6 x 40.6 cm). Extent: Support (PTG)" .

If "Support (PTG)" is a controlled value, you better make a thesaurus for it and we'll figure how to attach it with P2_has_type.


Page numbers, eg for

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.