From 90f74e4424101940627532073580e527f7bf3d43 Mon Sep 17 00:00:00 2001 From: Robert Soulliere Date: Tue, 8 Feb 2011 15:37:17 -0500 Subject: [PATCH 1/1] Move making electronic resources visible in the catalog to the cataloguing chapter since the process is more of a catalogiuing function not migration/systems function. --- 1.6/admin/migratingdata_1.6.xml | 36 --------------------------------- 1.6/stafftasks/cataloging.xml | 23 +++++++++++++++++++++ 2.0/admin/migratingdata_2.0.xml | 36 --------------------------------- 3 files changed, 23 insertions(+), 72 deletions(-) diff --git a/1.6/admin/migratingdata_1.6.xml b/1.6/admin/migratingdata_1.6.xml index b32c0086a1..4fe48515a0 100644 --- a/1.6/admin/migratingdata_1.6.xml +++ b/1.6/admin/migratingdata_1.6.xml @@ -616,42 +616,6 @@ COMMIT; the convenience of patron loads and the cost of processing these loads vs staff adding patrons manually. -
- Making Electronic Resources Visible in the Catalogue - migratingimporting bibliographic recordselectronic resources - For electronic resources that should be visible in the catalogue without any copies, you must set the source column value in the record.biblio_entry row for the respective - bibliographic record to a value that matches the corresponding ID of the config.bib_source where the transcendant value is - TRUE. Here's a practical example: - - - Connect to your Evergreen database with psql (substitute username / database name as required): - -psql -U postgres evergreen - - - - Add a source for your electronic resources: - - -# INSERT INTO config.bib_source(quality, source, transcendant) - VALUES (50, 'Institutional repository', TRUE); - - - - Find the ID that was generated for your new source: - -# SELECT ID FROM config.bib_source WHERE source = 'Institutional repository'; - - - - Update the source column for your bibliographic record for the electronic resource (for the sake of the example, let's assume that the ID returned from the new - source was 4, and that we know that the bib record with ID 75 is an electronic resource from your institutional repository): - -# UPDATE biblio.record_entry SET source = 4 where biblio.record_entry.id=75; - - - -
Restoring your Evergreen Database to an Empty State If you've done a test import of records and you want to quickly get Evergreen back to a pristine state, you can create a clean Evergreen database schema by performing the diff --git a/1.6/stafftasks/cataloging.xml b/1.6/stafftasks/cataloging.xml index e9c7145ef0..89c83a5f3c 100644 --- a/1.6/stafftasks/cataloging.xml +++ b/1.6/stafftasks/cataloging.xml @@ -608,6 +608,29 @@
+
+ Cataloguing Electronic Resources -- Finding Them in OPAC searches + cataloguingelectronic resources + For electronic resources to be visible in the catalog, you should add the 9 subfield in the 856 data field to indicate + which organizational units will be able to find the resource. + + + Open the record in the cataloging module + + + Add the 9 subfield to the record and enter the short name of the organizational unit for the value. For example: +856 40 $u http://lwn.net $y Linux Weekly News $9 BR1 + would make this item visible to people searching in a library scope that contains BR1. + You can enter more than one 9 subfield or you can enter the parent organizational unit to make this item visible in more than + one organizatuional unit under the same parent organizational unit. + + + + Save the record + After a short time the electronic resource should appear in OPAC searches + + +
Printing Spine and Pocket Labels labelsspine diff --git a/2.0/admin/migratingdata_2.0.xml b/2.0/admin/migratingdata_2.0.xml index 8fd026c044..db86f3e073 100644 --- a/2.0/admin/migratingdata_2.0.xml +++ b/2.0/admin/migratingdata_2.0.xml @@ -612,42 +612,6 @@ COMMIT; the convenience of patron loads and the cost of processing these loads vs staff adding patrons manually.
-
- Making Electronic Resources Visible in the Catalogue - migratingimporting bibliographic recordselectronic resources - For electronic resources that should be visible in the catalogue without any copies, you must set the source column value in the record.biblio_entry row for the respective - bibliographic record to a value that matches the corresponding ID of the config.bib_source where the transcendant value is - TRUE. Here's a practical example: - - - Connect to your Evergreen database with psql (substitute username / database name as required): - -psql -U postgres evergreen - - - - Add a source for your electronic resources: - - -# INSERT INTO config.bib_source(quality, source, transcendant) - VALUES (50, 'Institutional repository', TRUE); - - - - Find the ID that was generated for your new source: - -# SELECT ID FROM config.bib_source WHERE source = 'Institutional repository'; - - - - Update the source column for your bibliographic record for the electronic resource (for the sake of the example, let's assume that the ID returned from the new - source was 4, and that we know that the bib record with ID 75 is an electronic resource from your institutional repository): - -# UPDATE biblio.record_entry SET source = 4 where biblio.record_entry.id=75; - - - -
Restoring your Evergreen Database to an Empty State If you've done a test import of records and you want to quickly get Evergreen back to a pristine state, you can create a clean Evergreen database schema by performing the -- 2.43.2