Why Do RDA Conversion?
At the recent Ex Libris Users of North America in Minneapolis, Mark Sanford from William Paterson University spoke about his project to convert the library’s legacy bibliographic data to RDA compliance. Now all their data is more unified, and we will do the same work on new cataloging records that they send to us for processing.
➔ Why was this needed? Some reasons include the fact that their discovery layer had RDA requirements, and there was the potential to use RDA 33X and 34X fields to improve format facets.
See Mark’s presentation here. Please feel free to contact him for more information on their individual experience.
A good number of libraries do this type of work at the point of migration to a new system in order to showcase it in its best light. Migrating to Alma? Or already up on another new system? This work has been successfully performed in Ex Libris Aleph, Ex Libris Alma, Ex Libris Voyager, Follett Destiny, Koha, III Polaris, III Millennium, III Sierra, Sirsi Dynix Horizon, Sirsi Dynix Symphony, etc.
Want more information, including a preliminary quote? Send your inquiry to [email protected] or call us at 800-531-7678.
Written by Joan Chapa, MLS