SOW for Dec. 2016 work

Collection Builder

LibraryCloud

Background info

authentication/authorization

Please refer to https://jira.huit.harvard.edu/browse/LTSCLOUD-259 and https://jira.huit.harvard.edu/projects/LTSCLOUD/issues/LTSCLOUD-251 for details.

object in context

Here’s some background on the object in context question. Yes it is the mods url field with access=”object in context”; this is the link to the full record display in the context of its collection – Harvard Open collection, Omeka, Spotlight, etc. The primary use case for this is when DPLA harvests our mods, they use the object in context url to point back to our records in their native collection. Examples from our current MODS OAI:
 
<url usage="primary display" access="object in context">http://colonialnorthamerican.library.harvard.edu/cna/div00376c00007 </url>
 
<url usage="primary display" access="object in context"> http://ocp.hul.harvard.edu/dl/immigration/000069518 </url>
 
So the idea is that, per collection/set, the curator should be able to set the root url and path to precede the record id that will point to the external collection, and this (with the id) will be added as a mods field.