<elocation-id> Electronic Location Identifier

Bibliographic identifier for a document that does not have traditional printed page numbers.

Usage/Remarks

This element acts in the same way as a page identifier for a document that does not have traditional page numbers; the value could be an article identifier, publisher’s number, etc., for example, “E70”.
External Assigned Identifier
This element holds an externally assigned identifier, assigned to an article by a publisher, an archive, or library to help cite an article that is born digital and will never have page numbers. The contents of this element should not be confused with the @id attribute, which holds an internal document identifier that can be used by software to perform a simple link.
Related Elements
A number of elements in the Suite relate to page numbers:
  • <fpage> names the page number on which a work begins;
  • <lpage> names the page number on which a work ends (which should be the same page number or a number larger than the starting page number);
  • <elocation-id> replaces the start and end page elements just described for electronic-only publications;
  • <page-range> records discontinuous page ranges; and
  • <page-count> holds the total page count, if the publisher has provided one. Typically this element records what the publisher said and makes no validity claim. The element <page-count> should be used only in metadata. The citation elements (<element-citation> or <mixed-citation>) use the element <size> to tag the total page count of a cited work. (Historical Note: The deprecated <nlm-citation> element still uses the <page-count> element.)
Best Practice: The <page-range> is intended to record supplementary information and should not be used in the place of the <fpage> and <lpage> elements, which are typically needed for citation matching. The <page-range> element is merely a text string, containing such material as “8-11, 14-19, 40”, which would mean that the work began on page 8, ran through 11, skipped to page 14, ran through 19, and concluded on page 40.
Attributes

Base Attributes

Models and Context
May be contained in
Description
Text, numbers, or special characters
Content Model
<!ELEMENT  elocation-id (#PCDATA)                                    >
Tagged Sample

<article-meta>

...
<article-meta>
 ...
 <pub-date publication-format="print" date-type="pub" iso-8601-date="2002-08-28">
  <day>28</day>
  <month>08</month>
  <year>2002</year>
 </pub-date>
 <volume>2</volume>
 <elocation-id>E27</elocation-id>
 <history>
  <date date-type="accepted" iso-8601-date="2002-08-22">
   <day>22</day>
   <month>08</month>
   <year>2002</year>
  </date>
 </history>
 ...
</article-meta>
...