Differences

This shows you the differences between two versions of the page.

--- evergreen-admin:importing:bibrecords [2009/05/06 23:24] – import_holdings.pl versus parse_holdings.pl phasefx
+++ evergreen-admin:importing:bibrecords [2022/02/10 13:34] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
+<html>
+<br><br><br>
+</html>
+<html>
+<h2 style="color: red;">NOTE: This are older instructions for importing MARC records into Evergreen. If you are trying out the 2.3 or newer release of Evergreen the  docs would be the place to start</h2>
+</html>
+   * http://docs.evergreen-ils.org/ - Official Evergreen Documentation home
+   * http://docs.evergreen-ils.org/dev/_system_configuration_and_customization.html
+   * http://docs.evergreen-ils.org/dev/_migrating_from_a_legacy_system.html
+<html>
+<br><br><br>
+<br><br><br>
+<br><br><br>
+</html>
+----
+<html>
+<br><br><br>
+</html>
 ======Importing bibliographic records======
@@ Line 74: / Line 101: @@
 ====Importing volumes and copies from MARC21XML holdings====
-FIXME This section has been deprecated and only still works for EG 1.2.  There is now a 1.4/trunk friendly [[http://svn.open-ils.org/trac/ILS-Contrib/browser/import_demo/trunk|import demo]] in the [[http://svn.open-ils.org/trac/ILS-Contrib|Evergreen Contrib]] repository.  Specifically, three is a parse_holdings.pl that will create an insert_holdings.sql file for loading into the database via the psql client.  There is a [[http://open-ils.org/~denials/import_demo.tar.gz|tarball]] of this import demo available for download.
-If you have relatively clean MARC21XML formatted holdings statements, you may be able to use the trunk version of [[http://svn.open-ils.org/trac/ILS/browser/branches/rel_1_2/Evergreen/src/extras/import/import_holdings.pl|Evergreen/src/extras/import/import_holdings.pl]] to add volumes and copies to your Evergreen database.
-  * Determine which field the title control number (TCN) was drawn from during the ''marc2bre.pl'' step. ''marc2bre.pl'' starts with the ''001'' field, then falls through ''020a'', ''022a'', and ''010a''. ''import_holdings.pl'' defaults to the contents of the ''001'' field.
-  * Determine into which MARC field your holdings have been exported. The [[http://www.loc.gov/marc/holdings/echdhome.html|MARC holdings format standard]] suggests ''852'', but many systems place their holdings in the ''999'' field on export. ''import_holdings.pl'' defaults to the ''999'' field.
-    * Determine which subfields of the holdings field contain the following information:
-^ Information ^ import_holdings.pl default ^ MARC 21 holdings spec (852) ^ Parameter ^
-| Barcode | $i | $p | --bc |
-| Item call number | $a | $h $i | --lbl |
-| Owning library | $m | $a or $b | --own |
-| Item price | $p | N/A | --pr |
-| Copy number | $c | $t | --cpn |
-| Availability | $k | (?) | --avail |
-  * Run ''import_holdings.pl'', specifying the file to parse as the value of the ''--marc_file'' argument and any overrides of the default values.<code>
-perl import_holdings.pl --marc_file smallset.xml
-</code> This will generate two files in your current working directory: ''asset_volume.sql'' and ''asset_copy.sql''
-  * Import the volume and copy SQL files into your Evergreen database:<code>
-psql evergreen
-# \i asset_volume.sql
-# \i asset_copy.sql
-</code>
-If all goes well, your copies will now be visible in the public OPAC.
-====Alternate approach: rough notes====
 There is currently no simple method for importing holdings based on the contents of the MARC holdings field (''852'', as specified by http://www.loc.gov/marc/holdings/). However, a more or less automated method could be built that performs the following steps:
   - Create a tab-delimited file that contains your holdings information
     * Required elements: bibliographic ID, barcode, and call number
-    * Optional elements include: shelving location (text) -- see the ''asset.copy'' table in http://svn.open-ils.org/trac/ILS/browser/trunk/Open-ILS/src/sql/Pg/040.schema.asset.sql for a complete list of possible elements
+    * Optional elements include: shelving location (text) -- see the ''asset.copy'' table in http://git.evergreen-ils.org/?p=Evergreen.git;a=blob;f=Open-ILS/src/sql/Pg/040.schema.asset.sql;hb=HEAD for a complete list of possible elements
   - Create a staging table that matches the contents of your tab-delimited file.
   - Insert the contents of your tab-delimited file into the table.
@@ Line 113: / Line 112: @@
 If an ILS has the concept of "item categories", these may be mapped to Evergreen via statistical categories in the ''asset.stat_cat'' table. Note that statistical categories cannot be used as search filters; individual branches can define their own statistical categories; and define their own statistical category entries for individual items - best use case for statistical categories is probably for gifts.
-Mike offered a basic example of a staging import here: [[importing:holdings:import via staging table]]
+Mike offered a basic example of a staging table import here: [[importing:holdings:import via staging table]]
+In 2009, Conifer placed their migration tools in the [[http://svn.open-ils.org/trac/ILS-Contrib/browser/conifer/branches/rel_1_6_1/tools/migration-scripts|Conifer ILS-Contrib SVN repository]], which might be useful samples augmenting the basic staging table import approach.
+In 2010, Equinox contributed [[http://git.esilibrary.com/?p=migration-tools.git;a=summary|a set of migration utilities]]
 =====Making electronic resources visible in the catalogue=====
@@ Line 129: / Line 131: @@
 That's all there is to it! :)
+==FIXME== OUT OF DATE
 =====Example: Importing the Project Gutenberg records=====
@@ Line 162: / Line 165: @@
 </code>
 There will be some warnings and error messages... ignore them.