Cataloging Games IST 616, Fall 2008 Katharine Posner Bradley Shipps
Not much to go on… <ul><li>Since this is a developing field, there is not much literature on cataloging board games in libraries. However, we were able to find existing catalog records for board games, so we decided to do some modified copy cataloging. </li></ul>
Elon University Catalog Entry for Ticket to Ride: Europe
The College of St. Scholastic’s Record for Ticket to Ride: Europe
Based on the examples we found and AACR2 Ch. 10, we cataloged this similar title:
Getting Started <ul><li>What constitutes one game? </li></ul><ul><ul><li>What is the difference between an edition and a version? </li></ul></ul><ul><li>Our conclusion </li></ul><ul><ul><li>Nordic Countries indicates a different version of the original Ticket to Ride game. We chose to catalog this as a separate title rather than an edition because the board and cards are different than the original. </li></ul></ul>
Title and Statement of Responsibility (MARC 245) <ul><li>Ticket to ride [game]: Nordic countries / Alan R. Moon </li></ul>Often games do not list an individual creator – should the statement of responsibility then include the publisher? Our conclusion: According to AACR2 Chapter 10, the chief source of information is the container, so if an individual creator is not listed on the box, the publisher should be listed under the statement of responsibility. However, if the name of an individual creator is known through some other source, a cataloger might choose to include that information in brackets.
Other Considerations <ul><li>Although not relevant for this title, cataloging games raises other issues around what constitutes a title, for example: </li></ul><ul><ul><li>How is an extension set cataloged? Is it part of the main entry or can it be cataloged as a parent–child relationship or as a related resource? </li></ul></ul>
Publication Information (MARC 260) <ul><li>Los Altos, California: Days of Wonder, c2008 </li></ul>Game titles often change hands among the corporate entities that publish them. Because the chief source of information is the container, if a company sells the rights or gets bought out, the cataloger should still use the information on the box. Additional information could be placed in brackets or in a notes field as needed.
Description/Physical Details (MARC 300) <ul><li>1 game (1 board map of the Nordic countries, 120 colored train cars, 110 train car cards, 46 destination tickets, 1 globetrotter bonus card, 3 wooden scoring markers, 1 Days of Wonder online access number): cardboard, wood, plastic, col. ; in container 30 x 30 x 8 cm + 1 rule book (4p; ill.; 29 cm) </li></ul>This serves as an inventory so that circulation is certain that all pieces have been returned.
General Note (MARC 500) <ul><li>For 2-3 players. </li></ul><ul><li>Playing time 30-60 minutes. </li></ul>
Credits (MARC 508) <ul><li>Game Design by Alan R. Moon / ill. by Julien Delval </li></ul>This information is frequently not provided for games and might be left blank.
Audience (MARC 521) <ul><li>Ages 8 and above. </li></ul>
Summary (MARC 520) <ul><li>Players collect cards of various types of train cars that enable them to claim railway routes and pass through tunnels and onto ferries, as they connect cities throughout the Nordic Countries. </li></ul>The cataloger must choose a description that will be most helpful for patrons from the extensive text on back of box. If the box lacks a summary, the information might be found inside the box or created by the cataloger.
Genre (MARC 655) <ul><li>Games </li></ul>One record we found included “Board games” as a second genre. Another example place “Board games” under subject headings, MARC 650. We liked this better. A key consideration in cataloging any game should be including the type of game, such as card game, board game, video game, etc. In reviewing records for video games, we found that the platform or console, such as “Xbox” was sometimes included under Edition.
Subject Headings (MARC 650) <ul><li>Board games </li></ul>Neither example we found included any other subject headings, but given the time for more detailed cataloging, we might choose to include headings related to the content of the game, such as geography or trains. This would become more important to facilitate searches if a library’s game collection was large.
Added Entries <ul><li>(MARC 700) Moon, Alan </li></ul><ul><li>(MARC 710) Days of Wonder, Inc. </li></ul>
Related Resources (MARC 856) <ul><li>[http://static.ticket2ridegame.com/lang/english/images/tn_rules_en.pdf] </li></ul>This is a link to the rules for the game. The 856 field is reserved for electronic location and access. Neither catalog had this web address in brackets; however we feel that since it was not from the “container” it should be bracketed.
Some thoughts on Games and FRBR: <ul><li>More and more games are created in series, and a single title might include items in several genres. A board game might have a related card game, book, television show, video game, or movie. As more games are cataloged in libraries, a FRBR approach might serve patrons best. </li></ul>
Bibliography <ul><li>Gorman, N., & Winkler, P. W. (Eds.). (1978). Anglo-American cataloging rules (2nd ed.). Chicago: American Library Association. </li></ul><ul><ul><li>The guidelines for cataloging games are found in Chapter 10 Three-Dimensional Artefacts and Realia . </li></ul></ul><ul><li>Carol Grotnes Belk Library. (n.d.). Carol Grotnes Belk Library . Retrieved November 8, 2008, from Elon University: http://www. elon . edu/e-web/library/find/findhome .xhtml </li></ul><ul><li>The College of St. Scholastica. (2008). CSS Library . Retrieved November 8, 2008, from The College of St. Scholastica Library: http: //mnpals . css . edu/F ?RN=612293312& func=file &file_name=basic </li></ul><ul><ul><li>These two catalogs apply different labels to their fields and display them in different orders, but examination of their MARC records revealed nearly identical cataloging practices for games. We suspect they both represent copy cataloging of a record from the same source. </li></ul></ul>