Recent Posts

As Hillel mentioned in his post about the next steps in Project Electron, we’re working on three data services for our pipelines into a new archival description interface: fetchers, transformers, and indexers. Once the fetchers grab data from a specific data source, we need the transformers to, for lack of a better word, transform that data from its original structure to a new one that fits with our proposed discovery data model before we index it for researcher access. But how do we ensure that the transformers are creating structured data that fits our data model as it’s defined? We need some sort of validation process to ensure the standardized structure of our data, which is why we’ve created a rough JSON schema that we can validate transformed data against before pushing it into our index.

A few weeks ago I wrote about the next phase of Project Electron, which is full of possibilities and challenges, and will involve the time and talents of the entire D-Team, as well as many of our RAC colleagues (I’m not going to recap that here; go read the post if you’re interested). However, while writing that post it occurred to me that Project Electron is only one part of the D-Team’s work, so I’ve summarized a number of other things we’re doing which may be relevant to the broader archival community below. Please get in touch if you’re working on similar initiatives, or if you have Opinions (good or bad) about what we’re up to!

This past summer, we ran a series of usability tests in order to gather and distill feedback from our coworkers about a redesigned interface we developed for the Rockefeller Archive Center’s Documentation Website. This blog entry continues a discussion I started in a previous post about our motivations, approach, and processes for redesigning the site in order to enhance user discovery and access. I will explain how we planned and carried out the usability tests in order to effectively evaluate the changes we have made to the platform, and I will reflect on my experience with conducting usability testing for the first time. By describing the fixes we have proposed in response to the issues identified during usability testing, I hope to create a picture of how the Documentation Site will appear when we finish development!

Last July, I wrote a blog post announcing the public release of the Rockefeller Archive Center’s Documentation Website as a platform for storing and sharing our institution’s documentation. Now, a little more than a year later, I am writing a new post to update our colleagues at the RAC and in the wider archives field about the work we have completed following the success of our efforts to make more content available. I will reflect on our motivations, approach, and processes for redesigning the site in order to enable improved discovery and access.

After Bonnie’s post reporting back on her SAA experience this year, I also wanted to share some things I learned from the conference. It’s been a few weeks now, so I’ll focus on two sessions that I’m still thinking through in relation to my own work related to accessibility and disability in archives. These were the popup session “Where Are We? The State of Accessibility in Archives”, particularly Hannah Rosen’s report on the 2019 Lyrasis Accessibility Survey, and the working group session “Neurodiversity in Archives” led by Eric Hung, Lydia Tang, Chris Tanguay, and Zachary Tumlin.