Laserfiche WebLink
POLARIS <br /> Schedule K <br /> Data Migration - Data Requirements <br /> Preparatory Phase <br /> Test Records <br /> o Test record sets reflecting the actual data formats to be converted must be provided to Polaris at least one <br /> month before the beginning of the migration period . <br /> Profiling <br /> o Data mappings will be reviewed and approved by the library-assigned staff prior to completion of the <br /> conversion of the first data set. A final review of the data mappings will occur after the initial data load. <br /> Once the Library and Polaris agree to any final changes to the mappings, they will be approved in writing <br /> by the Library. Final alterations to the first data set and all data mappings for the final process will reflect <br /> these signed instructions. <br /> Data Files to be Migrated <br /> Bibliographic Records <br /> The bibliographic records must adhere to the following standards: <br /> o MARC communications format. <br /> o The data is to be provided via ftp (file transfer protocol), or tape (4mm or 8mm) . The file copy format <br /> must be approved by Polaris prior to beginning the data migration. <br /> o Each bibliographic record must contain a unique record identity and a unique link to the item record file <br /> (if different than the record identity). <br /> Authority Records <br /> The authority records must adhere to the following standards: <br /> o MARC communications format. <br /> o The data is to be provided via ftp (file transfer protocol), or tape (4mm or 8mm) . The file copy format <br /> must be approved by Polaris prior to beginning the data migration, <br /> Item Records <br /> The item records must adhere to the following standards: <br /> o Holdings must be stored in 852 or 9XX tags within the bibliographic record with one tag per unique item. <br /> Data field definitions must be provided by the Library to assist us in identifying the data in the various <br /> subfields. <br /> -OR- <br /> o Holdings must be provided in an ASCII text file with one record per line and a unique delimiter to <br /> separate fields (the delimiter must be a character (or characters) that is not used within the text of the <br /> data); file structure and data field definitions must be provided by Library or thud-party vendor to assist <br /> us in identifying the data in the various columns. <br /> o If the holdings are sent in a separate ASCII text file, the records must contain unique linking IDs that <br /> relate to their respective bibliographic records. <br /> o Data is not to be compressed. <br /> o Unique barcode numbers must be used for each item. <br /> 3/20/07 Indian River County Contract Page 29 of 30 <br />