Marcish Schema

The following is current as of May 13, 2009. Check the code for changes.

All fields are repeatable unless otherwise specified.


A text string.

Attribution (not repeatable)

A single text string, think of MARC’s 245$c statement of responsibility


Subfields: Name, Role


Subfields: seven discrete textual terms/phrases, each with an associated type

Subject Date

A numerical date or date range

Subject Geography

A geographical point or area

Call Numbers

Subfields: type, number, location


Subfields: Type, Language, Content, Notes

Pre-defined types include: description, transcription, translation, contents, review, notes, first words, last words, dedication, notable quotations, sample

Publication Information

Subfields: publisher, edition, language, date (and date certainty), copyright status, copyright note

Physical Details

Subfields: width, height, depth (and unites of measure), weight (and unit), duration (minutes or pages), cost (and currency)

Linked URLs

This is the equivalent of MARC’s 856 field (and thus nearly useless). My intention is to accept URLs in any field and properly link the data from there.


Information about the format of the object identified by the record.

Standard Numbers

Where you’d input ISBN, ISSN, and other standard numbers

Archival Source Details

Information about the provenance of the object.

Predefined relationships include: parent, child, next in series/page, previous, and reverse side. This field could also easily store FRBR relationships. The expected input is a URL to a local or remote record

Of the above fields, these are indexed:

  • creator
  • language
  • year of creation
  • month of creation
  • format
  • subject
  • genre
  • person
  • place
  • time
  • exhibit
  • subject year
  • subject month
  • subject day
  • collection
  • sourceid
  • isbn
  • issn
  • lccn
  • asin
  • ean
  • olid
  • oclc

One Response to “Marcish Schema”