User Tools

You are here: start » public » nnels » cataloguing » new-create-modify-record-set-in-marcedit
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
Next revision Both sides next revision
public:nnels:cataloguing:new-create-modify-record-set-in-marcedit [2024/04/04 23:37]
robert.macgregor 		public:nnels:cataloguing:new-create-modify-record-set-in-marcedit [2024/04/04 23:52]
robert.macgregor
Line 104: Line 104:
  
 The 306 field is for the length of an audiobook.  It needs to be in the form:  hhmmss.\\ The 306 field is for the length of an audiobook.  It needs to be in the form:  hhmmss.\\
-Example:  =306  \\$a132642\\+Example:  **=306  \\$a132642**\\
 This indicates 13 hours, 26 minutes, 42 seconds. This indicates 13 hours, 26 minutes, 42 seconds.
  
Line 111: Line 111:
 This is only used for audiobooks.  Drupal takes the field as is, so input here in the form First Name Last Name, eg:  John Doe.  If you can't figure out who the narrator is, leave it blank and it can be fixed later in Drupal.  Some Vendor and Copied Records will say "Narrated by " or "Read by: ", just delete these introductory statements. This is only used for audiobooks.  Drupal takes the field as is, so input here in the form First Name Last Name, eg:  John Doe.  If you can't figure out who the narrator is, leave it blank and it can be fixed later in Drupal.  Some Vendor and Copied Records will say "Narrated by " or "Read by: ", just delete these introductory statements.
  
-**If the author is the narrator, then write "Read by the author."**+If the author is the narrator, then write **Read by the author.**
  
 ====520 - Summary (Parsed)==== ====520 - Summary (Parsed)====
Line 118: Line 118:
  
 "Start of summary...End of summary" %%--%% Provided by Publisher.\\ "Start of summary...End of summary" %%--%% Provided by Publisher.\\
-Or the source at the end may be different, eg:  "..." %%--%% From book jacket\\+Or the source at the end may be different, eg:  "..." %%--%% From book jacket 
 Drupal parses this as is, so remove the quotation marks and the source attribution at the end. Drupal parses this as is, so remove the quotation marks and the source attribution at the end.
  
Line 125: Line 126:
 This is an important field that can be difficult at times.  There will usually be multiple 650 field entries.  We want at least one.  **Appendix B** is a batch method for copying large amounts of 650 fields at once through Z39.50. This is an important field that can be difficult at times.  There will usually be multiple 650 field entries.  We want at least one.  **Appendix B** is a batch method for copying large amounts of 650 fields at once through Z39.50.
  
-Important note:  Drupal only parses the 650 field, which is for topical subject terms.  You will come across other 6XX fields like 600 and 651 fields (people and places).  If you want these fields parsed in Drupal, you will need to change the field to 650 (it is generally safe to ignore the 648 field).+Important note:  Drupal only parses the 650 field, which is for Topical subject headings.  You will come across other 6XX fields like 600 and 651 fields (People and Places).  If you want these fields parsed in Drupal, you will need to change the field to 650 (it is generally safe to ignore the 648 field).
  
 We use FAST Subject Headings (and remove the rest).  They are essentially simplified Library of Congress (LoC) Subject Headings.  Over time working with them, they will become easier to recognize and get a feel for. We use FAST Subject Headings (and remove the rest).  They are essentially simplified Library of Congress (LoC) Subject Headings.  Over time working with them, they will become easier to recognize and get a feel for.
  
-LoC subject terms will be in the form:  =650  \0$aSubject term.\\ +LoC subject terms will be in the form:  **=650  \0$aSubject term.**\\ 
-FAST subject terms will be in the form:  =650  \7$aSubject term.$2fast\\+FAST subject terms will be in the form:  **=650  \7$aSubject term.$2fast**\\
 The 0 indicator specifically identifies Library of Congress, and the 7 means the term is from a taxonomy identified after the $2. The 0 indicator specifically identifies Library of Congress, and the 7 means the term is from a taxonomy identified after the $2.
  
-FAST terms can also be written in the form:  =650  \4$aSubject term.\\+FAST terms can also be written in the form:  **=650  \4$aSubject term.**\\
 The 4 indicates that the taxonomy is unidentified.  This is quicker and easier to do if FAST terms are not already included in the record with the \7...$2fast format. The 4 indicates that the taxonomy is unidentified.  This is quicker and easier to do if FAST terms are not already included in the record with the \7...$2fast format.
  
Line 139: Line 140:
  
 An LoC term may look like this:\\ An LoC term may look like this:\\
-=650  \0$aRefugees$zCambodia.+**=650  \0$aRefugees$zCambodia.**
  
 FAST would handle it this way:\\ FAST would handle it this way:\\
-=650  \4$aRefugees.\\ +**=650  \4$aRefugees.**\\ 
-=651  \4$aCambodia.\\+**=651  \4$aCambodia.**\\
 (and we would change the 651 to 650 to have Drupal parse it) (and we would change the 651 to 650 to have Drupal parse it)
  
Line 320: Line 321:
   - In Field enter 650, in Field Data enter $2fast, check Remove if field data does not match, then click Delete Field{{ :public:nnels:cataloguing:650_delete_non_fast.png?400 |}}   - In Field enter 650, in Field Data enter $2fast, check Remove if field data does not match, then click Delete Field{{ :public:nnels:cataloguing:650_delete_non_fast.png?400 |}}
   - A quick check should show all non-FAST Subject Headings have been deleted   - A quick check should show all non-FAST Subject Headings have been deleted
 +  - Save as a .mrk file and close MarcEditor
  
 ====Merging Subject Headings with Original .mrk File==== ====Merging Subject Headings with Original .mrk File====
  
 +  - From the main MarcEdit screen select Merge Records (if it is not there type Merge in the top-right search bar) 
 +  - The Source File is the original Vendor Set (should be in .mrk format) 
 +  - The Merge File is the .mrk file that we just created 
 +  - The Save File is the file that will be created by merging the Source and Merge Files 
 +  - Change the Record Identifier to 020$a and click Next 
 +  - In the Left Box select 650 then click the top Green Arrow (->), then click Next 
 +  - The final merged .mrk file will be created
  
 ====Final Cleanup==== ====Final Cleanup====
  
 Have a look through the final .mrk file to check that the Subject Headings were added properly.  There may be some subfields that still need to be changed to dashes (&&--&&).  There may also be some $d subfields that need to be modified as well (for Names and/or Named Events). Have a look through the final .mrk file to check that the Subject Headings were added properly.  There may be some subfields that still need to be changed to dashes (&&--&&).  There may also be some $d subfields that need to be modified as well (for Names and/or Named Events).
public/nnels/cataloguing/new-create-modify-record-set-in-marcedit.txt · Last modified: 2024/06/14 22:53 by robert.macgregor

Page Tools

BC Libraries Coop wiki

Site Tools