In most cases there is not a lot you can or have do to prepare your Legacy Library Management System (LLMS) for migration. Our standard data migration process, i.e., migrate one LLMS set of data to Infiniti data, is performed on bibliographic, holdings, patron, and circulation records for all current patrons. We will migrate the data for each of these areas after it is delivered by you to us as either a full database backup or as a set of exported records. You can tidy up unwanted data or incorrect after before you deliver it to us or wait until after your data is migrated to Infiniti. Our Migration Team can often assist you with this tidy up as part of the standard service or as an extended service (it depends on the quality of your data).
Data migration commences with your IT Team uploading a full backup of your LLMS database or as a set of exported records via to secure FTP site - you will receive instructions for this. Remember to ensure your IT Team will be available to prepare and deliver your LLMS backup approximately 7 days prior to the date scheduled as your commencement date. See below for guidance on what has to be backed up.
What Can I Do To Prepare Our LLMS For Migration?
Individual schools store bibliographic and holdings data in their LLMS in a variety of ways, often by following a set of in-house defined rules, which only they know and understand. Please tell us about any special ways or in-house rules you have practiced with your LLMS before we convert your data, including any special codes you have used. Also advise any data that has been stored in non-conventional "locations".
Below is a non-exhaustive list of cleanup tasks you may have time to do before uploading your LLMS backup. Don't worry if you don't have time to complete some or all of these tasks as they can also be completed post migration.
Resource Data Cleanup and Samples
- complete any open inventory/stocktakes.
- clean up bibliographic data: delete all unwanted bibliographic records and associated data.
- clean up holdings data: delete all unwanted holdings records and associated data.
- transfer partially imported records from MARC sources like SCIS, Libraries Australia, Library of Congress and other suppliers into your catalogue.
- generally check data and be satisfied it is ready for migration.
Patron/User Cleanup
- clean up user/patron data: deleted unwanted patrons, loans and other circulation data.
- place all current students into valid Year Level and/or Form classes to ensure transfer to the correct Year Level/Library Group in Infiniti. Year levels must be in a range from first year to last year.
- all students who are no longer at your school should be deleted.
- all teachers who are no longer your school should be deleted.
Data Samples Help With Data Migration
The following are "nice to haves" backup documents. They may help our Migration Team and/or they may help you post conversion:
- create screen shots/captures of the profile data of a small sample (say 6 to 12) patrons/borrowers/users in your current LLMS into a Word document or a Google Doc, e.g., male, female, primary, secondary, teachers. Submit the screen images to us via the support portal. Add any descriptions that may help our migration team understand your data. Ensure your screen shots include patron unique identifiers like barcode numbers and/or logon IDs if applicable.
- create screen shots/captures of circulation data of a small sample (say 6 to 12) patron and their loan history in your current LLMS into a Word document or a Google Doc, e.g., male, female, primary, secondary, teachers. Submit the screen images to us via the support portal. Add any descriptions that may help our migration team understand your data. Ensure your screen shots include patron unique identifiers like barcode numbers .
- create screen shots/captures of the bibliographic and holdings data of a cross section of your catalogue. Include fiction and non-fiction books, teacher reference books, kits, resource boxes, AV records, digital files and samples of other data currently stored in your LLMS. A couple of samples of each record type should be enough.
Local Considerations – do you have any?
- advise us about any aspects important to your library that we should know about or consider during data migration.
- advise us of any unconventional cataloguing practices that have been undertaken.
- advise us if you have "special data" against some records, e.g, copy numbers, accession numbers, serial numbers, asset numbers, special notes, and provide us with examples of each if you want this data migrated.
Note: If your IT Support can't backup your LLMS database you will have to export data as a series of CSV files.
Bibliotech
Has a backup facility. IT support should use this facility to create the backup and zip the files before FTPing.
Bookmark
Zip a copy of the latest BackupM__.LZH, e.g., BackupM23.LZH. This is usually a series of folders, subfolders, icons, book covers. etc. Whatever is below the main folder. Data files have the names such as Data.BMD, Settings.BMD, etc. The backup should pick up all this content.
Destiny
Libcode
Is a file system database. IT support support should zip the Libcode installation folder before FTPing.
Libcode DAVE
Is a file system database. IT support support should zip the Libcode installation folder before FTPing.
MLS 3
Is an Access database. IT support should zip the MLS 3 installation directory/folder installation folder before FTPing.
MLS/Capita Eclipse
In-school system - is an MS SQL database. Perform a normal MS SQL backup of the database and zip the database files before FTPing.
Hosted system - is an MS SQL database. Request Micro Library provide a backup to your school IT support who should zip the backup files before FTPing.
OCLC
Date can be exported from OCL via a MARC export and/or a CSV export. It support should zip the exported files before FTPing.
Oliver v5