Differences
This shows you the differences between two versions of the page.
phelp:helptextview [2011/04/25 21:29] |
phelp:helptextview [2021/12/29 16:21] (current) |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | Editing in Text View | ||
+ | |||
+ | You may find it easier to use Text View for certain edit functions, such as: | ||
+ | 1) working with huge fields | ||
+ | 2) quickly deleting large numbers of fields (eg holdings tags) | ||
+ | 3) copy and paste of large chunks of data (or portions of a record that exetend beyound a single tag) | ||
+ | |||
+ | That being said, there are a few quirks about using any text editor with MARC data that must be understood, so please read through these brief instructions before using it for the first time. | ||
+ | |||
+ | |||
+ | HOW THE TEXT EDITOR WORKS | ||
+ | |||
+ | Each tag must be entered as three digits: ' | ||
+ | |||
+ | There must be one blank space (and not a TAB) after each tag: '008 ' | ||
+ | |||
+ | For control fields (tags 000 to 009), the field data starts immediately after the blank space that follows the tag: | ||
+ | |||
+ | 000 01637cam | ||
+ | 001 1577 | ||
+ | 003 PPLC | ||
+ | 005 20041120123015.0 | ||
+ | 008 881108s1988 | ||
+ | |||
+ | We do not recomment editing fixed fields using a text editor. For instance, if you edit a fixed-length field like the leader or 008, and enter an extra blank space, or delete a required blank space, the conversion program will reject the whole record, and you will have to start again. | ||
+ | |||
+ | For variable fields, the indicators start immediately after the blank space that follows the tag. There is no spacing between the indicators, and by default, the first subfield delimiter follows the second indicator: | ||
+ | |||
+ | 100 1 $aLevchenko, | ||
+ | 245 00$aOn the wrong side :$bmy life in the KGB / | ||
+ | 300 $axi, 244 p. ;$c24 cm. | ||
+ | 650 0$aSpies$zSoviet Union$xBiography. | ||
+ | |||
+ | If you prefer a blank space after the second indicator, you can change the above behavior by going to Record Display page of the program options, and selecting 'Add blank after indicators in text format', | ||
+ | |||
+ | 100 1 $aLevchenko, | ||
+ | 245 00 $aOn the wrong side :$bmy life in the KGB / | ||
+ | 300 $axi, 244 p. ;$c24 cm. | ||
+ | 650 0 $aSpies$zSoviet Union$xBiography. | ||
+ | |||
+ | INDICATORS | ||
+ | |||
+ | The example above covers all possible formats of the indicators: | ||
+ | Both indicators blank: 300 | ||
+ | First indicator blank, second coded: 650 | ||
+ | Second indicator blank, first coded: 100 | ||
+ | Both indicators coded: 245 | ||
+ | |||
+ | SUBFIELDS | ||
+ | |||
+ | To enter a subfield delimiter, use whatever the Record Display option named 'Text subfield delimiter' | ||
+ | |||
+ | OTHER FORMATTING | ||
+ | |||
+ | There should not be any blank lines between the tags. A blank line is the signal to the text-to-MARC conversion program that it has reached the end of the record. The program will try to automatically deal with blank lines, but please try to avoid creating them in the first place. | ||
+ | |||
+ | SAVE | ||
+ | |||
+ | Press Save to save any changes made in Text View to the underlying record. | ||
+ | |||
+ | Changes made in Text View are automatically applied to the underlying record as soon as you change to another view. Therefore, you can switch to Text View, edit something, switch back to MARC View (w/o pressing Save) and view the changes you made in Text View. | ||
+ | |||
+ | If you navigate to another record, and haven' | ||
+ | |||
+ | FIND AND REPLACE | ||
+ | |||
+ | Multiple-level " | ||
+ | |||
+ | PRINT FORMAT | ||
+ | |||
+ | The 'Print Format' | ||
+ | |||
+ | Press this button once to reformat the text for printing. Press the button a second time to return to normal text view. | ||
+ | |||
+ | Note that while this view is in 'print mode', the text itself is in the read-only state. The button label font color will change as a reminder that the state of the text has changed. Do not worry if you forget to press the 'Print format' | ||
+ | |||
+ | The actual printing of the record is invoked from the File|Print menu. The shortcut for printing the text view window is < | ||
+ | |||
+ | If you want to append the brief messages for the current record to the print-out, use the shortcut < | ||
+ | |||
+ | PRINT FORMAT OPTIONS | ||
+ | |||
+ | The following options may be used to customize the print format view. | ||
+ | |||
+ | Add Rec#/File Header: If checked, this will add the current record number and filename to the top of the page, followed by a blank line. | ||
+ | |||
+ | Break Lines At: Select this option to change the length at which the program tries to break the lines. By default this is set to 72. | ||
+ | |||
+ | Diacritics to Hex: If checked, the program will convert all diacritic characters to hexadecimal notation. | ||
+ | |||
+ | Blank substitute (FF): Select this option to replace all blank spaces in fixed fields with another character (e.g., replace blank spaces with '#' | ||
+ | |||
+ | Add Blanks Around Subfs: Select this to add a blank space before and after each Subfield delimiter and code. For example, with this option selected, a 260 field might look like this: | ||
+ | 260 $a Valencia, CA : $b Black Belt Communications LLC, $c 2008. | ||
+ | |||
+ | Use MARCBreaker format: If selected, the print format button will render the record in LC's MARCBreaker format. This format represents blank spaces as a ' | ||
+ | |||
+ | PRINT FORMAT NOTES | ||
+ | |||
+ | Pressing the 'Print format' | ||
+ | |||
+ | The options above remain in force for the duration of the session, or until they are changed. At present, they are not saved (from one session to another). | ||
+ | |||
+ | If MARCBreaker formatting is selected, the '' | ||
+ | |||
+ | MARCBreaker diacritic formatting supports MARC-8 data; thus, the result of using this format on a record with unicode diacritics may be strange. However, MARC Report does fully support the MARCBreaker character conversion table, which in this case is called ' | ||
+ | |||
+ | TEXT VIEW NOTES | ||
+ | |||
+ | By design, this text editor does not possess much (if any) MARC intelligence. For instance, if the record contains a string like "110 dalmatians" | ||
+ | |||
+ | If you are copying and pasting a record (from a web browser) you may run into these problems: | ||
+ | | ||
+ | The 008 is not the correct length. Unfortunately, | ||
+ | |||
+ | The first subfield delimiter in each field is missing. Check your 'blank after indicators' | ||
+ | | ||
+ | If you really mess up a record using the text editor, go back to the MARC View for the record and press ' | ||
+ | |||
+ | WRAP (Word-Wrap) | ||
+ | |||
+ | By default word-wrap is turned off in the text editor. If you are dealing with a very long field, we recommend that you first maximize the text editor window. If that still doesn' | ||
+ | |||
+ | WARNING: Watch out for embedded carriage returns in the data of a field. In MARC View, MARC Report will indicate this problem with an error message like '520: Cannot display (x0D)', | ||
+ | |||