Hello Russell, Ah, DB/TextWorks -- nice thing about DBT (and similar special library toolboxes) is that they allow users to go beyond MARC and offer quick to develop, usuable interfaces for the "Jack/Jane of all trades" special librarian. The bad thing about DBT is that if you ever want to re-enter the legacy world of MARC21, you've got to re-map your way back into the sacred data chamber known as MARC21...
Some koha folks seemed to have migrated from DBT to MARC here: http://kohakenya.wordpress.com/migration/ George NRCan Library -----Original Message----- From: open-ils-general-boun...@list.georgialibraries.org [mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Russell McOrmond Sent: October 31, 2011 09:32 To: open-ils-general@list.georgialibraries.org Subject: [OPEN-ILS-GENERAL] Converting full set of DB/TextWorks fields intoEvergreen I will soon be acquiring/authoring/etc a tool to convert all fields from a series of DB/TextWorks managed databases into Evergreen. Before I do that I am wondering if anyone else has already done something like this, and can share ideas on what was done. For each DB/TextWorks database field in each database I will be creating a mapping to an existing or custom Evergreen field. While I recognize that our set of fields will be unique, I suspect there are tools out there that provide good infrastructure for doing this type of thing. Thanks. -- System Administration and software developer, Canadiana.org http://www.canadiana.ca