LISTSERV mailing list manager LISTSERV 16.0

Help for EAD Archives


EAD Archives

EAD Archives


EAD@LISTSERV.LOC.GOV


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

EAD Home

EAD Home

EAD  June 2007

EAD June 2007

Subject:

Re: Digital object linking

From:

Mark Carlson <[log in to unmask]>

Reply-To:

Encoded Archival Description List <[log in to unmask]>

Date:

Mon, 18 Jun 2007 14:55:50 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (132 lines)

There are a number of inconsistencies with DAO links in the EAD 
DTD/Schema.  For instance, there is no equivalent to #PCDATA <extref> 
element for DAO.  Instead, for <dao> you are required to put your local 
resource (the text that you click on if the object is not to be 
embedded) in one of the attributes of <dao> or within a child <daodesc> 
element.  This doesn't exactly follow the XLink specification.  The tag 
library example for <daogrp> also doesn't follow the XLink 
specification, which (XLink specification 1.1/section 5.2) states that 
the local resource (the text that you click on to traverse the link) 
should go in a resource-type element (<resource> in EAD) instead of 
<daodesc>.  So you first need to decide how you are going to work around 
these mapping issues no matter which element you end up using.

More responses below...

Mark Carlson
Computer Support Analyst
Special Collections Division
University of Washington Libraries
BOX 352900
Seattle, WA, 98195
(206) 543-1929
http://staff.washington.edu/carlsonm/


John Bewley wrote:
> Any help or opinions on the following would be greatly appreciated:

I'm always happy to give my opinion, especially in regards to linking 
elements and EAD ;)

> RLG, LC, NWDA guidelines all state that <daogrp> is recommended for use 
> for all linking to digital objects from collections, rather than <dao>. 
> Does this leave any uses of <dao> as recommended practice?

I have found, in practice, that for simple type links (where you are 
only linking to one item rather than multiple versions of the same 
item), <dao> is much easier to encode since you are just dealing with 
the one element (and possibly a child <daodesc> element) instead of the 
multiple required sub-elements of <daogrp>.  This might make your EAD 
encoders happier!

And once you have the mapping issues settled, you can easily convert a 
<dao> element to <daogrp> if you should need to do this for some reason 
down the road.

> Tag Library examples show <daogrp> stated within <did>. It could also be 
> stated within <scopecontent> or <c0X). Has anybody developed a rationale 
> for stating <daogrp) anyplace other than <did>?

We have embedded DAO objects within <bioghist>.  It's also available in 
<odd> in addition to <scopecontent> as you state.  This would be at the 
top of my wish list for future revisions to the EAD schema.  I have 
resorted to using <linkgrp> or <extref><extptr> when necessary as a work 
around.  The linking concepts are the same, so it's just a matter of 
being able to identify these as DAO links later on.

> The Tag Library uses the same example for <daogrp>, <daodesc>, <daoloc>, 
> <resource>, and <arc>. The example is for a thumbnail/reference image 
> setup. Can anybody provide examples that would provide links to multiple 
> images rather than multiple versions of the same image?

This is something that I grappled with for a long time.  One can make a 
<daogrp> element so complicated that it's difficult to construct and 
even more difficult for your stylesheet to parse.  I like to think of 
each <daogrp> element as capable of one or two traversals at the most.
There can be multiple resources (i.e. <daoloc>) on the first traversal 
if they are embedded, but only a single resource can be pointed to on 
the second traversal.  Beyond this, it just becomes to convoluted in my 
opinion, so you are better off just creating another <daogrp> element.

For two traversals (without using some scripting language link 
JavaScript) the only valid use for such a scenario would be to embed 
multiple images on the first traversal and then linking out to a single
resource on the second traversal.

This is covered in the XLink specification and there is also a quick 
reference to this in wikipedia that is pretty good:

http://en.wikipedia.org/wiki/XLink#Extended_links

Let's say you have three images that you want to embed in your document 
using a single link.  I would encode it like this:

<daogrp>
<resource label="start"/>
<daoloc label="image" href="image1.jpg" role="image/jpeg"/>
<daoloc label="image" href="image2.jpg" role="image/jpeg"/>
<daoloc label="image" href="image3.jpg" role="image/jpeg"/>
<arc from="start" to="image" show="embed" actuate="onload"/>
</daogrp>

Now let's say that you want to be able to click on these images to open 
another html page.  Just add another resource and another <arc>:

<daogrp>
<resource label="start"/>
<daoloc label="image" href="image1.jpg" role="image/jpeg"/>
<daoloc label="image" href="image2.jpg" role="image/jpeg"/>
<daoloc label="image" href="image3.jpg" role="image/jpeg"/>
<daoloc label="document" href="mydoc.html" role="text/html"/>
<arc from="start" to="image" show="embed" actuate="onload"/>
<arc from="image" to="document" show="new" actuate="onrequest"/>
</daogrp>

Note, these examples are encoded for the requirements of the EAD DTD. 
The values are different for the EAD schema.

> entityref vs. href - in the case of links to digital objects from 
> container lists (as opposed to logos or illustrations), does the use of 
> entityref have any benefits over the use of href in <daoloc> statements? 
> Does the use of entityref entail certain vulnerabilities concerning the 
> contribution of finding aids to shared, or regional databases of finding 
> aids?

I would recommend not using entity references for many reasons but 
mainly because the HREF attribute is a required attribute in XLink 
elements, so the EAD schema requires it (while the DTD doesn't).  So you 
should make all of your XLink elements XLink compliant.

> 
> How many institutions are now incorporating METS into their descriptions 
> and links to digital objects? Does that affect the choice of <dao> vs. 
> <daogrp> in any way? Is this becoming an accepted practice that is 
> likely to become standard practice?
> 
> 
> John Bewley
> Music Library
> University at Buffalo, The State University of New York
> 716 645-2924

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001
March 2001
February 2001
January 2001
December 2000
November 2000
October 2000
September 2000
August 2000
July 2000
June 2000
May 2000
April 2000
March 2000
February 2000
January 2000
December 1999
November 1999
October 1999
September 1999
August 1999
July 1999
June 1999
May 1999
April 1999
March 1999
February 1999
January 1999
December 1998
November 1998
October 1998
September 1998
August 1998
July 1998
June 1998
May 1998
April 1998
March 1998
February 1998
January 1998
December 1997
November 1997
October 1997
September 1997
August 1997
July 1997
June 1997
May 1997
April 1997
March 1997
February 1997
January 1997
December 1996
November 1996
October 1996
September 1996
August 1996
July 1996
June 1996
May 1996
April 1996
March 1996
February 1996
December 1995

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager