Union Catalog

Recommendations pertinent to outcomes of the ZL(u)C 2009

Union catalog

The union catalog is a conceptual, shared, national database of zines and other independently published materials that is used to collect all pertinent cataloging data for all materials, functions as an authority file, and communicates with local catalogs through downloadable files or another standardized file format that can be adapted to many different cataloging software systems.

Clint from SLCPL and Lily from Portland's IPRC are designated organizers of the union catalog workgroup. The workgroup is charged with exploring the requirements of the union catalog and providing recommendations for moving forward with the project.

1.      Software

Five different software packages were presented at the conference and the pros and cons of each discussed:

Biblios.net
Drupal (or other cms)
Zinewiki.com
Atheaneum (or other closed-source)
Librarything.com

The software package chosen for the union catalog must be able to accommodate or perform various functions. It must be compatible with the highest number of formats and other software programs. It must lend itself easily to upgrades, adjustments, and web standard developments.

1.1.   File types

The file type(s) selected as the standard for catalog entries must accommodate the largest variation of cataloging software possible. The success of the union catalog rests in a large way on the ease of communicating with the variety of local, digital cataloging programs. It may be wise to offer content in a diversity of formats. Possibilities include: .cvs, MARC, .xls.

1.2.   Sharing

All content of the union catalog must be protected by some open-source copyright method to insure that all who collect zines and similar materials have equal access to the knowledge database. The growth of independent publishing materials depends on transparency of content and equal access. It may be prudent to pursue alternates to standard copyright. Options include: Copyleft, GNU-style protection, Open-source licensing

1.3.   Data

Data collected on the union catalog should be comprehensive but efficient. An ideal union catalog would contain more information per entry than any local catalog uses, since we have established that every catalog in the country organizes materials in different ways. However, with an eye toward increased usability, all data entered must be able to be represented in ways that make sense to the user and also ways that make sense to the software.

1.3.1.      User-visible

Heading 2.1 contains a list of possible fields for catalog entries that should be considered.

1.3.2.      Meta

Each field in the union catalog’s software should have meta-data attached to it to make customizing views easier for catalogers. Meta-data includes:

1.3.2.1.Field labels and field relationships (including non-content based tagging)

1.3.2.2.Weights for content prioritization

1.3.2.3.Hyperlinks

1.3.2.4.Time stamps

1.3.2.5.Cataloger signature

1.3.2.6.Revision history

1.4.   Server location

The primary server for the union catalog should be housed in a neutral location. Consideration should be taken for:

1.4.1.      Ownership of server space

1.4.2.      Reliability of server

1.4.3.      Availability of tech support

1.4.4.      Mobility and catalog migration possibilities

1.5.   Backup

Best practice would be to mirror the catalog in a diversity of remote locations.

2.      Cataloging standards

2.1.   Cataloging fields
2.1.1.      Title
2.1.2.      Author
2.1.3.      Editor*
2.1.4.      Publisher*
2.1.5.      Subject*
2.1.6.      Tags
    2.1.6.1.Controlled
    2.1.6.2.Free
2.1.7.      Description
2.1.8.      Issue no.
2.1.9.      Publication date*
2.1.10. Received date
2.1.11. Physical contact info
2.1.12. Electronic presence/contact
2.1.13. Cover scan
2.1.14. Cataloger signature
2.1.15. Physical description
    2.1.15.1.        Size
    2.1.15.2.        Material
    2.1.15.3.        Pages
    2.1.15.4.        Additional items (ephemera)

* indicates a new field for SLCPL’s catalog.

2.2.   Subjects, categories, and tags

2.2.1.      LCSHs
2.2.2.      Zine-specific vocabularies
2.2.3.      Controlled tags
2.2.4.      Free tags