Swish-E, in particular, is extremely easy to set up; It's fast, lightweight, portable, and pretty robust. While I cannot really address issues as to its salability, I (heartily) second Clay's implicit endorsement.
If you're looking to tie the database with a publishing system, try xindice, and the suite of tools offered by the Apache Foundation @ http://xml.apache.org.
Yale University Library::Manuscripts and Archives
At 02:19 PM 10/8/2002 -0400, you wrote:
>If you're just looking for end user search engine capabilities in the vein
>of OPACs, have a look at SWISH-E (http://swish-e.org) and Harvest
>(http://harvest.sourceforge.net). These are just a couple of open source
>options. They aren't for EAD exclusively — they're XML-aware
>search/indexing engines. But you can define which fields you'd like to be
>indexed and searched, and they come with nice GUIs ready to plug into your
>American Institute of Physics
>Center for History of Physics
>Niels Bohr Library
>One Physics Ellipse
>College Park, MD 20740
> >>> [log in to unmask] 10/08/02 02:04PM >>>
>Can anyone direct me to a simple (preferably open source) tool for
>searching various tags or areas within an EAD finding aid? I'm envisioning
>something that works somewhat like an OPAC interface, with fields for
>searching by creator, title, date, controlled vocabulary, full-text keyword,
>provenance, <unitid>, etc.
>I am currently working on a very simple and straightforward such tool in
>Perl using CGI. It functions (to simplify significantly) by generating XSLT
>documents which contain tests for the queries input by the user, which are
>then applied to each EAD document within a specified filepath. Am I
>reinventing the wheel? If not, would there be any interest in such a
>program if I were to generalize it enough that it could be integrated with
>other institutions' web interfaces?
> Lower Cape Fear Historical Society