This shows you the differences between two versions of the page.
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/03 17:30] robert.macgregor [Appendix B - Batch Method for Copying 650 fields] |
public:nnels:cataloguing:new-create-modify-record-set-in-marcedit [2024/04/04 23:49] robert.macgregor |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | Notes:\\ | ||
- | Update Marc Field Text File\\ | ||
- | Update Genre Terms Excel Sheet\\ | ||
- | Upload files and include in this Doc\\ | ||
- | |||
- | Preamble of files to download\\ | ||
- | List of Important sites\\ | ||
- | Screenshots - WorldCat, Z39.50\\ | ||
- | |||
- | Formatting\\ | ||
- | **This is a .txt file with some of the following Marc fields that can be copy and pasted into MarcEditor** | ||
- | |||
======Creating and Modifying Record Sets in MarcEdit====== | ======Creating and Modifying Record Sets in MarcEdit====== | ||
- | |||
- | * [[https:// | ||
- | * Set up the Z39.50 module in MarcEdit using the OCLC credentials provided to you. | ||
Marc Record Sets will need to be edited in MarcEdit in 3 different instances (listed in order from easiest to hardest): | Marc Record Sets will need to be edited in MarcEdit in 3 different instances (listed in order from easiest to hardest): | ||
Line 22: | Line 7: | ||
- **New Records** - Records that are created from scratch (this is a last case scenario if existing records can not be found to copy) | - **New Records** - Records that are created from scratch (this is a last case scenario if existing records can not be found to copy) | ||
- | Some Record Sets will be a combination of Vendor Records and/or Copy Records and/or New Records. | + | Some Record Sets will be a combination of Vendor Records and/or Copy Records and/or New Records. In each case, the Record Sets will end up being relatively similar - getting there will be slightly different. |
- | In each case, the Record Sets will end up being relatively similar - getting there will be slightly different. | + | After a Record Set has been cleaned up/ |
- | + | ||
- | After a Record Set has been cleaned up/ | + | |
=====Downloads===== | =====Downloads===== | ||
- | |Current MarcEdit | + | |Current MarcEdit |
- | |Text file with some easy to copy Marc Fields|{{ : | + | |Text file with some easy to copy Marc fields|{{ : |
- | |Excel | + | |Excel |
Line 42: | Line 25: | ||
=====Getting Started===== | =====Getting Started===== | ||
+ | |||
+ | * Set up the Z39.50 module in MarcEdit using the OCLC credentials provided to you | ||
====Vendor Records==== | ====Vendor Records==== | ||
- | In MarcEdit: | + | If the Record Set is not in .mrk format, it will need to be converted in MarcEdit: |
* If the Record Set is in .mrk format, just open in MarcEditor and modify from there | * If the Record Set is in .mrk format, just open in MarcEditor and modify from there | ||
Line 57: | Line 42: | ||
=====Important Marc Fields within a Record===== | =====Important Marc Fields within a Record===== | ||
- | These fields are for the most part mandatory, or at least significant in certain ways. When copying records from Z39.50, try to find records that match the format (ie: audiobook item -> audiobook record), although it's not entirely necessary, | + | These fields are for the most part mandatory, or at least significant in certain ways. When copying records from Z39.50, try to find records that match the format (ie: audiobook item -> audiobook record), although it's not entirely necessary. Also, generally (although not always) choose the records that are more fulsome (ie: they have more information). |
When Record Sets are ingested into the NNELS website through Drupal, the .xml file will be parsed and each Marc field will have its contents uploaded in Drupal. | When Record Sets are ingested into the NNELS website through Drupal, the .xml file will be parsed and each Marc field will have its contents uploaded in Drupal. | ||
Line 63: | Line 48: | ||
These aren't full breakdowns of each field - basic knowledge of cataloguing is assumed. | These aren't full breakdowns of each field - basic knowledge of cataloguing is assumed. | ||
- | Include end of field punctuation, | + | Include end of field punctuation, |
- | + | ||
- | Catalogue in English, although the 520 (summary) field can be in the language of the item. | + | |
====LDR==== | ====LDR==== | ||
- | Each record needs an LDR. These are partially computer generated. | + | Each record needs an LDR. These are partially computer generated. |
- | ====001, 003==== | + | ====001, 003 - Control Numbers==== |
- | These fields are for Control Numbers. | + | These will generally be in Vendor and Copied Records, but are not necessary so can be omitted in New Records. |
- | ====005==== | + | ====005 |
This is a computer generated time stamp that records the last time the record was modified. | This is a computer generated time stamp that records the last time the record was modified. | ||
- | ====006==== | + | ====006 |
- | **This field is parsed by Drupal** - It contains various pieces of information about the nature of the record (intended audience, form, format). | + | This field contains various pieces of information about the nature of the record (intended audience, form, format). |
Example: | Example: | ||
Line 90: | Line 73: | ||
* **0** indicates nonfiction - other options are: 1 = fiction, d = dramas (plays), j = short stories, p = poetry | * **0** indicates nonfiction - other options are: 1 = fiction, d = dramas (plays), j = short stories, p = poetry | ||
- | ====008==== | + | ====008 |
This field contains the information in the 006 field and more. Drupal will take all the info from the 006 field, although this field contains 3 characters indicating the language. | This field contains the information in the 006 field and more. Drupal will take all the info from the 006 field, although this field contains 3 characters indicating the language. | ||
- | ====020==== | + | ====020 |
- | Identifier. | + | This is usually the ISBN. 13 digit ISBNs start with 978, which makes them easy to spot. 10 digit ISBNs are rare now. This is a good place to grab the ISBN to search with in Z39.50. |
- | ====028==== | + | ====028 |
- | Identifier for Drupal. | + | This field contains an identifier that will be used for NNELS when doing batch uploads. |
- | ====100==== | + | ====100 |
- | **This field is parsed by Drupal** - Author' | + | Author' |
- | ====245==== | + | ====245 |
- | **This field is parsed by Drupal** - Title. | + | We take an AARC2R approach - Capitalize the first word and leave the rest in lower case, except for proper nouns (articles like The and A stay at the front of the title). |
- | Example: | + | Example: |
- | ====260, 264==== | + | ====260, 264 - Publishing Information (Parsed)==== |
- | **This field is parsed by Drupal** - Publisher information. | + | Use either 260 or 264 (not both). |
- | ====3XX==== | + | ====3XX |
These fields indicate the content type. Make sure the content types match - for example, you may use a Copied Record for a print book to create a record for an audiobook, in which case you will need to change the 3XX fields from print to audio (copy and paste-able 3XX fields are in the Marc Field Text File). | These fields indicate the content type. Make sure the content types match - for example, you may use a Copied Record for a print book to create a record for an audiobook, in which case you will need to change the 3XX fields from print to audio (copy and paste-able 3XX fields are in the Marc Field Text File). | ||
The 306 field is for the length of an audiobook. | The 306 field is for the length of an audiobook. | ||
- | Example: | + | Example: |
- | This indicated | + | This indicates |
- | ====511==== | + | ====511 |
- | **This field is parsed by Drupal** - Narrator. | + | This is only used for audiobooks. |
- | ====520==== | + | **If the author is the narrator, then write "Read by the author." |
- | **This field is parsed by Drupal** | + | ====520 |
+ | |||
+ | This can come from Vendor Records or Copied Records. | ||
"Start of summary...End of summary" | "Start of summary...End of summary" | ||
Line 136: | Line 121: | ||
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. | ||
- | ====650 - Read Carefully==== | + | ====650 |
- | **This field is parsed by Drupal** - Subject Heading. | + | This is an important field that can be difficult at times. |
Important note: Drupal only parses the 650 field, which is for topical subject terms. | Important note: Drupal only parses the 650 field, which is for topical subject terms. | ||
Line 146: | Line 131: | ||
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 | + | The 0 indicator specifically |
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.\\ | ||
Line 177: | Line 162: | ||
=650 \7$aWomen%%--%%Social conditions.$2fast | =650 \7$aWomen%%--%%Social conditions.$2fast | ||
- | When Drupal parses subject terms, it splits terms based on the subfield indicators, so if there is an $x in the subject term, the Drupal record will actually show 2 separate terms (Women, Social conditions). | + | When Drupal parses subject terms, it splits terms based on the subfield indicators, so if there is an $x in the subject term, the Drupal record will actually show 2 separate terms (Women, |
You can check [[https:// | You can check [[https:// | ||
Line 198: | Line 183: | ||
OCLC Classify was the best place to get these terms, however it has shut down. These are generally the easiest alternatives, | OCLC Classify was the best place to get these terms, however it has shut down. These are generally the easiest alternatives, | ||
- | 1. Z39.50. | + | 1. Z39.50. |
Note that sometimes these Copied Records will not come with the 650 end of field punctuation (which is a . after the subject term/before the $2). Add that in. | Note that sometimes these Copied Records will not come with the 650 end of field punctuation (which is a . after the subject term/before the $2). Add that in. | ||
Line 214: | Line 199: | ||
The terms that WorldCat provides do not have subfields or double dashes (%%--%%), however when there is a capitalized word (ie: " | The terms that WorldCat provides do not have subfields or double dashes (%%--%%), however when there is a capitalized word (ie: " | ||
- | Note: Wives Crimes against. | + | Note: Wives Crimes against. |
You may also see terms that identify the genre of the item. This is what the 655 field is for, and so can be omitted in the 650 field. | You may also see terms that identify the genre of the item. This is what the 655 field is for, and so can be omitted in the 650 field. | ||
Line 222: | Line 207: | ||
=650 \0$aDetective and mystery fiction.\\ | =650 \0$aDetective and mystery fiction.\\ | ||
- | As well as these (they are deprecated LoC terms - old Genre terms for fiction ended in " | + | There are also deprecated LoC terms to keep an eye out for - some of the old Genre terms for fiction ended in " |
=650 \0$aDetective and mystery stories.\\ | =650 \0$aDetective and mystery stories.\\ | ||
Line 228: | Line 213: | ||
=650 \0$aLove stories.\\ | =650 \0$aLove stories.\\ | ||
- | ====655==== | + | ====655 |
- | **This field is parsed by Drupal** - Genre Heading. | + | This is a mandatory field. |
- | Over time, this list will become second nature. | + | Over time, this list will become second nature. |
- | **Juvenile fiction** - for Juvenile fiction only use the Genre term Juvenile Fiction - do not include other fictional terms (still | + | **Juvenile fiction** - for Juvenile fiction only use the Genre term Juvenile Fiction - do not include other fictional terms (still |
**Young adult fiction** - treat the same as adult fiction (full genre treatment). | **Young adult fiction** - treat the same as adult fiction (full genre treatment). | ||
- | Canadian terms are used for items by a Canadian | + | Canadian terms are used for items by a Canadian |
Picture books are used only for children' | Picture books are used only for children' | ||
Illustrated material can be for adult or juvenile non-fiction - it can be a photography book, or an art book with paintings or drawings, or a technical book with diagrams.\\ | Illustrated material can be for adult or juvenile non-fiction - it can be a photography book, or an art book with paintings or drawings, or a technical book with diagrams.\\ | ||
Line 246: | Line 231: | ||
Genre Headings can be tricky. | Genre Headings can be tricky. | ||
- | Use only Genre Headings that are in the Excel sheet. | + | Use only Genre Headings that are in the Excel sheet. |
{{: | {{: | ||
- | ====700==== | + | ====700 |
- | **This field is parsed by Drupal** - Added entry. | + | This is similar to the 100 field. |
====The Rest==== | ====The Rest==== | ||
Line 260: | Line 245: | ||
=====Creating New Records===== | =====Creating New Records===== | ||
- | If there is a need to create a New Record from scratch, there is a template in the Marc Fields | + | If there is a need to create a New Record from scratch, there is a template in the Marc Fields |
=====Final Step - Converting .mrk Files to .xml for Upload to Drupal===== | =====Final Step - Converting .mrk Files to .xml for Upload to Drupal===== | ||
+ | * From the main screen of MarcEdit click on Marc Tools | ||
+ | * Select the MarcMaker Operation | ||
+ | * Open the .mrk file | ||
+ | * Save as a .mrc file (you can use the same filename, but with the different file extension) | ||
+ | * Default Character Encoding should be MARC8 | ||
+ | * Check Translate to UTF8 | ||
+ | * Click Execute - this will generate a .mrc file | ||
+ | * Select the MARC21=> | ||
+ | * Open the .mrc file | ||
+ | * Save as a .xml file (you can use the same filename, but with the different file extension) | ||
+ | * Default Character Encoding should be changed to UTF8 | ||
+ | * Uncheck Translate to UTF8 | ||
+ | * Click Execute - this will generate the .xml file. | ||
=====Appendix A - Batch Method for Copying Records===== | =====Appendix A - Batch Method for Copying Records===== | ||
Line 280: | Line 277: | ||
=====Appendix B - Batch Method for Copying 650 fields===== | =====Appendix B - Batch Method for Copying 650 fields===== | ||
- | This method is useful for large sets of Vendor Records. | + | This method is useful for large sets of Vendor Records. |
+ | |||
+ | ====Create a List of ISBNs==== | ||
+ | |||
+ | - Make sure the record set you want to add the Subject Headings to is in .mrc or .mrk format (some record sets come in .xml format and need to converted using Marc Tools module | ||
+ | - Select Tools from the toolbar in MarcEdit -> Export -> Export Tab Delimited Records {{ : | ||
+ | - Use the default delimiter options, click on the folder icons to select the .mrc/.mrk file to open and the .txt file to save the ISBNs in (this method requires that the Vendor Records have ISBNs included in them), and click Next | ||
+ | - Check Normalize field data, select 020 from the Field dropdown menu, and put " | ||
+ | - Open the .txt file in Excel | ||
+ | - The Import Wizard should open -use the default settings (Fixed width) and click next | ||
+ | - Step 2 in the Wizard allows you to move the line breaks by moving the arrows - move them to either side of the ISBN and click Finish {{ : | ||
+ | - Delete any rows and columns that don't have ISBNs - You should only have one column with 1 ISBN per cell | ||
+ | - The ISBNs will appear in scientific notation - this needs to be changed by selecting the column of ISBNs | ||
+ | - Right click on the cells and select Format Cells | ||
+ | - Click on Custom, select 0, and click OK {{ : | ||
+ | - Copy the ISBNs into a text file - one ISBN per line | ||
+ | |||
+ | ====Batch Search for Records==== | ||
+ | |||
+ | Open Z39.50 and make sure ISBN is selected from the dropdown menu, check Batch Search, click the folder icon to navigate to the .txt file, and lastly click Search to create the .mrk file that the results will be saved in. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | Z39.50 will download all records with those ISBNs into the .mrk file. | ||
+ | |||
+ | ====Formatting the Subject Headings==== | ||
+ | |||
+ | - Open the created .mrk file in MarcEditor | ||
+ | - Press CTRL+R (or on the Toolbar click Edit and then Replace) | ||
+ | - In Find enter 600 and in Replace enter 650 {{ : | ||
+ | - Repeat, except in Find enter 651 and in Replace enter 650 (these 2 steps will make sure that Drupal can parse Name Subject Headings and Place Subject Headings - because if you remember, Drupal only parses the 650 Field for Subject Headings) | ||
+ | - On the Toolbar click Tools -> Edit Field Data | ||
+ | - In Field enter 650, in Find enter $x, in Replace enter %%--%% {{ : | ||
+ | - Repeat with any other subfields that need to be changed to dashes | ||
+ | - On the Toolbar click Tools -> Edit Field Data | ||
+ | - In Field enter 650, in Find enter $2fast, in Replace enter .$2fast | ||
+ | - Now in Edit Field Data, in Field enter 650, in Find enter ..$2fast, in Replace enter .$2fast | ||
+ | |||
+ | ====Removing Non-FAST Terms==== | ||
+ | |||
+ | - In the same .mrk file on the Toolbar click Tools -> Add/Delete Field | ||
+ | - In Field enter 650, in Field Data enter $2fast, check Remove if field data does not match, then click Delete Field{{ : | ||
+ | - 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==== | ||
+ | |||
+ | - 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==== | ||
- | - Make sure the record set is in .mrc or .mrk format (some record sets come in .xml format and need to converted using Marc Tools module | + | Have a look through |
- | | + | |
- | - | + |