New York, NY - American Numismatic Society today unveiled the new interactive ANS archival search tool, ARCHER (numismatics.org/archives/). ARCHER (ARCHival Electronic Resource) provides access to the ANS’ unrivalled collection of unique archival material, through a series of simple search screens.
ARCHER is powered by EADitor, open source software developed by the ANS for creating, managing, and publishing collections of archival finding aids described in Encoded Archival Description (EAD) XML. Like the society’s Collection database, MANTIS, ARCHER's public interface includes faceted searching and mapping of the collection. The administrative interface takes advantage of XForms, next-generation web forms, which enables the Society’s archivist, David Hill, to create the finding aids with an intuitive user interface that requires no technical knowledge of XML, a major advancement over many institutions' current workflows.
“The Society’s archives contains a rich diversity of material”, notes Deputy Director Andrew Meadows. “On the one hand there are the Society’s own archival records, spanning more than 150 years of our activity since 1858. As such, the archive is one of the oldest held by any learned society in the country. But in addition to that, the ANS also holds a remarkable archive of international significance, consisting of the papers of famous scholars, collectors and dealers in the field of numismatics. Documents, letters, notebooks and photographs relating to many famous individuals from within the numismatic community and beyond are held at the ANS. ARCHER provides a remarkably straightforward tool both for their cataloging, and for their search by the general public.”
The search interface is built on similar technology to the Society’s MANTIS database. Simple faceted searching based on personal names, places, dates, genre and Library of Congress subject headings are all provided. ARCHER also provides a map interface, which will allow users to visualize the places on the globe with relevant ANS archival material.
ANS Archivist David Hill explains, “What really sets ARCHER apart from other archives management systems is that it combines a simple method for the creation of full EAD with a powerful, built-in publishing feature that produces remarkably sophisticated finding aids. The faceted search capabilities give us an enhanced level of control over our archival holdings, ensuring that ANS staff and researchers can always find relevant materials from across our various collections.”
The design of ARCHER is the work of ANS Web Developer Ethan Gruber, working in close collaboration with David Hill. The database supports a variety of export formats that will encourage exploration of the links between numismatics and other disciplines. As with MANTIS, underlying this work is a technical approach called ‘Linked Open Data’. For the future this will mean increased opportunities both for the ANS to integrate searches across the whole range of its collections, such as books, coins, archives, and also for the rest of the world wide web to discover and link to our material. As Meadows notes, “The new suite of ANS search tools, comprising DONUM (the library catalog), MANTIS and ARCHER, will bring numismatic material to whole new audiences. In this the ANS is leading the world.”
For more information, contact ANS Deputy Director Andrew Meadows (212) 571-4470 ext. 111, meadows@numismatics.org.
The American Numismatic Society, organized in 1858 and incorporated in 1865 in New York State, operates as a research museum under Section 501(c)(3) of the Internal Revenue Code and is recognized as a publicly supported organization under section 170(b)(1)(A)(vi) as confirmed on November 1, 1970.
Friday, November 4, 2011
Bringing the ANS archives to a larger audience
Just a quick update on recent happenings...
Over the last several days, I have been working on creating an OAI-PMH service layer in Archer, the ANS's implementation of EADitor. It is complete and passed all of the OAI validation tests a few minutes ago. Openarchives.org has successfully registered it. Like the Atom feed, the OAI service is generated dynamically from Solr search results. Archer's OAI service will be added to the EADitor general distribution trunk soon, so you'll see it in the next beta release (coming by the end of the year)!
Over the last several days, I have been working on creating an OAI-PMH service layer in Archer, the ANS's implementation of EADitor. It is complete and passed all of the OAI validation tests a few minutes ago. Openarchives.org has successfully registered it. Like the Atom feed, the OAI service is generated dynamically from Solr search results. Archer's OAI service will be added to the EADitor general distribution trunk soon, so you'll see it in the next beta release (coming by the end of the year)!
Thursday, October 20, 2011
Mapping Archival Collections via Atom
As mentioned in a previous blog post, EADitor enables georeferencing of archival collections, either as a whole or perhaps on the component level, by tapping into APIs provided by geonames.org. A mapping interface solicits user input of facets to query EADitor's built-in Solr-to-KML service to render results in the form of an OpenLayers map.
Currently, only one collection in the American Numismatic Society Archives has been georeferenced, but we expect to add more geographic locations in the coming weeks and months as we continue to refine the collections' descriptions. The more places that have been added into the Solr index, the more useful the Ajax-driven facet querying interface will be.
On top of this, GML points have been added into the Atom feed for the collection. Like KML, the Atom feed is driven by Solr and can be queried with the Lucene syntax. Google Maps is capable of rendering an Atom feed which contains GML points, which you can see here.
The ANS code is about a week ahead of what exists in the Google Code trunk for the EADitor general distribution, but I will work on integrating these new mapping features into the trunk before the beta release that should come in early November.
Currently, only one collection in the American Numismatic Society Archives has been georeferenced, but we expect to add more geographic locations in the coming weeks and months as we continue to refine the collections' descriptions. The more places that have been added into the Solr index, the more useful the Ajax-driven facet querying interface will be.
On top of this, GML points have been added into the Atom feed for the collection. Like KML, the Atom feed is driven by Solr and can be queried with the Lucene syntax. Google Maps is capable of rendering an Atom feed which contains GML points, which you can see here.
The ANS code is about a week ahead of what exists in the Google Code trunk for the EADitor general distribution, but I will work on integrating these new mapping features into the trunk before the beta release that should come in early November.
Thursday, September 29, 2011
A Brief Description of Recent Updates
The American Numismatic Society's finding aid collection (an ANS implementation of EADitor) is tentatively set to be released in late October, and I am planning a major release of the EADitor general distribution beta to coincide with this event. Over the last few weeks, I have been making some improvements to the code, several of which I will discuss briefly in this post. A number of these improvements have been borrowed from Numishare, which is our software for managing and publishing collections of coins and similar objects. Like EADitor, Numishare's back-end is built on top of XForms and the server-side XForms processor, Orbeon, so much of the code is interchangeable.
The list:
Screenshot showing "sunny" jQuery UI theme and a thumbnail served from flickr. The banner text "EADitor: XForms for EAD" is stored in the configuration file and editable in the admin section.
The list:
- A major effort to remove hard-coded URLs to eXist and Solr, placing them, instead, into configuration files that can be edited by an XForms web form.
- Introduction of themes configured through a web form. Though rudimentary so far, they are documented here. Currently, the user can select from a list of available jQuery UI themes and select the layout of the search results page: facet list in a left or right-aligned column.
- Flickr API integration.
- The introduction of a new Solr core for storing docs of every finding aid in eXist (including those not published), so that the file list page in the admin section loads faster and enables full-text searching of the collection. I will eventually develop methods for more advanced searching and sorting of records in the admin page. Each time the file list page is loaded, it verifies the number of eXist documents is the same as Solr documents, so that if finding aids are added/removed with the eXist client, the Solr index is flushed and the collection reindexed.
- Batch publication of all finding aids to the public Solr index and batch removal of all documents from this index.
- The ability to edit a container-type template.
- Significant improvements in performance due to rewriting of some XBL components in which a glitch in my code resulting in commands being fired off numerous times, and other general bug fixes.
Screenshot showing "sunny" jQuery UI theme and a thumbnail served from flickr. The banner text "EADitor: XForms for EAD" is stored in the configuration file and editable in the admin section.
Monday, August 22, 2011
EADitor featured in SAA Description Expo 2011
EADitor was recently honored by making the short list of archive and EAD-related projects at this year's Description Expo of the Society of American Archivists.
Read more about the projects!
Read more about the projects!
Monday, June 27, 2011
Permissions Editing Simplified
EAD allows for an audience attribute to be set for any element within the schema. There are two options to select for the audience, internal and external, used to designate user permission to the content. By default, the lack of the audience attribute signifies that content of the element (and its descendants) is open to the public. Sometimes it is necessary for a finding aid to contain components for internal use, but are not intended to be seen by end users. Perhaps an entire series within an archival collection contains private materials--financial or membership records--but within this series are a few items which may be publicly highlighted.
EADitor now enables the editing of any of the attributes for components, including the setting of audiences.

The attribute popup pictured above is shown upon clicking the "@" link adjacent to the "Edit Component" heading at the top of the image. This link is also visible next to each EAD component under the Subcomponents tab. This popup window is an XBL component, and can very easily be applied to any element within the XForms application. The XBL file parses the EAD 2002 schema to look up the name of the element and extract all attributes and attribute groups associated with the element to dynamically populate the window (see code here).
Moreover, there is now a specific interface for editing component permissions, accessible from the administrative page (code):
Components with their audience attribute set to "internal" appear orange, while "external" ones appear green. Components that lack the audience attribute inherit the audience of their parent, which, in the case of top-level series, are visible by default.
The XSLT stylesheets to render finding aids into public XML and HTML documents were modified to put these permissions into practice. The stylesheets packaged with the EADitor general distribution will show only the unit title of an internal component if it contains an external descendant; otherwise, internal components are hidden entirely. These stylesheets can be modified fairly easily to show containers, unit dates, or other desired elements.

Ultimately, EADitor should accommodate the modification of the audience for any element in EAD--not just components as a whole--but such a feature is a delicate balancing act between usability and function. Setting the permissions at a more granular level should not interfere with the ease of the user interface. Implementation of more sophisticated access controls is ultimately dependent on user demand.
EADitor now enables the editing of any of the attributes for components

The attribute popup pictured above is shown upon clicking the "@" link adjacent to the "Edit Component" heading at the top of the image. This link is also visible next to each EAD component under the Subcomponents tab. This popup window is an XBL component, and can very easily be applied to any element within the XForms application. The XBL file parses the EAD 2002 schema to look up the name of the element and extract all attributes and attribute groups associated with the element to dynamically populate the window (see code here).
Moreover, there is now a specific interface for editing component permissions, accessible from the administrative page (code):

The XSLT stylesheets to render finding aids into public XML and HTML documents were modified to put these permissions into practice. The stylesheets packaged with the EADitor general distribution will show only the unit title of an internal component if it contains an external descendant; otherwise, internal components are hidden entirely. These stylesheets can be modified fairly easily to show containers, unit dates, or other desired elements.

Ultimately, EADitor should accommodate the modification of the audience for any element in EAD--not just components as a whole--but such a feature is a delicate balancing act between usability and function. Setting the permissions at a more granular level should not interfere with the ease of the user interface. Implementation of more sophisticated access controls is ultimately dependent on user demand.
Thursday, June 9, 2011
Improving Authority Control in EADitor
Having just returned Sunday from LOD-LAM and gotten pumped up on linked open data and learned about all sorts of cool stuff, I was eager Monday to get started on improving authority control in EADitor (much of which will later be applied to the Numishare general distribution). I learned of VIAF, an OCLC corporate and personal name authority service, and set off to integrate this service into EADitor's XBL components in the same way that one searches geonames for the EAD geogname element or id.loc.gov for LCSH terms for subject.

I was able to get this working in just a few short hours the other day thanks to VIAF's well-documented APIs. Like geonames, the EADitor user can still select arbitrary terms from local authority lists or input new names, but searching VIAF will go a long way toward tightening controlled access terms in EAD finding aids. Moreover, it will enable direct linking to various services from the finding aid display page itself, and those services often provide external links to other useful sites, like wikipedia or worldcat.

The links to terms listed above point the user to EADitor's search results page for that particular query. The image to the right of the term links the user to the URI for that term, hosted by the appropriate service, e.g., http://www.geonames.org/4811020/ for Kirby (W.Va.) or http://viaf.org/viaf/126085739/ for the American Numismatic Society. Also of note here is another significant change. The results from geonames are transformed into AACR2-compliant place names, with the exception of Malaysia since I have not yet been able to find a list of standard abbreviations for its territories.
I see also another use for controlled vocabulary service integration. Third parties will be able to query the EAD collection for finding aids which contain particular terms. For example, suppose that from the VIAF record for Thomas Jefferson (http://viaf.org/viaf/41866059/) one can link back to an institution's search results page for finding aids containing @authfilenumber '41866059' from @source 'viaf'.
After all, better metadata is the foundation for better information systems.
NOTE the code is available below:
http://code.google.com/p/eaditor/source/browse/trunk/xbl/eaditor/corpname/corpname.xbl
http://code.google.com/p/eaditor/source/browse/trunk/xbl/eaditor/geogname/geogname.xbl
http://code.google.com/p/eaditor/source/browse/trunk/xbl/eaditor/persname/persname.xbl

I was able to get this working in just a few short hours the other day thanks to VIAF's well-documented APIs. Like geonames, the EADitor user can still select arbitrary terms from local authority lists or input new names, but searching VIAF will go a long way toward tightening controlled access terms in EAD finding aids. Moreover, it will enable direct linking to various services from the finding aid display page itself, and those services often provide external links to other useful sites, like wikipedia or worldcat.

The links to terms listed above point the user to EADitor's search results page for that particular query. The image to the right of the term links the user to the URI for that term, hosted by the appropriate service, e.g., http://www.geonames.org/4811020/ for Kirby (W.Va.) or http://viaf.org/viaf/126085739/ for the American Numismatic Society. Also of note here is another significant change. The results from geonames are transformed into AACR2-compliant place names, with the exception of Malaysia since I have not yet been able to find a list of standard abbreviations for its territories.
I see also another use for controlled vocabulary service integration. Third parties will be able to query the EAD collection for finding aids which contain particular terms. For example, suppose that from the VIAF record for Thomas Jefferson (http://viaf.org/viaf/41866059/) one can link back to an institution's search results page for finding aids containing @authfilenumber '41866059' from @source 'viaf'.
After all, better metadata is the foundation for better information systems.
NOTE the code is available below:
http://code.google.com/p/eaditor/source/browse/trunk/xbl/eaditor/corpname/corpname.xbl
http://code.google.com/p/eaditor/source/browse/trunk/xbl/eaditor/geogname/geogname.xbl
http://code.google.com/p/eaditor/source/browse/trunk/xbl/eaditor/persname/persname.xbl
Subscribe to:
Posts (Atom)