About | Governance | Join SHARE  Leap

Editing Checklist – Video Games

Home > Content > Editing Checklist – Video Games

Printable PDF verson (non-accessible) 

Resources

This is not an exhaustive checklist. Here are some places you can get further information.

Instructions

In Polaris Client: Place your cursor in the tag and the tag information will appear at the bottom of the record. Note: Tag information won’t display when record is maximized.

In Leap: Click the check box next to a tag and click the Edit tag button.

In Connexion: In the variable fields, right click anywhere in a field, and click on MARC Field Help. In the fixed field elements, click on the element name.

Note: Examples in this document show only some of the possibilities. See OCLC Bibliographic Formats and Standards or the MARC21 for Bibliographic Records website for more examples.

Edits to OCLC Records

Examples reflect spacing and display of subfields in OCLC record. Subfield a at the beginning of a field does not display in OCLC. Other subfields at the beginning of a field will display.
SHARE local practice requires the use of ISBD punctuation in all records imported to Polaris. Examples in this document will include full ISBD punctuation. OCLC records may or may not include ISBD punctuation.

040:

  • Add subfield ‡b with eng if not present
  • Add ‡e with rda when upgrading record to RDA
  • ‡e comes before ‡c

Example: 040 _ _ IHI ǂb eng ǂe rda ǂc IHI

007:

  • Add field if not present, or review to make sure codes are correct
  • Recommend using OCLC macro or creating a text string to add or edit

Examples: 007 _ _ c ǂb b ǂd c ǂe z ǂf a  (a Nintendo cartridge game)

        007 _ _ c ǂb o ǂd c ǂe g ǂf a  (a PlayStation or Xbox disc game)

024:

  • Enter the 12-digit UPC code from the container
    • 1st indicator: 1
    • 2nd indicator: blank, 0, or 1
  • If present, ensure qualifying information in ‡q is in parentheses

Example: 024 1_ 688321201827

028:

  • Enter publisher’s number in subfield a
    • 1st indicator: 5
    • 2nd indicator: 1
  • If present, ensure qualifying information in ‡c is in parentheses
  • Will often have multiple entries, both for the container and for the disc/cartridge itself

Example: 028 51 PPSA-08329 ǂb Sony Interactive Entertainment LLC ǂq (disc)  -or-

028 51 1000031635 ǂb Sony Interactive Entertainment LLC ǂq (container)

041:

Language code(s) of language tracks and accompanying material

  • 1st indicator: 1 if game has multiple language tracks
  • Multiple codes in one subfield should be split into separate subfields
  • If only one language present, omit this field
  • Check bib standards for full list of subfields and what they are used for
  • Note: Current video games are typically issued as single language resources, with the option to switch languages being a function of the game system

1XX:

  • Authorized form of creator name, as established in an authority record; may not be the same as on the item
  • Video game records rarely have a 1XX field, as it is uncommon for them to be the work of a single creator

245: Title

  • Indicator 1
    • If 1XX field is present: 1 (Note: this is rare for video games)
    • If no 1XX field is present: 0
    • Example: 245 00 Elden Ring
  • Indicator 2
    • 0-9
    • Tells the system to ignore non-filing characters and initial articles in searches, including initial articles in non-English languages. Includes the space between the article or character and the next word.
    • 0 if there are no characters to be skipped
    • Examples:
      • 245 04 The last of us
      • 245 00 No man’s sky
      • 245 02 A boy and his blob
  • Transcribe title and statement of responsibility from the title screen or title frames (preferred source, if applicable), or from the disc or cartridge label, container, accompanying material or other internal source (i.e., startup menu)
  • If no title is available, cataloger devises title
  • Include a 588 note with the source of the title
    • Example:
      245 00 No man’s sky

588 0_ Title from container.

  • Do not transcribe introductory words that are clearly not intended to

be part of the title. If considered important, this information may be

given as a variant title or note.

Example:
245 00 Ratatouille.

  1.  _ _ ǂi Title appears on cartridge label as: ǂa Disney Pixar Ratatouille
  • If working with a franchise title, include the names of both the franchise and the individual work in the title proper, as well as a number if it is explicitly present in the title. Add a colon after the the name of the franchise if not already present. DO NOT use subfields ǂb, ǂp, and/or ǂn for this purpose.
    • Example: 245 00 Call of duty 4: modern warfare.

NOT

  1.  Call of duty: ǂb Modern warfare

NOT

245 00 Call of duty n4, p Modern warfare

  • ‡h – not used in RDA; do not use in OCLC records; delete if present
    • See below for SHARE local practice
  • ‡c – Statement of Responsibility are almost never appropriate for video game records, and should only be included when there is a very clear statement of responsibility on the piece

246: Variant title

  • Add variant titles as applicable
  • Do not record initial articles
  • Do not add ending punctuation that is not part of the title
  • See OCLC bib formats for possible 1st and 2nd indicators

Example:
245 00 Destiny 2
246 30 Destiny two

250: Edition statement

  • Record edition statement as it appears on the item
  • Spell out abbreviated words as needed to match wording on the item
  • Add an edition statement for the game system or computer type. This should be added to any existing edition statement(s), separated by a comma

Example:
250 _ _ Collector’s edition.
250 _ _ Nintendo Switch, Collector’s edition.
250 _ _ [PC compatible].

257:

  • Names of country or countries where principal office(s) of producer(s) are located. If term is from a controlled vocabulary, ǂ2 contains a code for the source of the term
  • Optional to add; do not delete if present

Example: 257 _ _ Italy ǂ2 naf

264: Publication information

  • May have multiple 264s with indicators for different functions (production, publication, distribution, manufacture, copyright)
    • 1st indicator: blank
    • 2nd indicator: 0-4
  • 264 for a Copyright Notice Date (2nd indicator 4) does not have ending punctuation
  • Change MARC tag 260 to 264

Example: 264 _1 Redmond, WA : ǂb Nintendo of America, ǂc [2023]
                     264 _4 ǂc ©2023

264 ‡a: Place of publication

  • Transcribe place of publication as it appears on the item
  • If a place name is entered in brackets, do not abbreviate. Spell out if abbreviated in the record
    • Example: 264 _1 [Chicago, Illinois] 
      Not: 264 _1 [Chicago, Ill.]
  • If a record has “[S.l.]” or “[Place of publication not identified]”, enter a place if possible, even if only a country. Enter in brackets
    • Note: Be sure to code the Ctry fixed field accordingly

264 ‡b: Publisher

  • Transcribe name of publisher as it appears on the item, including Inc., Ltd, etc.
  • If publisher’s name is shortened or truncated in the record, edit to match the item
  • If a record has “[s.n]”, try to determine a publisher and enter in brackets. If a publisher can’t be determined, enter “[publisher not identified]”

Example: 264 _1 San Mateo, CA : ǂb Sony Interactive Entertainment, Inc., ǂc [2022]

264 ‡c: Date

  • Record publication date if present (rare for video games)
  • If there is no publication date but there is a copyright date for the video game, enter copyright date in brackets as implied publication date
  • If an implied publication date is entered with dashes, or if the record has “[date of publication not identified]”, change to an estimated date or range of dates, in brackets
    • Note: Be sure to code the DtSt and Date One and Date Two fixed field elements accordingly
       
  • Record copyright date in separate 264 with 2nd indicator 4
    • Record based on copyright symbol or the word copyright as stated on item

Example: 264 _1 Redmond, WA : ǂb Nintendo of America, ǂc [2023]
                     264 _4 ǂc ©2023

300: Physical description

  • Make sure physical description is complete and punctuation is correct
  • Spell out abbreviations
    • Exceptions: Abbreviate inch(es) as “in.” and centimeters as “cm”
  • Standard measurement of a game disc is 4 3/4 in.; Nintendo Switch cartridge is 1 1/4 in.
  • Use the phrase “computer disc” for disc games and the phrase “computer chip cartridge” for cartridge games. If the disc is Blu-ray, note that in the 34X/538 fields instead of the 300 field

Examples:

300 _ _ 1 computer disc : ǂb sound, color ; ǂc 4 3/4 in. + ǂe 1 booklet (9 pages : illustrations ; 18 cm)

300 _ _ 1 computer chip cartridge : ǂb sound, color ; ǂc 1 1/4 in.

33X:

  • 336, 337, and 338 describe content, media, and carrier type
  • Recommend using OCLC constant data tool to add if needed; otherwise, verify information is correct

For video game discs:

336 _ _ two-dimensional moving image ǂb tdi ǂ2 rdacontent
336 _ _ computer program ǂb cop ǂ2 rdacontent
337 _ _ computer ǂb c ǂ2 rdamedia
338 _ _ computer disc ǂb cd ǂ2 rdacarrier

For video game cartridges:

336 _ _ two-dimensional moving image ǂb tdi ǂ2 rdacontent
336 _ _ computer program ǂb cop ǂ2 rdacontent
337 _ _ computer ǂb c ǂ2 rdamedia
338 _ _ computer chip cartridge ǂb cb ǂ2 rdacarrier

34X:

  • Add fields as needed
  • Record each term in a separate 34X field
  • If multiple terms are present in one field, split into separate fields
    • Example: Before: 344 _ _ digital ǂb optical ǂg surround ǂ2 rda

After:

344 _ _ digital 2 rdatr

344 _ _ b optical 2 rdarm

344 _ _ g surround 2 rdacpc

  • Check the applicable RDA registry list for terms
    • Link to each registry list may be found in the OCLC Bib Formats entry for the field and subfield
    • If a term does not come from a controlled vocabulary, omit ‡2
  • Add ‡3 at the beginning of the field if the term applies to a specific component of the resource

340: Physical medium

  • Optional to include if dimensions are recorded in 300 ‡c; retain if present
  • ‡d not required if item is a commercially produced disc. If present, will have the term stamping. Don’t need to add; retain if present
  • Include ‡g with color content. Include in addition to 300 ‡b
    • Possible values are “monochrome” and “polychrome.” See the RDA Color Content index for more information
  • ‡i should contain the name of the appropriate video game system

Example:

340 _ _ ǂb 4 3/4 in.
340 _ _ ǂg polychrome ǂ2 rdacc
340 _ _ ǂi Sony PlayStation 4.

344: Sound characteristics

  • Include in addition to 300 ‡b
  • Always include ǂa and ǂb: include other subfields as applicable
  • Always include ǂi with the term sound or silent as applicable

Example:

344 _ _ digital ǂ2 rdatr
344 _ _ ǂb optical ǂ2 rdarm
344 _ _ ǂg stereo ǂ2 rdacpc
344 _ _ ǂi sound ǂ2 rdasco

346: Video format and broadcast standard

  • Do not include ǂa. It is used for analog recordings only. Video game discs and cartridges are digital
  • Record ǂb for broadcast standard. Most common is HDTV
    • Example: 346 _ _ ǂb HDTV ǂ2 rdabs
  • DO NOT use “laser optical”; that is a term specifically referring to the Laser Disc format
  • Note: Different broadcast standards must go on different records.

347: Digital file characteristics

  • Do not record file type (subfield ǂa) or encoding format (subfield ǂb) for video games
  • If regional encoding (“Region J”, “USA”) is given on the game or the container, record it in subfield ǂe

Examples:

347 _ _ ǂe USA
347 _ _ ǂe Region J ǂ2 rdare

380: Form of work

  • Should be the same for all video games
    • 380 _ _ Video games ǂ2 lcgft

490: Series statement

  • Should not be used for franchise titles (i.e.  “The legend of Zelda”). Series statements are uncommon for video game records

5XX: Notes

  • Include notes as appropriate. Video game records often have many notes. See the OLAC guide for notes that should be included. Examples are only some of the possibilities
  • Record number of players, noting local and/or online requirements as pertinent
    • Example: 500 _ _ Single player ; 2-3 players, local multiplayer ; 2-4 players, online multiplayer.
       
  • Record note about internet access requirements
    • Example: 500 _ _ This game may require internet access for updates. Some

online services / downloads may require additional hardware, software, memberships and/or fees.

  • Record ESRB rating and content information, using the wording found on the source, in a 521 note
    • Example: 521 8 _ ESRB rating: E 10+, Everyone 10+ (fantasy violence, mild suggestive themes).
  • Record information on game audio language and container language in a 546 note
    • Example: 546 _ _ Game audio in English, French and Spanish. Container in English and Spanish.
  • Check OCLC bib formats for indicators, subfields, and ending punctuation as applicable

538: System requirements

  • These might be quite extensive, depending on what is listed on the game container
  • Examples:
    • 538 _ _ System requirements: Nintendo Switch game system; Nintendo Switch Pro Controller compatible.
    • 538 _ _ System requirements: Xbox One or Xbox Series X consoles with optical drive; Requires download(s) (significant storage, broadband internet connection and ISP fees apply); Xbox Game Pass Ultimate or Xbox Live Gold required for online multiplayer/co-op.

588: Source of title note

  • Include for all non-book records
  • First indicator 0
    • Example: 245 00 No man’s sky

588 0_ Title from container.

6XX: Subject and genre headings

  • Review to make sure they are appropriate for the record
  • Add subject and genre headings as needed; especially double-check for genre headings and headings for fictitious characters
    • Note: Fictitious characters may be established in either a name authority record or a subject authority record. Verify in the authority file and code accordingly.
    • Example: 600 10 Kenobi, Obi-Wan ǂc (Fictitious character) ǂv Video games.
  • For all video games and computer games, use subdivision ǂv Video games after topical headings
    • Example: 650 _0 Dragons ǂv Video games.
  • For all video games and computer games, add the LCGFT genre Video games.
    • 655 _7 Video games. ǂ2 lcgft

7XX: Added entries – names and/or related works

  • May be a personal name (700), family name (700), corporate body name (710), or conference/meeting name (711)
  • Enter name(s) as established in an authority record; may not be the same as on the item
    • Examples:
    • 700_ Stewart, Patrick, ǂd 1940- ǂe voice actor.
    • 700 1 _ ǂi Based on (work): ǂa Tolkien, J.R.R. ǂq (John Ronald Reuel), ǂd 1892-1973. ǂt The Hobbit.
  • Verify form of name and 1st indicator
  • If no authority record, format name as instructed in RDA Toolkit
  • 2nd indicator: 2 when resource includes the work referenced in the 7XX
  • Remove initial articles from titles in ǂt
  • Relationship designator may be present either in ǂe (relator term) or ǂ4 (relator code). Relator term is preferred over relator code. See local practice below
    • Example: 710 2 _ Nintendo of America Inc., ǂe software developerǂ4publisher.
  • Do not include ǂe or ǂ4 when ǂt is present
  • Do not include initial articles in titles in ǂt
  • Add ǂi with relationship information in 7XX author/title entries and entries for related works

753: System details

  • Record the platform of the machine used to play the game. See the Game & Metadata Citation Project Computer Game Platform vocabulary for platform names and operating systems.
  • Examples:
    • 753 _ _ Nintendo Switch ǂ2 gcipplatform
    • 753 _ _ Microsoft Windows 11 ǂ2 gcipplatform

Fixed Fields:

  • Converts to 008 or LDR when imported to Polaris
  • Type: m (computer file)
  • ELvl: If upgrading a less-than-full-level record, or if code ‘l’ is present, change to blank
  • Audn: enter appropriate code
  • Lang: Make sure code agrees with the language of the piece, or the first language code in the 041 field, if present
  • Form: ‘q’ (direct electronic)
  • Ctry: Make sure code agrees with the place of publication in 264 ‡a
  • Desc: Will have code ‘i’ for RDA when ISBD punctuation is included or code c for RDA when ISBD punctuation is omitted. If upgrading a record, include ISBD punctuation and enter code ‘i’.
  • File: ‘g’ (game)
  • Dtst: ‘s’ if there is a single date in 264 ǂc; ‘t’ if a publication date and copyright date are present in the 264 ǂc, even if they are the same
  • Date One: Should agree with date in 264 _1 ǂc
  • Date Two: Should agree with copyright date in 264 _4 ǂc or with date of original production given in a note

SHARE Local Edits

Local edits may be done in OCLC prior to exporting or in MarcReport or Polaris after exporting.

Do not permanently save local edits to the OCLC record.

Examples reflect display and spacing of subfields in Polaris.

SHARE cataloging local practices may be found on the SHARE Website: Bibliographic & Cataloging Standards | SHARE

Format Icons:

  • Check or edit coding in the LDR, 006, and/or 007 to generate appropriate icon

ELvL Fixed field:

  • Code as blank

ISBD punctuation:

  • Include applicable ISBD punctuation between subfields and at the end of fields
  • Enter code ‘i’ in the descriptive cataloging form element in the Leader field

245:

  • If OCLC record is imported with title in all caps, edit formatting to distinguish from on-order records; capitalize first word of each title and any proper names; all other words are lower case
  • Add a General Material Designation (GMD) of [electronic resource] to all records for video games and computer games
    • ǂh comes after ǂa, ǂn, and ǂp. Comes before ǂb and ǂc
    • Example: 245 04 ǂaThe Legend of Zelda: tears of the kingdomǂh[electronic resource].

250:

  • Add an edition statement to all record for Playaway Launchpads
    • 250 _ _ [Playaway Launchpad].

264 ‡c:

  • If copyright date is used as implied publication date, add 264 _4 ‡c with copyright date
    • 264 _1 ǂaRedmond, WA :ǂNintendo of America,ǂc[2023]
    • 264 _4 c©2023

6XX:

7XX (or 1XX if present):

  • Change ‡4 to ‡e and replace relator code with applicable relator term
    • 710 2 _ ǂaNintendo of America Inc., 4swd ǂ4pbl

Change to:

710 2_ ǂaNintendo of America Inc., ǂe software developer, ǂepublisher.