Hi Nathan –
This kind of relates to a question I asked on the list a while ago, about how best to make sure the minimum required information for constructing a link (any kind of link) is present and properly encoded in the EAD. For example, if your <dao> targets are just sitting on the file system, you have a file name; if they’re in ContentDM you have a collection name and an object ID. To my mind, you’d want to put only that bare minimum in the EAD, no path or full URL or anything, and let your stylesheet do the rest. That way if you want/need to change the link, all you need to do is alter the style sheet, or apply a different one.
From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf Of Nathan Tallman
Sent: Tuesday, June 21, 2011 9:28 AM
To: [log in to unmask]
Subject: Absolute or Relative Links
I'm trying to get a handle on whether institutions are using relative or absolute links for linking digital content. Relative is probably the preferred for coding standards, but what if your are sending your EADs off to a consortium or central finding aid repository, in addition to your own website? Won't all the links be broken? Perhaps one can work some find/replace magic to make them all absolute.
Just curious how others are handling this, especially since finding aid repositories are on the rise.
American Jewish Archives