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/04 22:57] robert.macgregor |
public:nnels:cataloguing:new-create-modify-record-set-in-marcedit [2024/04/05 00:01] robert.macgregor |
||
---|---|---|---|
Line 104: | Line 104: | ||
The 306 field is for the length of an audiobook. | The 306 field is for the length of an audiobook. | ||
- | Example: | + | Example: |
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. | This is only used for audiobooks. | ||
- | **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" | "Start of summary...End of summary" | ||
- | Or the source at the end may be different, eg: " | + | Or the source at the end may be different, eg: " |
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 - Subject Headings (Parsed) | + | ====<note important> |
This is an important field that can be difficult at times. | This is an important field that can be difficult at times. | ||
- | Important note: Drupal only parses the 650 field, which is for topical | + | Important note: Drupal only parses the 650 field, which is for Topical |
We use FAST Subject Headings (and remove the rest). | We use FAST Subject Headings (and remove the rest). | ||
- | LoC subject terms will be in the form: =650 \0$aSubject term.\\ | + | LoC subject terms will be in the form: |
- | FAST subject terms will be in the form: =650 \7$aSubject term.$2fast\\ | + | FAST subject terms will be in the form: |
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: |
The 4 indicates that the taxonomy is unidentified. | The 4 indicates that the taxonomy is unidentified. | ||
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 149: | Line 150: | ||
LoC term:\\ | LoC term:\\ | ||
- | =650 \0$aWomen$xSocial conditions. | + | **=650 \0$aWomen$xSocial conditions.** |
FAST term:\\ | FAST term:\\ | ||
- | =650 \4$aWomen%%--%%Social conditions.\\ | + | **=650 \4$aWomen%%--%%Social conditions.**\\ |
or\\ | or\\ | ||
- | =650 \7$aWomen%%--%%Social conditions.$2fast | + | **=650 \7$aWomen%%--%%Social conditions.$2fast** |
The subfield indicator separating the terms is replaced by 2 dashes (%%--%%). | The subfield indicator separating the terms is replaced by 2 dashes (%%--%%). | ||
- | =650 \7$aWomen$xSocial conditions.$2fast\\ | + | **=650 \7$aWomen$xSocial conditions.$2fast**\\ |
This should be changed to:\\ | This should be changed to:\\ | ||
- | =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 instead of 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, Social conditions instead of Women%%--%%Social conditions). | ||
Line 168: | Line 169: | ||
Also be aware that some FAST syntaxes are different than LoC. For example, place names. | Also be aware that some FAST syntaxes are different than LoC. For example, place names. | ||
- | LoC: =650 \0$aGeorgia (Atla.)\\ | + | LoC: |
- | FAST: =650 \4$aAtlanta%%--%%Georgia. | + | FAST: |
- | LoC is City first with State/ | + | LoC is City first with State/ |
The majority of FAST terms can simply be derived from LoC terms by just taking the first part of the LoC subject term. This is most apparent when it comes to fiction.\\ | The majority of FAST terms can simply be derived from LoC terms by just taking the first part of the LoC subject term. This is most apparent when it comes to fiction.\\ | ||
LoC adds the term $vFiction at the end of subject terms for works of fiction. For example:\\ | LoC adds the term $vFiction at the end of subject terms for works of fiction. For example:\\ | ||
- | =650 \0$aMissing persons$vFiction.\\ | + | **=650 \0$aMissing persons$vFiction.**\\ |
The FAST term would just be:\\ | The FAST term would just be:\\ | ||
- | =650 \4$aMissing persons. or =650 \7$aMissing persons.$2fast | + | **=650 \4$aMissing persons.** or **=650 \7$aMissing persons.$2fast** |
**Where to find FAST subject terms** | **Where to find FAST subject terms** | ||
Line 205: | Line 206: | ||
For example you may omit this term from the 650 field: | For example you may omit this term from the 650 field: | ||
- | =650 \0$aDetective and mystery fiction.\\ | + | **=650 \0$aDetective and mystery fiction.**\\ |
- | There are also deprecated LoC terms to keep an eye out for - some of the 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.**\\ |
- | =650 \0$aRomance stories.\\ | + | **=650 \0$aRomance stories.**\\ |
- | =650 \0$aLove stories.\\ | + | **=650 \0$aLove stories.**\\ |
+ | |||
+ | These can be removed as well. | ||
====655 - Genre Headings (Parsed)==== | ====655 - Genre Headings (Parsed)==== | ||
Line 223: | Line 226: | ||
**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 auther or are about Canada; Indigenous materials follows the same principle.\\ | + | **Canadian terms** are used for items by a Canadian auther or are about Canada; Indigenous materials follows the same principle.\\ |
- | 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.\\ |
- | Biographies and autobiographies will usually have another genre term related to the subject of the biography (ie: Music if the biography is about a musician).\\ | + | **Biographies and autobiographies** will usually have another genre term related to the subject of the biography (ie: Music if the biography is about a musician).\\ |
Do not use both Canadian drama and Drama - just one term. Same with Poetry. | Do not use both Canadian drama and Drama - just one term. Same with Poetry. | ||
Line 281: | Line 284: | ||
====Create a List of ISBNs==== | ====Create a List of ISBNs==== | ||
- | - 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 | + | - 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 {{ : | - 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 | - 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 | ||
Line 296: | Line 299: | ||
====Batch Search for Records==== | ====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==== | ||
+ | |||
+ | | ||
+ | - 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==== | ||
+ | |||
+ | Have a look through the final .mrk file to check that the Subject Headings were added properly. |