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

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

Changes (214)

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:
- create RForms for your objects

See [RS Plan 3.7#Get Yale on-board with ResearchSpace|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

h2. Eyeball

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


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: 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 [http://collection.britishart.yale.edu/id/ontology/PX_display_wrap]
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
h2. Pubby

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":
- (-) VUFind record (i.e. "home page")
[http://collections.britishart.yale.edu/vufind/Record/1669236]
Note: the last part the CCD id [http://collection.britishart.yale.edu/id/object/5005/ccd]
- all [#Images], including Deep Zoom images
- LIDO record
[http://collections.britishart.yale.edu/oaicatmuseum/OAIHandler?verb=GetRecord&identifier=oai:tms.ycba.yale.edu:7&metadataPrefix=lido]
Note: this link currently doesn't work
- ODAI (Yale Digital Collections Center) aggregation:
[http://discover.odai.yale.edu/ydc/Record/1669236]
- Google Cultural Institute (Google Art Project)
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]
These issues are not about the mapping, but how RDF is presented by Pubby.
If you switch to Forest / OwlimWorkbench, they'll go away (and probably be replaced by different issues ;-) )

- (-) {status:title=low prio|color=gray} Pubby prefixes are not setup: shows "?:..."
Lec: does same for BM, will try to fix

h3. Link to download Turtle file

I'm now getting actual RDF and Turtle files for the sample set on box.com.

(?) Better to fix this on Pubby & VUFind:
- Pubby eg [http://collection.britishart.yale.edu/id/object/7], top right has link "View Collections Online Record" (to VUFind)
- VUFind eg [http://collections.britishart.yale.edu/vufind/Record/1670806] has link "RDF" that leads back to the pubby page
This 303 redirects to [http://collection.britishart.yale.edu/id/page/object/7] (HTML)
I am not sure what Accept header to use, since a HEAD request doesn't show any negotiation info.
-- I suggest to change the "RDF" to a direct link, e.g. [http://collection.britishart.yale.edu/id/object/7.rdf]
-- If possible, also add "Turtle" format, e.g. [http://collection.britishart.yale.edu/id/object/7.ttl]
Pubby has this at the bottom, e.g. [http://collection.britishart.yale.edu/id/data/object/7?output=ttl], but only for the current node, not its subnodes

h3. Inverse links considered harmful

(?) I cannot examine a URI like [http://collection.britishart.yale.edu/id/page/thesauri/department] because pubby tries to show "is P51_current_keeper *of*" all objects and that takes forever.
Is there a way to switch these inverse links off?

h1. Thesauri

{status:title=postponed|color=blue}
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.

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.
Each term should be both a CRM entity of appropriate type (see [#CRM Types of Thesauri]) and a skos:Concept; and should have skos:inScheme.
- (-) 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:

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

| *Meta ConceptScheme* | *comment* |
| [http://collection.britishart.yale.edu/id/thesauri/activity/|http://collection.britishart.yale.edu/id/thesauri/activity/]\\ | |
| [http://collection.britishart.yale.edu/id/thesauri/group/|http://collection.britishart.yale.edu/id/thesauri/group/]\\ | |
| [http://collection.britishart.yale.edu/id/thesauri/image/flag/] | |
| [http://collection.britishart.yale.edu/id/thesauri/person-institution/]\\ | |
| [http://collection.britishart.yale.edu/id/thesauri/authority/] | What's its relation to /production |
| [http://collection.britishart.yale.edu/id/thesauri/extent/] | |
| [http://collection.britishart.yale.edu/id/thesauri/inscription/] | |
| [http://collection.britishart.yale.edu/id/thesauri/likelihood/] | |
| [http://collection.britishart.yale.edu/id/thesauri/material/] | |
| [http://collection.britishart.yale.edu/id/thesauri/materialType/] | |
| [http://collection.britishart.yale.edu/id/thesauri/matcult/] | |
| [http://collection.britishart.yale.edu/id/thesauri/identifier/] | |
| [http://collection.britishart.yale.edu/id/thesauri/identifier/exhibition/] | |
| [http://collection.britishart.yale.edu/id/thesauri/person-institution/] | YCBA is already listed in ULAN, and you have person-institution. So do you really need this? EDG: we need this until ULAN IDs are in TMS/LIDO |
| [http://collection.britishart.yale.edu/id/thesauri/qualification/] | Called above /likelihood - removed, done - EDG: for commenced by, completed by, finished by |
| [http://collection.britishart.yale.edu/id/thesauri/title/] | |
| [http://iconclass.org/rdf/2011/09/] | |
| [http://vocab.getty.edu/aat/300000000/] | |
| [http://vocab.getty.edu/aat/300264088/|http://vocab.getty.edu/aat/300264088/]\\ | |
| [http://vocab.getty.edu/aat/300264090/|http://vocab.getty.edu/aat/300264090/]\\ | |
| [http://vocab.getty.edu/aat/300264091/|http://vocab.getty.edu/aat/300264091/]\\ | |
| [http://vocab.getty.edu/tgn/] | |
| [http://vocab.getty.edu/ulan/] | |

h3. Validate Instance Schemes

This command extracts skos:inScheme statements from instance data (all Ttl files). Run it in the data/ directory:
{code:bash} grep -h inScheme ttl/* cds_ttl/* ycba2cds/* | perl -pe "s{.*inScheme }{}; s{ [;.]$}{}" | sort | uniq {code}
If you're on linux you got these tools. If you're on Windows, install [http://cygwin.org].

(+)  The current list of Concept Schemes in instances is below. Resolve it against meta:
- Schemes in instances but not in meta: are undefined
- Schemes in meta but not in instances: are either useless, or indicate a defect in instance mapping (scheme is not specified).
In particular I'm worried that the instance list is quite shorter than the meta list.
- (!) It DOES matter whether there is a trailing slash or not. My preference is to consistently use a trailing slash (so the scheme is a full prefix of the term), but that's up to you. Whatever you choose, you must be consistent

| *Instance ConceptScheme* | *comment* |
| [http://collection.britishart.yale.edu/id/thesauri/genre/] | ok |
| [http://collection.britishart.yale.edu/id/thesauri/image/flag/] | ok: but wrong in meta - done |
| [http://collection.britishart.yale.edu/id/thesauri/image/format/] | ok: but wrong in meta - done |
| [http://collection.britishart.yale.edu/id/thesauri/inscription/] | ok |
| [http://collection.britishart.yale.edu/id/thesauri/matcult/] | ok: But note that "16th century" is NOT a [#Period/Culture] |
| [http://collection.britishart.yale.edu/id/thesauri/material/] | ok |
| [http://collection.britishart.yale.edu/id/thesauri/nationality] | ok |
| [http://collection.britishart.yale.edu/id/thesauri/objecttype/] | ok |
| [http://collection.britishart.yale.edu/id/thesauri/place] | ok |
| [http://collection.britishart.yale.edu/id/thesauri/subject/] | ok |
| [http://collection.britishart.yale.edu/id/thesauri/periods/] | For '16th century', ... |
| [http://collection.britishart.yale.edu/id/thesauri/person-institution/|http://collection.britishart.yale.edu/id/thesauri/person-institution/] | |
| [http://collection.britishart.yale.edu/id/thesauri/authority/|http://collection.britishart.yale.edu/id/thesauri/authority/]\\ | commissioned by: CO |
| [http://collection.britishart.yale.edu/id/thesauri/collection/]\\ | used to be thesauri/department/ |
| [http://collection.britishart.yale.edu/id/thesauri/dimension/|http://collection.britishart.yale.edu/id/thesauri/dimension/]\\ | |
| [http://collection.britishart.yale.edu/id/thesauri/extent/|http://collection.britishart.yale.edu/id/thesauri/extent/]\\ | |
| [http://collection.britishart.yale.edu/id/thesauri/event/|http://collection.britishart.yale.edu/id/thesauri/event/]\\ | |
| [http://collection.britishart.yale.edu/id/thesauri/identifier/|http://collection.britishart.yale.edu/id/thesauri/identifier/] | |
| [http://collection.britishart.yale.edu/id/thesauri/likelihood/|http://collection.britishart.yale.edu/id/thesauri/likelihood/]\\ | |
| [http://collection.britishart.yale.edu/id/thesauri/materialType/|http://collection.britishart.yale.edu/id/thesauri/materialType/]\\ | |
| [http://vocab.getty.edu/ulan/|http://vocab.getty.edu/ulan/]\\ | |
| [http://vocab.getty.edu/tgn/|http://vocab.getty.edu/tgn/]\\ | |
| [http://vocab.getty.edu/aat/300264088]\\ | AAT Styles and Periods Facet: British, American, etc |
| [http://vocab.getty.edu/aat/300264090]\\ | |
| [http://vocab.getty.edu/aat/300264091]\\ | |
| [http://vocab.getty.edu/aat/300000000]\\ | |
| [http://collection.britishart.yale.edu/id/thesauri/production/|http://collection.britishart.yale.edu/id/thesauri/production/]\\ | |
| [http://collection.britishart.yale.edu/id/thesauri/technique/|http://collection.britishart.yale.edu/id/thesauri/technique/]\\ | |
| [http://collection.britishart.yale.edu/id/thesauri/units/|http://collection.britishart.yale.edu/id/thesauri/units/]\\ | |
| [http://iconclass.org/rdf/2011/09/|http://iconclass.org/rdf/2011/09/]\\ | |
| [http://collection.britishart.yale.edu/id/thesauri/event/type/|http://collection.britishart.yale.edu/id/thesauri/event/type/]\\ | |
| [http://collection.britishart.yale.edu/id/thesauri/gender/|http://collection.britishart.yale.edu/id/thesauri/gender/]\\ | |
| [http://collection.britishart.yale.edu/id/thesauri/identifier/source/|http://collection.britishart.yale.edu/id/thesauri/identifier/source/]\\ | |
| [http://collection.britishart.yale.edu/id/thesauri/identifier/exhibition/|http://collection.britishart.yale.edu/id/thesauri/identifier/exhibition/]\\ | |
| [http://collection.britishart.yale.edu/id/thesauri/title/]\\ | |
| [http://collection.britishart.yale.edu/id/thesauri/group/]\\ | |
| [http://collection.britishart.yale.edu/id/thesauri/qualification/] | |
| [http://collection.britishart.yale.edu/id/thesauri/activity/]\\ | |

h3. CRM Types of Thesauri

Each ConceptScheme determines a CRM type (rso:hasRange), which in term determines which FRs (searches) are applicable to it. The mechanism is described in [Meta-Thesaurus and FR Names#Thesaurus to FR Compatibility|Meta-Thesaurus and FR Names#Thesaurus to FR Compatibility]. Consequently RS needs each term to be attached to a single ConceptScheme.

The CRM types are shown on the diagram at the end of that page, and listed below. For each CRM type we give the relevant ConceptSchemes. While ULAN and TGN map to one type each, AAT comprises several [Facets|http://www.getty.edu/vow/AATHierarchy?find=formica&logic=AND&note=&subjectid=300000000] (top-level URLs) that map to different types:
- crm:E39_Actor: ULAN, YCBA People
- crm:E53_Place: TGN, YCBA Places
- crm:E4_Period: AAT Styles and Periods Facet (see [#Period/Culture])
- crm:E57_Material: AAT Materials Facet
- rso:E55_Technique: AAT Activities Facet (includes Processes and Techniques)
- crm:E55_Type: all the rest of AAT: Objects, Associated Concepts, Physical Attributes, Agents (these are kinds of agents, not specific agents\!), Brand Names (see [#Brand Names])
- crm:E58_Measurement_Unit (not searchable): YCBA Units
- crm:E31_Document (not searchable): YCBA Bibliography

h3. AAT Concept Schemes

(-) Declare different AAT concept schemes in the Meta Thesaurus, as per the type breakdown above. Use the actual [AAT Facet|http://www.getty.edu/vow/AATHierarchy?find=&logic=AND&note=&english=N&subjectid=300000000]:
{noformat}
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
<http://vocab.getty.edu/aat/300264091> a skos:ConceptScheme; rdfs:label "AAT Materials".
<http://vocab.getty.edu/aat/300264090> a skos:ConceptScheme; rdfs:label "AAT Activities/Processes/Techniques".
<http://vocab.getty.edu/aat/300264088> a skos:ConceptScheme; rdfs:label "AAT Styles/Periods".
<http://vocab.getty.edu/aat/300000000> a skos:ConceptScheme; rdfs:label "AAT". # all the rest of AAT
{noformat}
- TODO Vlado: use actual AAT identifiers above, and use the AAT Facets (top-levels) as concept schemes

(-) Export AAT terms to these different schemes, but isolate in a prefix definition:
{noformat}
@prefix aat_materials: <http://vocab.getty.edu/aat/300264091> . # Materials Facet
@prefix aat_activities: <http://vocab.getty.edu/aat/300264090> . # Activities Facet, includes Processes and Techniques
@prefix aat_periods: <http://vocab.getty.edu/aat/300264088> . # Styles and Periods Facet
@prefix aat: <http://vocab.getty.edu/aat/300000000> . # all the rest of AAT

<http://vocab.getty.edu/aat/300014078> skos:inScheme aat_materials: . # canvas: Materials facet
<http://vocab.getty.edu/aat/300230058> skos:inScheme aat_activities: . # oil golding: Activities facet
<http://vocab.getty.edu/aat/300111159> skos:inScheme aat_periods: . # British (modern): Styles and Periods facet
<http://vocab.getty.edu/aat/300033618> skos:inScheme aat: . # paintings (visual works): Objects facet
<http://vocab.getty.edu/aat/300250148> skos:inScheme aat: . # horses (animals) [prefLabel=Equus caballus (species)]: Agents facet
{noformat}

You already do this for Technique but use a Yale scheme
{noformat}
aat:230058 a skos:Concept; skos:prefLabel "oil gilding";
skos:inScheme <yale/thes/technique>.
{noformat}

Limitation:
- RS currently needs each term to be assigned to a single concept scheme.
- Each term invokes one set of FRs, as per [Meta-Thesaurus and FR Names#FR Names Table|Meta-Thesaurus and FR Names#FR Names Table].
- The "split facets" Materials; Activities; Styles invoke these corresponding FRs: made of; used technique; was present at, about period.
- Object Type, Shape, About subject (where the subject is a type or Iconclass, not Period/Agent/Place) are mapped to E55_Type and thus to FR "is/has/about"
- So if a painting has a *Subject* selected from the "split facets", currently it cannot be found through this term. But such Subject is not very likely
- {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



h3. Brand Names

(-) Yale to check whether they use any terms from the [Brand Names Facet|http://www.getty.edu/vow/AATHierarchy?find=300028576&logic=AND&note=&subjectid=300343372], in particular:
- [<brand name materials>|http://www.getty.edu/vow/AATFullDisplay?find=300028576&logic=AND&note=&subjectid=300375551], such as Teflon (TM), Tupperware (TM).
-- there's an object using [Formica (TM)|http://www.getty.edu/vow/AATHierarchy?find=formica&logic=AND&note=&english=N&prev_page=1&subjectid=300014581]. Although this is a brand name, it is in the Materials Facet (Getty inconsistency)
- [<brand name techniques and processes>|http://www.getty.edu/vow/AATFullDisplay?find=300028576&logic=AND&note=&subjectid=300375174]

Vladimir: I think having a Brand Names Facet is logically inconsistent. These are Techniques, Materials etc; so they should be put in the corresponding facet, and have a flag to mark them as Brand Name. I'll talk to Getty

Emmanuelle: &nbsp;yes, we are using Formica (TM) as a material that went in the making of the table in Damien Hirst's installation&nbsp;[http://collection.britishart.yale.edu/id/page/object/4908|http://collection.britishart.yale.edu/id/page/object/4908]

This is the path of the 'Formica (TM)' term that we indexed:&nbsp;Formica (TM) / <plastic by production method> / plastic / organic material / <materials by composition> / materials / Materials / MATERIALS FACET / Art & Architecture Thesaurus

As Vladimir explains above, in our 15\+ year old copy of the AAT there is no&nbsp;[<brand name materials>|http://www.getty.edu/vow/AATFullDisplay?find=300028576&logic=AND&note=&subjectid=300375551]&nbsp;facet. The term is in the Material facet. &nbsp;The current online AAT has a&nbsp;[<brand name materials>|http://www.getty.edu/vow/AATFullDisplay?find=300028576&logic=AND&note=&subjectid=300375551]&nbsp;facet, but it still does not include Formica (TM) (it's still in the Materials facet)

h3. Searchable/Taggable Thesauri

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

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: 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|#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
h2. Term Code Discrepancy

Your LIDO has some AAT codes that are truncated compared to the original. Eg object/7:
{code:xml}
<lido:termMaterialsTech>
<lido:conceptID lido:type="medium" lido:source="AAT">15050
<lido:term>oil paint
<lido:termMaterialsTech>
<lido:conceptID lido:type="support" lido:source="AAT">14078
<lido:term>canvas
{code}
The original codes are [aat:300015050|http://www.getty.edu/vow/AATFullDisplay?find=oil+paint&logic=AND&note=&english=N&prev_page=1&subjectid=300015050] and [aat:300014078|http://www.getty.edu/vow/AATServlet?english=N&find=300014078&logic=AND&page=1&note=]. I have seen the same for "oil gilding": "230058" vs aat:300230058.

You map "canvas" to a local term (instead of AAT), and skip "oil paint" altogether:
{noformat}
<http://collection.britishart.yale.edu/id/thesauri/14078> a crm:E57_Material , skos:Concept ;
skos:prefLabel "canvas" ;
skos:inScheme <http://collection.britishart.yale.edu/id/thesauri/material> .
{noformat}

(-) Don't know how this happened but it is crazy. Can you fix it in the conversion script?

* Emmanuelle:&nbsp;YCBA LIDO has some AAT codes that are truncated compared to the&nbsp;original because this is how the AAT codes were 15\+ years ago when they&nbsp;were loaded in TMS.&nbsp; Unfortunately the vendor never updated the TMS&nbsp;thesaurus manager.
* Vladimir:&nbsp;The best way is to fix at the source (TMS). Think you need to speak to them about an upgrade.&nbsp;If they can't do it soon enough, then fix in the conversion.
* Emmanuelle: If we want to fix this problem in the conversion&nbsp;script, then it will be helpful to know that AAT terms always start&nbsp;with 30 and are always 9 digits.&nbsp; So if the old AAT code for 'oil&nbsp;paint' was 15050, the current one should be 300015050.&nbsp; The same&nbsp;behavior happens in the TGN with the 70 prefix.&nbsp;
* Lec:&nbsp;We can catch and add the prefixes but this cannot be done in RDFer (limitations of the digit functions) let me see if our move to XSLT is done, and if COBOAT can fill this in. Back in touch with you soon
* Ken:&nbsp;All the more reason to leave those old things out for now.&nbsp;Also worth bringing up at Getty in September.&nbsp;
* Vladimir:&nbsp;At this stage Yale will be emitting its own version of terms (embedded in object data), so Lec you don't need to fix it.&nbsp;It matters only to your students when they do coreferencing to BM thesauri.&nbsp;But longer term it needs to be fixed.
* Emmanuelle: One thing to be aware&nbsp;of, however, is that the current AAT is somewhat different from our 15&nbsp;year old copy and some terms valid back then have been decommissioned today.&nbsp;








{color:#000000}{*}Local Terms{*}{color}

(-) don't export a term as "-1", eg [http://collection.britishart.yale.edu/id/thesauri/AAT/-1]
- Lec: Emmanuelle, please have some students go through TMS, I exclude now anything that has \-1
- Lec: Emmanuelle there are cases where subjects are TGN where conceptID = 0, I will try to ignore. Example ObjectID = 34
- Lec: Emmanuelle, there are cases where subjects are TGN where conceptID=0, I will try to ignore. Example: object/34
- Vlado: in chat Emmanuelle said "-1" come from Yale local terms. Then emit them as such, don't look them up in AAT.
You absolutely must emit the local terms, else you'll be missing important data.

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

h3. Nationality

Nationality and Profession are modeled as Groups (Gender is merely a Type), eg:
{noformat}
<http://collection.britishmuseum.org/id/person-institution/207075>
a crm:E21_Person, skos:Concept;
skos:inScheme id:person-institution;
skos:prefLabel "Alfonso Ruspagiari";
bmo:PX_gender <http://collection.britishmuseum.org/id/thesauri/gender/male>;
bmo:PX_nationality <http://collection.britishmuseum.org/id/thesauri/nationality/Italian>;
bmo:PX_profession <http://collection.britishmuseum.org/id/thesauri/profession/sculptor/medallist>.

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 .
{noformat}
This lets you search eg for "things produced by Italians" or "things produced by Sculptor-Medallists".

object/52176 has a complication: <[http://collection.britishart.yale.edu/id/person-institution/6436]> has nationality "British, active in Italy (1837-1839)". This is not 1 but 2 "nationalities", the second one temporary (only 2 years). This causes an invalid URL:
{jira:RS-1922}
The URL can be fixed but that's not enough. If you model this as a single "nationality", you'd get too many unrelated "nationalities" and if you search by eg "American", you won't find the above person.

(-) So you must break this up. Options:
# Nationality plus Activity
{noformat}
<person-institution/6436>
bmo:PX_nationality <thesauri/nationality/American>;
P14i_performed <person-institution/6436/activity>.
<person-institution/6436/activity> a E7_Activity;
P2_has_type <thesaurus/activity/active>;
P7_took_place_at <place/Italy>;
P4_has_time-span <person-institution/6436/activity/date>.
<person-institution/6436/activity/date> a E52_Time-Span;
P82a_begin_of_the_begin "1837"^^xsd:gYear;
P82b_end_of_the_end "1938""^^xsd:gYear.
{noformat}
Pro: most faithful modeling. Cons: won't let the user search by "creator from Italy" because this P14i_performed is not included in FR_created_by.
# Treat Temporary "Nationality" as Permanent:
{noformat}
<person-institution/6436>
bmo:PX_nationality <thesauri/nationality/American>, <thesauri/nationality/Italian>.
{noformat}
Pro: user can search by "creator from Italy".
Cons: Less faithful modeling, since the temporary "nationality" is represented the same way as the permanent nationality.
Cons: Requires Yale to correlate country of activity ("Italy") to nationality ("Italian")
# Discard Temporary "Nationality"
{noformat}
<person-institution/6436> bmo:PX_nationality <thesauri/nationality/American>.
{noformat}
Pro: easiest to implement
Cons: loses information

(+) &nbsp;Emmanuelle: solution #1 is the best one to implement for Yale data. &nbsp;"Creator from India" seems to imply that indeed the creator is Indian, which is not the case. &nbsp;An example is&nbsp;[http://collections.britishart.yale.edu/vufind/Record/1668426|http://collections.britishart.yale.edu/vufind/Record/1668426]. &nbsp;It is impossible to mistaken&nbsp;Thomas Daniell's hunting scene for the work of a native Indian artist.

h3. Birth Place

"Born in" should be mapped to E67_Birth - P7_took_place_at.

For E67 reuse the same URL (e.g. <person-institution/6046/birth>)


h3. Life Dates

(+) 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
{noformat}
<person-institution/142>
crm:P92i_was_brought_into_existence_by <person-institution/142/birth> ;
crm:P4_has_time-span <person-institution/142/birth/date>
{noformat}
-- - (+) 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
(-) This is wrong
{noformat}
<person-institution/6046/birth> a crm:E67_Birth ;
crm:P82_at_some_time_within <person-institution/6046/birth/date> .
<person-institution/6046/birth/date> a crm:E52_Time-Span ;
rdfs:label "1609" ;
crm:P82a_begin_of_the_begin "1609"^^xsd:gYear .
<person-institution/6046/death> a crm:E69_Death ;
crm:P82_at_some_time_within <person-institution/6046/death/date> .
<person-institution/6046/death/date> a crm:E52_Time-Span ;
rdfs:label "1672" ;
crm:P82b_end_of_the_end "1672"^^xsd:gYear .
{noformat}
- The relation to E52 must be P4 not P82
- You don't use P82a vs P82b depending on the nature of the event (birth or death). When you have a single event date, just use P82

Should be:
{noformat}
<person-institution/6046/birth> a crm:E67_Birth ;
crm:P4_has_time-span <person-institution/6046/birth/date> .
<person-institution/6046/birth/date> a crm:E52_Time-Span ;
rdfs:label "1609" ;
crm:P82_at_some_time_within "1609"^^xsd:gYear .
<person-institution/6046/death> a crm:E69_Death ;
crm:P4_has_time-span <person-institution/6046/death/date> .
<person-institution/6046/death/date> a crm:E52_Time-Span ;
rdfs:label "1672" ;
crm:P82_at_some_time_within "1672"^^xsd:gYear .
{noformat}

h3. Dates Variety

Lec: we have more variety in Person dates. Emmanuelle provided examples, Vlado provided Turtle code:
- Some institutions have documented dates of existence: Published by Advanced Graphics London, 1969-present in [http://collection.britishart.yale.edu/id/page/object/48770]
{noformat}
<person-institution/11215> a E74_Group, skos:Concept; # not E21_Person! If you know it's incorporated, use E40_Legal_Body (see next section)
skos:prefLabel "Advanced Graphics London";
P92i_was_brought_into_existence_by <person-institution/11215/birth>;
# P93i_was_taken_out_of_existence_by <person-institution/11215/death>; # NO death/date, therefore omit this altogether
{noformat}
- 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]
Same as above
- institution as Rights Administrator: Design and Artists Copyright Society in [http://collection.britishart.yale.edu/id/page/object/5054]
We don't map this, see [#Copyrighted]
- Richard Wilson, 1712 or 1713-1782 in [http://collection.britishart.yale.edu/id/object/423]
{noformat}
<person-institution/N/birth/date> a crm:E52_Time-Span ;
rdfs:label "1712 or 1713" ;
crm:P82a_begin_of_the_begin "1712"^^xsd:gYear ;
crm:P82b_end_of_the_end "1713"^^xsd:gYear
{noformat}
Emmanuelle: shouldn't it be crm:P82b_end_of_the_begin "1713"^^xsd:gYear rather?
- Damien Hirst, born 1965 in [http://collection.britishart.yale.edu/id/object/4908]
Skip all of these altogether:
{noformat}
# <person-institution/N> P100i_died_in <person-institution/N/death>.
# <person-institution/N/death> a E69_Death;
# <person-institution/N/death/date> P4_has_time-span.
# <person-institution/N/death/date> HAS NONE
{noformat}
- John Samuel Agar, ca. 1770-after 1820 in [http://collection.britishart.yale.edu/id/page/object/26383]
{noformat}
<person-institution/N/death/date> a crm:E52_Time-Span ;
rdfs:label "after 1820" ;
crm:P82a_begin_of_the_begin "1712"^^xsd:gYear ;
crm:P82b_end_of_the_end "1713"^^xsd:gYear
{noformat}
(?) &nbsp;Emmanuelle: I am not sure where 1712 and 1713 come from? &nbsp;His&nbsp;crm:P82a_begin_of_the_begin should be&nbsp;1765 and his&nbsp;crm:P82b_end_of_the_end should be 1830.
- Print made by John Bruce, fl. 1826 in [http://collection.britishart.yale.edu/id/page/object/30564]
"Flourit" can be modeled as E7_Activity that the person P12i_was_present_at, see [BMX Issues#Person / Biographical Dates]

(+) Lec: LIDO may not contain the correct data in the eraliestDate earliestDate and latestDate in vitalRecord for all dates esp., most of these above are in Display, so I recommend we ignore for time being
(?) Vlado: ok, but first consider the Turtle snippets above

(+) &nbsp;Emmanuelle: Lec, when there are values in&nbsp;earliestDate and latestDate they are mostly correct. &nbsp;The most common case is that&nbsp;earliestDate and latestDate do not carry any values and we only have the Display.


h3. Gender

(-) &nbsp;Gender terms are used with&nbsp;bmo:PX_gender (eg <[http://collection.britishart.yale.edu/id/thesauri/gender/male]>) but are not defined


h3. Person vs Group vs Institution

If you can distinguish in LIDO different kinds of Actors (Person/ Group (informal)/ Legal Body (institution)) then use specific subclasses and subprops. The number of dashes below shows class nesting:
| *Actor* | *Begin* | *begin prop* | *end* | *end prop* |
| E39_Actor | E63_Beginning_of_Existence | P92i_was_brought_into_existence_by | E64_End_of_Existence | P93i_was_taken_out_of_existence_by |
| \-E21_Person | \-E67_Birth | P98i_was_born | \-E69_Death | P100i_died_in |
| \-E74_Group | \-E66_Formation | P95i_was_formed_by | \-E68_Dissolution | P99i_was_dissolved_by |
| \--E40_Legal_Body | \-E66_Formation | P95i_was_formed_by | \-E68_Dissolution | P99i_was_dissolved_by |
URLs: strictly speaking "/birth" and "/death" are correct only for E21_Person, but it's good enough to also use for other actors

(+) Lec: we are taking into account both person and groups
(?) Vlado: consider the extended version above. You don't have to distinguish E40_Legal_Body: you can stick with E74_Group

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:
{noformat}

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

h3. Getty URIs

- Don't use YCBA-specific URIs for Getty, eg
[http://collection.britishart.yale.edu/id/thesauri/ULAN/500303557]
[http://vocab.getty.edu/ulan/500303557]
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
{noformat}
<thesauri/ULAN/500303557> a crm:E74_Group , skos:Concept ;
[http://vocab.getty.edu/tgn/]
[http://vocab.getty.edu/ulan/]
- Note: unfortunately you can't use a prefixed name starting with digit in Turtle 1.0 (Turtle 1.1 allows that), else we'd configure a prefix to isolate this dependency to just one place.

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

h3. Title Types

- Why do you need these duplicate types?
{noformat}crm:P2_has_type <thesaurus/title/Alternate-title> , <thesaurus/title/alternate> .{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)
{noformat}

h3. Title Language

- (optional) Indicate the title language:
{noformat}
{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}
<object/19850/title/N> a E35_Title;
(Actually it's more likely this is the *original* title, so you may want to use P73_has_translation instead of P73i)

h2. Related Resources

List all URLs closely related to the object: web pages, LIDO XML, etc.
Eg for [http://collection.britishart.yale.edu/id/object/5005] "Mrs. Abington as Miss Prue in Love for Love by William Congreve" this includes:
- VUFind record: "home page" of the object.
[http://collections.britishart.yale.edu/vufind/Record/1669236]
The last part of the URL is the CCD id [http://collection.britishart.yale.edu/id/object/5005/ccd]
- LIDO XML record: source of the RDF representation
[http://collections.britishart.yale.edu/oaicatmuseum/OAIHandler?verb=GetRecord&identifier=oai:tms.ycba.yale.edu:7&metadataPrefix=lido]
- ODAI (Yale Digital Collections Center): aggregates records from various Yale museums and centers
[http://discover.odai.yale.edu/ydc/Record/1669236]
- Google Cultural Institute: aggregation by the Google Art Project
-- 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]
Includes a descriptive part "mrs-abington-as-miss-prue-in-love-for-love-by-william-congreve", but note that you can put anything there (eg "aaaa").
I think it's enough to use only the long form, which is more descriptive.
- (?) Pubby page
[http://collection.britishart.yale.edu/id/page/object/5005]
I don't think we need it since the object URI [http://collection.britishart.yale.edu/id/object/5005] resolves through content negotiation to the above URL
- (+) All [#Images], including different [#Image Derivations] and [#Deep Zoom Image]

h3. Representing Related Resources

An important question is how to represent these related resources and how to link them to the object. CRM doesn't have specific classes for "web page" or "XML record" but E31_Document is appropriate: "identifiable immaterial items that make propositions about reality. These propositions may be expressed in text, graphics, images, audiograms, videograms or by other similar means. Documentation databases are regarded as a special case of E31 Document." (Therefore a single XML record is also E31_Document). See [document_references@crmg], [reference@crmg]

It's also nice to include the media type of these documents (dc:format).
- for web pages that's "text/html"
- for LIDO we use "text/xml". There's no registration for LIDO specifically, so we follow [RFC 3023: XML Media Types|http://www.ietf.org/rfc/rfc3023.txt]: "If an XML document -- that is, the unprocessed, source XML document -- is readable by casual users, text/xml is preferable. Application/xml is preferable when the XML MIME entity is unreadable by casual users."

(-) Representation:
{noformat}
<http://collection.britishart.yale.edu/id/object/5005> P70i_is_documented_in
<http://collections.britishart.yale.edu/vufind/Record/1669236>,
<http://collections.britishart.yale.edu/oaicatmuseum/OAIHandler?verb=GetRecord&identifier=oai:tms.ycba.yale.edu:7&metadataPrefix=lido>,
<http://discover.odai.yale.edu/ydc/Record/1669236>,
<http://www.google.com/culturalinstitute/asset-viewer/mrs-abington-as-miss-prue-in-love-for-love-by-william-congreve/tQHBb0Q2MZF2uQ>.
<http://collections.britishart.yale.edu/vufind/Record/1669236>
a E31_Document; dc:format "text/html"; P2_has_type <thes/document/home-page>.
<http://collections.britishart.yale.edu/oaicatmuseum/OAIHandler?verb=GetRecord&identifier=oai:tms.ycba.yale.edu:7&metadataPrefix=lido>
a E31_Document; dc:format "text/xml"; P2_has_type <thes/document/lido-xml>.
<http://discover.odai.yale.edu/ydc/Record/1669236>
a E31_Document; dc:format "text/html"; P2_has_type <thes/document/ydc-page>.
<http://www.google.com/culturalinstitute/asset-viewer/mrs-abington-as-miss-prue-in-love-for-love-by-william-congreve/tQHBb0Q2MZF2uQ>
a E31_Document; dc:format "text/html"; P2_has_type <thes/document/google-art-page>.
{noformat}
(?) Optionally, you could add Creation records to state who created the above documents.

(-) We already use E31_Document for Bibliography. For symmetry, we should add P2_has_type:
{noformat}
<http://collection.britishart.yale.edu/id/object/80>
crm:P70i_is_documented_in <http://collection.britishart.yale.edu/id/bibliography/1075>.
<http://collection.britishart.yale.edu/id/bibliography/1075> a crm:E31_Document ;
P2_has_type <thes/document/bibliography>;
rdfs:label "David Lee, Ladies of the Knight, Arts Review, Vol. 47, May 1995, pp. 26-29, N1 A792 + (A & A)" .
{noformat}

(-) The type terms mentioned above:
{noformat}
<thes/document/home-page> a E55_Type, skos:Concept; skos:inScheme <thes/document>;
skos:prefLabel "Home page (VUFind record)".
<thes/document/lido-xml> a E55_Type, skos:Concept; skos:inScheme <thes/document>;
skos:prefLabel "LIDO XML record".
<thes/document/ydc-page> a E55_Type, skos:Concept; skos:inScheme <thes/document>;
skos:prefLabel "Yale Digital Collections Center page".
<thes/document/google-art-page> a E55_Type, skos:Concept; skos:inScheme <thes/document>;
skos:prefLabel "Google Cultural Institute (Google Art) page".
<thes/document/bibliography> a E55_Type, skos:Concept; skos:inScheme <thes/document>;
skos:prefLabel "Bibliography".

<thes/document> a skos:ConceptScheme; skos:prefLabel "Document Type".
{noformat}

h2. Images

h3. Image Metadata

Yale keeps numerous image assets, and Yale ODAI provides extensive metadata about the images:
- documentation: [https://docs.google.com/document/d/1rfUHjy_YvVC5fSIsB4aCi5-t2ZhNYrDui-L9EEXXm9g/edit]

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 | http://deliver.odai.yale.edu/content/id/482f519c-eebf-4596-819c-4c8197c4d3e5/format/1 | logical URL (request this) |
| ./source | http://b02.deliver.odai.yale.edu/48/2f/482f519c-eebf-4596-819c-4c8197c4d3e5/ba-obj-7-0001-pub-sm.jpg | physical URL (redirects to it) |
| ./bucketDNS | b02.deliver.odai.yale.edu | physical server |
| ./bucketName | b02.deliver.odai.yale.edu | 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 | http://hdl.handle.net/10079/gb5mkww | redirects to http://britishart.yale.edu/collections/using-collections/image-use |
| ./usageTerms | http://hdl.handle.net/10079/gb5mkww | always same(?) |
| ./imageCopyrightNotice | | always(?) empty |
| ./imageCopyrightMarked | false | always(?) false |
| ./assetId | d70ae2b604a64bd24809441a5d24233a8d406925 | another GUID |
| X/contentId | 482f519c-eebf-4596-819c-4c8197c4d3e5 | GUID, same as above |
| *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 | [http://deliver.odai.yale.edu/content/id/482f519c-eebf-4596-819c-4c8197c4d3e5/format/1] | logical URL (request this) |
| ./source | [http://b02.deliver.odai.yale.edu/48/2f/482f519c-eebf-4596-819c-4c8197c4d3e5/ba-obj-7-0001-pub-sm.jpg] | physical URL (redirects to it) |
| ./bucketDNS | b02.deliver.odai.yale.edu | physical server |
| ./bucketName | b02.deliver.odai.yale.edu | 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 | Only the Yale unit that created the image should have access |
| ./cas | false | Login through CAS is required (campus-only access) |
| ./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 | [http://hdl.handle.net/10079/gb5mkww] | redirects to [http://britishart.yale.edu/collections/using-collections/image-use] |
| ./usageTerms | [http://hdl.handle.net/10079/gb5mkww] | always same(?) |
| ./imageCopyrightNotice | | always(?) empty |
| ./imageCopyrightMarked | false | always(?) false |
| ./assetId | d70ae2b604a64bd24809441a5d24233a8d406925 | another GUID |
| X/contentId | 482f519c-eebf-4596-819c-4c8197c4d3e5 | GUID, same as above |

Questions:

h3. Image URLs

ODAI has several URLs that redirect to the physical URL:
# (x) Using object id:
eg [http://deliver.odai.yale.edu/content/repository/YCBA/id/ba-obj-7-0001-pub.tif/format/2]
#- 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:&nbsp;
{jira:RS-1920}
#- for format/1,2,3,6
{noformat}http://deliver.odai.yale.edu/content/id/<contentId>/format/<Y>{noformat}
{noformat}http://scale.ydc2.yale.edu/iiif/<contentId>{noformat}

| *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 [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 [http://scale.ydc2.yale.edu/iiif/279ce6c0-c584-43e4-a5b4-5af2c90b82a0] |

In the sections below we use these image aliases for brevity. In RDF the actual http URL should be used. *Not* a "made up" node with P1_is_identified_by pointing to the actual URL

h3. Image Sizes Formats

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] |
| *url suffix* | *format code* | *format label* | *width* | *file type* | *use in RS* |
| format/1 | sm | Screen small | 250 | jpeg | result list thumbnail (or could use 2) |
| format/2 | med | Screen medium | 480 | jpeg | lightbox, object view, data basket preview |
| format/3 | large | Screen large | 1920 | jpeg | |
| format/6 | print-lg | Print large | 3000 | tiff | |
| format/7 | JPEG2000 \\ | 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 [http://collections.britishart.yale.edu/vufind/Record/1669236] has:
This URL doesn't return anything, but you can append parameters to get what you need.
- the tile URLs are of this form:
[http://scale.ydc2.yale.edu/iiif/1b747e8f-7754-482c-b5a2-9e1dc1986f4b/0,2048,1024,1024/\!256,256/0/native.jpg|http://scale.ydc2.yale.edu/iiif/1b747e8f-7754-482c-b5a2-9e1dc1986f4b/0,2048,1024,1024/!256,256/0/native.jpg]
- If you request a non-existing GUID, you get "Error: No response from server [http://scale.ydc2.yale.edu/iiif]". Occasionally I get the same error for an existing GUID, but that is a temporary outage
- another client that also implements IIIF tiles is OpenSeadragon (and one can get sample code to implement the same):
[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
We need to implement IIIF support in RS Image Annotation, and multiplexing between IIP and IIIF

[#Image Metadata]:
- The URL included in the metadata (X/derivatives/7/url), eg [http://deliver.odai.yale.edu/content/id/1b747e8f-7754-482c-b5a2-9e1dc1986f4b/format/7], is not appropriate since it serves the whole image.
- One should concatenate the server URL [http://scale.ydc2.yale.edu/iiif/] 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). Flags.
Eg the lovely Miss Prue [http://collections.britishart.yale.edu/vufind/Record/1669236] has 8 image views, each with 1..3 comma-separated Flags:
[^5005-images.html]
{html}

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

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

h3. Image Flags

The views have these Flags (Aspects), coming from&nbsp;contentSet/content/metadata@caption which is&nbsp;comma-separated:
0. cropped to image, recto, unframed (0 is always the Main View)
1. recto, unframed

Lec: these strings are not from a controlled thesaurus, so people can put anything.
Vlado: it still seems to me they are fairly consistent, so Yale could represent this by breaking on space and making a thesaurus:
For now I think it's enough to lump them in one thesaurus, eg:
{noformat}

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.
<http://britishart.yale.edu/collections/using-collections/image-use> a E30_Right; rdfs:label "See link for details".
{noformat}
-- (-) don't use rdfs: label for an URL (label should be a readable string).
{noformat}
<http://collection.britishart.yale.edu/collections/using-collections/image-use> a crm:E30_Right ;
rdfs:label "http://hdl.handle.net/10079/gb5mkww" .
{noformat}
If you like you can make this an E42_Identifier, though I don't see what use that URL is
{noformat}
<http://collection.britishart.yale.edu/collections/using-collections/image-use> a crm:E30_Right ;
P48_has_preferred_identifier <http://hdl.handle.net/10079/gb5mkww>.
<http://hdl.handle.net/10079/gb5mkww> a E42_Identifier.
{noformat}

Discussion:

h3. Image Representation
(-) both of these are wrong, see [image_objects_carriers@crmg]

(See image aliases in the [#Image URLs] table)
- (-) The correct properties to use are:
{noformat}
<object/7> bmo:PX_has_main_representation <view0/format2> . # Main View
<object/7> P138i_has_representation <view1/format2> . # other views
<object/7> P138i_has_representation <view2/format2> . # ...
{noformat}
- both of these are wrong, see [image_objects_carriers@crmg]
{noformat}
<object/7> P62_depicts <object/7/image/1> .
<object/7> P65_shows_visual_item <object/7/image/1> .
{noformat}
- The correct properties to use are:
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:
{noformat}
<object/7> bmo:PX_has_main_representation <http://deliver.odai.yale.edu/content/repository/YCBA/object/7/image/0/format/2> . # Main View
<object/7> P138i_has_representation <http://deliver.odai.yale.edu/content/repository/YCBA/object/7/image/1/format/2> . # other views
P138i_has_representation <view0/format2>
bmo:PX_has_main_representation <view0/format2>
{noformat}
- 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
h3. Image Derivation

We connect only format2 directly to the object (PX_has_main_representation or P138i) and declare all formats derivatives thereof (P130i).
This is a trick required by RS, so it can show only one format on screen, and provide links for the rest (as in [#Image Views]):
{noformat}
P138i_has_representation <http://deliver.odai.yale.edu/content/repository/YCBA/object/5005/type/2/format/1>
bmo:PX_has_main_representation <http://deliver.odai.yale.edu/content/repository/YCBA/object/5005/type/2/format/1>
<object/7> bmo:PX_has_main_representation <view0/format2> .
<view0/format2> P130i_features_are_also_found_on <view0/format1>, <view0/format2>, <view0/format3>, <view0/format6>, <view0/format7>.

<object/7> P138i_has_representation <view1/format2> .
<view1/format2> P130i_features_are_also_found_on <view1/format1>, <view1/format2>, <view1/format3>, <view1/format6>, <view1/format7>.

...
{noformat}

h3. Image Creation

- (-) this is wrong
{noformat}
-- Vladimir: ok, but use the correct type and properties for Image (a conceptual object), and YCBA's URL:
{noformat}
<object/7/image/1> P94i_was_created_by <object/7/image/1/creation>.
<viewX/formatY> P94i_was_created_by <viewX/creation>.
<object/7/image/1/creation> <viewX/creation> a E65_Creation; P14_carried_out_by <thesauri/ULAN/500303557>.
{noformat}
[#Image Metadata] shows that all derivations (formats) share the same source&imageCredit, but each view has individual source&imageCredit.

h3. Image Derivation
We connect only format2 directly to the object (P138i) and declare the other formats derivatives thereof (P130i)
{noformat}
<object/7> P138i_has_representation <view0/format2> .
<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.
- 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|http://www.shared-canvas.org/datamodel/spec/#Annotation]: DC and EXIF, but skip filename and sizeBytes
exif:width 359 ;
dc:format "image/jpeg" ;
P94i_was_created_by <http://collection.britishart.yale.edu/id/object/7/image/creation>; <view0/creation>;
P130i_features_are_also_found_on <view0/format1>, <view0/format2>, <view0/format3>, <view0/format6>, <view0/format7>.

# other formats
P104_is_subject_to <http://britishart.yale.edu/collections/using-collections/image-use> ;
bmo:PX_image_format <yale/thes/image/format/sm> ;
exif:height 249 ; #
exif:width 186 ;
dc:format "image/jpeg" ;
P94i_was_created_by <http://collection.britishart.yale.edu/id/object/7/image/creation>. <view0/creation>.
# format3,6 are similar and differ only by size and dc:format

# Deep Zoom format. Same as above, with an extra statement
<http://deliver.odai.yale.edu/content/repository/YCBA/object/7/image/0/format/7> <view0/format7>
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> ;
bmo:PX_image_format <yale/thes/image/format/JPEG2000> ;
exif:height 4279 ; #
exif:width 3201 ;
dc:format "image/jp2" ;
P94i_was_created_by <http://collection.britishart.yale.edu/id/object/7/image/creation>; <view0/creation>;
# It's on an IIIF server. Statement suggested by Michael Appleby
dct:conformsTo <http://library.stanford.edu/iiif/image-api/1.1/conformance.html#level1>.

# view0 Creation event (shared by all formats)
<view0/creation> a E65_Creation;
P14_carried_out_by <ulan/500303557>; # lookup "source" in thesaurus
rdfs:label "Digital Image: Yale Center for British Art". # imageCredit

# other views: 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>;
exif:width 438 ;
dc:format "image/jpeg" ;
P94i_was_created_by <http://collection.britishart.yale.edu/id/object/7/image/creation>; <view1/creation>;
P130i_features_are_also_found_on <view1/format1>, <view1/format2>, <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
<http://collection.britishart.yale.edu/id/object/7/image/creation>
a E65_Creation;
P14_carried_out_by <thesauri/ULAN/500303557>;
# view1 Creation event (shared by all formats)
<view1/creation> a E65_Creation;
P14_carried_out_by <ulan/500303557>; # lookup "source" in ULAN thesaurus
rdfs:label "Digital Image: Yale Center for British Art". # imageCredit
{noformat}

- (-) Denote pixels as xsd:integer.
Turtle allows a short way:
{noformat}
exif:height 480 ; # is xsd:integer
exif:width 359 ;
{noformat}
If you prefer to use quotes, then you need to put the type explicitly:
{noformat}
exif:height "186"^^xsd:integer ;
exif:width "249"^^xsd:integer ;
{noformat}

- (-) Shorten the URL a bit:
-- in this URL: <[http://collection.britishart.yale.edu/id/object/482f519c-eebf-4596-819c-4c8197c4d3e5/image/creation]>
-- the image URL is: <[http://collection.britishart.yale.edu/id/object/482f519c-eebf-4596-819c-4c8197c4d3e5]>
-- so you don't need to append "/image" to it, use <[http://collection.britishart.yale.edu/id/object/482f519c-eebf-4596-819c-4c8197c4d3e5/creation]>

h2. Depiction

Couple issues here:
{noformat}
# (-) image/X: don't use such made up nodes, use actual image URLs. See [#Image RDF]

h2. IconClass

See [IconClass#IconClass Use at YCBA]:
- (-) Emit P129 for each use
- (-) Emit Iconclass term data

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.

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:

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):
- (-) This is wrong, it should describe the specific sub-organization (department) (see [YCBA sub-orgs|#YCBA sub-orgs]?):
{noformat}
crm:P50_has_current_keeper <http://collection.britishart.yale.edu/id/thesauri/department> ;
{noformat}
If you don't have departments, don't say anything (you already say that YCBA is the keeper).
\\
Emmanuelle: &nbsp;We do pass departments designations to our XML files in the OAI&nbsp;<setSpec>{color:#000000}ycba:ps{color}</setSpec>. &nbsp;Frames are included in the Paintings & Scupture department.

h2. Current Location

You currently use per-object place representations. Such places are not searchable since they're not in a thesaurus.
{noformat}

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]

h3. Copyrighted

There are some objects that are copyrighted. Let's consider one:
- view: [http://collections.britishart.yale.edu/vufind/Record/1669290]

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

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
- -FB-finished by-
- \-M-maker\-
- R-printer (printed by)
- PM-printmaker (print made by)
- Z-publisher (published by)
- TU-touched up by (print)
- \-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

Use [http://collection.britishart.yale.edu/id/thesauri/production/|http://collection.britishart.yale.edu/id/thesauri/production/]
| crm:P14_carried_out_by | *R* | printed by |
| crm:P14_carried_out_by | *Z* | published by |
| crm:P14_carried_out_by | *5* | Drawn by |
| crm:P14_carried_out_by | *P* | Painted by |
| crm:P14_carried_out_by | *M* | Made by |
These codes mean the same:
| crm:P14_carried_out_by | *PM* | print made by |
| crm:P14_carried_out_by | *TU* | touched up by |
| crm:P14_carried_out_by | *E* | Engraved by |
| crm:P14_carried_out_by | *AQ* | Aquatinted by |
| crm:P14_carried_out_by | *VEB* | Variously engraved by |
| crm:P14_carried_out_by | *EB* | engravings by |

h3. Formerly Attributed To

object/7: "Formerly attributed to Benjamin Williams Leader" is mapped without any mention of "Formerly attributed":
{noformat}
<http://collection.britishart.yale.edu/id/object/7/production/1> a crm:E12_Production ;
crm:P14_carried_out_by <http://collection.britishart.yale.edu/id/person-institution/1180> .
{noformat}

- (-) Qualify Production with an EX_Association having type <thes/likelihood/formerly-attributed>.
See [BM Association Mapping v2#Probably/Unlikely Produced By]
- (?) What other lido:attributionQualifierActor have you got?
- (+) &nbsp;Emmanuelle: these are YCBA attribution qualifiers (also documented in&nbsp;[https://confluence.ontotext.com/display/ResearchSpace/Meta-Thesaurus+and+FR+Names&#124;../../../../../../../../../../display/ResearchSpace/Meta-Thesaurus+and+FR+Names&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;&#124;\||]&nbsp;as&nbsp;[http://collection.britishart.yale.edu/id/thesauri/likelihood|http://collection.britishart.yale.edu/id/thesauri/likelihood]):&nbsp;Attributed to, Formerly, Formerly attributed to, After, Follower of, Imitator of, Style of, Circle of, Studio of, Workshop of

h3. Production Qualification

Look in [LIDO:29334|http://collections.britishart.yale.edu/oaicatmuseum/OAIHandler?verb=GetRecord&metadataPrefix=lido&identifier=oai:tms.ycba.yale.edu:29334]. Search for "Object related role": there are 2 actors and a qualification:
| *Actor* | *Role* | *Qualification* |
| Samuel Palmer | Printmaker | Print made by |
| Alfred Herbert Palmer | Printmaker | completed by |

As you see in [BM Association Mapping v2#Produced By Specific Process], BM models "Printmaker" as a production sub-event with P2_has_type <printing> and P14_carried_out_by <actor>. They don't have a Qualification as you have above.
- Emmanuelle: I thought BM was using Qualifications as well? &nbsp;Here a BM record with "Drawn by Elizabeth Emily Murray":
[http://www.britishmuseum.org/research/collection_online/collection_object_details.aspx?objectId=739275&partId=1&people=113629&peoA=113629-2-9&page=1]
- Vladimir: see the data at
[http://test.researchspace.org:8081/resource?uri=http://collection.britishmuseum.org/id/object/PDB15015]
I think the relevant production fact is
[http://test.researchspace.org:8081/resource?uri=http://collection.britishmuseum.org/id/object/PDB15015/production/3]
and it says that Emily Ruskin carried out a Production with P2_has_type <thesauri/production/drawing>.
No qualification whether she started, completed, or whatever

You have 2 options:
# Further split up the production type <thesaurus/technique/printmaker> into <thesaurus/technique/printmaker/print_made_by> and <thesaurus/technique/printmaker/completed_by>.
#- This is not faithful because "completed by" is not related in any way to printing. It's about who started something and who finished it, a pattern that can apply to any production technique (e.g. someone made a cast and another made the final sculpture from it).
#- Emmanuelle: I beg to differ. &nbsp;In this case what is implied for Alfred Palmer when his name is prefaced with 'completed by' is that we suspect that he etched and printed the plate. &nbsp;This is a case where further research will precisely identify his role, which in turn will change his roles and qualifications. &nbsp;Regardless of Alfred Palmer's role, however, it absolutely has to do with printing. &nbsp;
#- Vladimir: What I mean is that "completing" something is applicable not just for Printing, but for other processes as well (eg making a sculpture from a cast).
If you use "completed by" only for Printing, then you should call it "Print completed by" to be more specific.
# (-) Model the Qualification as a [Reified Association|BM Association Mapping v2#Translated Code In Reified Association]. An example application of this pattern is [production attribution (probably/unlikely)|BM Association Mapping v2#Probably/Unlikely Produced By].
{noformat}
<prod> P9_consists_of <prod/1>,<prod/2>.
<prod/1> P14_carried_out_by <SamuelPalmer>; P2_has_type <thesaurus/technique/printmaker>.
<prod/1/association> a bmo:EX_Association;
P140_assigned_attribute_to <prod/1>; P141_assigned <SamuelPalmer>; bmo:PX_property P14_carried_out_by;
P2_has_type <thesaurus/qualification/made_by>.
<prod/2> P14_carried_out_by <AlfredHerbertPalmer>; P2_has_type <thesaurus/technique/printmaker>.
<prod/2/association> a bmo:EX_Association;
P140_assigned_attribute_to <prod/2>; P141_assigned <AlfredHerbertPalmer>; bmo:PX_property P14_carried_out_by;
P2_has_type <thesaurus/qualification/completed_by>.
{noformat}
#- Emmanuelle: I have no objections against Reified Association but it seems given the&nbsp;(-) &nbsp;before it that you/Vladimir already decided against it?
#- Vladimir: everywhere in this page, the red minus means Yale should do something (and change it to a green plus)

| CB: commenced by |
| CPB:&nbsp;completed by |
| FB:&nbsp;finished by |


h3. Probably/Unlikely Produced By

* *Probably*

*A*: Attributed to


*PA*: Print attributed to

*&nbsp; &nbsp; &nbsp;* *AO*: attributed to office of

*&nbsp; &nbsp; &nbsp;* *PR*: perhaps

*&nbsp; &nbsp; &nbsp;* *PRB*: perhaps by

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *PRA*: perhaps with assistance from

*&nbsp; &nbsp; &nbsp;*{*}PO*: possibly

*&nbsp; &nbsp; &nbsp;*{*}POB*: possibly by

*&nbsp; &nbsp; &nbsp;* *OPO*: or possibly

*&nbsp; &nbsp;* *COPO*: Circle of or possibly
* *Unlikely*

*AE*: Formerly attributed to:&nbsp;



h3. Use P14_carried_out_by and thesaurus/likelihood


h3. Influenced By

(-) "After" (and other similar codes) should be mapped to P15_was_influenced_by, with EX_Association and P2 code that says "after". See [BM Association Mapping v2#Influenced By] or Dominic’s document sec 6.6.16. Jana checked the document: a separate Production node is used in this case.

The current representation uses P14_carried_out_by for both "created" and "after" which is incorrect:
{noformat}
<http://collection.britishart.yale.edu/id/object/34464/production> a crm:E12_Production ;
crm:P9_consists_of <http://collection.britishart.yale.edu/id/object/34464/production/1> , <http://collection.britishart.yale.edu/id/object/34464/production/2> .

<http://collection.britishart.yale.edu/id/object/34464/production/1> a crm:E12_Production ;
crm:P14_carried_out_by <http://collection.britishart.yale.edu/id/person-institution/3732> ;
crm:P2_has_type <http://collection.britishart.yale.edu/id/thesauri/production/artistic_production> ;
crm:P4_has_time-span <http://collection.britishart.yale.edu/id/object/34464/production/1/date> .

<http://collection.britishart.yale.edu/id/object/34464/production/2> a crm:E12_Production ;
crm:P14_carried_out_by <http://collection.britishart.yale.edu/id/person-institution/6418> ;
crm:P2_has_type <http://collection.britishart.yale.edu/id/thesauri/production/artistic_production> .
{noformat}


Use P15_was_influenced_by

*AT*: After

*ATPO*: After possibly

*POAT*: possibly after

*ATPOB*: after possibly based on a model by

*AF*:&nbsp;follower of

*AI*: imitator of

*AL*: Manner/style of

h2. Production Authority


h3. Production Motivated By

*CO*: Commissioner

h2. Unknown Artist
{status:title=postponed|color=gray} Some records say "production performed by Unknown Artist".
- 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".

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

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

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

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

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

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

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

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


h3. Closely Related Group

- 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: [http://research.ng-london.org.uk/wiki/index.php/Category:EN41-Artist_Sub_Group]:
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.
-- 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:
<object/7/production/3> crm:P14_carried_out_by <unknown> .
{noformat}
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".


*Closely Related Group association codes:*

AG; studio of
W: workshop of
AJ: circle of


*Produced by Closely Related Individual:*

N: Pupil of



h2. Curatorial Comment

- (-) Yale: PX_curatorial_comment needs date and author added to the data model
- {jira:RS-1926}
- Vlado: easy to tackle with EX_Association, which is is a subclass of E13_Attribute_Assignment (see [attribute_assignment@crmg] and [recorder@crmg]):
{noformat}
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. "2013-07-06"^^xsd:date.
{noformat}
-- 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

{jira:RS-1925}
- Obviously in P141 you need to put the actual PX_curatorial_comment string, not the word "comment".
- Use a XSD type that corresponds to the date's resolution:
P82_at_some_time_within "2007-01"^^xsd:gYear : should use gYearMonth

h2. Inscriptions

Please include TTL samples with Inscription info.
- [http://collections.britishart.yale.edu/vufind/Record/1670022]
skos:prefLabel "Lettering"; skos:inScheme <thes/inscription/>.
{noformat}
- Inscription, Signed and Dated and Lettering should all be mapped to E34_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
h3. Marks

(-) Marks are different: unlike E34_Inscription, E37_Mark is not a subclass of E33_Linguistic_Object (see [cidoc_class_hierarchy@crmg]) so they should *not* include label/transcription.
Eg [object/14670|http://collections.britishart.yale.edu/oaicatmuseum/OAIHandler?verb=GetRecord&identifier=oai:tms.ycba.yale.edu:14670&metadataPrefix=lido] has LIDO:
{code:xml}
<lido:inscriptions lido:type="Marks">
<lido:inscriptionTranscription>Paul Mellon collector's mark</lido:inscriptionTranscription>
</lido:inscriptions>
{code}
and should be mapped to
{noformat}
<http://collection.britishart.yale.edu/id/object/14670> P65_shows_visual_item
<http://collection.britishart.yale.edu/id/object/14670/inscription/1>. # "mark" would be more accurate but will complicate the mapping
<http://collection.britishart.yale.edu/id/object/14670/inscription/1> a E37_Mark;
rdfs:label "Paul Mellon collector's mark";
P2_has_type <thes/inscription/marks>. # could skip since it says nothing more than E37_Mark
{noformat}

- (?) Emmanuelle: What about when the data only says ‘watermark’ or ‘stamp’?&nbsp; Since it is not a transcription of the mark per se, do we still model as if it were a transcription?
-- Vlado: I think it would be too hard to determine from the word whether that's a true inscription, or a curator's description of a mark. So I suggest to rely on lido:type alone: map Marks to E37_Mark, and the other 3 types to E34_Inscription

h3. Not Marked

(-) "not marked" should be ignored (emit nothing), eg [object/41229|http://collections.britishart.yale.edu/oaicatmuseum/OAIHandler?verb=GetRecord&identifier=oai:tms.ycba.yale.edu:41229&metadataPrefix=lido]:
{code:xml}
<lido:inscriptions lido:type="Marks">
<lido:inscriptionTranscription>not marked</lido:inscriptionTranscription>
</lido:inscriptions>
{code}

- (?) Emmanuelle: Two other similar fields are problematic in our data: Signed and Inscriptions.&nbsp; They are problematic because, on the model of the marks field above, they record both the transcriptions of the signatures and inscriptions as well as the fact that we may have searched for a signature and inscription on a work but did not find any and consequently these fields may carry the value: not signed, not dated, no inscription.
The variations on these 3 values are multiple, unfortunately (not inscribed,…)&nbsp; In order to not emit administrative data about signatures and inscriptions (not signed, not dated, no inscription), we would need to filter out all of these variations
-- Vlado: I see the difficulty. Ok, let's not do such filtering, and just emit the strings as they are. (Semweb says not to record missing facts, but here you've recorded the fact that you searched for it and none was found)
- all Signed and Inscriptions values that do not contain “”.&nbsp; The double quotation marks are a sure sign that a transcription is recorded. &nbsp;Is it possible?
-- Vlado: I think that giving meaning to punctuation is too brittle: maybe some curators didn't use them, or used slightly different punctuation...
I say cancel this whole section

h2. Dimensions

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


You state object dimensions (including their properties):
{noformat}
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:extentMeasurements>Support (PTG)
{code}
- (?) If you have data with lido:qualifierMeasurements, we should also consider it

You can add it like this:
- &nbsp;I assume "Support (PTG)" is a (semi-)controlled value, so better make a term:
{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 ;
P2_has_type <thes/measurement/Support-PTG> ;
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)" .

<thes/measurement/Support-PTG> a skos:Concept, E55_Type;
skos:inScheme <thes/measurement/>;
skos:prefLabel "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. Period/Culture

This ain't mapped: object/7:
{code:xml}
<lido:culture>
<lido:conceptID lido:source="AAT" lido:type="local">300111159
<lido:term>British
{code}

Yale uses the field lido:culture and a term from the AAT Styles and Periods facet.
Previously we mapped BM's Period/Culture field to crm:E4_Period (see [BMX Issues#Specific CRM Constructs] and again [BMX Issues#Period/Culture]).
These are slightly different concepts but closely related, so the mapping is correct:
- LIDO: culture: "culture, cultural context, people, or also a nationality"
- AAT: Styles and Periods: "names of art and architecture styles, historical periods, and art movements. Names of cultures, peoples, individuals, and sites are included only if they designate styles or periods (e.g.g., Yoruba, Celtic, Louis XIV). Geographic descriptors are included only for broad cultural regions and nations."
- CRM: E4_Period: "sets of coherent phenomena or cultural manifestations bounded in time and space. It is the social or physical coherence of these phenomena that identify an E4 Period and not the associated spatio-temporal bounds."

(-) Map to:
{noformat}
<object/7/production/1> crm:P10_falls_within aat:300111159.
aat:300111159 a skos:Concept, crm:E4_Period;
skos:inScheme aat_periods: ;
skos:prefLabel "British".
{noformat}
The scheme is defined in [Meta-Thesaurus|#Meta-Thesaurus].

(-) &nbsp;Periods are complex cultural phenomena that may have time and place dimensions, even a union of such dimensions (think of Fascism). These are not Periods, they are mere Time-Spans:&nbsp;16th century, 17th century, 18th century, 16th century-17th century.

h2. Material and Technique

lido:termMaterialsTech has 3 types:
- support (eg laid paper, wove paper, canvas)
- medium (eg graphite, watercolor, oil paint, gold leaf)
- technique (eg etching, mezzotint, original gilding, oil gilding)

(?) Do you know of any other types?

(!) You seem to map only "support". Maybe related to [#Term Code Discrepancy]. Map all of them:
- support and medium (AAT Materials facet) to P45_consists_of (E57_Material)
- technique (AAT Processes and Techniques facet) to P32_used_general_technique (E55_Type)

For example:
{noformat}
<object/64421>
P45_consists_of
aat:300011914, # wood
aat:300264831. # gold leaf
<object/64421/production>
P32_used_general_technique
aat:300230058, # oil gilding
<thes/technique/original_gilding>. # original gilding
{noformat}

h2. Object Type and Genre

&nbsp;(+) &nbsp;resolved issue



(-) Object Type and Genre (lido:objectWorkType) are missing, eg
{code:xml}
<lido:objectWorkType>
- There is a term for the 1st but it's not connected to the object.
{noformat}<http://collection.britishart.yale.edu/id/thesauri/AAT/300033618>{noformat}
- You try to make a term for the 3rd but seems seem to look it up in the wrong thesaurus (it's local not AAT):
{noformat}
<http://collection.britishart.yale.edu/id/thesauri/AAT/-1> a crm:E55_Type , skos:Concept ;
{noformat}

I'd represent the first 2 as "type" and the last one as "subject":
Represent "Object name" as "type" (P2_has_type) and "Genre" as "subject" (P62_depicts):
{noformat}
<http://collection.britishart.yale.edu/id/object/7>
P2_has_type <http://vocab.getty.edu/aat/300033618>,; # painting
<http://vocab.getty.edu/aat/300015636>; # landscape
P62_depicts <http://collection.britishart.yale.edu/id/thesauri/subject/7>. # architectural subject
P62_depicts <http://vocab.getty.edu/aat/300015636>; # landscape
<http://collection.britishart.yale.edu/id/thesauri/genre/7>. # architectural subject

<http://collection.britishart.yale.edu/id/thesauri/genre/7> a skos:Concept, E55_Type;
skos:inScheme <http://collection.britishart.yale.edu/id/thesauri/genre/>;
skos:prefLabel "architectural subject".
{noformat}

- Note1: 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. YCBA
- Note2: don't be confused like me that "landscape" above means "painting in landscape orientation", which is a subtype (describes *is*\-ness of the object).
It means "a landscape is painted", as you can see in [Abstract Landscape (Dark Fir Shoreham II Morning)|http://collections.britishart.yale.edu/vufind/Record/1666154] which is in portrait orientation

h2. Collection

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

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

h2. Classification

LIDO XML has a field <lido:classification> that's similar to <lido:objectWorkType>. LIDO defines them like this:
- objectWorkType: The specific kind of object / work being described.
- classification: Concepts used to categorize an object / work by grouping it together with others on the basis of similar characteristics. The category belongs to a systematic scheme (classification) which groups objects of similar characteristics according to uniform aspects. This grouping / classification may be done according to material, form, shape, function, region of origin, cultural context, or historical or stylistic period. In addition to this systematic grouping it may also be done according to organizational divisions within a museum (e.g., according to the collection structure of a museum).

Which leaves me a bit puzzled how to map "classification": object type or "sub-collection".
- I wrote a little script to extract these 2 fields from Yale data:
{code:bash} egrep -A1 'type="(Classification|Object name)"' * | perl -pe "s{.*edu_(\d+).*?>([^<]*)(<.*)?}{$1: $2}" {code}
- For many Yale objects, objectWorkType and classification are the same (painting, scuplture, frame, etc)
- For some objects (4 of 13) there are differences:
| *object* | *ObjectWorkType* | *classification* | *n* |
| 4005 | 999 No ObjectWorkType for Record | 300041273 Print | 1 |
| 15206 | 300033973 drawing; 300078925 watercolor | 300033973 Drawing & Watercolor | 2 |
| 19850 | 300033973 drawing | 300033973 Drawing & Watercolor | 3 |
| 21890 | 300041338 intaglio print | 300041273 Print | 4 |
| 57163 | 300255019 cake; 300047090 sculpture | 300047090 Sculpture | 5 |

Analysis of the differences:
# Missing ObjectWorkType but Classification exists.
Object type is a fairly important field, so it's not very good for it to be missing.
(-) If ObjectWorkType=999, use Classification for P2_has_type
# and 5. Several ObjectWorkTypes, Classification reflects just one of them.
Perhaps Corresponds to interpreting Classification as "sub-collection".
# ObjectWorkType and Classification are the same, just that a different label "Drawing & Watercolor" has been used
(the official AAT label is "drawings (visual works)")
# ObjectWorkType is a sub-division of Classification.
Corresponds to interpreting Classification as "sub-collection"

As described in the prev section, none of these terms is connected to the object in RDF.
- (-) Check whether lido:classification is always consistent with the collection (eg classification="Sculpture" is always found in "Paintings and Sculpture")
- (-) Map lido:classification to a sub-collection (1)
{noformat}
<object/57163> P2_has_type aat:300255019, aat:300047090; # cake, sculpture.
P46i_forms_part_of
<id/collection/sculpture>, # (1) comes from Classification
<id/collection/paintings-and-sculptures>. # (2) comes from Collection

<id/collection/paintings-and-sculptures> a E78_Collection; rdfs:label "Paintings and Sculptures".
<id/collection/sculpture> a E78_Collection; rdfs:label "Sculpture";
P46i_forms_part_of <id/collection/paintings-and-sculptures>.
{noformat}

If Classification is consistent with Collection then statement (2) is redundant because P46i_forms_part_of is transitive

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.
But YCBA has other object types (Prints, Drawings, Sculpture, Paintings, Frames, even Cakes\!), for which the mapping could be slightly different.
- (!) Lec to include various object types in the samples
- The available Search fields and [#Classification] vary by collection

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

{table-plus:columnTypes=S,I|autoTotal=true}
|*collection*|*count*|*search, | *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%5B]="Paintings+and+Sculpture"&type0%5B]=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%5B]="Prints+and+Drawings"&type0%5B]=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%5B]="Rare+Books+and+Manuscripts"&type0%5B]=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%5B]="Reference+Library"&type0%5B]=collection_facet] |
| Frames | 1376 |[search|http://britishart.yale.edu/collections/search/frames] [browse|http://collections.britishart.yale.edu/vufind/Search/Results?lookfor0%5B]="Frames"&type0%5B]=collection_facet] |
| Paintings and Sculpture | 2226 | [search|http://britishart.yale.edu/collections/search/paintings-and-sculpture] [browse|http://collections.britishart.yale.edu/vufind/Search/Results?lookfor0%5B%5D="Paintings+and+Sculpture"&type0%5B%5D=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%5B%5D="Prints+and+Drawings"&type0%5B%5D=collection_facet] |
| Frames | 1376 | [search|http://britishart.yale.edu/collections/search/frames] [browse|http://collections.britishart.yale.edu/vufind/Search/Results?lookfor0%5B%5D="Frames"&type0%5B%5D=collection_facet] |
{table-plus}

TODO TODO TODO:
Prints, Drawings, Sculpture (even Cakes!), Paintings, Frames, Folios, Books
- Collections that are out of scope for now:
Eg see [MARC21|http://columbus.library.yale.edu:8055/OAI_Orbis/src/OAIOrbisTool.jsp?verb=GetRecord&identifier=oai:orbis.library.yale.edu:3505631&metadataPrefix=marc21] and [OAI_DC|http://columbus.library.yale.edu:8055/OAI_Orbis/src/OAIOrbisTool.jsp?verb=GetRecord&identifier=oai:orbis.library.yale.edu:3505631&metadataPrefix=oai_dc] records for a book

Cake: [VUFind|http://collections.britishart.yale.edu/vufind/Record/1670022], [LIDO|http://collections.britishart.yale.edu/oaicatmuseum/OAIHandler?verb=GetRecord&identifier=oai:tms.ycba.yale.edu:57163&metadataPrefix=lido]
- objectWorkType: cake, portrait, sculpture
- classification: Sculpture
- eventMaterialsTech: "Inkjet on iced fruitcake plus cardboard box"
-- termMaterialsTech/type="technique": printing, ink jet
-- termMaterialsTech/type="support": cardboard
-- termMaterialsTech/type="medium": fruitcake
- subjectConcept: boxes (containers), portrait, genre subject
{table-plus:columnTypes=S,I|autoTotal=true}
| *collection* | *count* | *search, browse* |
| 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%5B%5D="Rare+Books+and+Manuscripts"&type0%5B%5D=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%5B%5D="Reference+Library"&type0%5B%5D=collection_facet] |
{table-plus}

h2. Paintings and Sculpture

- Search fields:
Title:
Painting
Ceramic
Sculpture (and TODO)
Silver
Wedgwood

h3. Cake

Interesting example: a cake: [VUFind|http://collections.britishart.yale.edu/vufind/Record/1670022], [LIDO|http://collections.britishart.yale.edu/oaicatmuseum/OAIHandler?verb=GetRecord&identifier=oai:tms.ycba.yale.edu:57163&metadataPrefix=lido]
- Object name: cake, sculpture
OK [#Object Type and Genre]
- Genre: portrait
OK [#Object Type and Genre]
- Classification: Sculpture
OK [#Classification]
- eventMaterialsTech: "Inkjet on iced fruitcake plus cardboard box"
OK [#Material and Technique]
-- technique: printing, ink jet
-- support: cardboard
-- medium: fruitcake
- subjectConcept:
-- boxes (containers)
*NOK* P62_depicts, since it includes a box as part of the object, it's not about boxes (*is* not *about*).
But I don't see how we can recognize this as a part, given that it's mapped to subjectConcept
-- portrait
OK P62_depicts
-- genre subject
OK P62_depicts

Emmanuelle: Contemporary art always brings up challenging cataloguing and intellectual issues.
The cake titled 'Boots' is a 2001 work by&nbsp;Sarah Lucas, a contemporary British artist. &nbsp;It is effectively a cake with an inkjet portrait of the artist on it (think edible frosting\!) contained in a box.
Inside the box lies this rather intriguing inscription: "Cake (2001): a series of 12 iced fruit cakes with inkjet images. Each cake is an edition of 25. Produced by Cakes Direct, Ilford, Essex. This signed box certifies the authenticity of the artwork contained within. It must accompany the work through any changes of ownership. \| Edition number 20/25 \[hand written\] Date 2001\[hand written\]" The inscription is followed by the signature of the artist. &nbsp;So in fact the work of art 'Boots' is not only the cake, but the cake within the box. They cannot be separated. That is why we catalogued 'boxes (containers)' as a subject term.

h2. Prints and Drawings

- Search fields:
Title:
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. Frames

- search fields
Title: