From 6e4fd8acb45d6418970631524f84c5995e6dc7c6 Mon Sep 17 00:00:00 2001 From: rsoulliere Date: Tue, 27 Sep 2011 08:56:18 -0400 Subject: [PATCH] Apply fixes to exporting MARC records -- patch from Dan Scott. --- 1.6/admin/migratingdata_1.6.xml | 21 ++++++++++----------- 2.0/admin/migratingdata_2.0.xml | 20 ++++++++++---------- 2 files changed, 20 insertions(+), 21 deletions(-) diff --git a/1.6/admin/migratingdata_1.6.xml b/1.6/admin/migratingdata_1.6.xml index a443dfe770..dd830ae171 100644 --- a/1.6/admin/migratingdata_1.6.xml +++ b/1.6/admin/migratingdata_1.6.xml @@ -690,17 +690,17 @@ COMMIT;
Exporting Bibliographic Records into MARC files migratingexporting bibliographic recordsMARC - The following procedure explains how to export Evergreen bibliographic records into MARC files using the marc_export support script. All steps should be performed by the - opensrf user from your Evergreen server. + The following procedure explains how to export Evergreen bibliographic records into MARC files using the marc_export support script. All steps should be + performed by the opensrf user from your Evergreen server. - Create a text file list of the Bibliographic record ids you would like to export from Evergreen. One way to do this is using SQL: + Create a text file list of the Bibliographic record IDs you would like to export from Evergreen. One way to do this is using SQL: SELECT DISTINCT bre.id FROM biblio.record_entry AS bre - JOIN asset.call_number AS acn ON acn.record-bre.id - WHERE bre.deleted='false' and ownling_lib=101 \g /home/opensrf/records.txt; + JOIN asset.call_number AS acn ON acn.record = bre.id + WHERE bre.deleted='false' and owning_lib=101 \g /home/opensrf/records.txt; - This query will create a file called records.txt containing a column of distinct ids of items owned by the organizational unit with the + This query will create a file called records.txt containing a column of distinct IDs of items owned by the organizational unit with the id 101. @@ -710,13 +710,13 @@ SELECT DISTINCT bre.id FROM biblio.record_entry AS bre - Run marc_export, using the id file you created in step 1 to define which files to export. + Run marc_export, using the ID file you created in step 1 to define which files to export. cat /home/opensrf/records.txt | ./marc_export -i -c /openils/conf/opensrf_core.xml \ -x /openils/conf/fm_IDL.xml -f XML --timeout 5 > exported_files.xml - The example above export the records into MARCXML format. + The example above exports the records into MARCXML format. For help or for more options when running marc_export, run marc_export with the option: @@ -726,8 +726,8 @@ SELECT DISTINCT bre.id FROM biblio.record_entry AS bre - Processing time for exporting records will depond on several factors such as the number of records you are exporting. It is recommended that you divide the - export id files (records.txt) into manageable number of records if you are exporting a large number of records. + Processing time for exporting records depends on several factors such as the number of records you are exporting. It is recommended that you divide the + export ID files (records.txt) into a manageable number of records if you are exporting a large number of records.
@@ -741,7 +741,6 @@ SELECT DISTINCT bre.id FROM biblio.record_entry AS bre The major advantages of the command line approach are its speed and its convenience for system administrators who can perform bulk loads of authority records in a controlled environment. - Run marc2are.pl against the authority records, specifying the user name, password, MARC type (USMARC or XML). Use STDOUT redirection diff --git a/2.0/admin/migratingdata_2.0.xml b/2.0/admin/migratingdata_2.0.xml index cf8ce7c92c..90268aaee5 100644 --- a/2.0/admin/migratingdata_2.0.xml +++ b/2.0/admin/migratingdata_2.0.xml @@ -669,17 +669,17 @@ COMMIT;
Exporting Bibliographic Records into MARC files migratingexporting bibliographic recordsMARC - The following procedure explains how to export Evergreen bibliographic records into MARC files using the marc_export support script. All steps should be performed by the - opensrf user from your Evergreen server. + The following procedure explains how to export Evergreen bibliographic records into MARC files using the marc_export support script. All steps should be + performed by the opensrf user from your Evergreen server. - Create a text file list of the Bibliographic record ids you would like to export from Evergreen. One way to do this is using SQL: + Create a text file list of the Bibliographic record IDs you would like to export from Evergreen. One way to do this is using SQL: SELECT DISTINCT bre.id FROM biblio.record_entry AS bre - JOIN asset.call_number AS acn ON acn.record-bre.id - WHERE bre.deleted='false' and ownling_lib=101 \g /home/opensrf/records.txt; + JOIN asset.call_number AS acn ON acn.record = bre.id + WHERE bre.deleted='false' and owning_lib=101 \g /home/opensrf/records.txt; - This query will create a file called records.txt containing a column of distinct ids of items owned by the organizational unit with the + This query creates file called records.txt containing a column of distinct IDs of items owned by the organizational unit with the id 101. @@ -689,13 +689,13 @@ SELECT DISTINCT bre.id FROM biblio.record_entry AS bre - Run marc_export, using the id file you created in step 1 to define which files to export. + Run marc_export, using the ID file you created in step 1 to define which files to export. cat /home/opensrf/records.txt | ./marc_export -i -c /openils/conf/opensrf_core.xml \ -x /openils/conf/fm_IDL.xml -f XML --timeout 5 > exported_files.xml - The example above export the records into MARCXML format. + The example above exports the records into MARCXML format. For help or for more options when running marc_export, run marc_export with the option: @@ -705,8 +705,8 @@ SELECT DISTINCT bre.id FROM biblio.record_entry AS bre - Processing time for exporting records will depond on several factors such as the number of records you are exporting. It is recommended that you divide the - export id files (records.txt) into manageable number of records if you are exporting a large number of records. + Processing time for exporting records will depends on several factors such as the number of records you are exporting. It is recommended that you divide the + export ID files (records.txt) into manageable number of records if you are exporting a large number of records.
-- 2.11.0