Differences
This shows you the differences between two versions of the page.
— |
phelp:helpmarcreview [2021/12/29 16:21] (current) |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | MARC REVIEW | ||
+ | |||
+ | MARC Review will search a MARC file of any size for any content, either plain text or MARC coding, or both, and produce highly-customizable reports of the search results. | ||
+ | |||
+ | When setting up a search in MARC Review, it is important to think literally. The purpose of this utility is not to replace your OPAC, but to give you the power to drill down into your data at a level the OPAC is not generally aware of. | ||
+ | |||
+ | NOTE: This program is launched from MARC Report, and the source file is set to whatever MARC file you have (most recently) selected in MARC Report. The name of the current source file is always visible in the status bar at the bottom of the screen. To switch to a different source file, double-click on the picture on the left before you go to the next screen (in either MARC Review or MARC Global). | ||
+ | |||
+ | REVIEWS | ||
+ | |||
+ | In MARC Review, you first specify the data to search for, which we call a pattern, and then you specify the output options. The combined set of these options is referred to as a ' | ||
+ | |||
+ | Reviews can be saved (the Save option appears at the end of the run). When you want to run a Review that you have previously saved, press the ' | ||
+ | |||
+ | The remainder of this help page describes the components of a pattern. There are separate help pages available for output options and saved reviews. | ||
+ | |||
+ | PATTERNS | ||
+ | |||
+ | Whether using MARC Review or MARC Global, a good understanding of the implementation of patterns is a requirement for your successful use of the software. | ||
+ | |||
+ | The basic unit of the MARC Review search is called a pattern. Each pattern that you specify will be applied to each tag in each record. To run a MARC Review, at least one pattern must be specified; there is no limit on the number of patterns that can be specified. | ||
+ | |||
+ | If you have specified more than one pattern, you can use the navigational buttons--' | ||
+ | |||
+ | When you have finished entering patterns, click the ' | ||
+ | |||
+ | The components of the pattern form are as follows: | ||
+ | |||
+ | TAG | ||
+ | |||
+ | Enter any valid MARC tag (000-999). The Tag is the only required field on the form. | ||
+ | |||
+ | If you are searching for data in a fixed field, enter the field (eg ' | ||
+ | |||
+ | It is possible to search a range of tags using the ' | ||
+ | |||
+ | You can also search the whole MARC record (000-999) for a string by entering ' | ||
+ | |||
+ | All of the remaining fields on the form qualify the MARC tag specified here. When an Indicator, Subfield, etc., is specified on the same form, they are ' | ||
+ | |||
+ | OCC (TAG) | ||
+ | |||
+ | The first occurrence field refers to the MARC Tag. You can specify a Tag's occurrence by number (by entering ' | ||
+ | |||
+ | See the 'Note about Occurrences' | ||
+ | |||
+ | INDICATOR 1 / INDICATOR 2 | ||
+ | |||
+ | If you want to find only tags with/ | ||
+ | |||
+ | Hint: If you want to search for an indicator value that is not valid, like a letter, you can turn off the form validation by right-clicking on the 'Ind 1' or 'Ind 2' label (or clicking ' | ||
+ | |||
+ | If you want to find indicators that match a range of values, you can use a regular expression in one of the Ind boxes. For example, if Tag=245 and Ind2 is [5-9] and Regular Expression is checked, the program will find all 245 fields with a second indicator in the range 5..9. | ||
+ | |||
+ | Note: To use a regular expression in an indicator box, the DATA box for the pattern should contain a single period. (The reason for this is that the routine that validates the regular expression requires a non-empty DATA value; entering a period in a regular expression will match any non-null value, so it will not harm the pattern.) | ||
+ | |||
+ | SUBFIELD | ||
+ | |||
+ | If you want to find only tags with/ | ||
+ | |||
+ | SUBFIELD PATTERNS | ||
+ | |||
+ | If more than one subfield code is entered into the SUBF box, the program assumes you want to search for tags with matching subfield patterns. This function is useful for research, troubleshooting, | ||
+ | |||
+ | For example, if you enter 245 in the TAG box and ' | ||
+ | |||
+ | Hint: To force a more literal match, enclose the subfield pattern in quotes. For example, in X10, a search for ' | ||
+ | |||
+ | Also, enclosing subfields in quotes is the only way to match subfield patterns where any subfields inthe pattern are repeated. For example, to find cases of $a $b $b $c in the 260, you must enter ' | ||
+ | |||
+ | NB. Enclosing subfields in single quotes (or double-quotes, | ||
+ | |||
+ | It is also possible to specify a negated subfield pattern using regular expression syntax. For example, if you enter 6XX in the TAG box, and ' | ||
+ | |||
+ | Finally, a regular expression can be entered into the subf box if it is enclosed in double-quotes. For example, if you want to find all 245 tags that contains at least five subfield delimiters, you could enter this into the SUBF box: | ||
+ | " | ||
+ | where each dot will match a subfield code. Or, to find all 245 tags that contain combinations of $n and $p, enter the following into the SUBF box: | ||
+ | " | ||
+ | |||
+ | Do not set the Regular expression checkbox for either of the last two examples. The program will automatically assume a regular expression when it sees enclosing quotes in the SUBF box. | ||
+ | |||
+ | |||
+ | OCC (SUBF) | ||
+ | |||
+ | The second occurrence field refers to the subfield. You can specify a Subfield' | ||
+ | |||
+ | DATA | ||
+ | |||
+ | If you want to find only records containing certain data in the tag/ | ||
+ | |||
+ | Do not enter indicators in the Data box. | ||
+ | |||
+ | To embed a subfield in the Data pattern, press < | ||
+ | |||
+ | The Data box supports regular expressions and embedded booleans (described in detail below). | ||
+ | |||
+ | REGULAR EXPRESSIONS | ||
+ | |||
+ | If the Regular Expression box is selected, the program will treat the pattern entered in the DATA box as a regular expression. The most common metacharacters used in regular expression patterns are listed below: | ||
+ | |||
+ | . | ||
+ | * | ||
+ | ^ | ||
+ | $ | ||
+ | [ begin character class definition | ||
+ | ] end character class definition | ||
+ | - | ||
+ | \ | ||
+ | |||
+ | For example, if the Regular Expression box is checked, and your data pattern contains: | ||
+ | | ||
+ | the program will match any data that contains ' | ||
+ | |||
+ | SPECIAL NOTE: Although ' | ||
+ | |||
+ | ±[^0-9a-z] | ||
+ | |||
+ | This would match any subfield delimiter ± that is followed by a character __not__ in the character class 0-9a-z. | ||
+ | |||
+ | Do not use commas to separate individual values in a character class. For example, this is the correct way to pattern match the ten numeric digits and the uppercase letters ' | ||
+ | |||
+ | [0-9ABC] | ||
+ | |||
+ | But the following regular expression will also match any string containing a comma in it: | ||
+ | |||
+ | [0-9, | ||
+ | |||
+ | PCRE | ||
+ | |||
+ | Beginning with version 236, MARC Report uses Perl Compatible Regular Expressions (PCRE), which greatly expands the pattern matching capabilities of previous versions. | ||
+ | |||
+ | If you are planning to make full use of the PCRE support in the program, then you should not use the curly braces technique (described above) for matching diacritics inside a regular expression. Instead, when matching a diacritic in a regular expression, use ' | ||
+ | |||
+ | Applying this to the example used above: to find all title fields that begin with the diacritic Ayn, search: | ||
+ | |||
+ | TAG=245 SUBF=a | ||
+ | |||
+ | if leader/09 = ' | ||
+ | if leader/09 = ' ' set the DATA box to: ^\xB0 | ||
+ | |||
+ | You can easily get a hexadecimal listing of all characters in a file by running the MARC Analysis utility on it; when the report is ready, scroll down to the bottom and look for MARC-8 or UTF-8 character set usages tables. | ||
+ | |||
+ | For more examples on using PCRE regular expressions in MARC Review, please visit: | ||
+ | http:// | ||
+ | |||
+ | For official PCRE documentation, | ||
+ | |||
+ | FINDING DIACRITCS | ||
+ | |||
+ | To search for a character not on your keyboard, you will need to know the value of the character(s) in hexadecimal format (there are many free pages on the web that provide this information--search for ' | ||
+ | |||
+ | To enter the code, prepend ' | ||
+ | |||
+ | For example, to search for the copyright character, you might enter | ||
+ | |||
+ | TAG=264 | ||
+ | |||
+ | if your records are unicode, or | ||
+ | |||
+ | TAG=264 | ||
+ | |||
+ | if your record use MARC-8 encoding. | ||
+ | |||
+ | This is not a regular expression on its own, so it does not check the regular expression box checked. | ||
+ | |||
+ | However, if you were searching for a copyright symbol only at the beginning of the subfield $c, you would instead enter (using the unicode example): | ||
+ | |||
+ | TAG=264 | ||
+ | |||
+ | and check the Regular expression' | ||
+ | |||
+ | DIACRITICS (Deprecated) | ||
+ | |||
+ | The old way to search for diacritics is now (version 248) deprecated and may not work in future versions of MARC Report and MARC Global. | ||
+ | |||
+ | This method entered the numeric value of the diacritic character enclosed in curly braces. You may use either decimal or hexadecimal notation for this number; decimal numbers must be zero-filled to three digits and fall within the range 000-255; hex numbers must begin with a ' | ||
+ | |||
+ | For example, to search for the copyright character in unciode records, enter: | ||
+ | |||
+ | TAG=264 | ||
+ | |||
+ | and select the regular expression checkbox. | ||
+ | |||
+ | Even though curly braces have another meaning in standard regular expressions, | ||
+ | |||
+ | |||
+ | CASE SENSITIVE | ||
+ | |||
+ | This option controls whether case-sensitive matching is performed on the data to be matched (if any). For example, if this box is checked, and your data pattern contains ' | ||
+ | |||
+ | RULE | ||
+ | |||
+ | The Match Rule parameter defaults to ' | ||
+ | |||
+ | The Match Rule can also be set to ' | ||
+ | |||
+ | ' | ||
+ | |||
+ | The Match Rule can also be set to ' | ||
+ | |||
+ | Use ' | ||
+ | |||
+ | Use ' | ||
+ | |||
+ | Use ' | ||
+ | |||
+ | SPECIAL RULES | ||
+ | |||
+ | ' | ||
+ | |||
+ | When a repeatable tag is specified in more than one pattern, and the rule in each pattern is ' | ||
+ | |||
+ | | ||
+ | | ||
+ | |||
+ | This review will match records where any 651 tag contains ' | ||
+ | |||
+ | 651 0$aUnited States$xEmigration and immigration$xHistory. | ||
+ | 651 0$aNew York (N.Y.)$xBuildings, | ||
+ | |||
+ | To require that both patterns be present in the same occurrence of a tag, use the ' | ||
+ | |||
+ | | ||
+ | | ||
+ | |||
+ | --then the record containing the 651 example above would not have matched; instead, only records with a 651 that matches both patterns will match; for example: | ||
+ | |||
+ | 651 0$aUnited States$xEmigration and immigration$xHistory$vJuvenile literature. | ||
+ | |||
+ | ' | ||
+ | |||
+ | When you want to perform an action in MARC Review or MARC Global only when the data in two different fields is the same (or is not the same), use the ' | ||
+ | |||
+ | ' | ||
+ | |||
+ | The data match rules must be used in pairs: the first match rule must always be ' | ||
+ | |||
+ | For example, to find all records where 049 subfield $a contains the same data as 949 subfield $a (regardless of what that data might be, as long as some data is present), use the following review: | ||
+ | |||
+ | TAG=049 SUBF=a DATA= RULE=Data | ||
+ | TAG=949 SUBF=a DATA= RULE=And/ | ||
+ | |||
+ | Another example, to find all records where 041 subfield $a contains a code that is different from that in 008/35, use the following review: | ||
+ | |||
+ | TAG=041 SUBF=a DATA= RULE=Data | ||
+ | TAG=008 POS=35 LEN=3 DATA= RULE=Not/ | ||
+ | |||
+ | When using the ' | ||
+ | |||
+ | ABOUT RULES | ||
+ | |||
+ | When we refer to a pattern in MARC Review, we usually mention the match rule at the beginning, even though on the pattern data entry form the match rule appears near the end; some examples of this marc-review-speak are: | ||
+ | |||
+ | AND 650 $x=Fiction | ||
+ | NOT 1XX AND NOT 245 I1=1 | ||
+ | |||
+ | The list of rules is context-sensitive; | ||
+ | |||
+ | |||
+ | SEARCH WHOLE RECORD | ||
+ | |||
+ | It is possible to search the whole MARC record by entering ' | ||
+ | |||
+ | One requirement of the ' | ||
+ | |||
+ | Also available in the Whole Record search is the 'Data Occ' box. This option defaults to ' | ||
+ | |||
+ | When setting up your output options for this type of review, the default is a 'Full Record', | ||
+ | |||
+ | EMBEDDED PATTERNS | ||
+ | |||
+ | It is possible, and sometimes necessary, to specify multiple patterns in a single ' | ||
+ | |||
+ | The following boolean symbols are supported within the DATA box: | ||
+ | |||
+ | && = and | ||
+ | || = or | ||
+ | !! = not | ||
+ | |||
+ | You can use the following English equivalents for the above interchangeably, | ||
+ | |||
+ | < | ||
+ | < | ||
+ | < | ||
+ | |||
+ | An example of each of these three boolean expressions follows. | ||
+ | |||
+ | ' | ||
+ | True if both ' | ||
+ | |||
+ | ' | ||
+ | True if either ' | ||
+ | |||
+ | ' | ||
+ | True if there is a $d ' | ||
+ | |||
+ | These patterns can be combined with the standard Match Rules ' | ||
+ | |||
+ | NOTE: If you use a regular expression with an embedded boolean, it must be repeated for each argument. For example: 949 $a = ' | ||
+ | |||
+ | WHEN TO USE EMBEDDED PATTERNS | ||
+ | |||
+ | Whenever you find yourself entering two separate patterns for the same MARC data element, you should consider using embedded patterns. | ||
+ | |||
+ | The standard pattern match design works well in most cases. However, especially when using ' | ||
+ | |||
+ | Specifying two separate patterns will not work, since each pattern is run on each tag. Therefore, the pattern 'NOT 035 $a (OCoLC)' | ||
+ | |||
+ | The way around this is to use an embedded pattern: 'NOT 035 $a (OCoLC)||(DLC)' | ||
+ | |||
+ | FOR BEST RESULTS | ||
+ | |||
+ | Do not specify the same MARC data element in more than one pattern. Consider the example: | ||
+ | |||
+ | Pattern1: TAG=651 SUBF=a DATA=United Rule=AND | ||
+ | Pattern2: TAG=651 SUBF=a DATA=States Rule=AND | ||
+ | |||
+ | Both patterns reference the same MARC data element (651 $a); this review would be better formed by the following: | ||
+ | |||
+ | TAG=651 SUBF=a DATA=United< | ||
+ | |||
+ | If you are stringing together a long list of terms joined by ' | ||
+ | |||
+ | LEXICAL COMPARISONS | ||
+ | |||
+ | MARC Review can also compare a user pattern against a MARC data string using the following lexical comparison operators: | ||
+ | |||
+ | -gt The MARC data is greater than the user pattern | ||
+ | -ge The MARC data is greater than or equal to the user pattern | ||
+ | -lt The MARC data is less than the user pattern | ||
+ | -le The MARC data is less than or equal to the user pattern | ||
+ | |||
+ | To use these operators in a pattern, enter the operator, followed by a blank space, followed by the string you wish to compare, in the DATA box. This syntax must be followed exactly; if the dash is not the first character entered, or if the blank space after the operator is missing, the review will not work as intended. | ||
+ | |||
+ | This option is most useful for comparing data in fixed fields, and for comparing numerical data in variable fields. For example, you can use a lexical comparison to quickly and easily pull out all records for items published before/ | ||
+ | |||
+ | In the TAG box, enter 008 and press < | ||
+ | Click the Format icon (Book + Question Mark) and select 'Any Format' | ||
+ | Enter a publication date (eg. ' | ||
+ | In the DATA box, type '-le ' before the ' | ||
+ | |||
+ | This review will find all records in the file with an 008/Date 1 that is less than or equal to 1980. (Change the '-le ' to '-gt ' to find all records in the file with an 008/Date 1 that is greater than 1980.) | ||
+ | |||
+ | Also, you can combine this review with another review. So, for example, you could find all records that have a 6XX beginning ' | ||
+ | |||
+ | Lexical comparisons can be used to compare data in variable fields, as long as no other special characters (regular expressions, | ||
+ | |||
+ | In the TAG box, enter 050; in the SUBF box, enter ' | ||
+ | In the DATA box, enter '-ge PZ7' | ||
+ | Click the 'Next Pattern' | ||
+ | Except in the DATA box, enter '-le PZ8' | ||
+ | |||
+ | This review will find all records with LC Class numbers between PZ7 and PZ8 | ||
+ | |||
+ | Note that in a variable field, the data to be lexically compared should be at the beginning of a tag or subfield. Indicators and subfields in variable fields are ignored unless they have been specified as part of the pattern. | ||
+ | |||
+ | Also note that this type of comparison will not have very good results when used on 2-digit year strings (such as those found in the MARC 008 Date Entered element). Dates before our current century will always compare greater than those of the present time; for example, Jan 1, 1999 will be seen as greater than Jan 1, 2013, because: | ||
+ | |||
+ | 990101 > 130101 | ||
+ | |||
+ | |||
+ | LIST SEARCHING | ||
+ | |||
+ | If you have a long list of items that you want to search, its possible to search them in a single step instead of creating a new pattern for each item. | ||
+ | |||
+ | For example, you could search your database for a list of control numbers, LCCNs, or ISBNs, or a list of call numbers, or a list of values from a codelist, and so on. Each time a record matches, you can use any of the usual MARC Review/MARC Global output actions. | ||
+ | |||
+ | To search a list of items you need a textfile containing these items. Each item in the list must be on a separate line. Each item should be entered exactly as it would be entered in the DATA box of a MARC Review pattern. Do not add any extra blank spaces to a line unless they are part of the item to be searched. The list must not contain any null (empty) lines, as a null line represents the end of the list to the program. | ||
+ | |||
+ | Once you have such a file of items, start MARC Review, goto the Pattern form, and enter the TAG, and SUBFIELD (if applicable) where the data from the list will be found. | ||
+ | |||
+ | Next, tab down to the DATA box, and right-click on it. An explorer window will appear--navigate to the file that contains your list, and select it. MARC Review check the file, and if it is acceptable, report the number of items loaded, put the filename in the DATA box, and flip the color of the ' | ||
+ | |||
+ | ABOUT LISTS | ||
+ | |||
+ | The maximum list size in the current version of the program is 5000 items. If your list is larger than this, an error message will appear and the list will be rejected. Simply open the list in your text editor, make it smaller, and try to load it again. | ||
+ | |||
+ | The list cannot contain data from two different fields, such as a mix of LCCNs and ISBNs. However, you could use one pattern to match a list of LCCNS and a second pattern, in the same review, to match a list of ISBNS. | ||
+ | |||
+ | All items in the list are joined together by an ' | ||
+ | |||
+ | List items are considered ' | ||
+ | |||
+ | Regular expressions per se are not supported in a list search. However, you can tell the program to match 'Whole words only'. (When a list is loaded into a pattern, the ' | ||
+ | When this option is selected, then then each item in the list must completely match the MARC data being searched. | ||
+ | |||
+ | For example, if 'Whole words only' is selected, and the MARC Data field/ | ||
+ | |||
+ | If you need to use a regular expression with a list of items, or search for terms within terms, then refer to the ' | ||
+ | |||
+ | TYPES OF LIST SEARCHING | ||
+ | |||
+ | MARC Review supports two different types of list searching: | ||
+ | |||
+ | 1. Simple list | ||
+ | 2. Value list | ||
+ | |||
+ | The " | ||
+ | |||
+ | $aDigital libraries | ||
+ | $aLibraries and people with disabilities | ||
+ | |||
+ | The "value list" search type is implemented differently. The program will match the content of the specified tag/ | ||
+ | |||
+ | $aLibraries | ||
+ | |||
+ | --it would not match headings where " | ||
+ | |||
+ | For more info and examples on list-searching, | ||
+ | http:// | ||
+ | |||
+ | TAG/ | ||
+ | |||
+ | MARC Review supports a method that will let you filter records containing tags or subfields of a specified length. For example, some OPACs may truncate a display field at a certain number of characters, and some systems may return an error when trying to load a record with a very long field. You could use this new MARC Review option to identify these records (and perhaps modify them accordingly). | ||
+ | |||
+ | In the TAG box, enter the tag number of the field you want to check. The usual MARC Review options apply here (e.g., ' | ||
+ | |||
+ | Leave the SUBF box blank to check the length of the whole tag; or, if you want to check the length of a specific subfield, specify a subfield here. | ||
+ | |||
+ | The DATA box is where you specify the length. The format that must be used is: | ||
+ | ' | ||
+ | operator (see the list below) | ||
+ | '#' | ||
+ | number (the length of the field or subfield) | ||
+ | |||
+ | The operators are: | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | |||
+ | Examples: | ||
+ | -ge# | ||
+ | -gt# | ||
+ | -le#512 Field/ | ||
+ | -lt# | ||
+ | -eq# | ||
+ | -ne# | ||
+ | |||
+ | This syntax must be followed exactly (so that MARC Review doesn' | ||
+ | |||
+ | When computing the length of a whole tag, indicators (if applicable), | ||
+ | |||
+ | HOW TO FIND RECORDS OVER A CERTAIN LENGTH | ||
+ | |||
+ | The short and simple answer is to use the MARC Verify Utility (the option ' | ||
+ | |||
+ | But you can also do this in MARC Review, and with quite alot more flexibility. The trick is to set a pattern on the Leader Record Length element. | ||
+ | |||
+ | On the pattern form, enter ' | ||
+ | |||
+ | This pattern will match all records where the leader' | ||
+ | |||
+ | |||
+ | NOTE ABOUT FIXED FIELDS | ||
+ | |||
+ | When working with Fixed Fields, the typical action is to enter the field in the Tag box, and then press the TAB key to bring up the Fixed Field Template. However, there are some cases when you do not want to do this. | ||
+ | |||
+ | If you simply want to test for the presence of a Fixed Field (eg. NOT 008), more than one Fixed Field (eg. AND 008 OCC=2), or search a complete Fixed Field without respect to position or length or format (eg. AND 008=' eng '), then instead of pressing TAB, click directly on the Data, Occ, or Rule box, as applicable. | ||
+ | |||
+ | The key is to keep the Pos and Len boxes empty (and pressing TAB will always set them to something when the Templates form closes). Whenever the Pos and Len boxes are empty in a Fixed Field pattern, the program will search the whole field for your pattern, without regard to position, length, or format. | ||
+ | |||
+ | You can also manually enter a position and a length for a Fixed Field. But since the default behavior is to not show these boxes, you will have to: enter a fixed field in the TAG box, press Tab, then press Cancel, to make the POS and LEN boxes appear on the form. | ||
+ | |||
+ | You can use this manual entry, for example, to search for data in fixed fields that is greyed out in the fixed field templates (like certain leader bytes that are not intended to be changed by a cataloger). | ||
+ | |||
+ | Finally, if you are on the Pattern form and need to re-display the Templates form, simply put your cursor in the TAG box and press TAB (assuming a fixed field has already been entered in the TAG box). | ||
+ | |||
+ | Hint: You can use MARC Review to find Fixed Fields that are not the correct length. For the 008, enter ' | ||
+ | |||
+ | Finding 007 length problems is more time-consuming because the 007 is a different length for each format; the trick is to follow the above steps for EACH type of 007. For example, enter ' | ||
+ | |||
+ | In either case, be sure to save the results as MARC records so that you can fix them in MARC Report. | ||
+ | |||
+ | NOTE ABOUT TAG OCCURRENCES | ||
+ | |||
+ | An additional feature of the Tag occurrence option is the ability to specify a relative occurrence vrs an absolute occurrence. This is necessary to allow advanced searching of repeatable fields (one of the most complex aspects of MARC, at least from the program' | ||
+ | |||
+ | In MARC Review (and MARC Global), all user-entered occurrences are absolute by default. This means that whenever you enter a specific occurrence number, the program will find a match only if 1) that occurrence of the tag exists, and 2) that occurrence of the tag matches your pattern. In short, the program simply goes to the specified occurrence and tries to match the pattern. | ||
+ | |||
+ | The following example shows a record that contains two 035 tags: | ||
+ | |||
+ | 035 $a(OCoLC)12345678 | ||
+ | 035 $a(FMlbTmq)2003012345 | ||
+ | |||
+ | If we were to enter a pattern consisting of ' | ||
+ | |||
+ | However, if we used the same pattern, the following record would not match, because the second occurrence does not contain ' | ||
+ | |||
+ | 035 $a(FMlbTmq)2003012345 | ||
+ | 035 $a(OCoLC)12345678 | ||
+ | 035 $a(FMlbTmq)2003012345 | ||
+ | |||
+ | If we want to find all records with two (or more) 035 tags that contained the same pattern (eg. ' | ||
+ | |||
+ | To set-up a ' | ||
+ | |||
+ | When a relative occurrence is specified, the program will evaluate every aspect of the pattern that you specify before it checks for occurrence. Therefore, if we use the same pattern as above (Tag=035, Occ=2, Data=FMlbTmq), | ||
+ | |||
+ | In the current version, the Relative Occ option applies only to tags (not to subfields). | ||
+ | |||
+ | ADDITIONAL HELP | ||
+ | |||
+ | If you come across a problem that you cannot solve using the methods on this page, please send us an email. There is usually a workaround that will do the job; or we may be able to update the program to meet your need. Don't be shy about this. We want MARC Review to do the things that need to be done by our customers. | ||