Last Friday, I attended the annual symposium of the Greater New York Metropolitan Area Chapter of the Association of College and Research Libraries (ACRL/NY). This year’s theme was Money and Power, and the talks covered standards, instruction, labor, and other library issues that intersect with issues of money and power.
A while ago I wrote a post detailing how data in DIMES is imported into Aeon to populate requests. Since then, I’ve had conversations with several individuals asking about the technical details of this implementation. As a way of documenting that work, and also offering some direction for future Aeon implementers, I thought I’d pull together a post describing the interaction in technical terms, since there’s limited documentation on how to do external EAD requesting for Aeon. I pieced together this information by looking at existing implementations, particularly Princeton’s archival discovery system, with a lot of false steps along the way. I hope to help others avoid the same frustrations and pitfalls! Continue reading
Among the many things that Aeon will do for us, communicating directly with DIMES to import data about our materials is among the most important, and a feature that will likely save both researchers and staff a great deal of time and frustration. Starting in February, researchers will no longer have to fill out requests for materials by hand; staff will no longer have to decipher researchers’ handwriting, correct inaccurate or missing information, or complete charge-outs by hand. In addition, we’ll be able to run much more accurate reports on use of our collections, which will help us better target digitization and preservation efforts. This post explains how that data moves from DIMES to Aeon, detailing some of the things that happen along the way with restrictions information and grouping of folders within the same box. Continue reading
Since the RAC was founded in 1974, we’ve collected information about our researchers, including contact details, visit dates, topics of research, and publications. Starting in the 1980s, we captured this information in a number of different databases. Currently, this data is stored in ATReference, a customized version of the Archivists’ Toolkit that was developed by the RAC. As part of both the Aeon and ArchivesSpace implementation processes, we needed to migrate that data forward into Aeon so we can continue to access and add to the wealth of information it contains without having to support ATReference. Continue reading
One of the sessions I found most intriguing at this year’s SAA Annual Meeting was “How Are We Doing? Improving Access Through Assessment,” which discussed a variety of tools and methodologies for quantifying information about users, collections and discovery tools, as well as how gathering that data can help us improve our users’ experience. Continue reading
As most of you know by now, we’ll be implementing Aeon here at the RAC starting in a couple of months. This will be a pretty big project, and one that gives us the opportunity to reconfigure and restructure some core reference services workflows. It’s an exciting prospect, but one that will also involve a lot of change, so I thought I’d outline the three major processes that will be affected by Aeon. Continue reading
Since a number of people weren’t able to make today’s lunch presentation, I thought I’d post the slides so those who missed out could catch up. They are pretty bare-bones, so if you have any questions, please don’t hesitate to ask!