Feature #2589

Add digital object link to EAD export

Added by Peter Van Garderen over 13 years ago. Updated about 9 years ago.

Status:VerifiedStart date:
Priority:HighDue date:
Assignee:José Raddaoui Marín% Done:

100%

Category:EADEstimated time:25.00 hours
Target version:Release 1.4.0
Google Code Legacy ID:atom-639 Tested version:
Sponsored:Yes Requires documentation:

Description

for providing links to digital objects

[g] Legacy categories: Import/Export, EAD

daowarning.png (39.3 KB) Jessica Bushey, 04/01/2013 01:33 PM

kitty-from-internet;ead.xml Magnifier (2.43 KB) Jessica Bushey, 04/01/2013 01:33 PM


Related issues

Related to Access to Memory (AtoM) - Feature #2590: Enable linking a digital object in EAD import Verified
Related to Access to Memory (AtoM) - Bug #4435: Rework how EAD imports/exports digital objects to get rid... Verified 12/13/2012

History

#1 Updated by Peter Van Garderen about 13 years ago

  • Target version changed from Release 1.0.6 to Release 1.1

[g] Labels added: Milestone-Release-1.1
[g] Labels removed: Milestone-Release-1.0.6

#2 Updated by Peter Van Garderen about 13 years ago

[g] Labels added: Component-EAD

#3 Updated by Peter Van Garderen about 13 years ago

  • Target version set to Release 1.0.8

[g] Labels added: Milestone-Release-1.0.8

#4 Updated by Peter Van Garderen almost 13 years ago

  • Priority changed from High to Medium

[g] Labels added: Priority-Medium
[g] Labels removed: Priority-High

#5 Updated by Peter Van Garderen over 12 years ago

  • Target version changed from Release 1.0.8 to Release 1.1

[g] Labels added: Milestone-Release-1.1
[g] Labels removed: Milestone-Release-1.0.8

#6 Updated by Anonymous almost 12 years ago

  • Priority set to Low

[g] Labels added: Priority-Low

#7 Updated by Evelyn McLellan almost 12 years ago

  • Priority changed from Low to High

Moved to high. Also, make sure that <daogrp> link is to reference display copy.

[g] Labels added: Priority-High
[g] Labels removed: Priority-Low

#8 Updated by Evelyn McLellan over 11 years ago

  • Target version set to Release 1.2

[g] Labels added: Milestone-Release-1.2

#9 Updated by David Juhasz almost 11 years ago

[g] New owner: MJ Suhonos

#10 Updated by David Juhasz almost 11 years ago

  • Priority set to Medium

[g] Labels added: Priority-Medium

#11 Updated by David Juhasz over 10 years ago

  • Target version set to Release 1.3

Roll over to Release 1.3

[g] Labels added: Milestone-Release-1.3

#12 Updated by Jesús García Crespo almost 10 years ago

[g] New owner: David Juhasz

#13 Updated by David Juhasz almost 10 years ago

Reassign to David's new account.

[g] New owner: David Juhasz

#14 Updated by Anonymous over 9 years ago

Is there a way to export XML that contains links to the digital objects without this fix? I need a way to import data into an external system and would like to include the images.

#15 Updated by Jessica Bushey over 9 years ago

  • Target version changed from Release 1.3 to Release 2.1.0

[g] Labels added: Milestone-Release-2.0
[g] Labels removed: Milestone-Release-1.3

#16 Updated by Jesús García Crespo over 9 years ago

  • Subject changed from add <daogrp> to EAD export to Add <daogrp> to EAD export
  • Sponsored set to No

#17 Updated by David Juhasz over 9 years ago

  • Category set to EAD
  • Assignee changed from David Juhasz to José Raddaoui Marín
  • Priority changed from Medium to High
  • Target version changed from Release 2.1.0 to Release 1.4.0
  • Sponsored changed from No to Yes

#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'.

<daogrp>
<daodesc><p>xxx</p></daodesc>
<daoloc href="url to thumb image" role="thumb"/>
<daoloc href="url to reference image" role="reference"/>
</daogrp>

But if the unittitle of the fonds or archival description is sufficient to identify the digital object, a <daodesc> caption is not necessary.

#20 Updated by Jesús García Crespo about 9 years ago

  • % Done changed from 0 to 100

Applied in changeset atom|commit:052584fc777d21023ddad9f5e2f85412572da76c.

#21 Updated by David Juhasz about 9 years ago

We have decided to use a simple <dao> element instead of the <daogrp> element.

e.g.
<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).

#22 Updated by David Juhasz about 9 years ago

  • Subject changed from Add <daogrp> to EAD export to Add digital object link to EAD export

#23 Updated by David Juhasz about 9 years ago

The role element should either be equal to "master" or "reference".

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

Thanks!

<dao> in the EAD Tag Library (for reference): http://www.loc.gov/ead/tglib/elements/dao.html

#25 Updated by Jesús García Crespo about 9 years ago

  • Status changed from Feedback to QA/Review

Applied in changeset atom|commit:4417acfd7d81ac8e3f1b4e4c2ec264fc9cdf64b1.

#26 Updated by Jessica Bushey about 9 years ago

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.

#27 Updated by José Raddaoui Marín about 9 years ago

Sorry Jessica.

I can see in 1.x that my changes are not included. I guess something went wrong when Sevein merged it. I will send the fix to him again.

#28 Updated by David Juhasz about 9 years ago

  • % Done changed from 100 to 90
  • Estimated time set to 25.00

#29 Updated by Jesús García Crespo about 9 years ago

  • Status changed from Feedback to QA/Review
  • % Done changed from 90 to 100

Applied in changeset atom|commit:6210be013442c55884bc0feb89a6c3c8f55a4a2a.

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

Also available in: Atom PDF