Metadata Services staff create metadata for journals besides Project Euclid titles. These non-Euclid journals are colloquially referred to as "DPubs" journals. While the folders for these DPubs journals are in the Euclid_DPubs folder on Library21, alongside the Euclid folders, there are a few differences between Euclid and DPubs journals which should be noted.
a. What is DPubs? From the DPubs website: "DPubS (Digital Publishing System) is an open-source software system designed to enable the organization, presentation, and delivery of scholarly journals, monographs, conference proceedings, and other common and evolving means of academic discourse." Project Euclid is actually a DPubs project, but due to the nature and volume of its content, it is a unique case. This document discusses the handling of other, non-Euclid DPubs projects and titles. DPubs titles include "CRE" (also called "CRER") or The Cornell Real Estate Review, MPAT or Medieval Philosophy and Theology, and INDO or Indonesia.
b. DPubs Workflow: Word that a DPubs issue is ready to be processed usually comes from the DLIT Technologies Project Manager in charge of Special Projects and Initiatives. This PM will provide Metadata Services staff with the files needed to process the issue in hand. They are in contact with the journal's publisher, and are our liaison with the publisher. If there is a problem with the quality of the files provided by the publisher, the DLIT PM would be the person to turn to for assistance.
As with Project Euclid issues, questions about XML syntax should be directed to either the Director of ePublishing Technologies or the ePublishing Technologies Project Manager.
When the .xml has been completed and the submission .zip file has been created (just as for Euclid issues), contact the DLIT Project Manager in charge of Special Projects and Initiatives and the Director of ePublishing Technologies. There is no online submission interface for DPubs titles; they must be loaded "by hand" by ePublishing Technologies staff.
When you have completed your work, record time spent in the Euclid_DPubs/TimeSheets/MiscProjects/MiscProjectTimeSheet for the appropriate fiscal quarter.
c. DPubs has its own schema. In the Euclid_DPubs/dtds folder is a dpubs subfolder containing three scheme:
Euclid_DPubs/dtds/dpubs/dpubs_journal_issue.xsd -- This is the schema to be used for serials issues published in DPubs.
Euclid_DPubs/dtds/dpubs/dpubs_monograph.xsd -- This is the schema to be used for monographs published in DPubs.
Euclid_DPubs/dtds/dpubs/dpubs_proceedings.xsd -- This is the schema to be used for conference proceedings published in DPubs.
The screenshot below shows the proper encoding for the header in the .xml for a DPubs journal issue. Note that the <journal_issue> tag is very different from that of a journal which uses a .dtd. Observe that DPubs journals have unique journal_ids. If you are unsure of the journal_id for the issue in hand, contact the Director of ePublishing Technologies or the ePublishing Technologies Project Manager. Note also that DPubs journals require "pii" identifiers, just as Euclid issues do.
d. Filetypes in DPubs Issues: As of this writing, only .tiff and .pdf files have been received from DPubs journal publishers; however, due to the individual nature of these projects, other filetypes may be received for future titles. CRER often includes one large pdf that encompasses the entire contents of the issue. This journal also often does not separate out the Foreword and the Letter from the Editors from the rest of the miscellaneous frontmatter; it may be necessary to extract those pages from the "front" .pdf using Adobe Professional, in order to create a separate .pdf and separate <record> for each of these items. If an item is listed in the Table of Contents, it ideally should have it's own .pdf and <record>.
