Bound Volumes - pulibrary/BlueMountain GitHub Wiki

Blue Mountain Bound Volumes

1 Dealing with Bound Volumes in Blue Mountain

1.1 Introduction

After several months of processing magazines with the docWorks configuration CCS devised for us, we have discovered that configuration is not sufficient for all the Blue Mountain materials. We need to extend the configuration, or create a new one, to handle magazine issues that exist in bound form.

Up until now, Blue Mountain’s policy was to treat the issue as the atomic entity, or primary object. More specifically, the metadata for Blue Mountain centered on the issue: our MODS documents (descriptive metadata records) were issue-level, and the METS/ALTO documents we contracted with DDD to produce described and constituted digital realizations of issues. We were aware that for a number of our titles, the physical items held by the PUL were parts of bound volumes, but we assumed we could disbind those volumes, either physically or virtually, and retain the issue-centered nature of our archive without harm.

That assumption was wrong, for several reasons. The relationships among the physical objects, the digital photographs of them, and the resources created by Blue Mountain are not entirely clear, but we have always been uneasy about creating a derivational/generational gap between the physical items that were photographed and the virtual objects Blue Mountain produced. This gap, and how a project chooses to treat it, distinguishes among digital reproductions and digital editions.

We also believed we could safely reconstruct issues as issued without distortion: that is, we assumed that binding was a secondary format imposed on singly-issued items. This assumption has proven false: while it is true that some issues were acquired separately by the library (or the private collector) and then bound (for convenience, for preservation, etc.), it is also true that publishers often printed (or reprinted) issues already bound together, not infrequently with additional material that had not been published serially (indexes, for example, or prefaces). These latter sort of bound volumes are first-class bibliographic entities, not simple, decomposable collections.

We have concluded, therefore, that Blue Mountain’s policy of virtual disbinding was an error. None of the materials already digitized by Blue Mountain have been virtually disbound, so there is little harm done. But there are practical ramifications to designing and creating new kinds of virtual objects for the Blue Mountain collection:

  • A new docWorks configuration (and perhaps two) must be designed and implemented, with the help of CCS;
  • DDD must be trained to use it;
  • Veridian must be configured to handle it.

1.2 Blue Mountain Objects

Free Issues
the status quo: digitizations of free-standing issues, usually with covers.
Bound Volumes
a set of issues bound together, usually reformatted (covers and advertisements left out), and often containing supplementary material (indexes, prefaces, additional front- and back-matter).
Bound Issues
The issues collected in a bound volume. They differ from Free Issues, because they may be missing covers and advertisements that were published in the free edition.

1.2.1 Bound Volumes

1.2.1.1 <dmdSec>s

1.2.1.1.1 <dmdSec> for the Volume

The Volume-level METS encapsulates the MODS record for the volume itself:

<dmdSec ID="theVolume">
  <mdWrap MDTYPE="MODS">
    <xmlData>
      <mods xmlns="http://www.loc.gov/mods/v3" ID="v">
        <recordInfo>
          <recordIdentifier>urn:PUL:bluemountain:dmd:bmtnabc_1873_01</recordIdentifier>
        </recordInfo>
        <identifier type="bmtn">urn:PUL:bluemountain:bmtnabc_1873_01</identifier>
        <genre>Periodicals-Volume</genre>
        <titleInfo>
          <nonSort>La</nonSort>
          <title>Chronique Musicale</title>
        </titleInfo>

        <relatedItem type="series" ID="v.series" xlink:href="urn:PUL:bluemountain:bmtnabc">
          <recordInfo>
            <recordIdentifier>urn:PUL:bluemountain:dmd:bmtnabc</recordIdentifier>
          </recordInfo>
          <part type="volume">
            <detail type="volume">
              <number>1</number>
            </detail>
          </part>
        </relatedItem>
      </mods>
    </xmlData>
  </mdWrap>
</dmdSec>
1.2.1.1.2 A <dmdSec> for each bound issue

For each issue in the bound volume, the METS contains a pointer to the MODS record corresponding to the issue.

<dmdSec ID="issue1">
  <mdRef LOCTYPE="URN" MDTYPE="MODS" xlink:href="urn:PUL:bluemountain:dmd:bmtnabc_1873-07-01_01"/>
</dmdSec>
<dmdSec ID="issue2">
  <mdRef LOCTYPE="URN" MDTYPE="MODS" xlink:href="urn:PUL:bluemountain:dmd:bmtnabc_1873-07-15_01"/>
</dmdSec>
<dmdSec ID="issue3">
  <mdRef LOCTYPE="URN" MDTYPE="MODS" xlink:href="urn:PUL:bluemountain:dmd:bmtnabc_1873-08-01_01"/>
</dmdSec>
<dmdSec ID="issue4">
  <mdRef LOCTYPE="URN" MDTYPE="MODS" xlink:href="urn:PUL:bluemountain:dmd:bmtnabc_1873-08-15_01"/>
</dmdSec>
<dmdSec ID="issue5">
  <mdRef LOCTYPE="URN" MDTYPE="MODS" xlink:href="urn:PUL:bluemountain:dmd:bmtnabc_1873-09-01_01"/>
</dmdSec>
<dmdSec ID="issue6">
  <mdRef LOCTYPE="URN" MDTYPE="MODS" xlink:href="urn:PUL:bluemountain:dmd:bmtnabc_1873-09-15_01"/>
</dmdSec>

1.2.1.2 FileSec

The <fileSec> contains pointers to all the files comprising the digital object: all the image files and official derivations; the ALTO files; PDFs.

1.2.1.3 Physical StructMap

Represents the physical makeup of the bound volume:

<structMap TYPE="Physical">
  <div TYPE="BoundVolume">
    <div TYPE="Binding"/>
    <div TYPE="FrontMatter"/>
    <div TYPE="BodyMatter"/>
    <div TYPE="BackMatter"/>
    <div TYPE="Binding"/>
  </div>
</structMap>
1.2.1.3.1 <div TYPE=”Binding” />

Represents the binding of the volume

<div TYPE="Binding">
  <div TYPE="OuterUpper"/>
  <div TYPE="InnerUpper"/>
  <div TYPE="EndPaper" />
  <div TYPE="Blank" />
</div>

<!-- the contents of the volume go here -->

<div TYPE="Binding">
  <div TYPE="Blank" />
  <div TYPE="EndPaper" />
  <div TYPE="InnerLower"/>
  <div TYPE="OuterLower"/>
</div>

This degree of div-type specificity may be overkill; it may be enough to designate “Cover” and “Page”:

<div TYPE="Binding">
  <div TYPE="Cover"/>
  <div TYPE="Cover"/>
  <div TYPE="Page" />
  <div TYPE="Page" />
</div>
1.2.1.3.2 <div TYPE=”FrontMatter” />

Contains a set of pages comprising the front matter of the volume not part of any issue – title pages, dedications, etc.

1.2.1.3.3 <div TYPE=”BodyMatter” />

Contains the main contents of the volume, usually magazine issues.

<div TYPE="BodyMatter" LABEL="Body Matter" ORDER="3">
  <!-- First issue -->
  <div TYPE="BoundIssue" DMDID="v.issue1" LABEL="Issue 1" ORDER="1">
    <div TYPE="Page" LABEL="Page" ORDER="1">
      <fptr FILEID="img11"/>
    </div>
    <div TYPE="Page" LABEL="Page" ORDER="2">
      <fptr FILEID="img12"/>
    </div>
    <div TYPE="Page" LABEL="Page" ORDER="3">
      <fptr FILEID="img13"/>
    </div>
    <!-- remaining pages of the issue -->
  </div>
  <!-- Second issue -->
  <div TYPE="BoundIssue" DMDID="v.issue1" LABEL="Issue 1" ORDER="2">
    <div TYPE="Page" LABEL="Page" ORDER="1">
      <fptr FILEID="img11"/>
    </div>
    <div TYPE="Page" LABEL="Page" ORDER="2">
      <fptr FILEID="img12"/>
    </div>
    <div TYPE="Page" LABEL="Page" ORDER="3">
      <fptr FILEID="img13"/>
    </div>
    <!-- remaining pages of the issue -->
  </div>
  <!-- remaining issues -->
</div>
1.2.1.3.4 <div TYPE=”BackMatter” />

Contains a set of pages comprising the back matter of the volume not part of any issue – indexes, etc.

1.2.1.4 Logical StructMap

In order to keep the size of the volume METS manageable, a mets:mptr/ element is used to point to an external METS document representing each issue, rather than representing the issues explicitly in line.

<structMap TYPE="Logical">
  <div TYPE="BoundVolume">
    <div TYPE="FrontMatter"/>
    <div TYPE="BodyMatter">
      <div TYPE="BoundIssue" LABEL="Volume 1, Number 1" DMDID="v.issue1" ORDER="1">
        <mptr LOCTYPE="URN" xlink:href="urn:PUL:bluemountain:td:bmtnabc_1873-07-01_01"/>
      </div>
      <div TYPE="BoundIssue" LABEL="Volume 1, Number 2" DMDID="v.issue1" ORDER="2">
        <mptr LOCTYPE="URN" xlink:href="urn:PUL:bluemountain:td:bmtnabc_1873-07-15_01"/>
      </div>
    </div>
    <div TYPE="BackMatter"/>
  </div>
</structMap>

1.2.2 Bound Issues

The typical content of a Bound Volume.

1.2.2.1 DmdSec

A MODS record describing the issue. It includes a <relatedItem type=”series”/> to indicate the magazine, and a <relatedItem type=”host”/> to indicate the physical volume containing it.

<dmdSec ID="dmd1">
  <mdWrap MDTYPE="MODS">
    <xmlData>
      <mods xmlns="http://www.loc.gov/mods/v3" ID="issue">
        <recordInfo>
          <recordIdentifier>urn:PUL:bluemountain:dmd:bmtnabc_1873-07-01_01</recordIdentifier>
        </recordInfo>
        <identifier type="bmtn">urn:PUL:bluemountain:bmtnabc_1873-07-01_01</identifier>
        <titleInfo>
          <nonSort>La</nonSort>
          <title>Chronique Musicale</title>
        </titleInfo>

        <relatedItem type="series" ID="i.series" xlink:href="urn:PUL:bluemountain:bmtnabc">
          <recordInfo>
            <recordIdentifier>urn:PUL:bluemountain:dmd:bmtnabc</recordIdentifier>
          </recordInfo>
          <part type="issue">
            <detail type="volume">
              <number>1</number>
            </detail>
            <detail type="issue">
              <number>1</number>
            </detail>
          </part>
        </relatedItem>

        <relatedItem type="host" xlink:href="urn:PUL:bluemountain:bmtnabc_1873_01">
          <recordInfo>
            <recordIdentifier>urn:PUL:bluemountain:dmd:bmtnabc_1873_01</recordIdentifier>
          </recordInfo>
          <part type="issue">
            <detail type="issue">
              <number>1</number>
            </detail>
          </part>
        </relatedItem>

        <relatedItem type="constituent" ID="c1">
          <titleInfo>
            <title>Préface</title>
          </titleInfo>
          <name>
            <displayForm>Arthur Heulhard</displayForm>
            <role>
              <roleTerm type="code">cre</roleTerm>
            </role>
          </name>
        </relatedItem>

        <!-- Remaining item-level constituents go here. -->

      </mods>
    </xmlData>
  </mdWrap>
</dmdSec>

1.2.3 Free Issues

These are the issues Blue Mountain has already been digitizing: physically free-standing, with covers and advertising.

Add a custom footer
⚠️ **GitHub.com Fallback** ⚠️