Curator's Workbench
The Curator’s Workbench is a tool that automates and streamlines the process of preparing collections of digital materials for submission to a repository. The Workbench will capture and stage files, generate manifests that include fixity information, arrange folders and objects, normalise metadata to custom requirements, and finally create a submission package for ingest into the archive.
Provider
Carolina Digital Repository, an initiative of the University Libraries of UNC Chapel Hill.
Licensing and cost
Apache 2.0 – free.
Development activity
Version 4.1.5 of the Curator’s Workbench was released in April 2014. The software was created for the Carolina Digital Repository, and continues to be developed to support the workflow needs of UNC Libraries.
Platform and interoperability
The software is built upon the Eclipse Rich Client Platform, using Eclipse’s Modeling Framework and Graphical Modeling Framework, and requires Java 7. Standalone versions have however been compiled for 32-bit Windows and 64-bit Windows, Mac OSX and Linux. The software incorporates iRODS jargon client libraries, and is extensible by plug-in.
Functional notes
The Workbench’s crosswalk tool is able to map user-supplied metadata fields to MODS elements, allowing the user to define how each MODS record is created, which elements are used and where they come from in the source metadata. This can be done at the project level, allowing batch staging; the software is capable of migrating thousands of descriptive records at a time and linking them to data objects. As of version 4.0, crosswalks can be copied between projects and reused, and common mappings can shared by means of data dictionaries.
As materials are selected, arranged, and described, the software generates a METS file that documents these processes. In addition, it generates checksums and UUIDs for each object. When a project is ready for submission, an export function translates the internal METS into an XML-viewable submission package ready for ingest. BagIt export is also supported.
Curator’s Workbench was designed for use in the Carolina Digital Repository, which uses a web interface for ingest into a Fedora repository with iRODS storage. To address the unreliability of web ingest, the software can stage files in advance. In the CDR setup, individual users have accounts in a staging area within the iRODS grid; files placed there by the Workbench are readable by the Fedora instance at ingest time, at which point they are also copied into archival storage.
Documentation and user support
Carolina Digital Repository does not provide direct support. There are Google groups for users and developers, though the former seems to be only intermittently used and the latter remains entirely unused. Issues may be reported using the GitHub issue tracker.
The Workbench incorporates its User Manual into its help system but does not provide a separate PDF instance of the document. Some technical information is available on a GitHub wiki.
Usability
The Workbench GUI is extremely simple and easy to use, although solid familiarity with metadata standards is essential.
Expertise required
Installation and configuration require deep system administration knowledge.
Standards compliance
The Workbench uses METS XML for project definition files and submission files, provides BagIt as an export option, and incorporates MODS XML for description.
Influence and take-up
Curator’s Workbench is used within the UNC library system.
- Home
- Digital curation
- About us
- News
- Events
- Resources
- Briefing Papers
- Introduction to Curation
- Annotation
- Appraisal and Selection
- Curating Emails
- Curating e-Science Data
- Curating Geospatial Data
- Data Accreditation
- Data Citation and Linking
- Data Protection
- Database Archiving
- Digital Repositories
- Freedom of Information
- Genre Classification
- Interoperability
- Persistent Identifiers
- Trust Through Self Assessment
- Using OAIS for Curation
- Web 2.0
- What is Digital Curation?
- Common Directions in Research Data Policy
- 5 Steps to Research Data Readiness
- Citizen Science
- Making the Case for RDM
- Legal Watch Papers
- Standards Watch Papers
- Technology Watch Papers
- Introduction to Curation
- How-to Guides & Checklists
- Appraise & Select Research Data for Curation
- Cite Datasets and Link to Publications
- Develop RDM Services
- Develop a DMP
- Discover Requirements
- Five Steps to Decide What Data to Keep
- Five Things You Need to Know About RDM and the Law
- License Research Data
- Track Data Impact with Metrics
- Using RISE
- Where to keep research data
- Write a Lay Summary
- Developing RDM Services
- Reviewing research data platform capabilities at CISER
- Using EPrints to Build a Repository for UEL
- Assigning DOIs at Bristol
- DMPs in the Arts and Humanities
- Improving RDM at Monash
- Improving Research Visibility
- Increasing Participation in Training
- RDM Training for Librarians
- RDM strategy: moving from plans to action
- Storing and Sharing Data in Hull
- Curation Lifecycle Model
- Curation Reference Manual
- Peer review
- Editorial Board
- Completed chapters
- Appraisal and Selection
- Archival Metadata
- Archiving Web Resources
- Automated Metadata Generation
- Curating Emails
- File Formats
- Investment in an Intangible Asset
- Learning Object Metadata
- Metadata
- Ontologies
- Open Source for Digital Curation
- Preservation Metadata
- Preservation Scenarios for Projects Producing Digital Resources
- Preservation Strategies
- Principles for Enabling Access to Engineering Design Information Through Life
- Scientific Metadata
- The Role of Microfilm in Digital Preservation
- Chapters in production
- Policy and legal
- Data Management Plans
- Tools
- Case studies
- Repository audit and assessment
- Standards
- Publications and presentations
- Roles
- Curation journals
- Informatics research
- External resources
- Online Store
- Briefing Papers
- Training
- Projects
- Community
- Tailored support
