View Source

{excerpt}Notes from May-Jul 2013{excerpt}

h1. Intro

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

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
- 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 use IIP Image for RKD images, while you use IIIF)
- 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!

h2. Legend
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

h2. Eyeball
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..

h1. General Problems
- (-) {status:title=low prio|color=gray} Pubby prefixes are not setup: shows "?:..."
Lec: does same for BM, will try to fix
- (+) STRONGLY Suggest to have 1 URI per object, not 3 sameAs URIs
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
- (+) 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.

h2. 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":
- (-) VUFind record (i.e. "home page")
Note: the last part the CCD id []
- all [#Images], including Deep Zoom images
- LIDO record
Note: this link currently doesn't work
- ODAI (Yale Digital Collections Center) aggregation:
- Google Cultural Institute (Google Art Project)
Short: []
Long: []
- (/) Pubby page. I don't think we need it since

h1. Thesauri

h2. 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

h2. 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).

h3. Meta-Thesaurus
(-) 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.
- {status:title=future|color=blue} 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]

h2. 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?
Emmanuelle: the AAT only has a few frames terms. The YCBA has developed a highly specialized frame vocabulary with a frame expert. For an example, take a look at the ornament description for []
- 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

h2. Local Terms
(-) don't export a term as "-1", eg []
- 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
- Vlado: in chat Emmanuelle said "-1" come from Yale local terms. Then emit them as such, don't look them up in AAT

h2. Agents
- (+) remove crm:E55_Type: a Group is *not* a Type
{noformat}<thesauri/nationality/British> a crm:E55_Type , crm:E74_Group , skos:Concept ;{noformat}
- (+) 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" ;
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
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. Emmanuelle to provide some more examples
- Some institutions have documented dates of existence: Published by Advanced Graphics London, 1969-present in []
- Creator that is an institution: Monro School (but no documented dates of existence in our system): []
- institution as Rights Administrator: Design and Artists Copyright Society in []
- Richard Wilson, 1712 or 1713-1782 in []
- Damien Hirst, born 1965 in []
- John Samuel Agar, ca. 1770-after 1820 in []
- Print made by John Bruce, fl. 1826 in []

Lec: LIDO may not contain the correct data in the eraliestDate and latestDate in vitalRecord for all dates esp., most of these above are in Display, so I recommend we ignore for time being

h2. 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

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 [].
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
- Lec: updated with standard ID based URIs

h3. Getty URIs
- Don't use YCBA-specific URIs for Getty, eg
This won't let your data mesh with other data using Getty.
- (+) Use the official namespace that Getty just decided (20-Jun-2013)
Lec: ULAN, AAT, TGN converted to Getty URIs
- (-) Vlado: The URI structure is still under discussion. My suggestion is:
Getty will have a board meeting Jul 15, and may decide the URL structure then. Leave it as is for now, but you'd probably have to change it one more time after they finalize
- same for the scheme: currently is
<thesauri/ULAN/500303557> a crm:E74_Group , skos:Concept ;
skos:inScheme <thesauri/institution> .
should be:

h2. Bibliography
- (-) Page numbers, eg for []
- Vlado: BM uses [BIBO|], for example see [].
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

h2. Titles

h3. Title Types
- Why do you need these duplicate types?
{noformat}crm:P2_has_type <thesaurus/title/Alternate-title> , <thesaurus/title/alternate> .{noformat}
- I'm not sure what "Repository title" is. But if it means Preferred, then this is also unnecessary duplication:
{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.

- CRM has no notion of "preferred title" (unlike P48_has_preferred_identifier)
- RS prints the titles in order, together with the title type
- Luckily Lec also emits rdfs:label equal to the preferred title, so we use that in result lists

(-) I propose to merge the two sets of values because preferred/alternate is already covered by Repository/all-the-rest:
- Emit "Preferred" instead of "Repository"
- Emit the titles in order, the Preferred one first
- Don't emit "alternate"
- shorten the term URL a bit since the thesaurus URL already says "title":
{noformat} <thesaurus/title/ForeignLanguage>{noformat}

h3. Duplicate Titles
- (-) 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> .

h3. Title Language
- (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.
- (-) Vladimir: fair enough! So indicate language only for that type, and say it's translation of the Preferred one:
<object/19850/title/N> a E35_Title;
rdfs:label "Malvolio Danse"@fr ;
P2_has_type <thesaurus/title/ForeignLanguage>;
P72_has_language <thesaurus/language/french>;
P73i_is_translation_of <object/19850/title/1>.
(Actually it's more likely this is the *original* title, so you may want to use P73_has_translation instead of P73i)

h2. Images

h3. Image Metadata
Yale keeps numerous image assets, and Yale ODAI provides extensive metadata about the images:
- documentation: []
(Not [])
- XML: eg []
-- 14 samples: on Box, folder data/cds_xml: []
-- 2 samples: [^7-image-info.xml] (2 views), [^5001-image-info.xml] (8 views)
- JSON: eg []
-- slightly worse format (two extra parentheses):
-- this sanitized version was in the RDF but is a broken link
-- you can use [] to format it
-- 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) |
| ./formatId | 1 | size id |
| ./formatShort | sm | size name |
| ./label | Screen small | size label |
| ./url | | logical URL (request this) |
| ./source | | physical URL (redirects to it) |
| ./bucketDNS | | physical server |
| ./bucketName | | physical server |
| ./bucketPath | 48/2f/482f519c-eebf-4596-819c-4c8197c4d3e5/ba-obj-7-0001-pub-sm.jpg | physical path |
| ./contentId | 482f519c-eebf-4596-819c-4c8197c4d3e5 | GUID |
| ./filename | ba-obj-7-0001-pub-sm.jpg | file name |
| ./unitAccessOnly | false | (?) |
| ./cas | false | (?) |
| ./captcha | false | protected by captcha? Only size 5 are |
| ./format | image/jpeg | image format |
| ./sizeBytes | 33169 | file size |
| ./pixelsX | 249 | width |
| ./pixelsY | 186 | height |
| X/metadata | | describes Image View X |
| ./caption | cropped to image, recto, unframed | enumerates Flags of the Image View |
| ./source | Yale Center for British Art | credits |
| ./imageCredit | Digital Image: Yale Center for British Art | credits |
| ./webStatement | | redirects to |
| ./usageTerms | | always same(?) |
| ./imageCopyrightNotice | | always(?) empty |
| ./imageCopyrightMarked | false | always(?) false |
| ./assetId | d70ae2b604a64bd24809441a5d24233a8d406925 | another GUID |
| X/contentId | 482f519c-eebf-4596-819c-4c8197c4d3e5 | GUID, same as above |

- Are there other formats that we care about?
-- (+) 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
- What 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 URLs
ODAI has several URLs that redirect to the physical URL:
# (x) Using object id:
eg []
#- Unfortunately such redirect is set only for the Main View (X=0) (I tried varying "type" but got nowhere).
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:
where filename1 is "filename" with "formatShort" chopped off and extension replaced with ".tif"
eg []
#- As described in [#Deep Zoom Image], the JPEG2000 URL [] is unsuitable since it serves the whole image.
# (/) Using ODAI GUID:
#- for format/1,2,3,6
eg []
#- for format/7 (deep zoom): the IIIF service URL

| *image alias* | *format* | *URL* |
| view0/format1 | sm | |
| view0/format2 | med | |
| view0/format3 | large | |
| view0/format6 | print-lg | |
| view0/format7 | JPEG2000 | |
| view1/format1 | sm | |
| view1/format2 | med | |
| view1/format3 | large | |
| view1/format6 | print-lg | |
| view1/format7 | JPEG2000 | |

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* |
| format/1 | Screen small | 250 | jpeg | result list thumbnail (or could use 2) |
| format/2 | Screen medium | 480 | jpeg | lightbox, object view, data basket preview |
| format/3 | Screen large | 1920 | jpeg | |
| format/6 | Print large | 3000 | tiff | |
| format/7 | Zoom (JPEG 2000) | 4279 | jp2 | This is the max available size. We don't use this URL for annotation since it serves the whole [#Deep Zoom Image] |

h3. Deep Zoom Image
Many YCBA objects have Deep Zoom images (JPEG2000), sometimes even several per object.
Eg Miss Prue [] has:
- *main*: []
- *X-Ray*: []

This is an IIPMooViewer client using a Djatoka Adore IIIF server
(May 2013: IIP Server has beta support for the IIIF Image API)
- the server implements the IIIF Image API, a simple URL-based protocol:
- the sc:hasRelatedService URL for the first image is:
This URL doesn't return anything, but you can append parameters to get what you need.
- the tile URLs are of this form:
- If you request a non-existing GUID, you get "Error: No response from server". 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):

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

[#Image Metadata]
- The URL included in the metadata (X/derivatives/7/url), eg [], is not appropriate since it serves the whole image.
- One should concatenate the server URL [] and X/derivatives/7/contentId to make the sc:hasRelatedService URL, which is used as base of the tile URLs

h3. Image Views
Image Views are different photographs of the same painting, using different modes (Flags).
Eg the lovely Miss Prue [] has 8 image views, each with 1..3 comma-separated Flags:
0. cropped to image, recto, unframed (0 is always the Main View)
1. recto, unframed
2. framed, recto
3. framed, verso
4. detail, recto
6. detail, recto
6. Composite X-radiograph
7. cropped to image, recto, unframed

RKD has similar flags, broken into separate thesauri (BM doesn't have such flags):
- 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

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:
PX_has_main_representation <>.
PX_image_flag <yale/thes/image/flag/cropped_to_image>, <yale/thes/image/flag/recto>, <yale/thes/image/flag/unframed>.

<yale/thes/image/flag/cropped_to_image> a E55_Type, skos:Concept;
skos:prefLabel "cropped to image"; skos:inScheme <yale/thes/image/flag/>.
<yale/thes/image/flag/recto> a E55_Type, skos:Concept;
skos:prefLabel "recto"; skos:inScheme <yale/thes/image/flag/>.
<yale/thes/image/flag/unframed> a E55_Type, skos:Concept;
skos:prefLabel "unframed"; skos:inScheme <yale/thes/image/flag/>.

h3. Image Rights
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:
<object/7/image/1> P104_is_subject_to <> # 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. not specific to this image, so don't use per-image node
rdfs:label ""; # 3. should be URI not string, 4. this redirects, just use the final destination
rdf:type crm:E62_String. # 5. means nothing. So-called "CRM Primitive types" should not be used
- (-) simply use this:
<object/7/image/X/format/Y> P104_is_subject_to <>. # 6.
<> a E30_Right; rdfs:label "See link for details".

- All webStatement and usageTerms are the persistent link [] which redirects to [].
-- 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):
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.
-- 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
(-) both of these are wrong, see [image_objects_carriers@crmg]
<object/7> P62_depicts <object/7/image/1> .
<object/7> P65_shows_visual_item <object/7/image/1> .
- The correct properties to use are:
<object/7> bmo:PX_has_main_representation <> . # Main View
<object/7> P138i_has_representation <> . # other views
- Explanation: a thing (E24) can show many visual items (eg an inscription and a couple of images).
But when you take a photo of a painting (E1), you create a unique Image (E38) that represents the painting.

(-) No need to repeat since bmo:PX_has_main_representation is subprop of P138i_has_representation
P138i_has_representation <>
bmo:PX_has_main_representation <>

h3. Image Creation
- (-) 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>; # Created 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> a E65_Creation; P14_carried_out_by <thesauri/ULAN/500303557>.

h3. Image Derivation
We connect only format2 directly to the object (P138i) and declare the other formats derivatives thereof (P130i)
<object/7> P138i_has_representation <view0/format2> .
<view0/format2> P130i_features_are_also_found_on <view0/format1>, <view0/format3>, <view0/format6>, <view0/format7>.
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.
- 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
- The first image view is the Main representation
- We provide MIME type and pixel size using the same vocabularies as [SharedCanvas|]: DC and EXIF, but skip filename and sizeBytes
- We create subproperties of P2_has_type for various image characteristics

# Prefixes
#prefix crm: <> . # assumed by default below
@prefix dc: <> . # Dublin Core Elements
@prefix dct: <> . # Dublin Core Terms
@prefix exif: <> . # EXIF vocabulary
@prefix bmo: <> .
@prefix rdfs: <> .
@prefix skos: < > .

# Properties
bmo:PX_image_flag rdfs:subPropertyOf P2_has_type; rdfs:label "Image Flag"; rdfs:comment "eg recto, verso, cropped, X-Ray".
bmo:PX_image_format rdfs:subPropertyOf P2_has_type; rdfs:label "Image Format"; rdfs:comment "eg Small, Medium, Large".

# Thesauri
<yale/thes/image/flag/> a skos:ConceptScheme; skos:prefLabel "Image Flag".
<yale/thes/image/format/> a skos:ConceptScheme; skos:prefLabel "Image Format".

# Terms
<yale/thes/image/flag/cropped_to_image> a E55_Type, skos:Concept;
skos:prefLabel "cropped to image"; skos:inScheme <yale/thes/image/flag/>.
<yale/thes/image/flag/recto> a E55_Type, skos:Concept;
skos:prefLabel "recto"; skos:inScheme <yale/thes/image/flag/>.
<yale/thes/image/flag/unframed> a E55_Type, skos:Concept;
skos:prefLabel "unframed"; skos:inScheme <yale/thes/image/flag/>.

<yale/thes/image/format/sm> a E55_Type, skos:Concept;
skos:prefLabel "Screen small"; skos:inScheme <yale/thes/image/format/>.
<yale/thes/image/format/med> a E55_Type, skos:Concept;
skos:prefLabel "Screen medium"; skos:inScheme <yale/thes/image/format/>.
<yale/thes/image/format/large> a E55_Type, skos:Concept;
skos:prefLabel "Screen large"; skos:inScheme <yale/thes/image/format/>.
<yale/thes/image/format/print-lg> a E55_Type, skos:Concept;
skos:prefLabel "Print large (CAPTCHA protected)"; skos:inScheme <yale/thes/image/format/>.
<yale/thes/image/format/JP2000> a E55_Type, skos:Concept;
skos:prefLabel "Zoom (JPEG 2000)"; skos:inScheme <yale/thes/image/format/>.

# Objects/Images
PX_has_main_representation <view0/format2>;
crm:P138i_has_representation <view1/format2>.

# 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 <> ;
bmo:PX_image_format <yale/thes/image/format/med> ;
exif:height 480 ; # is xsd:integer
exif:width 359 ;
dc:format "image/jpeg" ;
P94i_was_created_by <>;
P130i_features_are_also_found_on <view0/format1>, <view0/format3>, <view0/format6>, <view0/format7>.

# 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 <> ;
bmo:PX_image_format <yale/thes/image/format/sm> ;
exif:height 249 ; #
exif:width 186 ;
dc:format "image/jpeg" ;
P94i_was_created_by <>.
# format3,6 are similar and differ only by size and dc:format

# Deep Zoom format. Same as above, with an extra statement
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 <> ;
bmo:PX_image_format <yale/thes/image/format/JPEG2000> ;
exif:height 4279 ; #
exif:width 3201 ;
dc:format "image/jp2" ;
P94i_was_created_by <>;
# It's on an IIIF server. Statement suggested by Michael Appleby
dct:conformsTo <>.

# other view: similar, only Image Flags are different
<view1/format2> a E38_Image;
bmo:PX_image_flag <yale/thes/image/flag/recto>, <yale/thes/image/flag/unframed>;
P104_is_subject_to <> ;
bmo:PX_image_format <yale/thes/image/format/med> ;
exif:height 480 ;
exif:width 438 ;
dc:format "image/jpeg" ;
P94i_was_created_by <>;
P130i_features_are_also_found_on <view1/format1>, <view1/format3>, <view1/format6>, <view1/format7>.

# view1/format1,3,6,7: same as above

# Shared Creation node. We could even share it across all objects
a E65_Creation;
P14_carried_out_by <thesauri/ULAN/500303557>;
rdfs:label "Digital Image: Yale Center for British Art". # imageCredit

h2. Depiction
Couple issues here:
crm:P62_depicts <> , <> ...;
crm:P62_depicts <> , <> ...;
bmo:PX_display_wrap "Subject :: transportation" , "Subject :: workers" , "Subject :: boats"...;
crm:P128_carries <> .
a crm:E73_Information_Object ;
crm:P129_is_about <> , <>...
# (-) concept/1 is a useless intermediate node. Look at [image_objects_carriers@crmg]. According to VUFind, the places are Represented on the painting, which carries a Visual Object. So you should use P138 which is stronger than P129: but then you may as well use the shortcut P62_depicts. So it boils down to:
crm:P62_depicts aat:55244, aat:25886...
If you use P62 for the Subjects, why not 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 merely "about".
# (-) (minor) Print out the Places in a PX_display_wrap
# (-) 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:
<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" .
-- 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|]) 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:
<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 .

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" .
- (-) This is probably wrong, it should describe the specific sub-organization (department):
crm:P50_has_current_keeper <> ;
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.
<> 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

h2. Object Rights

h3. Public Domain
The majority of works in YCBA's collection are in the Public Domain. For example:
- view: []
-- shows "Public Domain"
-- images are available in various [#Image Sizes]
- [#Image Metadata]: []
-- webStatement and usageTerms are []. See [#Image Rights]
-- imageCopyrightMarked is "false".
- (!) RDF: [] has some problems:
PX_has_copyright "Public Domain"; # 1. Unnecessary since you have it structured. To output a string, use PX_display_wrap
P104_is_subject_to <>. # 2. Public Domain is the same, so shouldn't be per object
<> a E30_Right; # 3. Use CC, since CC is a stronger authority about PD than YCBA
P2_has_type <>; # 4. Shouldn't be per object.
P3_has_note "Public Domain".
- Use this:
PX_display_wrap "Rights :: Public Domain";
P104_is_subject_to <>.
# See and
# Another option is CC0, see
<> a E30_Right;
rdfs:label "Public Domain Mark".

h3. Copyrighted
There are some objects that are copyrighted. Let's consider one:
- view: []
-- shows "© Estate of the Artist"
-- images are available only in Small size
- [#Image Metadata]: []
-- 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: []
-- imageCopyrightMarked is "", which means different from "false"
- LIDO XML: []
<lido:conceptID lido:source="YCBA" lido:type="object copyright">under copyright</lido:conceptID>
<lido:appellationValue>© Estate of the Artist</lido:appellationValue>
<lido:legalBodyWeblink>Henrietta Garnett</lido:legalBodyWeblink>
<lido:creditLine>Yale Center for British Art, Paul Mellon Fund</lido:creditLine>
<lido:legalBodyID lido:type="URL"></lido:legalBodyID>
<lido:appellationValue>Yale Center for British Art</lido:appellationValue>
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: [] has many problems:
PX_has_copyright "© Estate of the Artist"; # 1. Unnecessary since you have it structured
P104_is_subject_to <>.
<> a E30_Right;
P105_right_held_by <>; # 2. Hardcoded won't do
P2_has_type <>; # 3. Shouldn't be per object
P3_has_note "© Estate of the Artist".
<> a E55_Type;
rdfs:label "under copyright";
<> 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
- Use this:
PX_display_wrap "Rights :: © Estate of the Artist";
P104_is_subject_to <>.
<> a E30_Right;
# 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:
P2_has_type <>;
P3_has_note "© Estate of the Artist".

# Only if you need to make an owner on the fly:
<> a E39_Actor;
rdfs:label "Henrietta Garnett".

# redirects to this. I don't see the benefit of using a handle
<> a E55_Type;
rdfs:label "Under copyright".

h2. Production
When and why to use {nf} <obj/production/M/association> a ycba:EX_Association {nf}
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

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
- 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

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:
-- 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".

h3. 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]

!YCBA Production2 unknown creator.png!

- 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]
-- EN44-Associate of, EN21-Follower of, EN22-Imitator of, EN42-After: [BM Association Mapping v2#Influenced By]
-- EN43-Attributed to: [BM Association Mapping v2#Probably/Unlikely Produced By]
- 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.:
-# [] has 2 records:
<object/7/production/1> crm:P14_carried_out_by <id/person-institution/1180> . # 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]
-# 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".

h2. Curatorial Comment
- (-) Yale: PX_curatorial_comment needs date and author added to the data model
- Vlado: easy to tackle with EX_Association, which is is a subclass of E13_Attribute_Assignment (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

h2. Inscriptions
Please include TTL samples with Inscription info.
- []
<lido:inscriptions lido:type="Inscription">
Inscribed in black on proper left inside flap: [word BOOTS circled]
<lido:inscriptions lido:type="Signed and Dated">
Signed and dated on proper left inside flap: "2001 | SARAH LUCAS"
- (-) Represent like this (a small part of [mark_inscription@crmg])
P65_shows_visual_item <>,
<> a E34_Inscription;
rdfs:label "Inscribed in black on proper left inside flap: [word BOOTS circled]";
P2_has_type <thes/inscription/inscription>.
<> 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/>.

- 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):
crm:P43_has_dimension <> ;
crm:P43_has_dimension <> ;

(-) But you omit lido:extentMeasurements, i.e. don't state what was measured:
<lido:displayObjectMeasurements>12 1/16 x 16 inches (30.6 x 40.6 cm)
<lido:extentMeasurements>Support (PTG)
(?) 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.

h2. Object Type and Genre
(-) Object Type and Genre (lido:objectWorkType) are missing, eg
<lido:conceptID lido:source="AAT" lido:type="Object name">300033618
<lido:conceptID lido:source="AAT" lido:type="Genre">300015636
<lido:conceptID lido:source="YCBA" lido:type="Genre">7
<lido:term>architectural subject
- 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.

h2. Collection
- (-) Indicate the collection for each object, see [collection#crmg]
<object/7> P46i_forms_part_of <id/collection/prints-and-drawings>.

<id/collection/prints-and-drawings> a E78_Collection; rdfs:label "Prints and Drawings".
- (?) 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".

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

The available Search fields (and some item types or classifications) vary by collection

|*collection*|*count*|*search, browse* |
| Paintings and Sculpture | 2226 |[search|] [browse|[]="Paintings+and+Sculpture"&type0[]=collection_facet] |
| Prints and Drawings | 48968 |[search|] [browse|[]="Prints+and+Drawings"&type0[]=collection_facet] |
| Rare Books and Manuscripts | 15392 |[search|] [browse|[]="Rare+Books+and+Manuscripts"&type0[]=collection_facet]|
| Reference Library | 33173 |[search|] [browse|[]="Reference+Library"&type0[]=collection_facet] |
| Frames | 1376 |[search|] [browse|[]="Frames"&type0[]=collection_facet] |

Prints, Drawings, Sculpture (even Cakes!), Paintings, Frames, Folios, Books

| *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:
Subject Terms:
Places Represented:
Accession Number:
- Classification:
Painted Object
Sculpture (and

h2. Prints and Drawings
- Search fields:
Subject Terms:
Places Represented:
Accession Number:
- Classification:
Brass Rubbing
Drawing &amp; Watercolor
Drawing &amp; Watercolor-Architectural
Drawing &amp; Watercolor-Miniature
Drawing &amp; Watercolor-Sketchbook
Paint Box
Rare Book

h2. Rare Books and Manuscripts
- search fields:
Place of Publication:
Publisher or Printer:
Form or genre: (eg Sketchbooks; "Commonplace books"; Panoramas)
Illustration technique:
- 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
Mixed materials
Three-dimensional artifact or naturally occurring object
Manuscript language material

h2. Reference Library
- Search fields:
Place of Publication:
Publisher or Printer:
- 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
Mixed materials
Three-dimensional artifact or naturally occurring object
Manuscript language material

h2. Frames
- search fields
Style: (eg "Provincial Rococo"; Neoclassical; "Louis XIV style")
Ornament: (eg acanthus; cartouche; rocaille)
Accession Number: