The functionality for creating original records in Evergreen, at least for PINES libraries, is minimal. PINES libraries are encouraged to add original records to OCLC first and then import the record into PINES. We, at least by policy, allow only very specific kinds of items to be added to the PINES database without a corresponding OCLC record. These records tend to be for ephemeral items, kits created by libraries and other formats that they do not intend to loan via ILL. If a PINES library must create a record in PINES for something outside those parameters in order to get an item out quickly (or if no one on staff is trained to add items to OCLC), they are encouraged to follow up to get a more complete record in OCLC and overlay the PINES record with that record. As a result, there may not be full functionality to create all elements of a complete MARC record.
Elaine J. Elaine Hardy PINES Bibliographic Projects & Metadata Manager Georgia Public Library Service 1800 Century Place, Ste 150 Atlanta, Ga. 30345-4304 404.235-7128 404.235-7201, fax [email protected] www.georgialibraries.org www.georgialibraries.org/pines ----- Original Message ----- From: "Repke de Vries" <[email protected]> To: "Evergreen Discussion Group" <[email protected]> Sent: Tuesday, September 22, 2009 8:43:10 AM GMT -05:00 US/Canada Eastern Subject: [OPEN-ILS-GENERAL] Original cataloging: the produced TCN does not seem to follow MARC We are evaluating with Evergreen 1.4 and testing "first" or "original" cataloging where our library & archive has unique material and is the first in the world to catalogue. Here is for example how our template looks like for cataloging audio material: http:// screencast.com/t/mM0HJcEgY In MARC field 040 [1] in the template we pass on to Evergreen "who we are" as Cataloging Source: AmISG Cataloging finished we expected Evergreen to - construct a Title Control Number (TCN) starting with AmISG and followed by some unique sequential number; - to create a MARC 001 field [2] holding that concatenated string "AmISG" "unique number" What we observe is: - "AUTO-GENERATED" instead of "AmISG", followed by a unique number - there is no 001 field created at all; instead - only visible after exporting the record: a 900 of Evergreen's choice: 901 \\$aAUTOGENERATED-11$bAUTOGEN$c20 Is there any Evergreen setting we forgot to look at ? Should we add a 003 field with "AmISG" to our cataloging templates ? Surely Evergreen can do original cataloging according to MARC ? (TCN-s already present in MARC 001 when pre-cataloging or importing existing records are handled fine) (I know from a question on this list by UPEI in Canada that the string AUTO-GENERATED can be changed but that leaves the lacking automatic 001 field generation) Thanks, Repke, IISH [1] http://www.loc.gov/marc/bibliographic/bd040.html [2] http://www.loc.gov/marc/bibliographic/bd001.html [3] http://www.loc.gov/marc/bibliographic/bd003.html
