User Tools

Site Tools


cat:database_maintenance

This is an old revision of the document!


Database Maintenance

<font 12.0pt/inherit;;inherit;;inherit>Qualifications for doing PINES Database Maintenance Work:</font>

All related bibliographic searching and matching knowledge/skills as required for PINES Cat1s: knowledge of PINES title control numbers (TCNs); knowledge of, and experience with, the use of Z39.50 interface to OCLC’s WorldCat, and experience with using transfer and merging functions in PINES Evergreen.

<font 12.0pt/inherit;;inherit;;inherit>Steps in importing, merging, or updating bibliographic records:</font>

  1. <font 12.0pt/inherit;;inherit;;inherit>Avoid bringing in duplicate records or overlaying wrong records in PINES. Always search PINES database again before importing a record. When loading an in-coming OCLC record, please stop the process if you are warned of a matching record found in PINES. For example: “A record with TCN ocm33023358 already exists.”</font>
  2. <font 12.0pt/inherit;;inherit;;inherit>Currently, Evergreen does not stop you from importing a duplicated record whose other numbers (ISBN, LCCN, etc) may be used as TCNs of pines records. For instance, you won’t see a warning as “matching record found on ISBN [020]—i0890240825”, so please be extra careful in searching to avoid importing duplicated records in such cases.</font>
  3. <font 12.0pt/inherit;;inherit;;inherit>If the matching record is an old version of an OCLC record and the in-coming OCLC record has been updated (such as a CIP record), replace the PINES old record with the updated one. However, a PINES record may have added ISBNs or other useful notes such as 520/505, etc.; so please make a printout of the PINES record before overlaying it if additional information is present. That way, you can re-enter that data from the PINES record.</font>
  4. <font 12.0pt/inherit;;inherit;;inherit>If the PINES record has the original OCLC number but the bibliographic record has been altered, please report the case to the PINES Cataloging Coordinator.</font>
  5. <font 12.0pt/inherit;;inherit;;inherit>If the PINES record uses anything other than an OCLC number for the TCN but the record matches the in-coming OCLC record, you may overlay the PINES record so that its TCN will be an number based on an OCLC number.</font>

Transferring copies to better records or merging duplicated records:

  1. <font 12.0pt/inherit;;inherit;;inherit>All catalogers are encouraged to respond to postings on the CAT-L list, suggesting transferring their copies from poor records to good ones, especially when TCNs of both the bad and the good records are provided for such a purpose.</font>
  2. <font 12.0pt/inherit;;inherit;;inherit>All PINES CAT1 catalogers have merging authority, so they are responsible for merging duplicate records with their own system. They are also encouraged to help PINES merge obvious duplicated records across the system.</font>
cat/database_maintenance.1503496136.txt.gz · Last modified: 2018/10/11 20:15 (external edit)