Intro

This is same as part Dominic's manual (to best of our understanding)

Does it comply with BM's latest changes to modeling Association codes (esp re Acquisition, Production)?
BM Association Mapping v2. Dominic's document probably reflects this, but these are recent changes and I haven't checked.

If there is something else you need to get this to work with Research Space please let me know

Once it's compliant, we should:

try loading the data
load your thesauri. complete Getty or only the subset used by your objects?
create RForms for your objects

Procedural

Eyeball

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

Have you tried Eyeball? See here: RDF Validation and Conversion#Eyeball,
RS-1071

Turtle files

The Pubby view on top right contains "View Collections Online Record", this will take you back to our online collection record that contain both RDF and XML from which the RDF came from.

The pubby page http://collection.britishart.yale.edu/id/object/7 leads to the COL page http://collections.britishart.yale.edu/vufind/Record/1670806 and from where:
- XML indeed leads to a LIDO XML file
- but "RDF" leads back to the pubby page, which 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

If you prefer actual RDF files happy to put them online for you.

Yes, send me Turtle (or RDF) files for the objects that you quoted.

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 this on/off?

Problems

General

pubby doesn’t show prefixes but "?:"
STRONGLY Suggest to have 1 URI per object, not 3 sameAs URIs
crm:PX_* (e.g. crm:PX_display_wrap) is wrong, should be bmo:PX_*

Thesauri

use more logical URIs that don't reflect their genesis in existing systems. Eg
<thesauri/event/exhibition_history> -> <thesauri/event/exhibition> (An exhibition is NOT "exhibition history")
<thesauri/identifier/TMS/exhibition_history> -> <thesauri/identifier/exhibition> (doesn't matter your system is called TMS)
Getty thesauri: don't like that you use a YCBA-specific URI for Getty, eg
http://collection.britishart.yale.edu/id/thesauri/ULAN/500303557
This won't let your data mesh with other data using Getty.
Haven't the Getty decided on an official namespace?

Images

This is wrong, see image_objects_carriers@crmg

TODO Vlado: write the correct one
This says nothing (has no fields)
http://collection.britishart.yale.edu/id/page/object/7/image/1/restriction
this is all wrong
- so simply use this:
- better yet, use a CreativeCommons URI, since CC is a stronger authority about rights than YCBA

Object Rights

PX_has_copyright "Public Domain" is unnecessary since you have it structured as
http://collection.britishart.yale.edu/id/page/object/7/object-rights.
If you want to output a string, use PX_display_wrap
http://collection.britishart.yale.edu/id/page/object/7/object-rights
is a completely unnecessary intermediate node
This should not be per-object
http://collection.britishart.yale.edu/id/object/7/public-domain
so overall, use just this in object data:

And this in thesaurus data, not per-object:
better yet, use a CreativeCommons URI, since CC is a stronger authority about rights than YCBA

Yale Mapping Problems