Viewing and understanding records

Clicking on a title in the results list will take you to the full record.

You can use the <  > buttons to move to the next or previous record in your results set. You can use the << and >> buttons to skip to the first or last record in your results set. The 'Back to results' button will take you back to the results list.

You can do a follow up search from the record display:

  • If the record contains an Author or other names, you can click on any name to run a search in Cataloguing for other records containing that name.
  • If the record contains Related items, you can click on any title to run a search in Cataloguing for other records for that title.
  • If a title is part of a Series, you can click on the series title to search for more works in that series.
  • If the record includes Subject keywords or terms, you can click on the terms to run a search in Cataloguing for other records containing that subject.

Online resources

Some materials are available online. Where we know a document is Open Access you will see the OA Open Access lock icon. This means the record should include a link to a freely available copy of the document online.

MARC issue reports

The MARC issue reports give details of issues identified by automated checking of the MARC structure in a record. Some issues are clear cut eg there should only be a single 245 field, others may be less so, eg checking non-filing characters isn't entirely straightforward and is dependant on the correct language code being included in the record. The issues also include a check for records where the language of cataloguing is not English; this is not an error but it may be a concern to some libraries. We will review the error checks in the light of testing and feedback. We will be looking at whether some checks create more spurious errors than they identify correct problems; as well as whether there are additional checks we can usefully include.

Summary of MARC Issue Reports
MARC Issue Explanation
Incorrect MARC leader This checks that all Leader character positions contain valid characters. Eg. it is not unusual to see records with #. This does not currently check that the codes used in the Leader are correct in the context of the rest of the record.
Incorrect 007 This checks that first two character positions contain valid characters. Character position 00 has to be a valid code. If there is a code in character position 01 this has to be valid in the context of the code in character position 00.
Incorrect 008 This checks that the first 6 characters are numeric, the date type is valid, that dates consist of a date, u | or space. Also checks the characters in character positions 38 and 39 are valid. At the moment there are no checks for material specific content.
Invalid 008 date 1 This checks character positions 6-10. If the date type is n it checks character positions 7-10 are uuuu. If the date type is b it checks character positions 7-10 are blank. Otherwise, it checks that the data starts with either 1 or 2.
No language Reports the absence of a language code in an 008 and no 041 field.
Invalid ISBN The ISBN in an 020 $a has an incorrect check digit.
Incorrectly formatted ISBN Reports an error in the ISBN in a $a, eg the inclusion of hyphens in the ISBN, or additional text in the subfield.
Invalid ISSN Reports an incorrect check digit in the ISSN in an 022 $a or $l
Incorrectly formatted ISSN Reports an error in the ISSN in a $a or $l, for example, an ISSN that is the wrong length or missing a hyphen.
Language of cataloguing is not English Reports records where the language of cataloguing is not English 040 $beng. The absence of an 040 field does not generate this error.
Mutually exclusive fields Reports the presence of both a 130 and 240; more than one of 100, 110, and 111; or the presence of both a 260 and 264.
Missing 1XX Used where a record has a 245 with indicator 1=1 but there is no 100, 110, 111, or 130. Similarly, used if the record has a 240 but no 100, 110, or 111
Invalid first Indicator First indicator isn't valid for the field in which it is used.
Invalid second Indicator Second indicator isn't valid for the field in which it is used.
Too many indicators A record might have more than two indicators, or space for more than two indicators, eg 24500 $a.
Too few indicators A record may lack an indicator and lack the space for an indicator, eg 2450$a.
Invalid subfield The subfield code is not valid within the given field. This may mean a subfield code has been capitalised, or that the code is actually missing and the first letter of the following word is being identified as the subfield code.
Missing subfield Indicates the absence of a 245$a. In an RDA record this can also indicate the absence of a 245$c; where there is an 020 it indicates there is no $q ; where there is a 700, 710, 711, 720 it indicates there is no $e or $4.
Repeating subfield A non-repeating subfield has been used more than once in the given field.
Repeating field A non-repeating field has been used more than once in a record.
Missing field This checks for the absence of a 245 or 008. In an RDA record it also checks for the absence of a 336, 337, or 338.
UTF-8 This is used where a MARC8 record appears to contain a valid UTF-8 sequence. This is likely to mean the Leader Character position 09 is incorrect, but it might also be a record that contains a mix of MARC8 and UTF-8.
Invalid UTF-8A sequence has been found that looks like invalid UTF-8. This could be in a MARC8 record or a UTF-8 record.
Escape characterAn Escape character has been used in a UTF-8 record. The presence of an escape character usually indicates MARC8, so there may be an error in the Leader character position 09. Or it may be an error in the record content.
Control characterControl characters should not appear in either UTF-8 or MARC8, but these may not be readily visible in the record. In this example our editor is showing that there is an end of field character in the middle of the 040 by using ^^, 040  $aDLC$beng$erda^^$cDLC
MARC8 A character that appears to be MARC is being used in a UTF-8 record. This may mean the Leader character position 09 is incorrect, but it might also be a record that contains a mix of MARC8 and UTF-8.
ANSEL reserved characterIn a MARC8 record this indicates a reserved character that shouldn't be used. It shouldn't appear in UTF-8, so if it does occur it may indicate the Leader character position 09 is incorrect, but it might also just be an error in the field.
Latin-1 characterThere is a character that appears to be Latin1 in either a MARC8 or UTF-8 record. This is often a copyright or pound symbol, perhaps indicating conversion from a non-MARC source.
Unicode escape sequence A unicode escape sequence in a record will look somthing like {u00BF}. It may occur where a data conversion hasn’t been able to convert a Unicode character, so it’s just been replaced it with a Unicode escape sequence to show the Unicode code-point of the character.
HTML entity An HTML entity will look something like &#x12324;. It may occur where, eg. a UTF-8 record has been converted to MARC8 and there is no character in the latter for a unicode letter, so an html entity has been used.
HTML element Checks are included for a number of common HTML tags eg. eg. <p>. These should not be included.
Incorrect character coding scheme This reports a potential Leader error where there seems to be a mis-match between the record content and the character coding scheme recorded in the Leader character position 09.
Incorrect linkage subfield Reports any formatting problems relating to an 880$6 link. The $6 must be correctly formatted and present in both the 880 and the related field.
The linkage subfield should be the first subfield Reports a $6 that doesn't appear as the first subfield in the field given.
Missing associated field Indicates an 880 that has a non-zero $6 but with no link in the associated field, or the associated field is missing. It is also generated where a field, eg. 245 has a $6, but there is no associated 880.
Other institution in $5 Reports where a field has a $5 code that doesn't match the MARC institution code for the contributor that supplied the record.
Missing series added entry Where a record has a 490 indicator 1 = 1, this indicates the absence of an 800, 810, 811 or 830.
Extraneous series added entry Where a record has a 490 indicator 1 = 0, this indicates the presence of an 800, 810, 811 or 830.
No physical description Reports a record that lacks a valid 007 character position 00, 245$h, 300$a and 338$a$b.
RDA invalid field Reports the presence of a 260 in an RDA record.
Incorrect filing character count The filing character checks report potential errors in the 240, 245 and 730. If the language of the document is English there is a check for non-filing characters in the indicators. An error will be reported if the non-filing character indicator is set to 0 but the title appears to start with a leading article. If the non-filing character indicator is not 0, the number of filing characters in the record is checked and an error reported if the last non-filing character is alphanumeric.
All upper case This reports a field where the content is all uppercase. Sometimes this will be correct, but it may often indicate a record likely to have other data problems. This check excludes leader, control fields, number fields and local fields.