In most cases there is not a lot you can do to prepare your Legacy Library Management System (LLMS) for conversion. Our standard data conversion process, i.e., convert one LLMS set of data to Infiniti data, is performed on bibliographic, holdings, authority, patron, and circulation records and full loan history for all current patrons. We will convert the data for each of these areas as it is delivered in your LLMS backup. While you can tidy up unwanted data or incorrect after it has been converted to Infiniti, it may be easier for you to do so after your data is in Infiniti. Our conversion team can often assist you with this tidy up as part of the service or as an extended service.

Data conversion commences with your IT support officer delivering a backup of your LLMS database to our secure FTP site. You will receive instructions for this. Remember to ensure your IT support officer 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 Conversion?

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 conversion.

Resource Data Cleanup and Samples

• complete any open 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 USMARC sources like SCIS, Libraries Australia, Library of Congress and other suppliers into your catalogue.
• generally check data and be satisfied it is ready for conversion.
• create screen shots/captures of the catalogue data of a small sample (say 12) of resource records in your current LLMS into a Word document or a Google Doc, e.g., books (fiction and non-fiction), kits, resource boxes, websites, other catalogued resources - if you use Word convert it to PDF. Submit the Word document or link the Google Doc to our Conversion Team via the support portal. Add any descriptions that may help our Conversion Team understand your data.

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 Year -2 (or similar) to Year 12.
• all students who have departed from your school should be deleted.
• all teachers who have departed from your school should be deleted.

Local Considerations – do you have any? 

• advise us about any aspects important to your library that we should know about or consider during data conversion.
• 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 converted.

Note: If your IT Support can't backup your LLMS database you will have to export data as a series of CSV files.

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.