Skip to main content

I. A. 7. Project Euclid Monographs

There have been a few instances where Euclid has published a monographic series. These works carry the title of the series in which they are being published, plus their own unique title. They may be a work which was written by a single author and contain chapters; they may be a collection of articles written by multiple authors on a central topic; they may be conference proceedings; or they may be a festschrift, a collection of articles written to honor a respected colleague. We may receive both backfile "batch jobs" or "current issues" to process for monographs.  The following is meant to be used mainly as a guide to identifying the different types of monographs you may encounter.  Each publication will have unique factors involved in the creation of its metadata, and will have to be considered on an individual basis to determine how any particular element will be handled.  You will be working very closely with the Director of EPT and the EPT Project Euclid Production Manager while creating this metadata.

Data Profile
XML Syntax
     Conference Proceedings
     Single Author
     Single Author with Editor
     Multiple Authors
Edition Numbers

 


 

I. Data Profile: Monographs in Project Euclid may contain many different types of front- and backmatter, depending on the type of monograph.  Some examples include:

  • The title page
  • The "tp verso," which contains publication information such as the ISBN of the work.
  • Table of Contents
  • Contributor's List
  • Preface or Introduction
  • A picture - commonly used in festschriften but sometimes found in conference proceedings.
  • A List of Publications or Bibliography - used in festschriften to list the works published by the honoree.
  • Conference Schedule - used in conference proceedings.
  • A List of Participants - used in conference proceedings.
  • Appendices
  • Indices
  • A Biographical Sketch - used in festschriften.
  • Comments
  • Notes, Thanks, Acknowledgments

Front- and backmatter .pdfs may need to be separated or aggregated, depending upon the condition of the files given us by the publisher.  A publisher may provide us with some basic .xml files for each item.  We may also receive .tif or .tex files as well.  These works may or may not contain abstracts.

 


II. XML Syntax: For Project Euclid monographs there are two different schemas which may be used: one is for conference proceedings, the other is for all other forms of monographs.  They may be found in the Euclid_DPUBS\dtds\euclid folder, and are named "dpubs_proceedings-e.xsd" and "dpubs_monograph-e.xsd," respectively.  Note that these filenames contain "dpubs" but are being used for Euclid publications.

There are many elements in these schemas which are unique to processing monographs, mostly found within the <monograph_data> element.

A. Example of Conference Proceedings Data:

Conference proceedings are collections of the papers presented at a conference, and therefore contain works by more than one author.  The header in the xml might look something like this:
  
undefined
 
Note that there is an editor listed along with the monograph title ("Proceedings on the..."), the series title ("Notre Dame Mathematical Lectures"), and the series number.

The monograph_data content for this particular issue is as follows:

  
undefined
  
Notice that there is a title, subtitle, and citation title for this work.  Note also that the monograph_processingLevel="parts".  This indicates that the issue contains individual works, each of which can stand on their own, as opposed to being chapters in a book which rely upon each other for their context.  Unlike regular periodicals, monographic series contain a publication_stmt instance AND a subjects instance for the entire issue.  Note also that there is an element called "extent" which shows the total number of pages in the issue, rather than a start_page and end_page, as in regular periodicals.
 
B. Example of Data for a Monograph by a Single Author:
This example is for a monograph which is written by a single author - basically, a book - which is being published as part of the monographic series. 
 
Below is the header for this issue:
 
undefined
 
Note that the monograph_desc includes the author's name and the issue number as well as the issue title and the series title.

Below is the monograph_data for the same issue:

 
undefined
 
Notice that monograph_processingLevel="whole" since the entire issue is written by one author.  Notice also in this example the use of an "affiliation" element for the author, a place to indicate the author's formal title and organization/institution.
 

C. Example of Monograph by a Single Author, with Editor

Here is an example of a monograph by a single author which is being edited by another person.  Below is the header for the issue:

undefined

Notice that the header includes the author name AND the editor, as well as the issue number, the issue title and the series title.

Below is the monograph_data for the same issue:

undefined

Note that both the author and the editor have "affiliation" elements, and both also have name_prefix instances containing the prefix "Dr."  This issue is also marked as the 1st edition, which would suggest that we should be watching out for subsequent editions.

D. Example of a Monograph with Multiple Authors

Here is an example of a monograph containing works by multiple authors, but the issue is not a conference proceedings publication.  Notice in the header data below that there is no issue title for this particular issue, and no author:

undefined

 

undefined

 

undefined


III. A Word About Edition Numbers: Edition numbers are not necessarily as straightforward as one might think in a monographic series.  If you look at the file list below, you'll notice that there are folders for two series 2's, one published in 1942 (NDML00029142) and one published in 1971 (NDML00021971).  Similarly, there are two series 6's and two series 10's.  What has happened here is that new editions of these series were published at a later date.  The publication year, therefore, becomes very important.

undefined

These works are also given edition numbers to help distinguish them. Please note, however, that the first edition is not given an edition number.  Below is a segment from the .xml for series 2, 1942:

undefined

and the same section of the .xml for series 2, 1971 (below) shows that this work is a second edition.

undefined

One surprising thing to note in this example is that the second edition was copyrighted in 1944, but was not published until 1971, according to notations found in the .pdfs for the second edition.  You will find such seemingly anomalous dates while processing monographic series.  It is usually preferable to make the copyright date match the date of publication, in most cases.  When you find such a discrepancy, check with the EPT Project Euclid Production Manager as to how these dates should be handled.