Merging duplicate video recording records: A field-by-field comparison

Type and BLvl

• Should match unless a record is cataloged on the wrong format.

Time

• If coded, should match; but be flexible regarding reasonable differences.

Form

• Should match but be aware of incorrect coding.

TMat

• Should match but be aware of incorrect coding.

Tech

• Should match but be aware of incorrect coding.

DtSt and Dates

• Use judgment on dates; be aware of different sources for dates and different kinds of bibliographic “events” (original production, release as motion picture, video release, etc.); usually disregard dates of design copyright and/or accompanying material.
• Also be aware of changing practices regarding the recording of uncertain, questionable, and unknown dates, as well as the different decisions that may be made in those instances.
• See also fields 260/264 subfield $c.

Lang

• A difference in this element alone does not justify a separate record. Compare fields 041, 240, 245, 377, 500, and 546. Specific differences in the language of text of the item may justify a separate record.
• See also fields 041 and 546

006 and 007

• Records may be considered duplicates for merge regardless of absence or presence of field 006 or 007.
• Compare fields 300, 34X, 500, 538, etc. to justify a merge.

007

• If present on both records subfield coding should match but be aware of incorrect coding and inconsistencies within each record.
  
  Examples:
  Subfield ‡d coded "c" does not match subfield ‡d coded "b".
  However, subfield ‡d coded "c" may possibly match subfield ‡d coded "u".
  Subfield ‡i coded "q" does not match subfield ‡i coded "s".
  However, subfield ‡i coded "q" may possibly match subfield ‡i coded "u".
   
• Compare fields 300, 34X, 500, 538, etc. to justify a merge.

020, 024, and 028

• ISBNs should match. But be aware that multiple ISBNs may apply to the same item. A different 020 alone does not justify separate records. The records could still be potential duplicates to be merged. Compare fields 245 through 5XX to justify a merge.
• The bibliographic significance of 024s and 028s for videorecordings is open to interpretation, but they may be useful in helping to justify a merge or to confirm differences that would argue against a merge.

041

• Ideally, 041s should match. But be aware that publishers are often inconsistent/incorrect in presenting language data (on package, in accompanying material, on video menu, etc.) and catalogers may be incomplete/inaccurate in coding and/or explaining language content.
• Compare fields 546, 5XX to justify a merge.
• Be somewhat flexible in considering language content.

245

• May not match exactly. Variations in the title proper may be due to differences in the source of information, judgment about what constitutes title proper, etc.
  
  Example:
  245 00  24. ‡p Season two ....
  500  Title from container.
  245 00  24. ‡p Second season....
  500  Title from disc label.

250

• If present on all records should match exactly.
• You may merge if one says "1st edition" and other says nothing.
• Compare 245 through 5XX for other differences to justify a merge. For instance, "widescreen" may be interpreted as edition statement, but may appear in 34X, 538, 5XX instead.

260 and 264

• Absence or presence of field 260 subfield $a, subfield $e, or field 264 subfield $a does not necessarily justify a new record. Specific differences in the place of production, publication, distribution, or manufacture may justify a new record.

300

• Information present must match.
• Be aware of differences between "black and white" and "color"; between "silent" and "sound".
• Compare fields 007, 34X, 500, 538, etc. to justify a merge.

33X

• Absence or presence does not necessarily justify a new record.
• The language of cataloging should match.
• A different content, media type, or carrier type may justify a new record. Compare fields 007, 245, and 5XX for other differences to justify a new record.

34X

• Absence or presence does not necessarily justify a new record.
• A difference may justify a new record. Compare fields 300 and 5XX for other differences to justify a new record.

4XX, 8XX

• Absence or presence does not necessarily justify a new record.
• Variation of series statements present may justify a new record.

501

The use of field 501 implies that there must be separate bibliographic record(s) for the resource(s) described following “With:” and that when all of those records are considered together, they describe the complete resource. If cataloged correctly, each of those records would describe only part of the complete resource, a fact that would be reflected in the 300 field.

• Records may be merged regardless of the presence or absence of fields 501 only if they represent the same complete resource, with fields 300 matching (according to the field 300 criteria) and all constituent parts of the resource being accounted for in fields 245, 505, and or 1XX/7XX
• In current cataloging, field 501 is primarily for rare, historical, and other special materials

508

• Contributors should match if present, but be aware of differences in completeness and accuracy.
• Compare 245 subfield $b, 5XX, 7XX.

511

• Performers if present should match, but be aware of differences in completeness and accuracy.
• Compare 245 subfield $b, 5XX, 7XX.

538

• All information present should match, but compare also 250, 300, 34X, other 5XX fields.
  • Video encoding format (DVD, Blu-ray Disc, etc.); also 347 subfield $b.
  • Broadcast standard (NTSC, PAL, SECAM, HDTV, etc.); also 346 subfield $b.
  • Regional encoding; also 347 subfield $e.
  • Aspect ratio (wide screen, full screen, etc.); also 500, possibly 345.
  • Sound ratio (wide screen, full screen, etc.); also 500, possibly 345.
• Be aware of differences in completeness and accuracy; tend to be flexible regarding missing data.
  
  Example:
  538  DVD video; NTSC; all region; wide screen (16:9); Dolby digital 5.1 surround sound or stereo surround sound.
  538  DVD video; NTSC; all region; full screen; Dolby digital 5.1 surround sound or stereo surround sound.
  Wide screen and Full screen do not match.

546

• Language of the main content and subtitles should match.
• Audio Enhancement/Audio Description, captioning, and “Subtitles for the Deaf and Hard of Hearing” (SDH) features should match if present.
• Be aware that publishers are often inconsistent/incorrect in presenting language data (on package, in accompanying material, on video menu, etc.) and catalogers may be incomplete/inaccurate in coding and/or explaining language content.
• Compare fields 546, 5XX to justify a merge.
• Be somewhat flexible in considering language content.

6XX

• Records may be considered duplicates for merge even with absence, presence, or differences in 6XX fields.

7XX

• Records may be considered duplicates for merge even with absence, presence, or differences in 7XX fields.