From b157d2f08a6850706b1754acb213ff4b14eb39eb Mon Sep 17 00:00:00 2001 From: Robert Soulliere Date: Thu, 16 Sep 2010 14:44:37 -0400 Subject: [PATCH] Found more typos. --- 1.6/admin/migratingdata.xml | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/1.6/admin/migratingdata.xml b/1.6/admin/migratingdata.xml index d5b0e4e6f0..d9844fe92a 100644 --- a/1.6/admin/migratingdata.xml +++ b/1.6/admin/migratingdata.xml @@ -16,11 +16,6 @@ system since this process may vary depending on where you are extracting your patron records. Patron could come from an ILS or it could come from a student database in the case of academic records. - - This section will explain the task of migrating your patron data from Comma Delimited Files into Evergreen. It does not deal with the process of exporting from the non-Evergreen - system since this process may vary depending on where you are extracting your patron records. Patron could come from an ILS or it could come from a student database in the case of - academic records.The Comma Delimited File used for importing the records should use Unicode (UTF8) character encoding. - When importing records into Evergreen you will need to populate 3 tables in your Evergreen database: actor.usr - This is the main table for user data @@ -32,7 +27,8 @@ in your import. It is important to understand the data types and constraints of the fields. - Export the patron data from your existing ILS or from another source into a Comma Delimited File. + Export the patron data from your existing ILS or from another source into a Comma Delimited File. The Comma Delimited File used for importing the records should + use Unicode (UTF8) character encoding. Create a staging table. A staging table will allow you to tweak the data before importing. Here is an example sql statement: -- 2.11.0