Dynaweb and ContentDM
http://library.uvm.edu/about/specialcollections/MarthaKennedy.html
Dynaweb – internal links to images
http://bailey.uvm.edu:6336/dynaweb/findingaids/marsh/@Generic__BookView;cs=default;ts=default
The newest DLXS enhancement - XPAT - is a powerful, SGML/XML-aware search engine, and an ultra-versatile tool for the development of digital libraries. XPAT provides excellent support for word and phrase searching, indexing of SGML elements and attributes, a baseline of support for XML (without Unicode), fast retrieval, and open systems integration. And ...
The Digital Library Production Service has developed a suite of tools for mounting collections of digital library content. Using object-oriented methods and widely available tools, this middleware has now been extended to support:
Encoded
text collections ("Text Class")
Digital
image collections ("Image Class")
Bibliographic
data ("Bib Class")
EAD2002-encoded
finding aids ("Findaid Class")
Examples
http://www.dlxs.org/about/samples.html
http://www.umich.edu/~bhl/EAD/
2.0 released January 31, 2005
Fedora is a general purpose repository service
developed jointly by The University of Virginia Library and Cornell University.
The Fedora project is devoted to the goal of providing open-source repository
software that can serve as the foundation for many types of information
management systems.
The software demonstrates how distributed digital
information management can be deployed using web-based technologies, including
XML and web services.
http://www.lib.virginia.edu/digital/resndev/fedora.html
VTLS Vital
http://www.vtls.com/Products/vital.shtml
Based on Fedora™, the open source software and architecture upon which VITAL is built, VITAL provides every feature—storing, indexing, cataloging, searching, retrieving—required to handle large text and image rich content collections. VITAL takes advantage of technology standards such as XML, TEI, EAD and Dublin Core to easily describe and index an assortment of electronic resources.
VITAL builds on the Fedora™ repository architecture by providing VTLS developed work flow extensions, management utilities and enhanced searching capabilities. Using Fedora™ defined web services, VITAL provides a mechanism for your organization to create tools, enhance the functionality provided by VTLS, or leverage the open source community for future applications. Together, the package is known as VITAL.
http://asteria.fivecolleges.edu/index.html
Five Colleges finding aids
The finding aids
included in this site are marked up in XML according to the Encoded Archival Description (EAD) standard.
The site runs Cocoon publishing
software that applies XSL stylesheets for displaying the finding aids as HTML
in any standard web browser. Lucene is the
site's search engine. Both Cocoon and Lucene are open source software projects
of The Apache Software Foundation.
The Cocoon project from Apache is quite stable and
powerful
AxKit <http://axkit.org/> also falls under the Apache
umbrella, but I had some problems with some elements of
rendering finding aids using this tool.
The site we are developing is based on Cocoon.
PLEADE
PLEADE is an open
source search engine and browser for archival finding aids encoded in XML/EAD.
Based on the SDX platform, it is a very flexible Web application. The current
release of PLEADE is v1.0.
If you want to try PLEADE on your personal computer, you'll
just need a Java
virtual machine, a servlet engine like Tomcat, SDX and PLEADE.
All these are free software, you can download them.
Just have a look at http://www.pleade.org/en/documentation/install.html.
Works with Apache (as a
Web server), Tomcat (for example, as a servlet engine), SDX (free platform
for searching and displaying XML documents, see http://adnx.org/sdx/ ),
which are free softwares as well.
Includes a search engine, may be configured easily.
The Denver Public Library (Colorado, USA) is also using
PLEADE for some
finding aids:
http://eadsrv.denver.lib.co.us:8080/sdx/pl/?l=en
http://www.iath.virginia.edu/ead/ead2002cookbookhelp.html
Step 4. Acquire a software application for
authoring finding aids.
Products currently
available include XMetaL, XML Spy, Oxygen, Note Tab, WordPerfect 2000, and
others. Consult your favorite web
search engine for current addresses and additional information about each of
these products.
Step 5. Install and configure the software. (Section 4)
Step 6. Create EAD-encoded finding aids. (Sections 3 and 4)
Step 7. Adopt or modify an
existing XSLT stylesheet or create your own.
(Section 5)
Step 8. Transform your EAD files into HTML or
print. (Section 6)
This section describes three widely used conversion programs. All are free. Saxon was created and is maintained by Michael Kay, one of the developers of XSLT. For many, it is the "gold standard" of transformation software. MSXML from Microsoft is very widely employed and is reputedly the "fastest" of the group. Xalan from Apache is often employed because of its connection with its popular web server software.
Step 9. Deliver your finding aids to your
users. (Section 7)
7.3 Access from Data Servers
A number of products are available if you wish to provide keyword or structured searching of the full text of your inventories. This obviously is a very complex and technical issue, well beyond the scope of the Cookbook. Several applications are available currently and new ones appear regularly. More detailed information may be found in Chapter 5 of the EAD Application Guidelines and other sources including:
The XSL list and archives:
http:www.mulberrytech.com/xsl/xsl-list
http:www.infotek.no/sgmltool/guide.html
http://library.nyu.edu/findingaids/
These finding aids have been marked up in XML (eXtensible Markup
Language) according to the EAD
(Encoded Archival Description) markup schema.
The XML documents have been loaded into an Oracle database
and indexed with Intermedia Text for searching within tags. If you click on
"retrieve this findingaid" you will be taken to the HTML frameset
dynamically generated from the XML version. Also available is a pointer to the
concommitant static HTML-encoded text of the finding aid, which allows you to
search within the findingaid. The third option is a printable non-frames
version.
Zope is an open source application server for building content management systems, intranets, portals, and custom applications. The Zope community consists of hundreds of companies and thousands of developers all over the world, working on building the platform and Zope applications. Zope is written in Python, a highly-productive, object-oriented scripting language.
http://www.oit.duke.edu/ows/cms.html
Implementations of online access
systems that utilize structured information stored in either relational
databases or XML encoded documents.
http://euterpe.bobst.nyu.edu/toolkit/
Key objectives of the application are to increase archival processing efficiencies and lower processing costs, including costs for specialized training; reduce the need for locally built tools; and promote standardization. When completed, the application will support collection accessioning and description, location tracking, and provenance registration, as well as outputs for the EAD and METS standards.
Berkeley
DB Sleepycat
http://www.sleepycat.com/products/xml.shtml
I would recommend that you check out some of the relational
databases
that have incorporated components of XML and have a suite of XML tools
The Berkeley DB Sleepycat comes to mind since it is freely available.
(But Oracle has done some similar work)
Essentially what you can do is store both "relational" data and data
that has embedded XML markup. You can do fielded searching on the
relational database fields and the XML elements - though the searching
on the RD fields is much more efficient because if the manner in which
it is stored and indexed.
I have only played with it a little - and not for over a year. But it
seemed like an elegant solution for storing mixed content with embedded
markup on which you might never search (except within its parent
element) - but may want to store for display purposes/ transformation
purposes on output.
You can still search the embedded markup if you must but just not as
efficiently.
http://www.rpbourret.com/xml/XMLAndDatabases.htm