Add digital object link to EAD export
|Assignee:||José Raddaoui Marín||% Done:|
|Category:||EAD||Estimated time:||25.00 hours|
|Target version:||Release 1.4.0|
|Google Code Legacy ID:||atom-639||Tested version:|
for providing links to digital objects
[g] Legacy categories: Import/Export, EAD
#18 Updated by José Raddaoui Marín over 9 years ago
- Status changed from New to QA/Review
How the <daogrp> contents should look like? Do you have any advice that I can follow?
This is just an example, but I don't know if we need all the elements, like the daocesc, arc and resource tags; or the id, role and label attributes of daoloc.
<daogrp linktype="extended"> <daodesc> <p>...</p> </daodesc> <resource linktype="resource" label="start"/> <daoloc href="path_to_object" linktype="locator" role="mime_type" id="id" label="object"/> <daoloc href="path_to_thumbail" linktype="locator" role="mime_type" id="id" label="thumb"/> <daoloc href="path_to_reference" linktype="locator" role="mime_type" id="id" label="reference"/> <arc linktype="arc" show="embed" actuate="onload" from="start" to="thumb"/> <arc linktype="arc" show="new" actuate="onrequest" from="thumb" to="reference"/> </daogrp>
Also, where should it be located? Inside the <did> tag or as a sibling?
#19 Updated by Jessica Bushey over 9 years ago
Your sample is consistent with EAD tag library.
And <daogrp> would be contained withing <did> </did> tags. I did read that a possible future development is to deprecate <daogrp> and replace with <dao href= "URL"/>.
From what I understand, <daogrp> is a wrapper element that contains two or more locations for representations of objects that share a common description. The image is linked to and not embedded in the display. An example would be a thumbnail image, labelled as 'thumb' that links to a full size image, labelled as 'reference'.
<daoloc href="url to thumb image" role="thumb"/>
<daoloc href="url to reference image" role="reference"/>
But if the unittitle of the fonds or archival description is sufficient to identify the digital object, a <daodesc> caption is not necessary.
#21 Updated by David Juhasz about 9 years ago
We have decided to use a simple <dao> element instead of the <daogrp> element.
<dao linktype="simple" href="http://www.example.com/uploads/r/acme-archives/2/3/230/sample.jpg" role="master"/>
If the "master" digital object is publicly accessible (check ACL) then it should be the linked resource. If the "master" is not publicly accessible, but the "reference" is, then use the reference as the linked resource. If neither representation is publicly avaialable, then drop the <dao> element (i.e. do not use the thumbnail as the linked resource, as it's too information poor).
#24 Updated by Dan Gillean about 9 years ago
- Status changed from QA/Review to Feedback
A couple other notes to add to Davids comments:
1) Because we are no longer using <daogrp>, this means we are porting over some of the attributes we used before in <daoloc> to our simplified <dao>.
So the <dao> should look like this:
<dao linktype="simple" href="http://www.example.com/uploads/r/acme-archives/2/3/230/sample.jpg" role="master" actuate="onrequest" show="embed"/>
2) As David mentioned, you should check for ACL permissions - but we should also check for null values, and skip it if found. This is because we found some examples where the EAD export contained the following:
... <daoloc href="" linktype="locator" role="" id="" label="thumb"/> <daoloc href="/uploads/r/city-of-vancouver-archives/3/6/361/0239_141.flv" linktype="locator" role="video/x-flv" id="469" label="reference"/> ...
Note that in the first case, the <daoloc> was exported with no data. With our simplified <dao> we want to check first to avoid this.
3) In simplifying, we can also get rid of some of the XLink elements, since we are not actively employing them. please remove the <arc> and <resource> elements completely. Also, because we do not have a template in AtoM to add descriptive metadata to a digital object, we don't need the the <daodesc> element either - this will be added back in a future release
4) Please ensure that the URI used in the @href for <dao> is a qualified URI (i.e., a full permalink, http://...). In the current use of <daoloc>, it is not.
<dao> in the EAD Tag Library (for reference): http://www.loc.gov/ead/tglib/elements/dao.html
#26 Updated by Jessica Bushey about 9 years ago
- File daowarning.png added
- File kitty-from-internet;ead.xml added
- Status changed from QA/Review to Feedback
Radda - can you please review comments #21-#24?
We are no-longer using <daogrp>
Ignore the attached screenshots - because you need to change the EAD export first.
#30 Updated by Jessica Bushey about 9 years ago
- Status changed from QA/Review to Verified
Here is an example of the verified ead:
<did> <unittitle encodinganalog="3.1.2">Photographs</unittitle> <unitid encodinganalog="3.1.1">s01</unitid> <dao linktype="simple" href="http://1.bp.blogspot.com/-vY_7Vd8NAL8/T9IGldaieiI/AAAAAAAAFLU/xNtLJwkgirE/s1600/Hello-kitty-wallpaper-7.jpg" role="master" actuate="onrequest" show="embed"/> </did>