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

Changes (164)

View Page History

h2. 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
Lec: We tried Eyeball, no luck have to contact dev community as we were not able to install it after number of tries. TBD..

h1. General Problems

h2. General
- (-) {status:title=low prio|color=gray} Pubby prefixes are not setup: shows "?:..."
Lec: does same for BM, will try to fix
Lec: BM has multiple, followed their lead
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
Lec: 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: this is *high priority* since RS cannot work with 3 sameAs URLs. And there's no good reason to publish your objects under 3 URLs: please explain why you want to do this
- (+) don't emit prefixes you don't need: lccn, oclc, ycba_aat, etc etc
TODO Vlado: write down appropriate representations

It's best to list all URLs closely related to each object, eg
[http://collection.britishart.yale.edu/id/object/5005]
"Mrs. Abington as Miss Prue in Love for Love by William Congreve":
Short: [http://www.google.com/culturalinstitute/asset-viewer/tQHBb0Q2MZF2uQ]
Long: [http://www.google.com/culturalinstitute/asset-viewer/mrs-abington-as-miss-prue-in-love-for-love-by-william-congreve/tQHBb0Q2MZF2uQ]
- (/) Pubby page. I don't think we need it since
[http://collection.britishart.yale.edu/id/page/object/5005]

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

h2. Local Terms
skos:prefLabel "Robert Smirke I" , "Robert Smirke R. A." , "Robert Smirk" , "Robert I Smirke" , "Robert Smirke" ;
{noformat}
Lec: Awaiting Emmanuelle confirmation if subjectActor will have multiple names, currently not in LIDO
Emmanuelle: yes a fair number of our subjectActor have alternate names in addition to their preferred names.
- (+) 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.
Lec: we now have P82 and are taking into account both person and groups

(+) Lec: we have more variety in Person dates. Emmanuelle to provide some more examples
- Some institutions have documented dates of existence: Published by Advanced Graphics London, 1969-present in [http://collection.britishart.yale.edu/id/page/object/48770]
- Creator that is an institution: Monro School (but no documented dates of existence in our system): [http://collection.britishart.yale.edu/id/page/object/5981]
- institution as Rights Administrator: Design and Artists Copyright Society in [http://collection.britishart.yale.edu/id/page/object/5054]
- Richard Wilson, 1712 or 1713-1782 in [http://collection.britishart.yale.edu/id/object/423]
- Damien Hirst, born 1965 in [http://collection.britishart.yale.edu/id/object/4908]
- John Samuel Agar, ca. 1770-after 1820 in [http://collection.britishart.yale.edu/id/page/object/26383]
- Print made by John Bruce, fl. 1826 in [http://collection.britishart.yale.edu/id/page/object/30564]


h2. 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 [http://collection.britishart.yale.edu/id/page/object/34].
{noformat}
{noformat}
- RS doesn't care what the URI is
- Lec: updated with standard ID based URIs

h3. Getty URIs
- Don't use YCBA-specific URIs for Getty, eg
[http://collection.britishart.yale.edu/id/thesauri/ULAN/500303557]
This won't let your data mesh with other data using Getty.
- (+) Use the official namespace that Getty just decided (20-Jun-2013)
[http://vocab.getty.edu]
Lec: ULAN, AAT, TGN converted to Getty URIs
[http://vocab.getty.edu/ulan/]

h2. Bibliography
- (-) Page numbers, eg for [http://collection.britishart.yale.edu/id/bibliography/2775]
- Vlado: BM uses [BIBO|http://bibotools.googlecode.com/svn/bibo-ontology/trunk/doc/index.html], for example see [http://test.researchspace.org:8081/resource?uri=http://collection.britishmuseum.org/id/bibliography/148].
But bibo:numPages is used wrongly, here should use bibo:pageStart and bibo:pageEnd for a continous page range. Or there's only one field, use bibo:pages

h1. Objects

{noformat}crm:P2_has_type <thesaurus/title/Repository-title> , <thesaurus/title/preferred> .{noformat}
- Emmanuelle: the capitalized title types talk about the purpose of the titles, not their ranking. Here are all title types possible: Alternate, Collective, Creator's, Exhibited, Foreign language, Former, Inscribed, Repository, Verso.
- Emmanuelle: The lowercase title attributes (alternate and preferred) talk about the ranking/preference of the titles.
- Can an object have different Repository title and Preferred title?
Emmanuelle: no, all Repository titles are always the preferred ones. But the alternate titles are not all of the type Alternate.
P72_has_language <thesaurus/language/english>.
{noformat}
- 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.
- (-) Vladimir: fair enough! So indicate language only for that type, and say it's translation of the Preferred one:
{noformat}
(Actually it's more likely this is the *original* title, so you may want to use P73_has_translation instead of P73i)

h2. Acquisition
- (+) The YCBA director does not want to publish which person gave up the object.
Emmanuelle: Right now, we absolutely cannot publish who were the previous owners of our objects, no matter if they have passed or not.
{noformat}
<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" .
{noformat}
- (-) 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:
{noformat} <thesauri/ULAN/500303557> a crm:E74_Group , skos:Concept ; skos:prefLabel "Yale Center for British Art" . {noformat}
- (?) The acquisition label (and the [Credit Line facet here|http://collections.britishart.yale.edu/vufind/Search/Results?join=AND&lookfor0%5B%5D=&type0%5B%5D=allfields&bool0%5B%5D=AND&lookfor1%5B%5D=&type1%5B%5D=title&bool1%5B%5D=AND&lookfor2%5B%5D=&type2%5B%5D=auth_author&bool2%5B%5D=AND&lookfor3%5B%5D=&type3%5B%5D=earliestDate&bool3%5B%5D=AND&lookfor4%5B%5D=&type4%5B%5D=topic&bool4%5B%5D=AND&lookfor5%5B%5D=&type5%5B%5D=geographic&bool5%5B%5D=AND]) 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:
{noformat}
<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 .
{noformat}

h2. Images
h3. Image Metadata
Yale keeps numerous image assets, and Yale ODAI provides extensive metadata about the images:
- documentation: [https://sites.google.com/a/odaiprojects.com/projects-site/home/content-delivery-service/cds-documentation/image-delivery-and-api] [https://docs.google.com/document/d/1rfUHjy_YvVC5fSIsB4aCi5-t2ZhNYrDui-L9EEXXm9g/edit]
(Not [https://sites.google.com/a/odaiprojects.com/projects-site/home/content-delivery-service/cds-documentation/image-delivery-and-api])
- XML: eg [http://deliver.odai.yale.edu/info/repository/YCBA/object/7/type/2?output=xml]
-- 14 samples: on Box, folder data/cds_xml: [https://yale.app.box.com/s/afdkkt46gcwyxlmrhy14/1/1006752027]
-- 2 samples: [^7-image-info.xml] (2 views), [^5001-image-info.xml] (8 views)
- JSON: eg [http://deliver.odai.yale.edu/info/repository/YCBA/object/7/type/2?output=json]
-- slightly worse format (two extra parentheses):
[http://deliver.odai.yale.edu/info/repository/YCBA/object/7/type/2?output=jsonp&callback]
-- this sanitized version was in the RDF but is a broken link
-- 3 samples formatted with Emacs: [^7-image-info.json] (2 views), [^5005-image-info.json] (8 views), [^5054-image-info.json] (supposed to have copyright)

Description: I haven't read the documentation but here's what I see.
| *path/field* | *eg* | *description* |
| X/derivatives/Y | | X ranges over [#Image Views] (0..M, 0 is Main View), Y ranges over [#Image Sizes] (1,2,3,6,7) |
| X/contentId | 482f519c-eebf-4596-819c-4c8197c4d3e5 | GUID, same as above |

(?) Questions for Lec:
Questions:
- aAre there other formats that we care about?
- do all webStatement and usageTerms redirect to http://britishart.yale.edu/collections/using-collections/image-use ?
Even the object you said is copyrighted (5054) points to the same page: [http://deliver.odai.yale.edu/info/repository/YCBA/object/5054/type/2?output=json]
- are there any imageCopyrightNotice and imageCopyrightMarked with true?
Even the object you said is copyrighted (5054) doesn't have these.
-- (+) Lec: we only care about image/jpeg, image/tiff, image/jp2. In the longer future maybe pdf/a, mp3, mp4, 3D formats, TBD as they will have different viewers
- wWhat are unitAccessOnly and cas, and do we care?
-- Lec: Proxy, CAS, login + session ticket. We do care as Linked Data may not always be Open, we can have some LOD and some LD. I can imagine on the long run giving access to all data and those without access with only see LOD. For now you can ignore.
-- (?) Vlado: Then these flags should be used to filter the dataset.
If you publish something out, it becomes LOD even if your intent is for some of it to be non-open LD :-)

h3. Image Redirects URLs
ODAI has setup two several URLs that both redirect to the physical URL:
# Using ODAI GUID:
{noformat}http://deliver.odai.yale.edu/content/id/<contentId>/format/<Y>{noformat}
eg [http://deliver.odai.yale.edu/content/id/482f519c-eebf-4596-819c-4c8197c4d3e5/format/2]
# (x) Using object id:
{noformat}http://deliver.odai.yale.edu/content/repository/YCBA/object/<objectId>/type/2/format/<Y>{noformat}
eg [http://deliver.odai.yale.edu/content/repository/YCBA/object/7/type/2/format/2]
This is better since it doesn't involve a GUID and is directly correlated to the object id.
#- Unfortunately such redirect is set only for the Main View (X=0) (I tried varying "type" but got nowhere).
# (!) YCBA should setup redirects like this for each view X, starting from the Main View X=0:
It's not suitable as a permanent URL, since if YCBA decides to remove one view from public access, all others after it in the sequence are promoted (decremented)
# (x) Using repository name and filename:
{noformat}http://deliver.odai.yale.edu/content/repository/YCBA/object/<objectId>/image/<X>/format/<Y>{noformat} {noformat}http://deliver.odai.yale.edu/content/repository/YCBA/id/<filename1>/format/<Y>{noformat}
where filename1 is "filename" with "formatShort" chopped off and extension replaced with ".tif"
eg [http://deliver.odai.yale.edu/content/repository/YCBA/object/7/image/0/format/2] [http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-7-0001-pub.tif/format/2]
# (!) As described in [#Deep Zoom Image], the deep zoom format [http://deliver.odai.yale.edu/content/repository/YCBA/object/7/image/0/format/7]
should NOT redirect to [http://deliver.odai.yale.edu/content/id/482f519c-eebf-4596-819c-4c8197c4d3e5/format/1] since this serves the whole image.
Instead, it should redirect to [http://scale.ydc2.yale.edu/iiif/482f519c-eebf-4596-819c-4c8197c4d3e5].
#- As described in [#Deep Zoom Image], the JPEG2000 URL [http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-7-0001-pub.tif/format/7] is unsuitable since it serves the whole image.
# (/) Using ODAI GUID:
#- for format/1,2,3,6
{noformat}http://deliver.odai.yale.edu/content/id/<contentId>/format/<Y>{noformat}
eg [http://deliver.odai.yale.edu/content/id/482f519c-eebf-4596-819c-4c8197c4d3e5/format/2]
#- for format/7 (deep zoom): the IIIF service URL
{noformat}http://scale.ydc2.yale.edu/iiif/<contentId>{noformat}

In summary (format/7 goes to an IIP Server, *not* to the whole JP2000 image)
| *view* | *fm* | *format* | *logical URL* | *redirect* |
| 0 | 1 | sm | http://deliver.odai.yale.edu/content/repository/YCBA/object/7/image/0/format/1 | http://deliver.odai.yale.edu/content/id/482f519c-eebf-4596-819c-4c8197c4d3e5/format/1 |
| 0 | 2 | med | http://deliver.odai.yale.edu/content/repository/YCBA/object/7/image/0/format/2 | http://deliver.odai.yale.edu/content/id/482f519c-eebf-4596-819c-4c8197c4d3e5/format/2 |
| 0 | 3 | large | http://deliver.odai.yale.edu/content/repository/YCBA/object/7/image/0/format/3 | http://deliver.odai.yale.edu/content/id/482f519c-eebf-4596-819c-4c8197c4d3e5/format/3 |
| 0 | 6 | print-lg | http://deliver.odai.yale.edu/content/repository/YCBA/object/7/image/0/format/6 | http://deliver.odai.yale.edu/content/id/482f519c-eebf-4596-819c-4c8197c4d3e5/format/6 |
| 0 | 7 | JPEG2000 | http://deliver.odai.yale.edu/content/repository/YCBA/object/7/image/0/format/7 | http://scale.ydc2.yale.edu/iiif/482f519c-eebf-4596-819c-4c8197c4d3e5 |
| 1 | 1 | sm | http://deliver.odai.yale.edu/content/repository/YCBA/object/7/image/1/format/1 | http://deliver.odai.yale.edu/content/id/279ce6c0-c584-43e4-a5b4-5af2c90b82a0/format/1 |
| 1 | 2 | med | http://deliver.odai.yale.edu/content/repository/YCBA/object/7/image/1/format/2 | http://deliver.odai.yale.edu/content/id/279ce6c0-c584-43e4-a5b4-5af2c90b82a0/format/2 |
| 1 | 3 | large | http://deliver.odai.yale.edu/content/repository/YCBA/object/7/image/1/format/3 | http://deliver.odai.yale.edu/content/id/279ce6c0-c584-43e4-a5b4-5af2c90b82a0/format/3 |
| 1 | 6 | print-lg | http://deliver.odai.yale.edu/content/repository/YCBA/object/7/image/1/format/6 | http://deliver.odai.yale.edu/content/id/279ce6c0-c584-43e4-a5b4-5af2c90b82a0/format/6 |
| 1 | 7 | JPEG2000 | http://deliver.odai.yale.edu/content/repository/YCBA/object/7/image/1/format/7 | http://scale.ydc2.yale.edu/iiif/279ce6c0-c584-43e4-a5b4-5af2c90b82a0 |
| *image alias* | *format* | *URL* |
| view0/format1 | sm | http://deliver.odai.yale.edu/content/id/482f519c-eebf-4596-819c-4c8197c4d3e5/format/1 |
| view0/format2 | med | http://deliver.odai.yale.edu/content/id/482f519c-eebf-4596-819c-4c8197c4d3e5/format/2 |
| view0/format3 | large | http://deliver.odai.yale.edu/content/id/482f519c-eebf-4596-819c-4c8197c4d3e5/format/3 |
| view0/format6 | print-lg | http://deliver.odai.yale.edu/content/id/482f519c-eebf-4596-819c-4c8197c4d3e5/format/6 |
| view0/format7 | JPEG2000 | http://scale.ydc2.yale.edu/iiif/482f519c-eebf-4596-819c-4c8197c4d3e5 |
| view1/format1 | sm | http://deliver.odai.yale.edu/content/id/279ce6c0-c584-43e4-a5b4-5af2c90b82a0/format/1 |
| view1/format2 | med | http://deliver.odai.yale.edu/content/id/279ce6c0-c584-43e4-a5b4-5af2c90b82a0/format/2 |
| view1/format3 | large | http://deliver.odai.yale.edu/content/id/279ce6c0-c584-43e4-a5b4-5af2c90b82a0/format/3 |
| view1/format6 | print-lg | http://deliver.odai.yale.edu/content/id/279ce6c0-c584-43e4-a5b4-5af2c90b82a0/format/6 |
| view1/format7 | JPEG2000 | http://scale.ydc2.yale.edu/iiif/279ce6c0-c584-43e4-a5b4-5af2c90b82a0 |

Below I use such URLs in examples. If YCBA cannot set such redirects, we'll use the GUID-based URLs (1).
(i) In any case: use the actual deliver.odai.yale.edu URL for the images, not a "made up" node with identifier pointing to that URL

h3. Image Sizes
YCBA keeps images in many sizes. These sizes or "formats" are over 15 and include video, 3D models, etc.
The ones I've encountered for images are listed below ("width" is just an example):
| *url suffix* | *size label* | *width* | *file* | *use in RS* |

h3. Deep Zoom Image
Many YCBA objects have Deep Zoom images (JPEG2000), sometimes even several per object.
Eg Miss Prue [http://collections.britishart.yale.edu/vufind/Record/1669236] has:
- *main*: [http://collection.britishart.yale.edu/danprac/iip.html?image=1b747e8f-7754-482c-b5a2-9e1dc1986f4b]

This is an IIPMooViewer client using a Djatoka Adore IIIF server
- the server implements this URL-based protocol:
(May 2013: IIP Server has beta support for the IIIF Image API)
- the server implements the IIIF Image API, a simple URL-based protocol:
[http://www-sul.stanford.edu/iiif/image-api/]
- the sc:hasRelatedService URL for the first image is:
[http://openseadragon.github.io/examples/tilesource-iiif/]

RS implements Image Annotation over Deep Zoom images using the IIP Server protocol.
{status:title=TODO|color=red} Implement IIIF tiles in RS Image Annotation, and multiplexing between IIP and IIIF


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 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}
<http://collection.britishart.yale.edu/id/object/5005>
PX_has_main_representation <http://deliver.odai.yale.edu/content/repository/YCBA/object/5005/image/0/format/2>.
<http://deliver.odai.yale.edu/content/repository/YCBA/object/5005/image/0/format/2>

h3. Image Rights
- (-) This says nothing (has no fields)
<object/7/image/1> P104_is_subject_to [http://collection.britishart.yale.edu/id/page/object/7/image/1/restriction]
- (-) this has the following problems:
YCBA doesn't claim copyright over any images, so we only need to point to a policy page.
See [#Object Rights] for a more substantial discussion of public domain over copyrighted objects.

- This has problems:
{noformat}
<object/7/image/1> P104_is_subject_to <http://collection.britishart.yale.edu/id/page/object/7/image/1/restriction> # 0. has no fields
<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 "http://hdl.handle.net/10079/w6m90dq"; # 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
{noformat}
- so (-) simply use this:
{noformat}
<object/7/image/1> P104_is_subject_to <http://britishart.yale.edu/terms/imaging/unrestricted>. # 6
<object/5054/image/1> P104_is_subject_to <http://britishart.yale.edu/terms/imaging/under_copyright>. # 7
<http://britishart.yale.edu/terms/imaging/unrestricted> a E30_Right; rdfs:label "Public Domain".
<http://britishart.yale.edu/terms/imaging/under_copyright> a E30_Right; rdfs:label "Under Copyright: © Estate of the Artist".
<object/7/image/X/format/Y> P104_is_subject_to <http://britishart.yale.edu/collections/using-collections/image-use>. # 6.
<http://britishart.yale.edu/collections/using-collections/image-use> a E30_Right; rdfs:label "See link for details".
{noformat}
- 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.

Discussion:
- All webStatement and usageTerms are the persistent link [http://hdl.handle.net/10079/gb5mkww] which redirects to [http://britishart.yale.edu/collections/using-collections/image-use].
-- Lec: for now yes, but in the long run this may not be the case. This comes from [#Image Metadata] (from Digital Asset Managment), so if YCBA's imaging/rights manager changes it, it will be reflected in this metadata
-- Vlado: ok, in that case different images could have different P104_is_subject_to.
-- Vlado: I don't see the benefit of using a "persistent link" since it is unreadable. The "image-use" URL doesn't say "public" or "copyrighted" so it doesn't reflect any policy, but at least it says what it is about. If you want to change the policy, just change the text on the page. This is in no way worse than redirecting the "persistent link" to a different URL
- 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):
{noformat}
<http://collection.britishmuseum.org/id/object/MCT3411>
crm:P138i_has_representation <http://www.britishmuseum.org/collectionimages/AN00589/AN00589075_001_l.jpg>.
<http://www.britishmuseum.org/collectionimages/AN00589/AN00589070_001_l.jpg>
crm:P105_right_held_by thesIdentifier:the-british-museum.
{noformat}
- -- 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

h3. Image Representation

h3. Image Derivation
We connect only format/2 directly to the object (P138i) and declare the other formats derivatives thereof (P130i)
{noformat}
<object/7> P138i_has_representation <object/7/image/1/format/2> <view0/format2> .
<object/7/image/1/format/2> P130i_features_are_also_found_on
<object/7/image/1/format/1>, <object/7/image/1/format/3>, <object/7/image/1/format/6>, <object/7/image/1/format/7>.
<view0/format2> P130i_features_are_also_found_on <view0/format1>, <view0/format3>, <view0/format6>, <view0/format7>.
{noformat}
This is a trick required by RS, so it can show only one format on screen, and provide links for the rest
h3. Image RDF
Tying it all together, this section defines the RDF mapping for images.
- We assume [#Image Redirects] are set for all image views
- For brevitiy we use image aliases as defined in the [#Image URLs] table. In RDF the actual http URL should be used.
*Not* a "made up" node with P1_is_identified_by pointing to the actual URL
- We assume Image View 0 The first image view is the Main representation
- We provide MIME type and pixel size using the same vocabularies as [SharedCanvas|http://www.shared-canvas.org/datamodel/spec/#Annotation]: DC and EXIF, but skip filename and sizeBytes
- We create P2 subproperties for variuos image characteristics
- We create subproperties of P2_has_type for various image characteristics

{noformat}
# Objects/Images
<http://collection.britishart.yale.edu/id/object/7>
PX_has_main_representation <http://deliver.odai.yale.edu/content/repository/YCBA/object/7/image/0/format/2>; <view0/format2>;
crm:P138i_has_representation <http://deliver.odai.yale.edu/content/repository/YCBA/object/7/image/1/format/2>. <view1/format2>.

# image/0/format/2 is the main format
<http://deliver.odai.yale.edu/content/repository/YCBA/object/7/image/0/format/2>
a E38_Image;
# main view, main format
<view0/format2> a E38_Image;
bmo:PX_image_flag <yale/thes/image/flag/cropped_to_image>, <yale/thes/image/flag/recto>, <yale/thes/image/flag/unframed>;
P104_is_subject_to <http://britishart.yale.edu/collections/using-collections/image-use> ;
exif:height 480 ; # is xsd:integer
exif:width 359 ;
dc:format "image/jpeg" ; # we skip filename and sizeBytes
P94i_was_created_by <http://collection.britishart.yale.edu/id/object/7/image/creation>;
P130i_features_are_also_found_on <view0/format1>, <view0/format3>, <view0/format6>, <view0/format7>.
<http://deliver.odai.yale.edu/content/repository/YCBA/object/7/image/0/format/1>,
<http://deliver.odai.yale.edu/content/repository/YCBA/object/7/image/0/format/3>,
<http://deliver.odai.yale.edu/content/repository/YCBA/object/7/image/0/format/6>,
<http://deliver.odai.yale.edu/content/repository/YCBA/object/7/image/0/format/7>.

# image/0/format/1
<http://deliver.odai.yale.edu/content/repository/YCBA/object/7/image/0/format/1>
a E38_Image;
# other formats
<view0/format1> a E38_Image;
bmo:PX_image_flag <yale/thes/image/flag/cropped_to_image>, <yale/thes/image/flag/recto>, <yale/thes/image/flag/unframed>;
P104_is_subject_to <http://britishart.yale.edu/collections/using-collections/image-use> ;
dc:format "image/jpeg" ;
P94i_was_created_by <http://collection.britishart.yale.edu/id/object/7/image/creation>.
# ... image/0/format/3,6,7 format3,6 are similar and differ only by size and dc:format

# format/7 is used for Deep Zoom
# Deep Zoom format. Same as above, with an extra statement
<http://deliver.odai.yale.edu/content/repository/YCBA/object/7/image/0/format/7>
a E38_Image;
exif:width 3201 ;
dc:format "image/jp2" ;
P94i_was_created_by <http://collection.britishart.yale.edu/id/object/7/image/creation>;
# It's on an IIIPF server. Next statement Statement suggested by Michael Appleby
dct:conformsTo <http://library.stanford.edu/iiif/image-api/1.1/conformance.html#level1>;.
P94i_was_created_by <http://collection.britishart.yale.edu/id/object/7/image/creation>.

# image/1: other view: similar, only Image Flags are different
<http://deliver.odai.yale.edu/content/repository/YCBA/object/7/image/1/format/2>
a E38_Image;
<view1/format2> a E38_Image;
bmo:PX_image_flag <yale/thes/image/flag/recto>, <yale/thes/image/flag/unframed>;
P104_is_subject_to <http://britishart.yale.edu/collections/using-collections/image-use> ;
dc:format "image/jpeg" ;
P94i_was_created_by <http://collection.britishart.yale.edu/id/object/7/image/creation>;
P130i_features_are_also_found_on <view1/format1>, <view1/format3>, <view1/format6>, <view1/format7>.
<http://deliver.odai.yale.edu/content/repository/YCBA/object/7/image/1/format/1>,
<http://deliver.odai.yale.edu/content/repository/YCBA/object/7/image/1/format/3>,
<http://deliver.odai.yale.edu/content/repository/YCBA/object/7/image/1/format/6>,
<http://deliver.odai.yale.edu/content/repository/YCBA/object/7/image/1/format/7>.

# ... image/1/format/1,3,6,7: view1/format1,3,6,7: same as above

# Shared Creation node. We could even share it across all objects
<http://collection.britishart.yale.edu/id/object/7/image/creation>
# Shared Creation node
<http://collection.britishart.yale.edu/id/object/7/image/creation>
a E65_Creation;
P14_carried_out_by <thesauri/ULAN/500303557>;
{noformat}
<http://collection.britishart.yale.edu/id/object/7>
crm:P62_depicts <http://collection.britishart.yale.edu/id/thesauri/AAT/55244> , <http://collection.britishart.yale.edu/id/thesauri/AAT/25886>... aat:55244, aat:25886...
{noformat}
If you use P62 for the Subjects, why not use also use P62 for the Places??
BM didn't have that luxury since not all of their objects carry an Image, and not all Subjects are "represented": some are only merely "about".
# (-) (minor) Print out the Places in a PX_display_wrap
# image/X: see [#Image RDF]
# (-) image/X: don't use such made up nodes, use actual image URLs. See [#Image RDF]

h2. Acquisition
- (+) The YCBA director does not want to publish which person gave up the object.
Emmanuelle: Right now, we absolutely cannot publish who were the previous owners of our objects, no matter if they have passed or not.
- (-) This means you can skip E8_Acquisition altogether, since YCBA is stated as current owner and keeper. Kill this:
{noformat}
<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" .
{noformat}
-- If not: format the label as "Transferred to ..." (now it reads as an Agent, not as a Transfer)
- (+) P30_transferred_custody_of is wrong direction
Lec: Replaced with P30i_custody_transferred_through

h3. YCBA sub-orgs
- (?) The acquisition label (and the [Credit Line facet here|http://collections.britishart.yale.edu/vufind/Search/Results?join=AND&lookfor0%5B%5D=&type0%5B%5D=allfields&bool0%5B%5D=AND&lookfor1%5B%5D=&type1%5B%5D=title&bool1%5B%5D=AND&lookfor2%5B%5D=&type2%5B%5D=auth_author&bool2%5B%5D=AND&lookfor3%5B%5D=&type3%5B%5D=earliestDate&bool3%5B%5D=AND&lookfor4%5B%5D=&type4%5B%5D=topic&bool4%5B%5D=AND&lookfor5%5B%5D=&type5%5B%5D=geographic&bool5%5B%5D=AND]) show that there are several "sub-orgs" (or sub-collections) under it: Paul Mellon Collection, Paul Mellon Fund, Gift of Mr. and Mrs. J. Richardson Dilworth, B.A. 1938, etc.
If it's important to preserve this information in RDF, you could create sub-agents under YCBA, eg like this:
{noformat}
<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 .
{noformat}

h2. Current Owner, Keeper
- (-) If YCBA is incorporated, use E40_Legal_Body instead of the more generic E74_Group:
{noformat} <thesauri/ULAN/500303557> a crm:E74_Group , skos:Concept ;
skos:prefLabel "Yale Center for British Art" .
{noformat}
- (-) This is probably wrong, it should describe the specific sub-organization (department):
{noformat}
crm:P50_has_current_keeper <http://collection.britishart.yale.edu/id/thesauri/department> ;
{noformat}
If you don't have departments, say that YCBA is the keeper.

h2. Current Location
You currently use per-object place representations. Such places are not searchable since they're not in a thesaurus.
{noformat}
<http://collection.britishart.yale.edu/id/object/5005/location/1> a crm:E53_Place ;
rdfs:label "Bay25" . # UnitType
<http://collection.britishart.yale.edu/id/object/5005/location/2> a crm:E53_Place ;
rdfs:label "401" . # SubSite
<http://collection.britishart.yale.edu/id/object/5005/location/3> a crm:E53_Place ;
rdfs:label "Yale Center for British Art" . # Site
<http://collection.britishart.yale.edu/id/object/5005/location/4> a crm:E53_Place ;
rdfs:label "New Haven" . # Geo location
{noformat}

Recommendations:
- (?) 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:
{noformat}
rdfs:label "Storage unit: Bay25, shelf: 401"
{noformat}
- (-) 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

h2. Object Rights
- PX_has_copyright "Public Domain" is unnecessary since you have it structured as
[http://collection.britishart.yale.edu/id/page/object/7/object-rights].
If you want to output a string, use PX_display_wrap
- [http://collection.britishart.yale.edu/id/page/object/7/object-rights]
is a completely unnecessary intermediate node
- This should not be per-object
[http://collection.britishart.yale.edu/id/object/7/public-domain]
- so overall, use just this in object data:
{noformat}<object/7> P104_is_subject_to <http://britishart.yale.edu/terms/public-domain>.{noformat}
And this in thesaurus data, not per-object:
h3. Public Domain
The majority of works in YCBA's collection are in the Public Domain. For example:
- view: [http://collections.britishart.yale.edu/vufind/Record/1669236]
-- shows "Public Domain"
-- images are available in various [#Image Sizes]
- [#Image Metadata]: [http://deliver.odai.yale.edu/info/repository/YCBA/object/5005/type/2?output=json]
-- webStatement and usageTerms are [http://hdl.handle.net/10079/gb5mkww]. See [#Image Rights]
-- imageCopyrightMarked is "false".
- (!) RDF: [http://collection.britishart.yale.edu/id/object/7] has some problems:
{noformat}
<http://britishart.yale.edu/terms/public-domain> a crm:E30_Right; rdfs:label "Public Domain".
<http://collection.britishart.yale.edu/id/object/7>
PX_has_copyright "Public Domain"; # 1. Unnecessary since you have it structured. To output a string, use PX_display_wrap
P104_is_subject_to <http://collection.britishart.yale.edu/id/object/7/copyright>. # 2. Public Domain is the same, so shouldn't be per object
<http://collection.britishart.yale.edu/id/object/7/copyright> a E30_Right; # 3. Use CC, since CC is a stronger authority about PD than YCBA
P2_has_type <http://collection.britishart.yale.edu/id/object/7/public-domain>; # 4. Shouldn't be per object.
P3_has_note "Public Domain".
{noformat}
- better yet, use a CreativeCommons URI, since CC is a stronger authority about rights than YCBA
- Use this:
{noformat}
<http://collection.britishart.yale.edu/id/object/7>
PX_display_wrap "Rights :: Public Domain";
P104_is_subject_to <http://creativecommons.org/publicdomain/mark/1.0/>.
# See http://creativecommons.org/choose/mark/ and http://creativecommons.org/about/pdm
# Another option is CC0, see http://creativecommons.org/about/cc0
<http://creativecommons.org/publicdomain/mark/1.0/> a E30_Right;
rdfs:label "Public Domain Mark".
{noformat}

h3. Copyrighted
There are some objects that are copyrighted. Let's consider one:
- view: [http://collections.britishart.yale.edu/vufind/Record/1669290]
-- shows "© Estate of the Artist"
-- images are available only in Small size
- [#Image Metadata]: [http://deliver.odai.yale.edu/info/repository/YCBA/object/5054/type/2?output=json]
-- webStatement and usageTerms are the same as for Public Domain. It was explained: "YCBA makes no assertion of copyright nor any denial of copyright we may have in our photograph/digital image of the underlying artwork". But YCBA restricts to Small size images only
-- images are available only in Small size (format/1). As the policy explains: "Thumbnail-sized images of copyrighted works are displayed under fair use".
If you try a bigger format, you get nothing, eg: [http://deliver.odai.yale.edu/content/id/0c4dadff-a5ae-4dc8-ba2d-2ff4d408ceb7/format/2]
-- imageCopyrightMarked is "", which means different from "false"
- LIDO XML: [http://collections.britishart.yale.edu/oaicatmuseum/OAIHandler?verb=GetRecord&identifier=oai:tms.ycba.yale.edu:5054&metadataPrefix=lido]
{code:xml}
<lido:rightsWorkWrap>
<lido:rightsWorkSet>
<lido:rightsType>
<lido:conceptID lido:source="YCBA" lido:type="object copyright">under copyright</lido:conceptID>
<lido:term></lido:term>
</lido:rightsType>
<lido:rightsHolder>
<lido:legalBodyName>
<lido:appellationValue>© Estate of the Artist</lido:appellationValue>
</lido:legalBodyName>
<lido:legalBodyWeblink>Henrietta Garnett</lido:legalBodyWeblink>
</lido:rightsHolder>
<lido:creditLine>Yale Center for British Art, Paul Mellon Fund</lido:creditLine>
</lido:rightsWorkSet>
</lido:rightsWorkWrap>
<lido:rightsHolder>
<lido:legalBodyID lido:type="URL">http://hdl.handle.net/10079/rfj6qd5</lido:legalBodyID>
<lido:legalBodyName>
<lido:appellationValue>Yale Center for British Art</lido:appellationValue>
</lido:legalBodyName>
</lido:rightsHolder>
{code}
This has various problems: legalBodyName/appellationValue is a proclamation not name, legalBodyWeblink is a name not url, legalBodyID is a proclamation page not organization's URL. But at least the data is present
- (!) RDF: [http://collection.britishart.yale.edu/id/page/object/5054] has many problems:
{noformat}
<http://collection.britishart.yale.edu/id/object/5054>
PX_has_copyright "© Estate of the Artist"; # 1. Unnecessary since you have it structured
P104_is_subject_to <http://collection.britishart.yale.edu/id/object/5054/copyright>.
<http://collection.britishart.yale.edu/id/object/5054/copyright> a E30_Right;
P105_right_held_by <http://collection.britishart.yale.edu/id/person-institution/99999-hardcoded>; # 2. Hardcoded won't do
P2_has_type <http://collection.britishart.yale.edu/id/object/5054/under-copyright>; # 3. Shouldn't be per object
P3_has_note "© Estate of the Artist".
<http://collection.britishart.yale.edu/id/object/5054/under-copyright> a E55_Type;
rdfs:label "under copyright";
<http://collection.britishart.yale.edu/id/person-institution/99999-hardcoded> a E39_Owner; # 4. No such type
skos:prefLabel "Anna Katrina Zinkeisen", ... # 5. Many prefLabels to the same URL won't do
"Estate of Anna Katrina Zinkeisen", # 6. (minor) This and the previous one should have been correlated
"Estate of Augustus Edwin John",
"Estate of C. R. W. Nevinson", ...
"Transport for London", ...
"Unknown rights administrator", # 7. Just don't emit any P105_right_held_by
"Yale Center for British Art" # 8. For known organizations, use AAT terms
{noformat}
- Use this:
{noformat}
<http://collection.britishart.yale.edu/id/object/5054>
PX_display_wrap "Rights :: © Estate of the Artist";
P104_is_subject_to <http://collection.britishart.yale.edu/id/object/5054/copyright>.
<http://collection.britishart.yale.edu/id/object/5054/copyright> a E30_Right;
P105_right_held_by
# If it's known in AAT (eg YCBA, Transport for London), use the AAT term.
# If it's in a local thesaurus, use the local term <id/person-institution/X>
# If it's "Unknown rights administrator", skip P105_right_held_by altogether
# ONLY if you need to make one on the fly, use this:
<http://collection.britishart.yale.edu/id/object/5054/copyright/owner>;
P2_has_type <http://britishart.yale.edu/terms/imaging/under_copyright>;
P3_has_note "© Estate of the Artist".

# Only if you need to make an owner on the fly:
<http://collection.britishart.yale.edu/id/object/5054/copyright/owner> a E39_Actor;
rdfs:label "Henrietta Garnett".

# http://hdl.handle.net/10079/rfj6qd5 redirects to this. I don't see the benefit of using a handle
<http://britishart.yale.edu/terms/imaging/under_copyright> a E55_Type;
rdfs:label "Under copyright".
{noformat}

h2. Production
When and why to use {nf} <obj/production/M/association> a ycba:EX_Association {nf}

h3. Produced By Specific Process
Emmanuelle: What do I do for the following crm:P14_carried_out_by association codes? Do they become types or labels?
Vlado: 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

h2. Unknown Artist
{status:title=postponed|color=gray} 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:
- Vladimir: You can express "French" and "Sculptor". Here's how the BM thesauri are modeled:
{noformat}
<http://collection.britishmuseum.org/id/person-institution/207075>
a crm:E21_Person, skos:Concept;
skos:inScheme id:person-institution;

- 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:
-- EN20-Studio of, EN23-Circle of, EN24-Workshop of, EN25-School of: [BM Association Mapping v2#Production by Closely Related Group]
-- 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.:
-# [http://collection.britishart.yale.edu/id/page/object/7] has 2 records:
h2. 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]:
- Vlado: easy to tackle with EX_Association, which is is a subclass of E13_Attribute_Assignment (see [attribute_assignment@crmg] and [recorder@crmg]):
{noformat}
<obj> bmo:PX_curatorial_comment "comment".

h2. Inscriptions
(?) I haven't seen any Inscription info in TTL. And in LIDO I see only empty XML tags for the following types but without data:
Please include TTL samples with Inscription info.
- [http://collections.britishart.yale.edu/vufind/Record/1670022]
[http://collections.britishart.yale.edu/oaicatmuseum/OAIHandler?verb=GetRecord&identifier=oai:tms.ycba.yale.edu:57163&metadataPrefix=lido]
{code:xml}
<lido:inscriptionsWrap>
<lido:inscriptions lido:type="Inscription">
<lido:inscriptions lido:type="Marks">
<lido:inscriptions lido:type="Lettering">
<lido:inscriptionTranscription>
Inscribed in black on proper left inside flap: [word BOOTS circled]
</lido:inscriptionTranscription>
</lido:inscriptions>
<lido:inscriptions lido:type="Signed and Dated">
<lido:inscriptionTranscription>
Signed and dated on proper left inside flap: "2001 | SARAH LUCAS"
</lido:inscriptionTranscription>
</lido:inscriptions>
</lido:inscriptionsWrap>
{code}
Are there any objects with inscriptions for me to check?
- (-) Represent like this (a small part of [mark_inscription@crmg])
{noformat}
<http://collection.britishart.yale.edu/id/object/57163>
P65_shows_visual_item <http://collection.britishart.yale.edu/id/object/57163/inscription/1>,
<http://collection.britishart.yale.edu/id/object/57163/inscription/2>.
<http://collection.britishart.yale.edu/id/object/57163/inscription/1> a E34_Inscription;
rdfs:label "Inscribed in black on proper left inside flap: [word BOOTS circled]";
P2_has_type <thes/inscription/inscription>.
<http://collection.britishart.yale.edu/id/object/57163/inscription/2> a E34_Inscription;
rdfs:label "Signed and dated on proper left inside flap: "2001 | SARAH LUCAS";
P2_has_type <thes/inscription/signed-and-dated>.

<thes/inscription/inscription> a skos:ConceptScheme;
skos:prefLabel "Inscription Type".
<thes/inscription/inscription> a E55_Type, skos:Concept;
skos:prefLabel "Inscription"; skos:inScheme <thes/inscription/>.
<thes/inscription/signed-and-dated> a E55_Type, skos:Concept;
skos:prefLabel "Signed and Dated"; skos:inScheme <thes/inscription/>.
<thes/inscription/marks> a E55_Type, skos:Concept;
skos:prefLabel "Marks"; skos:inScheme <thes/inscription/>.
<thes/inscription/lettering> a E55_Type, skos:Concept;
skos:prefLabel "Lettering"; skos:inScheme <thes/inscription/>.
{noformat}

- Marks and Lettering are other LIDO inscriptions/type..
-- Lettering should also be mapped to E34_Inscription
-- (?) Marks could be mapped to E37_Mark, but *only* if you're sure it doesn't include text/transcription.
Reason: in [cidoc_class_hierarchy@crmg]: E37_Mark is not a subclass of E33_Linguistic_Object.
If it could include text, it's safer to also map it to E34_Inscription

h2. Dimensions
You state object dimensions (including their properties):
{noformat}
crm:P43_has_dimension <http://collection.britishart.yale.edu/id/object/7/height> ;
crm:P43_has_dimension <http://collection.britishart.yale.edu/id/object/7/width> ;
{noformat}

(-) But you omit lido:extentMeasurements, i.e. don't state what was measured:
{code:xml}
<lido:objectMeasurementsSet>
<lido:displayObjectMeasurements>12 1/16 x 16 inches (30.6 x 40.6 cm)
<lido:objectMeasurements>
<lido:extentMeasurements>Support (PTG)
{code}
(?) If you have data with lido:qualifierMeasurements, we should also consider it

You can add it like this:
{noformat}
<http://collection.britishart.yale.edu/id/object/7>
P39i_was_measured_by <http://collection.britishart.yale.edu/id/object/7/measurement>.
<http://collection.britishart.yale.edu/id/object/7/measurement> a E16_Measurement ;
P40_observed_dimension <http://collection.britishart.yale.edu/id/object/7/height> ,
<http://collection.britishart.yale.edu/id/object/7/width> ;
rdfs:label "12 1/16 x 16 inches (30.6 x 40.6 cm). Extent: Support (PTG)" .
{noformat}

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.

h2. Object Type and Genre
(-) Object Type and Genre (lido:objectWorkType) are missing, eg
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.

h2. Current Owner, Keeper
(-) This is probably wrong, it should describe the specific sub-organization (department):
h2. Collection
- (-) Indicate the collection for each object, see [collection#crmg]
{noformat}
crm:P50_has_current_keeper <http://collection.britishart.yale.edu/id/thesauri/department> ;
{noformat}
If you don't have departments in YCBA, just don't say anything about departments.
<object/7> P46i_forms_part_of <id/collection/prints-and-drawings>.

h2. Current Location
You currently use per-object place representations. Such places are not searchable, and
<id/collection/prints-and-drawings> a E78_Collection; rdfs:label "Prints and Drawings".
{noformat}
<http://collection.britishart.yale.edu/id/object/5005/location/1> a crm:E53_Place ;
rdfs:label "Bay25" . # UnitType
<http://collection.britishart.yale.edu/id/object/5005/location/2> a crm:E53_Place ;
rdfs:label "401" . # SubSite
<http://collection.britishart.yale.edu/id/object/5005/location/3> a crm:E53_Place ;
rdfs:label "Yale Center for British Art" . # Site
<http://collection.britishart.yale.edu/id/object/5005/location/4> a crm:E53_Place ;
rdfs:label "New Haven" . # Geo location
{noformat}
- (?) this won't let the user search by Collection since FR search doesn't concern collections.
BM maps this to "department" (Agent) and the user can search by "keeper/owner".

Recommendations:
- (?) 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:
{noformat}
rdfs:label "Storage unit: Bay25, shelf: 401"
{noformat}
- (-) 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
h1. Collections and Object Types
The above sections are written after examining a few Paintings only.
But YCBA has numerous other object types, for which the mapping could be slightly different.
- (!) Lec to include various object types in the samples

h2. Dimensions
You state object dimensions (including their properties):
{noformat}
crm:P43_has_dimension <http://collection.britishart.yale.edu/id/object/7/height> ;
crm:P43_has_dimension <http://collection.britishart.yale.edu/id/object/7/width> ;
{noformat}
The available Search fields (and some item types or classifications) vary by collection

(-) But you omit lido:extentMeasurements, i.e. don't state what was measured:
{code:xml}
<lido:objectMeasurementsSet>
<lido:displayObjectMeasurements>12 1/16 x 16 inches (30.6 x 40.6 cm)
<lido:objectMeasurements>
<lido:extentMeasurements>Support (PTG)
{code}
(?) If you have data with lido:qualifierMeasurements, we should also consider it
|*collection*|*count*|*search, browse* |
| Paintings and Sculpture | 2226 |[search|http://britishart.yale.edu/collections/search/paintings-and-sculpture] [browse|http://collections.britishart.yale.edu/vufind/Search/Results?lookfor0[]="Paintings+and+Sculpture"&type0[]=collection_facet] |
| Prints and Drawings | 48968 |[search|http://britishart.yale.edu/collections/search/prints-and-drawings] [browse|http://collections.britishart.yale.edu/vufind/Search/Results?lookfor0[]="Prints+and+Drawings"&type0[]=collection_facet] |
| Rare Books and Manuscripts | 15392 |[search|http://britishart.yale.edu/collections/search/rare-books-and-manuscripts] [browse|http://collections.britishart.yale.edu/vufind/Search/Results?lookfor0[]="Rare+Books+and+Manuscripts"&type0[]=collection_facet]|
| Reference Library | 33173 |[search|http://britishart.yale.edu/collections/search/reference-library-and-archives] [browse|http://collections.britishart.yale.edu/vufind/Search/Results?lookfor0[]="Reference+Library"&type0[]=collection_facet] |
| Frames | 1376 |[search|http://britishart.yale.edu/collections/search/frames] [browse|http://collections.britishart.yale.edu/vufind/Search/Results?lookfor0[]="Frames"&type0[]=collection_facet] |

You can add it like this:
{noformat}
<http://collection.britishart.yale.edu/id/object/7>
P39i_was_measured_by <http://collection.britishart.yale.edu/id/object/7/measurement>.
<http://collection.britishart.yale.edu/id/object/7/measurement> a E16_Measurement ;
P40_observed_dimension <http://collection.britishart.yale.edu/id/object/7/height> ,
<http://collection.britishart.yale.edu/id/object/7/width> ;
rdfs:label "12 1/16 x 16 inches (30.6 x 40.6 cm). Extent: Support (PTG)" .
{noformat}
TODO TODO TODO:
Prints, Drawings, Sculpture (even Cakes!), Paintings, Frames, Folios, Books

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.
Cake: http://collections.britishart.yale.edu/vufind/Record/1670022
| *type/field* | *url/content* |
|Medium | Inkjet on iced fruitcake plus cardboard box |
|Subject Terms| boxes (containers), portrait, genre subject |

h2. Paintings and Sculpture
- Search fields:
Title:
Artist:
Date:
Classification:
Subject Terms:
Places Represented:
Genre:
Inscription:
Accession Number:
- Classification:
Ceramic
Model
Painted Object
Painting
Ceramic
Sculpture (and
Silver
Wedgwood

h2. Prints and Drawings
- Search fields:
Title:
Artist:
Date:
Classification:
Subject Terms:
Places Represented:
Genre:
Inscription:
Accession Number:
- Classification:
Archive
Brass Rubbing
Document
Drawing &amp; Watercolor
Drawing &amp; Watercolor-Architectural
Drawing &amp; Watercolor-Miniature
Drawing &amp; Watercolor-Sketchbook
Manuscript
Paint Box
Photograph
Poster
Print
Print-printing-plate
Rare Book
Video
Wedgwood


h2. Rare Books and Manuscripts
- search fields:
Title:
Creator:
Subject:
Place of Publication:
Publisher or Printer:
Date:
Notes:
Item-type:
Form or genre: (eg Sketchbooks; "Commonplace books"; Panoramas)
Illustration technique:
Provenance:
- Item-type:
Language material
Notated music
Manuscript notated music
Cartographic material
Manuscript cartographic material
Projected medium
Nonmusical sound recording
Musical sound recording
Two-dimensional nonprojectable graphic
Computer file
Kit
Mixed materials
Three-dimensional artifact or naturally occurring object
Manuscript language material

h2. Reference Library
- Search fields:
Title:
Author:
Subject:
Place of Publication:
Publisher or Printer:
Date:
Notes:
Item-type:
- Item-type:
Language material
Notated music
Manuscript notated music
Cartographic material
Manuscript cartographic material
Projected medium
Nonmusical sound recording
Musical sound recording
Two-dimensional nonprojectable graphic
Computer file
Kit
Mixed materials
Three-dimensional artifact or naturally occurring object
Manuscript language material

h2. Bibliography Frames
Page numbers, eg for [http://collection.britishart.yale.edu/id/bibliography/2775]
- search fields
Title:
Framemaker:
Date:
Materials:
Style: (eg "Provincial Rococo"; Neoclassical; "Louis XIV style")
Ornament: (eg acanthus; cartouche; rocaille)
Accession Number: