We kicked off this past month with a hackathon, hosted by our Marist College partners, to plan and start developing the part of Project Electron that enables the transfer of digital records from donor/depositor organizations to the RAC over a secure network connection. We worked with the Marist College team, including Marist students, to diagram the transfer structure and dependencies, building from the transfer specifications that we released in June and discussed in our last blog update. These specify the metadata and structural requirements for transfer and provide a bag profile to validate bags from donors. Additionally, we created wireframes and started building out the user interfaces (UIs) to view and track transfer information, view error messages, and manage user and organizational accounts. Continue reading
I am happy to introduce myself as the newest member of the RAC’s D-Team! I’ve joined the RAC thanks to the generous support of the Ford Foundation to work on Project Electron, and to help facilitate the transfer of digital records from our donor organizations. My work will have a specific emphasis on usability and user-centered design, a core value of Project Electron. Continue reading
This month we’re excited to announce the release of the first version of a specification for transferring digital records to the RAC over a network connection. In line with our project value of supporting archival practices and standards, we’ve built many parts of this specification on existing standards and frameworks such as BagIt, BagIt Profiles, Activity Streams, and OAIS. We believe this approach will make the products we come up with more easily reproducible at other institutions, which is another one of our project values. Continue reading
Our major news for this month is that, after evaluating a number of existing solutions against our requirements for archival storage, we have decided to use Fedora as the repository solution for Project Electron. Although there were other systems that met many of our requirements – DSpace for example – in the end we felt that Fedora was the closest match for our needs both in terms of feature coverage and scope. It does what we want it to do without requiring us to support a lot of extra functionality or complexity. Continue reading
As I mentioned last month, we’re moving forward with Project Electron on two fronts: defining the process by which digital records are transferred to the Rockefeller Archive Center and selecting a solution to provide archival storage for those records once they are in our custody. Continue reading
As I wrote in my last update, since kicking off Project Electron in September 2016, we’ve been gathering information through conversations, surveys and a literature review, and then structuring that information into user stories and personas. In line with our “open by default” licensing principle, we’re making these design artifacts available with a CC0 license, which means you can take them and use them freely in your own local environments.
Since Project Electron kicked off in September, we’ve made significant progress on a number of different fronts. First, together with our Marist College partners, we created a milestones document which lays out major phases of work. We also developed some general principles and overall approaches to licensing project deliverables, including code, documentation and planning documents. Since we anticipate both of these documents will change over time, we’ve versioned them using git (and have pushed a copy to GitHub) so we can keep track of those changes. Continue reading
Today we’re announcing a major project to build sustainable, user-centered and standards-compliant infrastructure to support the ongoing acquisition, management and preservation of digital records so we can make them available in the broadest and most equitable way possible. Because a snappy title makes everything better, we’ve codenamed this effort Project Electron, and we even have a cool mascot (Captain Electron, discovered by our internet expert Patrick Galligan): Continue reading