compared with
Current by Vladimir Alexiev
on Jul 16, 2014 10:32.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (29)

View Page History
h3. Meta-Thesaurus

(-) Each (+)  Each thesaurus (ConceptScheme) used by Yale must be described in [Meta-Thesaurus and FR Names#YCBA Thesauri|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.
There's a long list of bugs (currently in email), some are added below.
- Your thesaurus URIs must match those used in instance data, else things won’t mesh. E.g. in meta you’ve used thesauri/aspect. But the Turtle examples in my page, and Daniel’s RDF files about images, use thesauri/image/flag. If you prefer, call it thesauri/image/aspect, but then edit my examples and Daniel’s conversion to use that same ConceptScheme.

| *Meta ConceptScheme* | *comment* |
| [http://collection.britishart.yale.edu/id/thesauri/activity/|http://collection.britishart.yale.edu/id/thesauri/activity/]\\ | |
| [http://collection.britishart.yale.edu/id/thesauri/group/|http://collection.britishart.yale.edu/id/thesauri/group/]\\ | |
| [http://collection.britishart.yale.edu/id/thesauri/image/flag/] | |
| [http://collection.britishart.yale.edu/id/thesauri/person-institution/]\\ | |
| [http://collection.britishart.yale.edu/id/thesauri/authority/] | What's its relation to /production |
If you're on linux you got these tools. If you're on Windows, install [http://cygwin.org].

(-) The (+)  The current list of Concept Schemes in instances is below. Resolve it against meta:
- Schemes in instances but not in meta: are undefined
- Schemes in meta but not in instances: are either useless, or indicate a defect in instance mapping (scheme is not specified).
| [http://collection.britishart.yale.edu/id/thesauri/place] | ok |
| [http://collection.britishart.yale.edu/id/thesauri/subject/] | ok |
| vocab.getty.edu/aat/periods \\ \\
 [http://collection.britishart.yale.edu/id/thesauri/periods/] | nok: see [#AAT Concept Schemes] \- done  Also, thesauri/periods/ needs to be mapped to '16th century' like values (not AAT terms) |
| -ycba:person-institution- \\
[http://collection.britishart.yale.edu/id/thesauri/person-institution/|http://collection.britishart.yale.edu/id/thesauri/person-institution/]\\ | |
| [http://collection.britishart.yale.edu/id/thesauri/periods/] | For '16th century', ... |
| [http://collection.britishart.yale.edu/id/thesauri/person-institution/|http://collection.britishart.yale.edu/id/thesauri/person-institution/] | |
| [http://collection.britishart.yale.edu/id/thesauri/authority/|http://collection.britishart.yale.edu/id/thesauri/authority/]\\ | commissioned by: CO |
| [http://collection.britishart.yale.edu/id/thesauri/department/|http://collection.britishart.yale.edu/id/thesauri/department/]\\ | |
| [http://collection.britishart.yale.edu/id/thesauri/collection/]\\ | used to be thesauri/department/ |
| [http://collection.britishart.yale.edu/id/thesauri/dimension/|http://collection.britishart.yale.edu/id/thesauri/dimension/]\\ | |
| [http://collection.britishart.yale.edu/id/thesauri/extent/|http://collection.britishart.yale.edu/id/thesauri/extent/]\\ | |
| [http://vocab.getty.edu/ulan/|http://vocab.getty.edu/ulan/]\\ | |
| [http://vocab.getty.edu/tgn/|http://vocab.getty.edu/tgn/]\\ | |
| [http://vocab.getty.edu/aat/300264088]\\ | AAT Styles and Periods Facet: British, American, etc |
| [http://vocab.getty.edu/aat/300264088/]\\ [http://vocab.getty.edu/aat/300264090]\\ | |
| [http://vocab.getty.edu/aat/300264090/]\\ [http://vocab.getty.edu/aat/300264091]\\ | |
| [http://vocab.getty.edu/aat/300264091/]\\ [http://vocab.getty.edu/aat/300000000]\\ | |
| [http://vocab.getty.edu/aat/300000000/]\\ | |
| [http://collection.britishart.yale.edu/id/thesauri/production/|http://collection.britishart.yale.edu/id/thesauri/production/]\\ | |
| [http://collection.britishart.yale.edu/id/thesauri/technique/|http://collection.britishart.yale.edu/id/thesauri/technique/]\\ | |
This URL doesn't return anything, but you can append parameters to get what you need.
- the tile URLs are of this form:
[http://scale.ydc2.yale.edu/iiif/1b747e8f-7754-482c-b5a2-9e1dc1986f4b/0,2048,1024,1024/\!256,256/0/native.jpg\|http://scale.ydc2.yale.edu/iiif/1b747e8f-7754-482c-b5a2-9e1dc1986f4b/0,2048,1024,1024/\!256,256/0/native.jpg|http://scale.ydc2.yale.edu/iiif/1b747e8f-7754-482c-b5a2-9e1dc1986f4b/0,2048,1024,1024/!256,256/0/native.jpg] [http://scale.ydc2.yale.edu/iiif/1b747e8f-7754-482c-b5a2-9e1dc1986f4b/0,2048,1024,1024/\!256,256/0/native.jpg|http://scale.ydc2.yale.edu/iiif/1b747e8f-7754-482c-b5a2-9e1dc1986f4b/0,2048,1024,1024/!256,256/0/native.jpg]
- If you request a non-existing GUID, you get "Error: No response from server [http://scale.ydc2.yale.edu/iiif]". Occasionally I get the same error for an existing GUID, but that is a temporary outage
- another client that also implements IIIF tiles is OpenSeadragon (and one can get sample code to implement the same):
Image Views are different photographs of the same painting, using different Flags.
Eg the lovely Miss Prue [http://collections.britishart.yale.edu/vufind/Record/1669236] has 8 image views:
[^5005-images.html]
{html:script=^5005-images.html}{html} {html}

<table><tr>
<td valign="top"><img src="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0004-pub.tif/format/1"/><br/>cropped to image, recto, unframed<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0004-pub.tif/format/1">Screen small</a> (205x249)<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0004-pub.tif/format/2">Screen medium</a> (395x480)<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0004-pub.tif/format/3">Screen large</a> (1580x1920)<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0004-pub.tif/format/6">Print large</a> (2468x3000)<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0004-pub.tif/format/7">Zoom (JPEG 2000)</a> (4492x5460)<br/>
<td valign="top"><img src="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0004-bar.tif/format/1"/><br/>recto, unframed<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0004-bar.tif/format/1">Screen small</a> (169x249)<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0004-bar.tif/format/2">Screen medium</a> (325x480)<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0004-bar.tif/format/3">Screen large</a> (1300x1920)<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0004-bar.tif/format/4">Print small</a> (1016x1500)<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0004-bar.tif/format/5">Print medium</a> (1422x2100)<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0004-bar.tif/format/6">Print large</a> (2031x3000)<br/>
<td valign="top"><img src="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0002-pub.tif/format/1"/><br/>framed, recto<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0002-pub.tif/format/1">Screen small</a> (217x249)<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0002-pub.tif/format/2">Screen medium</a> (418x480)<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0002-pub.tif/format/3">Screen large</a> (1673x1920)<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0002-pub.tif/format/4">Print small</a> (1307x1500)<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0002-pub.tif/format/5">Print medium</a> (1830x2100)<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0002-pub.tif/format/6">Print large</a> (2614x3000)<br/>
<td valign="top"><img src="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0003-pub.tif/format/1"/><br/>framed, verso <br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0003-pub.tif/format/1">Screen small</a> (217x249)<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0003-pub.tif/format/2">Screen medium</a> (418x480)<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0003-pub.tif/format/3">Screen large</a> (1670x1920)<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0003-pub.tif/format/4">Print small</a> (1305x1500)<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0003-pub.tif/format/5">Print medium</a> (1826x2100)<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0003-pub.tif/format/6">Print large</a> (2609x3000)<br/>
<td valign="top"><img src="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0005-pub.tif/format/1"/><br/>detail, recto <br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0005-pub.tif/format/1">Screen small</a> (249x197)<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0005-pub.tif/format/2">Screen medium</a> (480x380)<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0005-pub.tif/format/3">Screen large</a> (1920x1519)<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0005-pub.tif/format/4">Print small</a> (1500x1187)<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0005-pub.tif/format/5">Print medium</a> (2100x1661)<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0005-pub.tif/format/6">Print large</a> (3000x2373)<br/>
<td valign="top"><img src="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-8001-mas.tif/format/1"/><br/>Composite X-radiograph<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-8001-mas.tif/format/1">Screen small</a> (209x249)<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-8001-mas.tif/format/2">Screen medium</a> (404x480)<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-8001-mas.tif/format/3">Screen large</a> (1614x1920)<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-8001-mas.tif/format/6">Print large</a> (2522x3000)<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-8001-mas.tif/format/7">Zoom (JPEG 2000)</a> (8016x9534)<br/>
<td valign="top"><img src="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0001-pub.tif/format/1"/><br/>cropped to image, recto, unframed<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0001-pub.tif/format/1">Screen small</a> (206x249)<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0001-pub.tif/format/2">Screen medium</a> (397x480)<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0001-pub.tif/format/3">Screen large</a> (1589x1920)<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0001-pub.tif/format/4">Print small</a> (1241x1500)<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0001-pub.tif/format/5">Print medium</a> (1737x2100)<br/><a href="http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-5005-0001-pub.tif/format/6">Print large</a> (2482x3000)<br/>
</tr></table>
{html}

RS should display something similar on the Related Images tab (but not laid out in such an ugly way): all views, one format as image, all formats as links. See [#Image Derivation] for the RDF data


Lec: these strings are not from a controlled thesaurus, so people can put anything.
Vlado: it still seems to me they are fairly consistent, so Yale could represent this by breaking on space and making a thesaurus:
For now I think it's enough to lump them in one thesaurus, eg:
{noformat}
See [BM Association Mapping v2#Probably/Unlikely Produced By]
- (?) What other lido:attributionQualifierActor have you got?
- (+) &nbsp;Emmanuelle: these are YCBA attribution qualifiers (also documented in&nbsp;[https://confluence.ontotext.com/display/ResearchSpace/Meta-Thesaurus+and+FR+Names&#124;../../../../../../../../../../display/ResearchSpace/Meta-Thesaurus+and+FR+Names&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;\||]&nbsp;as&nbsp;[http://collection.britishart.yale.edu/id/thesauri/likelihood|http://collection.britishart.yale.edu/id/thesauri/likelihood]):&nbsp;Attributed to, Formerly, Formerly attributed to, After, Follower of, Imitator of, Style of, Circle of, Studio of, Workshop of

h3. Production Qualification

Example: object/34466 is created "by unknown artist, 19th c.; after unknown artist."
In the current representation this maps to two production events using a single YCBA term. This is puzzling logically inconsistent (Unknown has influenced himself ;-) ):
- P14_carried_out_by <person-institution/616> and also
- P15_was_influenced_by the same <person-institution/616>

h3. Unknown Artist example
{jira:RS-1940}

Jana: These statements don't carry information and the birth/date dates are even wrong.
{noformat}
<http://collection.britishart.yale.edu/id/person-institution/616> a crm:E21_Person , skos:Concept ;
skos:inScheme ycba:person-institution ;
skos:altLabel "Unknown artist" ;
skos:prefLabel "unknown artist" ;
skos:altLabel "Unknown framemaker" , "Unknown rights holder" , "Unknown rights administrator" ;
crm:P98i_was_born <http://collection.britishart.yale.edu/id/person-institution/616/birth> ;
crm:P100i_died_in <http://collection.britishart.yale.edu/id/person-institution/616/death> ;
bmo:PX_gender <http://collection.britishart.yale.edu/id/thesauri/gender/unknown> .
<http://collection.britishart.yale.edu/id/person-institution/616/birth> a crm:E67_Birth ;
crm:P82_at_some_time_within <http://collection.britishart.yale.edu/id/person-institution/616/birth/date> .
<http://collection.britishart.yale.edu/id/person-institution/616/birth/date> a crm:E52_Time-Span ;
rdfs:label "0" ;
crm:P82a_begin_of_the_begin "0"^^xsd:gYear .
<http://collection.britishart.yale.edu/id/person-institution/616/death> a crm:E69_Death ;
crm:P82_at_some_time_within <http://collection.britishart.yale.edu/id/person-institution/616/death/date> .
<http://collection.britishart.yale.edu/id/person-institution/616/death/date> a crm:E52_Time-Span ;
rdfs:label "0" ;
crm:P82b_end_of_the_end "0"^^xsd:gYear .
{noformat}

Emmanuelle: Sorry to come back to this 'unknown' issue but if we don't emit 'unknown' creators as a group then works such as 4533 seem to have no creators since it is:
{noformat}
bmo:PX_display_wrap "Production by :: unknown artist" , "Production by :: After unknown artist"
{noformat}
This seems more wrong to me than modeling 'unknown' as a group?

Vlado: Not stating any facts about creators merely means that you don't know. It doesn't mean you assert there were no creators, due to semweb's Open World Assumption.
- Asserting that a single Unknown person created all these paintings is factually incorrect.
- Asserting he was born at year 0 is historically incorrect
Even if there was a year 0: I think that "0"^^xsd:gYear is invalid and will fail RDF validation.
- Asserting that he was influenced by (created them "After") himself is logically inconsistent.
- Asserting his gender is "unknown" is useless.

If you omit all these statements, you'd lose nothing, but gain correctness.

You and Ken described valid search use cases (see [#Closely Related Group], and we've postponed how to serve them.

Getty does have a bunch of unknown artists of *known* Nationality (e.g. Unknown Afghan).
But it's better to make a straightforward statement, and then you'd be able to search by nationality:
{noformat}
<object/4533/production> P14_carried_out_by <thesaurus/nationality/Afghan>.
{noformat}


h3. Closely Related Group



h2. Curatorial Comment

{color:#000000}{*}Curatorial Comment{*}{color}

- (-) Yale: PX_curatorial_comment needs date and author added to the data model
- {jira:RS-1926}
h2. Dimensions

{status:title=postponed\|color=blue}


You state object dimensions (including their properties):
{noformat}
{code}
- (?) If you have data with lido:qualifierMeasurements, we should also consider it
- (-) I &nbsp;I assume "Support (PTG)" is a (semi-)controlled value, so better make a term:
{noformat}
<http://collection.britishart.yale.edu/id/object/7>
h2. Object Type and Genre

&nbsp;(+) &nbsp;resolved issue



(-) Object Type and Genre (lido:objectWorkType) are missing, eg
{code:xml}
<lido:objectWorkType>
Which leaves me a bit puzzled how to map "classification": object type or "sub-collection".
- I wrote a little script to extract these 2 fields from Yale data:
{code:sh}{code}
{code:bash} egrep -A1 'type="(Classification|Object name)"' * | perl -pe "s{.*edu_(\d+).*?>([^<]*)(<.*)?}{$1: $2}" {code}
- For many Yale objects, objectWorkType and classification are the same (painting, scuplture, frame, etc)
- For some objects (4 of 13) there are differences: