User Tools

You are here: start » public » nnels » cataloguing » update-marc-records
Trace:

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
public:nnels:cataloguing:update-marc-records [2020/07/16 09:48]
farrah.little ↷ Links adapted because of a move operation 		public:nnels:cataloguing:update-marc-records [2024/03/14 17:17] (current)
robert.macgregor
Line 8: Line 8:
 Some metadata will be added in Drupal after the files are ingested, for example Audience and Language. Some metadata will be added in Drupal after the files are ingested, for example Audience and Language.
  
-When editing records in MarcEdit we want the files to be in .mrk format.  When we receive files from publishers they are generally in either .xml or .mrc format.  In opening screen of MarcEdit there is a button called "MARC Tools".  Click on that, and on the next screen there is a dropdown menu under "Select Operation."  MarcBreaker will convert .mrc to .mrk, and MARC21XML=>MARC21 will convert .xml to .mrc.  Using these 2 tools, we can convert the publisher files into .mrk files for editing.  After editing records in MarcEdit we want to convert them to .xml files to ingest into the NNELS repository ([[nnels:documentation:content:publishing:marc21-marcxml|see how to save to XML]]).+When editing records in MarcEdit we want the files to be in .mrk format.  When we receive files from publishers they are generally in either .xml or .mrc format.  In the opening screen of MarcEdit there is a button called "MARC Tools".  Click on that, and on the next screen there is a dropdown menu under "Select Operation."  MarcBreaker will convert .mrc to .mrk, and MARC21XML=>MARC21 will convert .xml to .mrc.  Using these 2 tools, we can convert the publisher files into .mrk files for editing.  After editing records in MarcEdit we want to convert them to .xml files to ingest into the NNELS repository ([[nnels:documentation:content:publishing:marc21-marcxml|see how to save to XML]]).
  
 ====Indicators and Subfields==== ====Indicators and Subfields====
Line 16: Line 16:
   *Ex:  =245  04$aThe Codfish Dream :$bChronicles of a West Coast Fishing Guide /$cby David Giblin   *Ex:  =245  04$aThe Codfish Dream :$bChronicles of a West Coast Fishing Guide /$cby David Giblin
   *2 spaces after the field number 245, indicators 04 (no added entry, 4 nonfiling characters - "The "), subfields $a, <space>:$b[Subtitle], <space>/$c[Author statement]   *2 spaces after the field number 245, indicators 04 (no added entry, 4 nonfiling characters - "The "), subfields $a, <space>:$b[Subtitle], <space>/$c[Author statement]
 +  *If copy cataloguing remove $h[electronic resource] if present
   *I don't think these need to be perfect - editing records in Drupal doesn't seem to affect subfields and indicators, for example adding a subtitle in Drupal won't add a $b to the MARC record   *I don't think these need to be perfect - editing records in Drupal doesn't seem to affect subfields and indicators, for example adding a subtitle in Drupal won't add a $b to the MARC record
   *We are trying to find a compromise between thoroughness and expediency, for example the author should be in field 100, so if there is no subfield $c present in the 245 field that shouldn't affect how it looks in Drupal   *We are trying to find a compromise between thoroughness and expediency, for example the author should be in field 100, so if there is no subfield $c present in the 245 field that shouldn't affect how it looks in Drupal
Line 30: Line 31:
     * 650/related fields (Subject headings - more information below) - one for each subject heading     * 650/related fields (Subject headings - more information below) - one for each subject heading
     * 655 (Genre - indicators will be /4 - we have a prescribed list here - only use these terms:  https://wiki.libraries.coop/doku.php?id=public:nnels:publishing:projects:cataloguing:metadata-cleanup:genre) - one for each genre term     * 655 (Genre - indicators will be /4 - we have a prescribed list here - only use these terms:  https://wiki.libraries.coop/doku.php?id=public:nnels:publishing:projects:cataloguing:metadata-cleanup:genre) - one for each genre term
-    * 946 (If BISAC subject headings come with the records - more information below) 
  
 ====Subject Headings==== ====Subject Headings====
  
-There is an automated process for adding subject headings in bulk to Record Sets.  We use OCLC to add FAST and Library of Congress Subject Headings.+There is an automated process for adding subject headings in bulk to Record Sets.  We use OCLC to add FAST.
  
 Here is a link to how that is done: Here is a link to how that is done:
  
 https://bclc.wiki.libraries.coop/doku.php?id=public:nnels:cataloguing:add-subject-headings https://bclc.wiki.libraries.coop/doku.php?id=public:nnels:cataloguing:add-subject-headings
- 
-===BISAC Subject Headings=== 
- 
-We have decided to keep BISAC headings if they come to us with Record Sets.  We don't want them to appear in the NNELS catalogue, but we want to store them in a hidden field for later use.  The field we will be "hiding" them in is the 946 field. 
- 
-Here is a link on how to do that: 
- 
-https://bclc.wiki.libraries.coop/doku.php?id=public:nnels:cataloguing:bisac 
  
  
public/nnels/cataloguing/update-marc-records.1594918082.txt.gz · Last modified: 2020/07/16 09:48 by farrah.little

Page Tools

BC Libraries Coop wiki

Site Tools