Migrated Data vs. New Cataloging
Migrated Data in Item Records
Because there are differences in how III displays and defines certain data elements from the way Sirsi did, our migrated records will look different in some ways from new cataloging that we put into Millennium. Below is a migrated item record. The Sirsi item record information displays as a 945 field. The III barcode field is on a separate line after the 945, as is the internal note (what we called a staff note in Sirsi). The rest of the III item record information is in the item record fixed fields. If you are editing an item record that migrated from Sirsi (for example, changing the item location fixed field), do not remove the 945 field information; we can use it to run reports to identify records that need cleanup in the new system.
Item Records for New Cataloging
New item records created in Millennium (or exported from Connexion) will have a different appearance from those migrated from Sirsi. Some item record information will be in the item record fixed fields. The 949 field from the OCLC record will not appear as a character string in the item record (as it does in migrated item records). Instead, it will appear as a MARC field at the bottom of the bib record (as it did in Sirsi). Item record variable fields for barcode and internal notes (cataloger's initials/date and OCLC number) will be below the fixed fields.
In Millennium, the bib record has duplicate call number fields. The call number index must be based on data in the bib record. Because we used our item record call numbers to build the index, the Sirsi item record call number appears in the "Call no." field in Millennium. The field lacks a subfield b in our migrated records (see example on next page). What was the Sirsi bib call number field is labeled "Misc." Only the "Call no." field is indexed.
Kathleen Wells, May 2010