View Source

Source LIDO + OAI-PMH Example:
* [^oai-tms.ycba.yale.edu-499.xml]
* [^oai-tms.ycba.yale.edu-757.xml]

RDF + CRM Examples:

* [http://collection.britishart.yale.edu/id/page/object/499|http://collection.britishart.yale.edu/id/page/object/499]
* [http://collection.britishart.yale.edu/id/page/object/757|http://collection.britishart.yale.edu/id/page/object/757]

h2. General

based on a *cursory* examination of oai_tms.ycba.yale.edu_499.rdf sent by [~lec.maj@yale.edu] on 9 May 2012.
Many of the fragments below are TTL, I've converted it to Turtle using [http://any23.org]
- {color:#993300}Why do we use double colon :: in the rdfs:label and P3_has_note? Do we need to for indexing in Lucene? {color}
- should use {{crm:P3_has_note}} vs {{rdfs:label}} more consistently
-* {color:#993300}Looks like we use has_note, rdfs:label, and skos:prefLabel \-\- I tried to define when to use which, is this correct?{color}\-*\** {color:#993300}{*}rdfs:label \-- *{color}{color:#993300}{*}primary representation ie; title, artist name{*}{color}*\-*\* {color:#993300}P3_has_note \-\- s{color}{color:#993300}econdary display{color}{color:#993300} ie; dimensions{color}\-** {color:#993300}skos:prefLabel \-\- ??{color}
-  

h2. Object - work of art ? (identifier = Object ID, Location, Title, Credit Line, Dimensions, Current Repository (building physical and legal custody keeper), Department (association?)

- re [http://collection.britishart.yale.edu/id/tgn/7008591/coordinates]
-- -skos:inScheme ycba_tgn:local : that's not a term value, so it should not be inScheme-
--* {color:#993300}I removed all the skos:inScheme that have: local{color}
-- -a crm:E47_Spacial_Coordinates : misspelt-
-- crm:P90_has_value "54.0000, \-4.5000" : better express this in a structured way.
-- You may want to consider the paper [Integration of Coordinate Information in CIDOC CRM|http://lists.ics.forth.gr/pipermail/crm-sig/attachments/20111107/f2d15017/attachment-0001.pdf]
--* {color:#993300}I represented this based on how Barry suggested using wgs84, awaiting some modification to RDFer for parsing lat,long into separate fields. Please take a look to see if I am missing anything: {color}[http://collection.britishart.yale.edu/id/tgn/7002445/location]
- <[http://collection.britishart.yale.edu/id/object/499/dimension]> a crm:E54_Dimension
I can see the DisplayWrap&nbsp;{{crm:P3_has_note "78 1/4 x 48 1/8 inches (198.8 x 122.2 cm)"}}
-but should also be represented in a structured way (with two dimension nodes: object/499/width and object/499/height)-
- {color:#993300}I represented this the way that BM has done now, crm:E54_Dimension is gone, so this does not have the&nbsp;{color}{color:#881280}lido:displayObjectMeasurements{color}&nbsp;{color:#993300}and&nbsp;{color}{color:#881280}lido:extentMeasurements.&nbsp;{color}{color:#993300}Do we agree to add crm:E54_Dimension to both as I had before with the structured way for width and height?{color}

- -[http://collection.britishart.yale.edu/id/thesaurus/indetifier/inventory-number:]-&nbsp;-misspelled-
-- This causes an invalid URI&nbsp;{{<crm:E55_Type>}}&nbsp;(prefixed yet enclosed in angle brackets)
{code:xml}<rdf:Description rdf:about="http://collection.britishart.yale.edu/id/thesaurus/indetifier/inventory-number">
<rdf:type rdf:resource="crm:E55_Type" />
</rdf:Description>{code}
- This causes a blank node that is not connected to anything (same for other legal bodies)[http://collection.britishart.yale.edu/id/legal_body/500303557]
{code:xml}<crm:P1_is_identified_by rdf:resource="500303557" />{code}

h2. documented (images, lido ID - admin data?), rights to object, rights to images of object, link to web page, )

\-\-

h2. Subject Terms (is_about) - geographical (tgn) or concepts (aat concepts can be keywords or people)

This is definitely not E55_Type
{code}
<http://collection.britishart.yale.edu/id/aat/22>
a crm:E55_Type , skos:Concept ; 
a crm:E4_Period ;
skos:inScheme ycba_aat:Period ; 
skos:prefLabel "18th century"{code}
- I think this is better mapped to E52_Time-Span since it's not a cultural period and has only a time aspect
- Consider using the excellent work on&nbsp;[Handling Time Periods in STAR|http://hypermedia.research.glam.ac.uk/kos/star/time-periods/]&nbsp;to assign actual dates to such time-spans, using the label
- {color:#993300}I already have time span defined with actual dates, the period is to provide label, if there is something else I need to do please let me know. I removed E55_Type.&nbsp;{color}
- {color:#993300}Production&nbsp;dates:&nbsp;{color}[http://collection.britishart.yale.edu/id/page/object/499/production/date|http://collection.britishart.yale.edu/id/page/object/499/production/date]
- {color:#993300}Period&nbsp;{color}[http://collection.britishart.yale.edu/id/page/getty/aat/300111159|http://collection.britishart.yale.edu/id/page/getty/aat/300111159]
- &nbsp;

- This is neither E55_Type nor E74_Group. It's a&nbsp;[E4_Period@crm]&nbsp;(see the Scope Note)
{code}<http://collection.britishart.yale.edu/id/getty/aat/300111159>
a crm:E55_Type , skos:Concept ; 
a crm:E74_Group ;
skos:inScheme aat:Culture ;  
skos:prefLabel "British"{code}
-- (!) &nbsp;See&nbsp;[BMX Issues#Theaurus Requirements]&nbsp;for more guidelines
-- {color:#993300}Looking at the requirements and notes between Ontotext and BM, I am confused as to what is the agreed solution.&nbsp;{color}
-- {color:#993300}Do I need anything else? I now have:{color}
-- {code}
<http://collection.britishart.yale.edu/id/getty/aat/300111159>
a crm:E4_Period ;a rdfs:label "British" ;a skos:inScheme aat:Culture
{code}
- &nbsp;



h2. Events


h4. Creation (Production)

\-\- creator

\-\- medium&nbsp;

\-\- support

\-\- technique

\-\- date of creation

\-\- culture

In this below the Medium (technique) is mapped ok, but Support should be mapped to E57_Material and you should attach it with&nbsp;{{crm:P45_consists_of}}&nbsp;and&nbsp;{{crm:P126_employed}}. See&nbsp;[Material and Medium-Technique|Material and Medium-Technique]&nbsp;for details
{code}
<http://collection.britishart.yale.edu/id/object/499/production> a crm:E12_Production ;
crm:P32_used_general_technique <http://collection.britishart.yale.edu/id/getty/aat/14078> ,
<http://collection.britishart.yale.edu/id/getty/aat/230810> .
<http://collection.britishart.yale.edu/id/getty/aat/14078> a crm:E55_Type , skos:Concept ;
skos:inScheme aat:support ; skos:prefLabel "canvas" .
<http://collection.britishart.yale.edu/id/getty/aat/230810> a crm:E55_Type , skos:Concept ;
skos:inScheme aat:medium ; skos:prefLabel "oil paint" .
{code}\*&nbsp;{color:#993300}Another quick look at this to make sure I setup Support correctly:{color}&nbsp;[http://collection.britishart.yale.edu/id/page/getty/aat/14078|http://collection.britishart.yale.edu/id/page/getty/aat/14078]
- crm:P82a_end_of_the_end "1752" : misspelt, that's P82b.
- -Also, you better put a type{-}{code}"1752"^^xsd:gYear{code}
{color:#993300}Production Date looks a bit different for YCBA and BM, we use&nbsp;{color}[P4_has_time-span|http://erlangen-crm.org/current/P4_has_time-span]{color:#993300}&nbsp;BM does not. Here is my example:&nbsp;{color}[http://collection.britishart.yale.edu/id/object/499/production|http://collection.britishart.yale.edu/id/page/object/499/production]

h4. Provenance

Currently big block of text represented as PX3_provenance

h4. Exhibition History&nbsp;

Currently only title of exhibition, comma&nbsp;separated, date (YYYY format). We also have the unique exhibition ID that is part of the URI. We model conceptID terms&nbsp;separately&nbsp;under subject terms, is this correct?&nbsp;

LIDO

{code}
<lido:eventSet>
<lido:displayEvent>Connections, 2011</lido:displayEvent>
<lido:event>
<lido:eventID lido:type="TMS">757</lido:eventID>
<lido:eventType>
<lido:conceptID lido:source="AAT" lido:type="LIDO">300054766</lido:conceptID>
<lido:term>exhibition history</lido:term>
</lido:eventType>
</lido:event>
</lido:eventSet>
{code}
RDF
{code}
<http://collection.britishart.yale.edu/id/exhibition/389> 
a crm:E7_Activity ;
crm:P3_has_note "Francis Hayman, 1987" .
{code}


h4. Publication

We have a text entry for bibliographic entry and plan to add URI to OCLC WorldCat and Google Books (at some point once these provide linked data, it will be all linked). As above term and concept ID is under subject terms.&nbsp;

LIDO

{code}
<lido:eventSet>
<lido:displayEvent>
J. H. Plumb, The pursuit of happiness, a view of life in Georgian England : an exhibition selected from the Paul Mellon collection, Yale Center for British Art, New Haven, 1977, pp. 45, 97, no. 67, N6766 Y34 1977 (YCBA)
</lido:displayEvent>
<lido:event>
<lido:eventID lido:type="TMS">191</lido:eventID>
<lido:eventType>
<lido:conceptID lido:source="AAT" lido:type="LIDO">300111999</lido:conceptID>
<lido:term>publication</lido:term>
</lido:eventType>
</lido:event>
</lido:eventSet>
{code}
RDF

{code}

{code}

h4. Acquisition \-&nbsp;\[TBD\]

\-\-

h4. Framing History (part addition) - \[TBD\]

\-\-

h4. Conservation (modification) - \[TBD\]

\-\-
----