Mini-Metadata Project: Graphic Novels Using Dublin Core
Stephanie Felice
San Jose State University
July 13, 2017
Introduction
During this project, I generate records for a selection of graphic novels and comic books using the Dublin Core schema. Due to their dual focus on textual and visual elements, graphic novels pose unique cataloging challenges. Although Dublin Core can be used to describe both text-based and visual objects, it is generally not regarded as the optimal choice for graphic novels. In an attempt to better describe graphic novels, both user-created and institution-created schemas have been developed in the past fifteen years. I will examine how Dublin Core captures and does not capture the peculiarities present in graphic novels and comic books.
The intended environment for this project is a library with a standalone graphic novel collection or a graphic novel collection in a special collections setting. The targeted user groups are graphic novel readers and graphic novel scholars. In real-world settings, this specialized user group and environment has a higher metadata need than the general public.
In this paper I will describe graphic novel metadata, explain my schema choice, provide a link to my metadata generator, include ten generated item records and discuss my experiences using DC for graphic novels.
Graphic novel metadata
Graphic novels can be described as ‘juxtaposed pictorial and other images in deliberate sequence, intended to convey information and/or produce an aesthetic response in the reader,’ or more succinctly as ‘sequential art’ (McCloud, 1993, pp. 27). These definitions reflect competing emphases on text and art, depending on the narrative’s requirements. Graphic novels pose several cataloging challenges. Comics are an interactive medium, relying on visual techniques that immerse the reader in the narrative and invite them to participate in interpreting the story. As such, ‘the material properties of the book – the codex form, the leaves and pages, the physical properties of the paper – are inseparable from the structure, pacing and design of the narrative’ (Walsh, 2014).
Comics often include paratextual components such as fan mail, editorial notes, celebrations of publication milestones, news and advertisements. These features are not always easy to reflect within traditional schemas and metadata vocabularies. Further, serial comics are published in small monthly issues and then published in volumes that include several issues in one bound book. Volumes are rebound and reissued to celebrate publication anniversaries and film adaptations. Different volumes will include further features such as forewards and alternative cover art.
Comics also frequently have a large number of contributors involved. Writers create the narrative; artists can be credited for artwork, letters, coloring, issue cover art or volume cover art.
Some artists specialize solely in cover art, which may not be included in every reprinting of an issue. While traditional schemas provide access points to an item’s creators and contibutors, they usually cannot adequately express what each person contributed to the final product.
Graphic novels and schemas
For most institutions and environments, traditional schema choices such as Dublin Core or cataloging formats such as MARC do an adequate job of describing graphic novels. The core elements present in a graphic novel are captured just as they are for a general collection item.
Many institutions will never need or want to pursue any specialized schema. However, the medium is actively collected and curated. Both private and public collections have pursued digitization projects and cataloging efforts to preserve and share their holdings. User-created schemas based on XML and Dublin Core have expanded metadata offerings that reflect contributor roles, issue variations, compilations and paratextual features
(Wright, 2014, pp. 3). Schemas like the Comic Book Schema address graphic novels on an item level using the Comic Book Ontology (CBO), a metadata vocabulary for describing comic books and collections (Petiya, 2017). Using the Comic Book Schema, comic book volumes are treated as compilations and each issue is cataloged with separate metadata elements within a single volume. Once metadata is created for an issue, it can combined with any other issue(s) for any compilation.
For fully digitized objects, Comic Book Markup Language (CBML) is a model based in
TEI describes the contents within a graphic novel. CBML allows for the addition of metadata for text and graphics and also offers the ability to address paratextual elements within the item
(Wright, 2014, pp. 4). The extensive language includes fields and controlled vocabularies for features such as transition type between panels, speech bubble styling and diegetic elements
(words that both the character and reader see, such as street signs) (Walsh, 2014).
Schema choice
For this project, I chose to create the records using Dublin Core. DC is a standard choice for text-based items. Although it is not preferred graphic novel metadata, I decided to use DC as my first exploration into graphic novel metadata. By describing my items using DC, I will be able to make observation about how adequately or inadequately it fits the medium. With that knowledge, I can make a more informed decision regarding which schema is most appropriate for graphic novels.
Dublin Core metadata generator and template
The records created for this project were generated using the Advanced Dublin Core
Generator accessed via http://www.dublincoregenerator.com/generator.html. The advanced version of the generator provides opportunities for precision not present in the simple generator.
A basic template derived from the Advanced Dublin Core Generator is included below.
In cases where more than one entry exists for one element, separate iterations of the element will be used.
Created metadata records
The following ten item records were created using the Dublin Core Advanced Generator.
Where possible, the records’ contents come from the front matter of the book itself, with Library of Congress Subject Headings taken from the Library of Congress Online Catalog. Terms are either drawn from a controlled vocabulary or used uniformly to maintain record consistency.
Both serial comic books and standalone graphic novels are included in this selection of items. To examine the differences in records for related items, I used three Batman volumes
(Records 3, 4 and 5) and two sequential volumes of Y: The Last Man (Records 7 and 8).
Record 1: Paper Girls by Brian K. Vaughan, https://lccn.loc.gov/2017218528
Record 2: Saga of the Swamp Thing Book One by Alan Moore, https://lccn.loc.gov/2012374624
Record 3: Batman: Hush by Jeph Loeb, https://lccn.loc.gov/2012372383
Record 4: Batman: The Long Halloween by Jeph Loeb, https://lccn.loc.gov/99218572
Record 5: Batman & Robin: Batman vs. Robin by Grant Morrison, https://lccn.loc.gov/2010525575
Record 6: Chew, Volume 1: Taster’s Choice by John Layman, https://lccn.loc.gov/2016590240
Record 7: Y: The Last Man – Cycles by Brian K. Vaughan, https://lccn.loc.gov/2004296756
Record 8: Y: The Last Man – One Small Step by Brian K. Vaughan, https://lccn.loc.gov/2004296756
Record 9: Che: A Graphic Biography by Sid Jacobson and Ernie Colon, https://lccn.loc.gov/2009004410
Record 10: This One Summer by Jillian and Mariko Tamaki, https://lccn.loc.gov/2012278152
Discussion
These records highlight the shortcomings Dublin Core has for describing graphic novels.
There were a number of instances in which I felt the created record did not adequately reflect the item. For most of the items, it was difficult to decide which contributors to designate as creators and which to include as contributors. Catalog records are not in uniform in assigning authorship of a graphic novel. I tended to use the item’s cover to credit creators, and all other contributors were left as such in the record. Some items have as many as five contributors, but DC has no option to identify their role.
Almost every item was composed of several issues republished in a single volume. I chose to include a description of the original issues in the ‘Description’ field. To further specify the issues, I could have used the ‘Description’ field to list the issue titles as a ‘Table of
Contents.’
The only thing linking the records for the three Batman volumes is the ‘Related’ field, which references the fictitious character. Two of the Batman volumes feature the Joker, and one features Catwoman, but there were no convenient places to note that in the record. For analysis purposes, a field denoting character appearances would be beneficial. Similarly, the only thing linking the records for Y: The Last Man, Volumes 2 and 3 is the ‘Related’ field.
I like the Dublin Core fields relating to accrual. For comics that are acquired at regular intervals, it is important to note that length of time. The ‘Accrual Periodicity’ field lists how often volumes are published, and ‘Accrual Policy’ field captures whether or not the serial is ongoing.
Conclusion Dublin Core is simple to use and simple to understand. The generator I used also provided explanations of each field and options available with the advanced version. This project showed me that schemas and metadata vocabularies dictate the information collected – and that is therefore searchable – from an item. DC sufficiently expresses the major publication details of a graphic novel but misses medium-specific characteristics.
There are several features of comics schemas that would greatly increase the description of graphic novels. Firstly, cataloging issues as separate items creates adequate metadata for issues, which can have different copyright dates, contributors and titles. The individual issues can then be combined into collections with additional forewards and components, allowing for both issue-specific metadata and volume-specific metadata. This is the case in the Comic Book
Schema. Comic books also benefit from metadata fields for characters that appear within the book, as characters exist in expansive universes. References Dublincoregenerator.com – A better Dublin Core generator. (n.d). Retrieved from
http://www.dublincoregenerator.com/generator.html.
Library of Congress Online Catalog. (n.d.). Retrieved from https://catalog.loc.gov/index.html.
McCloud, S. (1993). Understanding comics. New York: HarperPerennial.
Metadata for comic books and graphic novels. (n.d.). Retrieved from https://comicmeta.org.
Petiya, S. (2017). Comic Book Ontology. Retrieved from https://comicmeta.org/cbo/.
Walsh, J. (2012). Comic Book Markup Language: An introduction and rationale. Digital
Humanities Quarterly, 6(1). Retrieved from
http://www.digitalhumanities.org/dhq/vol/6/1/000117/000117.html.
What is CBML? (2012). Retrieved from http://dcl.slis.indiana.edu/cbml/.
Wright, V. (2014). Metadata for graphic novels and comic books: Comic Book Markup
Language and advanced comic book format. Library Philosophy and Practice, 1230, 1-
23. Retrieved from
http://digitalcommons.unl.edu/cgi/viewcontent.cgi?article=3168&context=libphilprac.