<production-dates> (
Production Dates)
Description
Description
This empty element contains the dates on which the article reached various states of its original publishing production process, such as the date on which it was received, and the date it was published in print. Each of these dates takes the form of an attribute value. The format must follow the convention of optional two digit day number, optional three letter month (any letter-case) and required four digit year, as in "Apr1888" and "05Mar1992" (5th March 1992) except in the case of the printpubdate which should contain the cover date written out:
<production-dates printpubdate="01Apr2003"
qaapprovdate="20Mar2003"
receiveddate="Oct1998"
reviseddate="Mar2001"
webpubdate="20Mar2003"/>
The month codes are "Jan", "Feb", "Mar", "Apr", "May", "Jun", "Jul", "Aug", "Sep", "Oct", "Nov", "Dec".
Parent Elements
The elements listed below may directly contain this element.
They are "parent" elements. Elements in referenced groups are included, up to two levels of group nesting.
Model Diagram
The DTD model for this element:
(no content allowed)
DTD Definition
The DTD contains the following element and attribute definitions
(note that embedded links are to definitions within the DTD page of this guide):
<!ELEMENT production-dates EMPTY>
<!ATTLIST production-dates
projectedprintpubdate CDATA #IMPLIED
printpubdate CDATA #IMPLIED
webpubdate CDATA #IMPLIED
receiveddate CDATA #IMPLIED
acceptdate CDATA #IMPLIED
reviseddate CDATA #IMPLIED
qaapprovdate CDATA #IMPLIED
finalapprovdate CDATA #IMPLIED
%a-group-CommonIDAttrs;>
.
Defined in DTD section
Metadata : Article Metadata : Miscellaneous Metadata
General Attributes (shared with other elements)
Local Attributes (defined for this element alone)
Description
This attribute holds the expected date for print publication of inpress articles.
Specification
This attribute is not required. It has text content.
DTD Definition
projectedprintpubdate CDATA #IMPLIED
.
Description
This date must be representative of the issue
coverdate (which may differ from actual publication date) but using the format for dates as given above.
It may be used for determining access to the journal articles and therefore must be accurate.
The value of printpubdate must be consistent across all articles in an issue. Please see
"Publication Dates in Online Files".
| |
- | printpubdate should at minimum contain a year based on the issue's cover date.
A month and day should be included if possible. |
| |
- | Seasons in an issue cover date can be mapped to corresponding months.
The following mapping is preferred: Spring = Mar, Summer = Jun, Autumn = Sep, Fall = Sep, Winter = Dec. |
| |
- | If the cover date does not include a day, 01 should be used as the day. |
| |
- | printpubdate cannot be a range of dates. If the cover date gives a range, the earliest date in the range should be used. |
For journals with iFirst workflow, always insert one, consistent printpubdate for the entire issue, reflecting the date of print publication of the issue. Dates for previous publication of iFirst articles may be retained in the webpubdate attribute.
Specification
This attribute is not required. It has text content.
DTD Definition
printpubdate CDATA #IMPLIED
.
Description
This attribute holds the date on which the article was published online.
For articles that publish online before being assigned to an issue, webpubdate should be populated with an projected date of online posting.
Typesetters preparing online files should insert the next calendar day from the date the files will be supplied.
It is important that this date be correct because it may be used for access control if
printpubdate is not specified.
Please see
"Publication Dates in Online Files".
Specification
This attribute is not required. It has text content.
DTD Definition
webpubdate CDATA #IMPLIED
.
Description
This attribute holds the date on which the article was received by Taylor & Francis. This should be the earliest date in the element.
Specification
This attribute is not required. It has text content.
DTD Definition
receiveddate CDATA #IMPLIED
.
Description
This attribute holds the date on which the article was accepted for publication (which must follow the received date, and precede publication dates).
Specification
This attribute is not required. It has text content.
DTD Definition
acceptdate CDATA #IMPLIED
.
Description
This attribute holds the date on which the article was revised, and will be absent if the article was not revised.
Specification
This attribute is not required. It has text content.
DTD Definition
reviseddate CDATA #IMPLIED
.
Description
This attribute holds the date on which the article passed quality assurance.
Specification
This attribute is not required. It has text content.
DTD Definition
qaapprovdate CDATA #IMPLIED
.
Description
This attribute holds the date on which the article was given final approval for publication.
Specification
This attribute is not required. It has text content.
DTD Definition
finalapprovdate CDATA #IMPLIED
.