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

Changes (14)

View Page History
- [<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 Valimir 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). (TM) (it's still in the Materials facet)

h3. Searchable/Taggable Thesauri
(-) 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;

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}
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:
{html:script=^5005-images.html}{html}
h3. Image Flags

The views have these comma-separated 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