User Tools

Site Tools


cat:database_maintenance

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
cat:database_maintenance [2017/08/23 13:50] ehardycat:database_maintenance [2018/10/11 20:15] (current) – external edit 127.0.0.1
Line 1: Line 1:
-======  Database Maintenance  ====== 
  
-===== <font 12px/Arial,Helvetica,sans-serif;;inherit;;inherit>Qualifications for doing PINES Database Maintenance Work:</font> =====+=====Database Maintenance ======
  
- All related bibliographic searching and matching knowledge/skills as required for PINES Cat1sknowledge 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.+===== Qualifications for doing PINES Database Maintenance Work=====
  
-===== <font 12px/Arial,Helvetica,sans-serif;;inherit;;inherit>Steps in importing, merging, or updating bibliographic records:</font> =====+All related bibliographic searching and matching knowledge/skills as required for PINES Cat1s: knowledge of PINES title control numbers (TCNs); knowledge ofand experience withthe use of Z39.50 interface to OCLC’s WorldCatand experience with using transfer and merging functions in PINES Evergreen.
  
-  -+===== Guidelines for importing, merging, or updating bibliographic records: =====
  
-<font 12px/Arial,Helvetica,sans-serif;;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> 
  
-  -+  * 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.” In these cases, investigate whether you need to merge records. Currently, Evergreen does not stop you from importing a duplicated record when the PINES record had a nonOCLC based TCNs. For instance, you won’t see a warning “matching record found on i0890240825”, so please be extra careful in searching to avoid importing duplicated records in such cases. Evergreen also does not warn of collisions based on dentifiers such as ISBNs, LCCNs, 024s, 028s, or ISSNs.
  
-<font 12px/Arial,Helvetica,sans-serif;;inherit;;inherit>CurrentlyEvergreen does not stop you from importing duplicated record whose other numbers (ISBNLCCN, etc) may be used as TCNs of pines recordsFor 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>+  * Update older records encounteredparticularly if you are attaching new itemswith current OCLC versions (such as a CIP record). However, a PINES record may have added ISBNs or other useful notes such as 520/505better subject headings, etc.; so please enter that data from the PINES record, preferably making those edits in OCLC before overlaying the record.
  
-  -+  * 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 12px/Arial,Helvetica,sans-serif;;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>+  * Overlay any PINES record with a TCN anything other than an OCLC number with a matching OCLC record. This will replace the TCN with the OCLC number.
  
-  - 
  
-<font 12px/Arial,Helvetica,sans-serif;;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>+===== Transferring copies to better records or merging duplicated records: =====
  
-  - 
  
-<font 12px/Arial,Helvetica,sans-serif;;inherit;;inherit>If the PINES record uses anything other than an OCLC number for the TCN but the record matches the in-coming OCLC recordyou may overlay the PINES record so that its TCN will be an number based on an OCLC number.</font>+  * Sometimes volumes or copies are attached to the wrong bibliographic record with correct holdings attached. In this case the incorrect volumes or copies should be transferred to the correct record rather than merging or overlaying. All catalogers are encouraged to transfer volumes and copies when a postings on the CAT-L list suggests transferring their copies from incorrect records to matching onesespecially when TCNs of both are provided. And catalogers are encourage to inform the list when they discover volumes and items that should be transferred.
  
-=====  Transferring copies to better records or merging duplicated records:  =====+  * All PINES CAT1 catalogers have merging authority, so they are responsible for merging duplicate records within their own system. They are also encouraged to help PINES merge obvious duplicated records across the system.
  
-  - 
- 
-<font 12px/Arial,Helvetica,sans-serif;;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> 
- 
-  - 
- 
-<font 12px/Arial,Helvetica,sans-serif;;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.1503496238.txt.gz · Last modified: 2018/10/11 20:15 (external edit)