Russell, I had this same problem. I don't know if this helps, but I believe that when I added the following to our stylesheets, the issue resolved. <xsl:when test='@href | @entityref'> <xsl:element name='a'> <xsl:attribute name="style"> *[Custom information here]* </xsl:attribute> <xsl:attribute name='href'> <xsl:call-template name="*[custom information here]"*/> </xsl:attribute> * <xsl:if test='@show="new"'> <xsl:attribute name="target">new</xsl:attribute> </xsl:if>* <xsl:apply-templates/> </xsl:element> </xsl:when> Best wishes, Amanda Ross Project Archivist Forest History Society On Mon, Jun 8, 2009 at 10:46 AM, Franks, Russell <[log in to unmask]>wrote: > Hello, > > > While we have been able to implement the use of the <extref> tags > successfully, using the show="new" attribute has no effect. I want the user > to be able to open the resource in a new browser window. The HTML coding for > this should be target="blank", but the DTD, and apparently the schema > version as well, doesn't allow for this. > > I tried hacking my local copy of the DTD as an experiment, but that didn't > work. So do I not worry about the user employing the browser back button to > return to the finding aid, or do I need to look at my style sheets to solve > this. What am I missing? Any ideas would be greatly helpful. > > > Thanks in advance, > > Russell Franks > > Librarian > Special and Archival Collections > Phillips Memorial Library > Providence College > 1 Cunningham Square > Providence, RI 02918-0001 > 401-865-2578 > [log in to unmask] > [log in to unmask] > http://www.providence.edu/archives > > -----Original Message----- > From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf Of > Custer, Mark > Sent: Wednesday, May 27, 2009 1:31 PM > To: [log in to unmask] > Subject: Re: <extref> in <addressline> > > To clarify: When I said "full-fledged" I should've said "fully hosted." > These two examples are listed in ArchiveGrid, but they point back to your > website (where you could easily display whatever Addresss/URL information > via your stylesheet or su_address.xml file). I was speculating about a > different issue/problem. > > It'd be nice if there was something like a consortial database of EAD > records that could be searched cross-institutionally. Give me everything > they've got that has material from 1818, for example. > > Otherwise, I'd say that Google ranks as the best online directory for > archival records (especially if you limit the domains that are searched). > In fact, nearly 75% of our traffic over the last year has been driven by > external search engines. For that reason and more, yes, we include links to > our homepages on all of our finding aids. > > Back to the question at hand, though: > > I guess that everything comes down to the design philosophy of EAD. It > seems to be created to be generic enough for a multitude of uses, whether > those uses be termed standardized, abusive, or innovative (For instance, > I've encoded relative links to our MARC records by means of the <num> tags > and our ILS's "bib numbers"). Though it's meant to be human-readable, I > wouldn't say that it's meant to be semantic (though perhaps future revisions > will go that route). > > So, after thinking about it some more, I wouldn't see a problem with any of > those three options, assuming that you did want/need to encode that > information in the EAD itself: > > <addressline><extptr xlink:href="www.wherever.com"/>... [After looking > again, the documentation does include the example of "pointers to an > institution's web page", so I'd assume that that's why they didn't include > the more robust <extref> in the <addressline> field] > > Or > > <addressline>URL:www.wherever.com... > > OR > > ...</addressline> > <p><extref xlink:href="www.wherever.com">www.wherever.com... > > > > > Mark Custer > > > > -----Original Message----- > From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf Of > Michele R Combs > Sent: Wednesday, May 27, 2009 11:31 AM > To: [log in to unmask] > Subject: Re: <extref> in <addressline> > > -----Original Message----- > From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf Of > Custer, Mark > Sent: Wednesday, May 27, 2009 10:36 AM > To: [log in to unmask] > Subject: Re: <extref> in <addressline> > > > After doing some cursory searching in ArchiveGrid and Archives USA, > however, I couldn't find > > any examples of full-fledged finding aids that had links back to the > institution's homepage > > All of ours do -- two examples: William Langner Papers, > http://archivegrid.org/web/jsp/s.jsp?q=william+langner or > http://library.syr.edu/digital/guides/l/langner_w.htm and Adams Wistar > Record Book http://archivegrid.org/web/jsp/s.jsp?q=adams+wistar or > http://library.syr.edu/digital/guides/a/adams_wistar.htm . > > One excellent argument for including a link back to the home page is that > increasingly people run across finding aids via a Google search, which means > they didn't navigate through our home page and may have no idea where this > stuff they're looking at lives. > > Michele > > (be green - don't print this email!) > ~~~~~~~~~~~~~~~~~~ > Michele Combs > Manuscripts Librarian > Special Collections Research Center > Syracuse University Libraries > 222 Waverly Ave. > Syracuse, NY 13244 > 315-443-2081 > [log in to unmask] > ~~~~~~~~~~~~~~~~~~ >