 |
 |
If the collection name you need for the search string is in the EAD someplace, like in unitid or eadid, you can construct custom strings with a single style sheet. For example, if the search string needs to be this: http://mydspace/[collectionname]/index.htm and you have this in your EAD <eadid identifier="[collectionname]"> Then your style sheet can construct the custom search string on the fly by grabbing the collection name from the identifier. Michele -----Original Message----- From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf Of Jaime Margalotti Sent: Friday, March 29, 2013 7:46 AM To: [log in to unmask] Subject: Re: Using a search box in EAD That makes sense and I'll do it if it's my only option. The search boxes are pointed to specific collections in DSpace and I had hoped to avoid having custom stylesheets for individual finding aids. Up until now we've just had a single stylesheet to handle everything. Thanks, Jaime Sent from my iPhone On Mar 28, 2013, at 10:27 PM, MicheleR <[log in to unmask]> wrote: > On 3/28/2013 5:40 PM, Jaime Margalotti wrote: >> Hi All, >> >> For several of our collections, we have digital content available in >> DSpace. In the HTML version of our finding aids, we include a DSpace >> search box in the "Materials Available in Alternative Format" >> section. Is there any way to make this functionality (<form >> action="http://udspace.udel.edu/handle/1971/5533/search" >> method="post">) into something that won't break my EAD finding aids? >> I've been slipping it into the HTML post-transformation, but that >> won't really be viable when we start transforming on the fly. > > Why won't that work with an on-the-fly transformation? It doesn't need to go into the EAD, your style sheet could insert it as part of the transformation. > > Michele > +==+==+==+==+==+==+==+==+==+ > All human troubles derive from our > inability to sit still and alone in a room. > -- Blaise Pascal > +==+==+==+==+==+==+==+==+==+