Troubleshooting the scheduled Patron XML Update v9.0, v9.5, and v9.8

Transcription

1 Troubleshooting the scheduled Patron XML Update v9.0, v9.5, and v9.8 The scheduled Patron XML Update process uses batch files and Windows scheduling to take a CSV file of patron data from the student management system, convert it into a file of XML data, and upload it into Destiny. A Follett Implementation Specialist usually sets this up at the time of the installation of Destiny. This topic explains the path the data takes between the CSV file and the Destiny Job Manager summary. The goal of this topic is to empower you to review the scheduled processing configuration and resolve issues for records that are not being updated correctly in Destiny. These issues normally are manifested as "not all of my records are getting to Destiny", "new students are not getting added", "students are not being transferred to their new schools", or "patron records are not being updated". You'll do all troubleshooting on the Destiny application server, browsing the files and folders on the drives, and navigating through the Destiny web interface. To successfully complete troubleshooting, you must have access to the \FSC-Destiny\ folder on the application server. Tips for Troubleshooting This topic follows the flow of data from student management system (SMS) to Destiny. Each of the following steps: Defines the technology Asks Troubleshooting questions Provides advice to assist you in determining whether the current step contains the problem. While we recommend that you review all of the steps to ensure that your system is working as desired, the best test of the transmission of the data is to view the Update Patrons job summary information (step 7). As you work through the steps below and make changes, run the scheduled task (Step 1), and then view the outcome of the change in Destiny (Step 7). Users do not need to be out of Destiny and Destiny performance should not be affected. Step 1 - Windows scheduling (p. 1) Step 2 - Batch file configuration (p. 5) Step 3 - Batch file log data (p. 6) Step 4 - CSV to XML processing log (p. 7) Step 5 - Patron Import Converter configuration (p. 8) Step 6 - Loading the records into Destiny (p. 10) Step 7 - The Update Patrons job summary (p. 10) Review (p. 11) Step 1 - Windows scheduling The Windows scheduling service triggers the process of loading the data. This is the starting place for troubleshooting. Windows 2003 and older To open the Scheduled Tasks dialog, click Start > Control Panel, right-click on Scheduled Tasks and select Open. This opens a list of all of the scheduled tasks on the server.

2 To view all the information, choose View > Details from the menu. You can review the schedule: how often the job is configured to run, the next run time, the last run time, the result code from the last run, and the current status of the job. Normally, the name of the job(s) for running the automated patron XML update begins with "process_", such as process_patrons, or process_students, or process_faculty. You may also see a variant form of the job, such as "process_patrons - full" or "process_patrons - weekly". See the description of the Delta process, below. The Last Result code for the job When the task scheduler successfully executed the batch file, the Last Result code displays 0x0. Troubleshooting: If the Last Result code is anything other than 0x0, there is a problem with the scheduled task configuration that is preventing the operating system from executing the batch file. Use the Last Result information to guide you in what to fix about the scheduled task configuration. Batch file parameters Right-click the Name of the scheduled task and select Properties. On the Task tab, note the full value in the Run box. This is the path to the batch file in the Destiny installation that is being executed. Troubleshooting: Is this path correct? Does the batch file exist? Also on the Task tab, examine the Run as value. Troubleshooting: Is this user correct? Is the password correct? Whenever possible, Follett recommends using the SYSTEM account to execute the batch file. Note: The SYSTEM account does not use a password. On the Schedule tab, verify that the settings are configured as desired for the scheduled processing of the data. Troubleshooting: The timing of the processing should be after the automated creation of the CSV file by the SMS. Be sure to schedule the process at a time that does not conflict with other processing, such as backups of Destiny or the server. Under normal circumstances, accept the default settings for both the Settings and Security tabs. The Delta process The batch files used to automate the upload of the patron XML data have the capability of transmitting to Destiny only the "new/changed" records. This is determined by comparing the current CSV file's contents to the previous CSV file's contents. Records that are exactly the same are dropped out of processing. Only new or changed records continue through the processing to Destiny. This has been the default configuration for the batch files. If you also see variant forms of the job in the Scheduled Tasks display, such as "process_patrons - daily" and "process_patrons - weekly", this would indicate that the system is set up to do two different jobs. It is set up for using the Delta process to send only the changed records during the week, and then the entire set of data over the weekend. This process was implemented previously when using a different and much slower technology: the transform utility and.xsl stylesheets. With that technology, the processing of large files could take hours. While the Delta comparison can reduce processing time, it also increases the chance for a disconnect between Destiny and the SMS. A record that is changed or deleted in Destiny may not be updated in the SMS and would be excluded from the update because nothing changed in the CSV file. This is the primary cause of complaints regarding patrons not being updated in Destiny. New technology in the Patron Import Converter makes this comparison unnecessary for most implementations. Page 2 of 14 Copyright 2010 Follett Software Company Rev A

3 Troubleshooting Back on the Task tab, does the end of the Run statement contain "NOCOMPARE" (either upper or lower case)? We recommend that, if your patron population is under 50,000 records, you turn off the Delta processing to ensure that all records are sent to Destiny every time. 1. To turn off the Delta comparison processing, add NOCOMPARE to the end of the "Run" statement of the scheduled task. For example, the "Run" statement might be "C:\Follett\FSC-Destiny\fsc\automate\process_patrons.bat NOCOMPARE". 2. If you've made any changes to the Properties of the scheduled task, save the changes, supplying the user account password if prompted. 3. To see if the changes made to the Task Properties resolve the issue, execute the scheduled task by right-clicking the task and choosing Run. 4. View the outcome of the change in Destiny (Step 7). Windows 2008 To open Task Scheduler, click Start > Administrative Tools > Task Scheduler. This opens a list of all of the scheduled tasks on the server. To review the user-created tasks that are configured to run on the server, click Task Scheduler Library in the left pane. Here you are able to review the triggers: how often the job is configured to run, the next run time, the last run time, the last run result, and the current status of the job. Usually, the name of the job(s) for running the automated patron XML update begins with "process_", such as process_patrons, or process_students, or process_faculty. You may also see a variant form of the job, such as "process_patrons - full" or "process_patrons - weekly". See the description of the Delta process, above. The Last Result for the job When the task scheduler successfully executes the batch file, the Last Result code displays "The operation completed successfully. (0x0)". Troubleshooting: If the Last Result code is anything other than this, there is a problem with the configuration of the scheduled task that is preventing the operating system from executing the batch file. Use the Last Result information to guide you in fixing the scheduled task configuration. Batch file and parameters Right-click the name of the scheduled task, and select Properties. On the General tab, review the Security options. These options determine how the operating system executes the task. Troubleshooting "When running the task, use the following user account:" should be set to the SYSTEM account. If it is not currently, click the Change User or Group button to enter and select the NT AUTHORITY\SYSTEM account. Note: The SYSTEM account does not use a password. Make sure the Run with highest privileges check box is selected. On the Triggers tab, verify that the settings are configured as desired for the scheduled processing of the data. To make any changes, click Edit. Page 3 of 14 Copyright 2010 Follett Software Company Rev A

4 Troubleshooting: The time of the processing should be after the automated creation of the CSV file by the SMS. Be sure to schedule the process at a time that does not conflict with other processing, such as backups of Destiny or the server. On the Actions tab, click Edit to view the action configuration: Action: Should display "Start a program" Program/script: Note thefull statement in therun box. This is the pathto thebatch filein thedestiny installation that is being executed. If you didn't find the resolution to the issue in the scheduled task properties, this is the next place to look. Add arguments (optional): This may contain the term NOCOMPARE. For a discussion of this, see the Delta process information, above. Start in (optional): This must contain the drive and path to the folder containing the batch file. By default, this would be {drive}:\follett\fsc-destiny\fsc\automate\. Under normal circumstances, accept the default settings for the Conditions, Settings, and History tabs. The Delta process For a complete description of the Delta process, see the description of the Delta process, above. Troubleshooting Back on the Actions > Edit Action dialog, does the Add Arguments box contain "NOCOMPARE" (either upper or lower case)? We recommend that, if your patron population is under 50,000 records, you turn off the Delta processing to ensure that all records are sent to Destiny every time. 1. To turn off the Delta comparison processing, add NOCOMPARE to the Add Arguments box. For example the value in the Details column might read: "C:\Follett\FSC- Destiny\fsc\automate\process_patrons.bat NOCOMPARE". 2. If you've made any changes to the properties of the task, save the settings, supplying the user account password if prompted. 3. To see if the changes made to the task properties resolve the issue, execute the scheduled task by right-clicking the task, and then choosing Run. 4. View the outcome of the change in Destiny (Step 7). Page 4 of 14 Copyright 2010 Follett Software Company Rev A

5 Step 2 - Batch file configuration Within the batch file itself are a number of configuration settings that determine what data is processed, how it is processed through the Patron Import Converter utility, and how it is loaded into Destiny. This batch file also creates a log file in the same folder, letting you review the activity of the previous job runs. 1. To validate the configuration of the batch file, locate the specific batch file being executed by the scheduled task. By default, the batch file is on the Destiny application server in the \FSC- Destiny\fsc\automate\ folder. Note: The Destiny installation has a few sample batch files. Be careful to select the file specified in the scheduled task and not a sample file (that is, select process_patrons.bat, not process_patrons_ sample.bat). 2. To view the contents of the batch file, right-click the file and choose Edit. 3. Locate the CUSTOMER-SPECIFIC CONFIGURATION section. 4. In the REQUIRED VARIABLES section, find the SOURCEDIR and SOURCEFILE parameters. The values following these settings define the name and location of the CSV file from the student management system. Troubleshooting: Is this information correct? Has something changed with the location or name of the CSV file? If so, update the batch file to match the new location and/or new name of the file. Is the file current? Is the data inside the file accurate? Note: If your student management system outputs more than one file to be processed, your upload process may have been implemented with a slightly different configuration. In this case, make sure that the SOURCEDIR value is correctly defining the folder containing the multiple CSV files. 5. In the OPTIONAL VARIABLES section, note the value of the PATRON_PROP parameter. This is the file that contains the configuration data for the Patron Import Converter application. This file is used to tell the converter how to manipulate the CSV data as it converts it to XML data for Destiny. These settings are validated in step 5. Note: If you are processing student and staff data as separate loads, the PATRON_PROP value will most likely be different for the process_student.bat file and the process_staff.bat file. Note: If you do not have a PATRON_PROP setting, but instead have a STYLESHEET= setting, your Destiny is configured to use the older Transform utility. This technology uses an.xsl stylesheet technology that is much harder to support because there is no GUI. For further support on this process, contact Technical Support for assistance. 6. Also in the OPTIONAL VARIABLES section, note the value of the UPDATE parameter. The file specified here contains the information used by Destiny to upload the converted data. This is reviewed in step Also in the OPTIONAL VARIABLES section, note the value of the FINAL parameter. The file specified here contains the patron data uploaded into Destiny. This will be verified in Step In the PROCESS COMMANDLINE ARGUMENTS section, make sure the SET NOCOMPARE parameter equals FALSE. This ensures that the only time the Delta process is executed is when the NOCOMPARE string is added to the scheduled task above in step 1. Having it configured in the scheduled task allows for easier access than making a change to the batch file. 9. If any changes have been made to the batch file configuration, save the batch file. 10. To see if the changes made to the batch file resolve the issue, run the scheduled task (Step 1), and then view the outcome of the change in Destiny (Step 7). Page 5 of 14 Copyright 2010 Follett Software Company Rev A

6 Step 3 - Batch file log data When the batch file executes, activity related to the bulk of the upload process is written to a.log file of the same name. This log file is stored in the same folder as the.bat file. By default, this should be the \FSC- Destiny\fsc\automate\ folder. Within this folder should be a scrolling list of eight log files (i.e. \FSC- Destiny\fsc\automate\process_patrons.log). Open the most recent log file to review the content. Some things to note: 1. The first line in the file show the date and time of the processing. This verifies that you are viewing relevant data. 2. If the Delta process is turned off, the second line is "NOCOMPARE specified". 3. The following line shows the source CSV file that is being processed. Troubleshooting: If the log displays "Error - No Patron data found in <path>", the batch file could not find the source file and source directory specified in the batch file (step 2.4). Verify that the settings in the batch file are correct and that the CSV file does exist in that location. 4. If you're not using the Delta comparison process, you'll see the line, "Skipping the delta compare", followed by "Deleting the delta file...". If you are using the Delta comparison process, statistics regarding the comparison of the file are output to the log. This provides you with the number of records in the previous file, how many were in the current file, how many were dropped because they were the same, and how many were written out to be processed because they were new/different. Note the line stating "x rows changed". This is either the number of records in your CSV file (if running with the NOCOMPARE parameter) or the number of the new/changed records in the current CSV file (if implementing the Delta processing). Troubleshooting: If you're using the Delta process, do the processing numbers look correct? Do you see "Updating delta data..." and "0 rows were changed"? If so, this means that no data is going to be processed further until the CSV file data changes. To continue troubleshooting, you must add the NOCOMPARE parameter to the scheduled task and execute the task again (or instead execute a "full" or "weekly" load task if one exists). 5. Locate the "Generating Destiny patron import file" line. This information is about the actual conversion of the data from CSV to XML. You may see a row of dots across the file. This represents the amount of time it processed. Below that should be a list of "Completed in x minutes, x seconds". Troubleshooting: If you see the text "<<<<<< ERRORS WERE DETECTED, PLEASE EXAMINE THE LOG FILE >>>>>>" and "One or more rows were skipped because of invalid data in the CSV file", it may or may not indicate that there was a problem converting the file. In this case, you need to browse to and open the "Log data is located at <drive:\path>\fsc-destiny\fsc\patdata\<batch file name>.log" file. This is discussed next in step If you see "Updating patron data with no changes...", this means that you're using the Delta comparison process and there was no difference between the previous CSV file and the current CSV file. Rather than just stopping the process, an empty XML file named destiny_patrons_nochange.xml is passed to Destiny so that an "empty" job appears in the Job Manager. This allows you to see quickly that the process did run and that there were no changes to process. Note: The name of the file may also appear as destiny_students_nochange.xml, or something similar, based on the configuration of the processing jobs. Page 6 of 14 Copyright 2010 Follett Software Company Rev A

7 7. The line reading "Updating patron data..." indicates that the XML data has begun uploading to Destiny for processing. This may be either a file of patron data or the destiny_patrons_nochange.xml file. Troubleshooting: The log file is informational. There are no changes to make here. You can gather information gathered about what the batch file is doing or problems it is encountering. Step 4 - CSV to XML processing log The Patron Import Converter utility creates a log file of its activity while processing the file. In its simplest form, the file contains two lines: 1. Generating Destiny patron import file {path} 2. Completed in x minutes, x seconds Seeing this output confirms that there were no records exceptioned from processing according to the configuration properties (Step 5 below). If the batch file log (Step 3) displays "ERRORS WERE DETECTED, PLEASE EXAMINE THE LOG FILE", then the processing log contains additional information regarding data in the CSV file that was exceptioned out of the XML file. A number of different messages can be logged depending on the data and the configuration of the utility (Step 5): "Row 1 skipped because it matched skip criteria" In this example, the value in one of the fields matched the configured values on the Patron Matching > Skip Rules tab of the utility. This record is skipped according to the user-defined criteria. Note: This is not an error. It is informational. There is no action needed. However, this message triggers the batch file log to display the "ERRORS WERE DETECTED..." message. "Row 1 skipped because there are too few fields. Expected 18 fields but read 17." In this example, the Patron Import Converter is configured to process a CSV file that has 18 fields of data per record. The data in the current CSV file being processed is missing a field and only contains 17 fields. This record is skipped completely as the utility cannot be sure that the data would be converted correctly. Note: If the message states that it read only 1 field, you need to check the data file being processed to verify that the fields are separated by commas and not tabs. The utility views all the fields of a tabdelimited file as one field. Troubleshooting: Examine the data to find what is different about the record(s). Often the resolution to this message lies in cleaning up the patron record in the SMS system's CSV file (missing data). "Row 1 skipped because there are too many fields. Expected 18 fields but read 19." In this example, the Patron Import Converter is configured to process a CSV file that has 18 fields of data. The data in the current CSV file being processed has an extra field and now contains 19 fields. This record is skipped completely as the utility cannot be sure that the data would be converted correctly. Troubleshooting: Examine the data to find what is different about the record(s). Often the resolution to this message lies in cleaning up the patron record in the SMS system's CSV file. Look for data that contains a comma within a field (for example, the "city" value). "Row 1 skippedbecause thefollowing field(s)cannot beempty: (Matchingusing DistrictID and nodistrict ID was supplied)" Inthis example, the fieldconfigured toprovide thevalue forthe patron's districtid was there, butwas empty. This record is skipped because, without this data, theresulting recordwould bean invalidxml record. Page 7 of 14 Copyright 2010 Follett Software Company Rev A

8 "Row 1 skipped because the following field(s) cannot be empty: (Matching using Barcode& Site Short Name and no barcode was supplied)." In this example, the field configured to provide the value for the patron's barcode was there, but was empty. This record is skipped because, without this data, the resulting record would be an invalid XML record. "Row 1 skipped because the following field(s) cannot be empty: (Matching using Barcode & Site Short Name and no site short name was supplied)" In this example, the field configured to provide the value for the patron's site short name (the school where the patron attends) was there but empty. This record is skipped because, without this data, the resulting record would be an invalid XML record. Troubleshooting: The above three message all indicate the same problem. Examine the data regarding the student's unique identification value in the district and the data regarding the school the patron attends. Often the resolution to this message lies in cleaning up the patron record in the SMS system's CSV file. "Error on row 1: Unable to parse field 5 using a SimpleDateFormat. Pattern=MMddyyyy Data=Feb " In this example, the utility is expecting data in a specific format but the string of data in the field is not in the correct format. This is most commonly experienced with date fields and phone number fields. This record is processed, but the field in question is skipped. Troubleshooting: Examine the data regarding the field(s) referenced in the log. Adjust the CSV file data or the configuration of the utility. Other than the "matched skip criteria" message, these messages indicate that there is a problem with the way the data in the CSV file aligns with the configuration of the Patron Import Converter. Continue to the next step to review the settings. Step 5 - Patron Import Converter configuration To review the way the patron records are being converted from CSV to XML data, first load the data file and the configuration file into the Patron Import Converter: 1. Browse to and execute \FSC-Destiny\fsc\bin\PatronImportConverter.exe. 2. On the Data Preview tab, click the Browse button. Browse to and open your source CSV file as defined in the batch file SOURCEDIR and SOURCEFILE parameters (Step 2.4). Opening this file will ensure that you are able to evaluate your configuration against all of your CSV records instead of a set of sorted records which may not have all of your data, due to Delta processing. 3. On the toolbar at the top, click Open. Browse to and select the properties file as defined in the batch file PATRON_PROP parameter (Step 2.5). Opening this file ensures that you can evaluate your configuration using the settings implemented by the batch file. Then, review your customized settings used to convert the data: 1. On the Data Preview tab, the "Data begins on row" value should be set to 1. If your process is sending all records (NOCOMPARE parameter specified in the scheduled task) and your CSV file has a header row, this can be eliminated using the skip criteria below. If your process is sending only the new/changed records (Delta process occurring), the header record in the CSV file would not change from day to day. Therefore, because the header doesn't change, it would not be in the "sorted" records file. Having the "Data begins on row" value set higher than 1 would skip valid patron records. Troubleshooting: If your problem with the patron records is that just one patron is being skipped, this most likely is the issue. Be sure this value is set to 1. Page 8 of 14 Copyright 2010 Follett Software Company Rev A

9 2. On the Field Mapping tab, review the configuration of the fields. Verify that the data from the records at the bottom of the screen is appearing in the desired fields in the Sample Output column, and that the formatting of the data is correct. Note: For a detailed explanation of the functionality of the Patron Import Converter, see "Getting started with the Patron Import Converter" in Destiny's online help. 3. On the Patron Matching tab, make sure the settings are configured as desired: A. The "Match patrons using their" setting should be configured for District ID. When set to District ID, you can transfer patron records from one school to another. This is not possible if the matching criterion is set to "Site short name and Barcode". Troubleshooting: You should use "Site short name and Barcode" only on rare occasions or when instructed by Technical Support. B. On the Skip Rules tab, you can configure the converter to drop records based on one or more criteria. This is where you would configure the converter to drop out a header record, patrons for schools that do not exist in Destiny, or other records that you do not wish to send to Destiny. Troubleshooting: Use this option to drop out the header record of the CSV file, if needed. C. On the Delete Rules tab, you can configure the converter to create a deletion XML record to be sent to Destiny based on one or more criteria. This is most commonly used to remove records from Destiny that have a status of inactive in the student management system. Troubleshooting: In this scenario, make sure that the SMS is only exporting records for students that are not active anywhere in the district (that is, don't export an inactive record for a student at an elementary school when the student is active at a middle school). D. On the Multiple Association Rules tab, you can configure the converter to create an association XML record to be sent to Destiny based on one or more criteria. This setting is used most commonly for associating itinerant teachers with multiple buildings where they teach. This also can be used to associate students who attend classes at multiple schools. See "Managing Multiple Site Associations" in the Destiny Online Help. If you changed any settings, click Save on the toolbar to save the configuration in the properties file. To test the new settings, execute the converter: 1. Click Run on the toolbar. 2. Provide a temporary file name such as test.xml. 3. To begin the conversion of the data, click Save. When the conversion is complete, a sample section of data appears in a browser window. Review these records. Troubleshooting: Does the data look correct? Review the text.xml.log file in the folder where you saved the test.xml file. Refer to step 4 above for resolving issues. When the settings have been refined and the XML output and the log data look accurate, run the scheduled task (Step 1), and then view the outcome of the change in Destiny (Step 7). Page 9 of 14 Copyright 2010 Follett Software Company Rev A

10 Step 6 - Loading the records into Destiny Upon completion of the CSV to XML conversion, the processing batch file calls the updatepatrons.exe utility to upload the records to Destiny. The way it loads the data is stored in the update properties file defined in the processing batch file (Step 2.6). To review these settings: 1. Browse to the \FSC-Destiny\fsc\bin folder. 2. In a text editor, open the properties file specified in the UPDATE variable of the batch file (Step 2.6). 3. Review the following settings: The patronfile value will display in the Summary section of the Update Patrons job view. This value must be the same as the FINAL property configured in the batch file (Step 2.7) The username and password values must contain the credentials of a valid district user account with the "Manage Patrons for the District" permission checked. These credentials will be used in step 7 to review the job summary. Troubleshooting: Follow the login procedure in step step 7.2 to validate the credentials. The deletionsproperty is used by Destiny when a deletion XML record is being processed. If the patron to be deleted has outstanding transactions, the system will look to this setting to see if the patron should be deleted. If the value is set to false (the default), the patron record will not be deleted but will be listed on the job summary. If the value is set to true, the patron will be deleted, any copies checked out to the patron will be marked Lost, and any other transaction (fines, holds, reserves) will be deleted. The limittoerrorsandwarnings parameter is used to configure Destiny for how it should build the Update Patrons job summary. If the value is set to true (default) only errors and warnings will be in the display. This makes the report much shorter and more manageable. If the value is set to false, then there will be output in the job summary for every record processed in the XML file. If you changed any settings in the file, save the file, run the scheduled task (Step 1), and then view the outcome of the change in Destiny (Step 7, next). Step 7 - The Update Patrons job summary The final step for troubleshooting is reviewing the way the uploaded data is processed by Destiny. Up to this point in the process, all of the data handling has been outside of the program and database. Now Destiny attempts to add the data to the database. However, at this step, there are the restrictions in place to ensure that the database integrity remains uncompromised. To review the job summary: 1. Enter your Destiny address in a web browser and click Login in the upper right corner. Note: If you are at your Destiny application server, just enter " ". 2. Enter the username and password from the update properties file (Step 6.3.2), and click Login. Troubleshooting: If the credentials supplied in the update properties file return as invalid, you need to use the Destinyadmin account to either update the existing user with a new password (you must be able to supply the current password) or create a new district user with the "Manage Patrons for the District" permission. Page 10 of 14 Copyright 2010 Follett Software Company Rev A

11 Once the new/updated username/password combination is validated here, edit the update properties file with the new values and save the file. 3. Open the Job Manager: If necessary, click District in the upper right of the Welcome page. Open the Back Office tab, and then the Job Manager on the side menu. 4. Locate the most recent Update Patrons job and click View to open the summary. 5. Review the Summary section at the top: Review A. Review the Import File name and Options. Troubleshooting: Do these values match the configured settings? Are you viewing the summary for the correct file load (that is, faculty vs. student data)? Note: "Use only blank fields to clear existing information from patron" is a constant setting. You cannot change it or configure it in a properties file. B. Review the Summary section of records read, deleted, added, updated, transferred, and skipped. Troubleshooting: Does the number of records read look correct? Does it match the number of records processed by the Patron Import Converter? To verify this: 1. Compare to the value from the XML log file summary at the bottom (Step 4) 2. If the XML log file does not have a summary section at the bottom, meaning no records were exceptioned out, see the batch file log statement regarding the number of "rows changed" (Step 3.4) Note: Once you have adjusted the process to the point where the number of records read by the update process equals the number of records correctly processed by the Patron Import Converter / batch file, then you shouldn't need to make any more changes to the processing system. However, there may still need to be further work done for invalid records detailed below. Does the number of patrons added look right? These should be new patrons that were not in Destiny before. Does the number of patrons transferred look correct? If the number looks high does the CSV file contain multiple records for one patron resulting in Destiny transferring the patron from school A to school B and then back to school A? C. Review the records listed below the summary in the record detail area: Note: Records listed as Added, Updated, or Transferred may or may not need further action taken. Records listed as Skipped could not be processed by Destiny; you'll need to take further action to get this data updated in Destiny. For detailed explanations of the messages possibly encountered, see the following articles in Destiny's Online Help: "Common Exceptions in the Update Patron Job Summary" "Resolving barcode conflicts in the Update Patrons job summary" At the end, conflicts in the database caused by manual data entry must be resolved through the manual updating of the patron records. If you are unable to resolve the issues through the steps outlined in this document, contact Follett's Technical Support department to discuss where in this document you are experiencing difficulty. Page 11 of 14 Copyright 2010 Follett Software Company Rev A