Special Elements in Records

Library Technical Services > Procedures & Documentation > Metadata Services > Euclid Issue Metadata > Special Elements in Records

III. C. 3. Special Kinds of Elements in Records

Records with No Page Numbers
Records with Roman Numeral Page Numbers
Non-Alphabetical Author Order
Use of the "div" Tag

a. Records with No Page Numbers: It is not uncommon for front- and backmatter items to be unnumbered; indeed sometimes they are not included in the Table of Contents at all! If you remove the <start_page> and <end_page> tags completely, the .xml file may not validate. The solution, then, is to include the tags with a "self-closing" slash. (See below.)

Example:

Rather than this,

undefined

THIS is the proper form.

undefined

b. Records with Roman Numeral Page Numbers: Sometimes frontmatter is given pagination, but in the form of Roman numerals. You should treat those Roman numerals just as you would Arabic numerals. (See below.)

Example:

Just as you would do this for Arabic numerals,

undefined

you would do the following for Roman numerals:

undefined

c. Non-alphabetical Author Order: Sometimes the Table of Contents will list the authors' names in non-alphabetical order, to give "first authorship" to the rightful holder of the honor. To ensure that these names appear in this non-alpha order on the Euclid site, you must assign them an order number. (See below.) You must do this for authors of "related _items" and "reviewed_items" as well.

Example:

d. Use of the <div> Tag: There are times when a Table of Contents has been divided to show different sections of the issue, or different types of content within the issue. These sections are usually indicated by a label or header within the Table of Contents. One would first learn of its existence when looking at the .pdf for the Table of Contents. In the example below, taken from the DPubs webpage for the journal Indonesia, there is a section of "Reviews." (See below.)

Example:

Note: This is example is from a DPubs publication, but the same principle holds for Project Euclid metadata as well.

Note that the titles after the word "Reviews" are indented. Our job is to reflect this hierarchy somehow in the DPubs display. The way to do this is to use the <div> tag as a wrapper around all the records that follow the "Reviews" header and are indented. An issue may have more than one labeled section, or there may be some works after the section that are not indented and should be interpreted as not being part of the labeled section.

The <div> tag for the example above was encoded thus:

Here is what the DPubs display for this section looks like:

Notice that DPubs doesn't indent the review articles under the "Reviews" label, but it does insert the bold section header clearly.