Metadata Migrator
An IMLS-funded tool that let small institutions map their own records to Dublin Core and share them through OAI-PMH, without writing code and without giving up control.

Built for institutions without programmers
Metadata harvesting worked well for large research libraries. They had systems that could expose records through OAI-PMH and staff who could configure them. Smaller institutions were left out. A local museum, a research centre or a small archive might keep excellent records in a desktop database, a spreadsheet or a collection management system that had no way to publish them.
The Metadata Migrator, funded by the Institute of Museum and Library Services, was designed for those institutions. It let collections specialists take their existing records and make them available for online searching through the Open Archives Initiative Protocol for Metadata Harvesting.
The users it had in mind were curators, archivists and registrars, not developers. The work it asked of them was intellectual, deciding how their fields corresponded to a common format, rather than technical.
That focus made the tool a practical bridge between small collections and large discovery services.

Map, convert, serve
The tool supported a simple sequence of steps.
- Map. A specialist matched the field names in the institution's records to Dublin Core elements. A field called
Makermight map tocreator; a field calledYear madetodate. This mapping is known as a crosswalk. - Convert. Using that mapping, the software produced OAI-compliant XML records.
- Serve. The tool set up a data provider, so OAI harvesters could collect those records and include them in larger services.
The records could then appear in aggregators of the time, including OAIster and the AmericanSouth.org portal. A researcher searching there would find an object held by a small museum alongside items from major libraries.
The steps are the same ones any institution follows today when it joins an aggregator. The tooling has changed; the logic has not. Good crosswalks still depend on people who know their own records well.
Sharing without losing control
One design choice set the Metadata Migrator apart. Institutions chose which fields from each record to include. Nothing was shared by default.
That mattered for collections with sensitive information. Records might include donor names, valuations, storage locations, condition notes or restrictions on access. None of that belongs in a public search index. With field-level selection, an institution could publish a general description of an item, enough for a scholar to know it exists and where it is, while keeping internal details private.
This also lowered the barrier to taking part. Staff could start with a few safe fields and add more as they grew comfortable with the process and saw how their records appeared.
Present-day note: the same principle applies to modern aggregation and to linked data projects. Clear, deliberate choices about what to expose build trust with the institutions that hold the records. Tools that make those choices visible tend to get more participation than tools that publish everything and ask for corrections later.

Where the tool came from
The Metadata Migrator was built as part of Music of Social Change, a MetaScholar project that connected library and museum records about music and the African American freedom struggle.
That project met the problem directly. Its partners included history museums and a music hall of fame as well as libraries, and their records were held in formats that could not talk to each other. A crosswalk tool that non-programmers could run was the simplest way to bring them into one searchable system.
The project framed the result as a model for library and museum collaboration, one that widened access to archival material for learning communities. The software was released as open source so that other institutions could use it in the same way.
For the wider history of harvesting in the programme, see the 2003 proceedings briefing and the MetaCombine project page.
