<xsd:element name="doi_batch"><xsd:annotation><xsd:documentation>Top level element for a metadata submission to Crossref. This element indicates the start and end of the XML file. The version number is fixed to the version of the schema. Be sure to set the name space attributes as shown above in order for the Xerces parser to process the instance correctly. For the purposes of parsing, you may also set xsi:schemaLocation to http://0-www.crossref.org.lib.rivier.edu/schema/4.x.x http://0-www.crossref.org.lib.rivier.edu /schema/4.x.x/crossref.xsd. A copy of the schema is located on the Crossref server at this URL and will remain constant for a given version of the schema. This location permits you to have a constant location for the schema for parsing without relying on a hardwired local directory on your development platform.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="head"/><xsd:element ref="body"/></xsd:sequence><xsd:attribute name="version" type="xsd:string" fixed="4.4.2"/></xsd:complexType></xsd:element>
<xsd:element name="head"><xsd:annotation><xsd:documentation>The container for information related to the DOI batch submission. This element uniquely identifies the batch deposit to Crossref and contains information that will be used as a reference in error messages sent by the MDDB.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="doi_batch_id"/><xsd:element ref="timestamp"/><xsd:element ref="depositor"/><xsd:element ref="registrant"/></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="doi_batch_id"><xsd:annotation><xsd:documentation>Publisher generated ID that uniquely identifies the DOI submission batch. It will be used as a reference in error messages sent by the MDDB, and can be used for submission tracking. The publisher must ensure that this number is unique for every submission to Crossref.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="100"/><xsd:minLength value="4"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="timestamp" type="xsd:nonNegativeInteger"><xsd:annotation><xsd:documentation>Indicates version of a batch file instance or DOI. timestamp is used to uniquely identify batch files and DOI values when a DOI has been updated one or more times. timestamp is an integer representation of date and time that serves as a version number for the record that is being deposited. Because Crossref uses it as a version number, the format need not follow any public standard and therefore the publisher can determine the internal format. The schema format is a double of at least 64 bits, insuring that a fully qualified date/time stamp of 19 digits can be submitted. When depositing data, Crossref will check to see if a DOI has already been deposited for the specific doi value. If the newer data carries a time stamp value that is equal to or greater than the old data based on a strict numeric comparison, the new data will replace the old data. If the new data value is less than the old data value, the new data will not replace the old data. timestamp is optional in doi_data and required in head. The value from the head instance timestamp will be used for all instances of doi_data that do not include a timestamp element.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="depositor"><xsd:annotation><xsd:documentation>Information about the organization submitting DOI metadata to Crossref</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="depositor_name"/><xsd:element ref="email_address"/></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="depositor_name"><xsd:annotation><xsd:documentation>Name of the organization registering the DOIs. The name placed in this element should match the name under which a depositing organization has registered with Crossref.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="130"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="email_address"><xsd:annotation><xsd:documentation>e-mail address to which batch success and/or error messages are sent. It is recommended that this address be unique to a position within the organization submitting data (e.g. "doi@...") rather than unique to a person. In this way, the alias for delivery of this mail can be changed as responsibility for submission of DOI data within the organization changes from one person to another.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="200"/><xsd:minLength value="6"/><xsd:pattern value="[\p{L}\p{N}!/+\-_]+(\.[\p{L}\p{N}!/+\-_]+)*@[\p{L}\p{N}!/+\-_]+(\.[\p{L}_-]+)+"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="registrant"><xsd:annotation><xsd:documentation>The organization that owns the information being registered.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="255"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="body"><xsd:annotation><xsd:documentation>The container for the main body of a DOI record submission. The body contains a set of journal, book, conference proceedings or stand alone component records. It is not possible to mix genres within a single DOI submission. It is possible to include records for multiple journals, books, conferences, or stand alone components in a single submission.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:choice><xsd:element ref="journal" maxOccurs="unbounded"/><xsd:element ref="book" maxOccurs="unbounded"/><xsd:element ref="conference" maxOccurs="unbounded"/><xsd:element ref="sa_component" maxOccurs="unbounded"/><xsd:element ref="dissertation" maxOccurs="unbounded"/><xsd:element ref="report-paper" maxOccurs="unbounded"/><xsd:element ref="standard" maxOccurs="unbounded"/><xsd:element ref="database" maxOccurs="unbounded"/><xsd:element ref="peer_review" maxOccurs="unbounded"/><xsd:element ref="pending_publication" maxOccurs="unbounded"/><xsd:element ref="posted_content" maxOccurs="unbounded"/></xsd:choice></xsd:complexType></xsd:element>
<xsd:element name="journal"><xsd:annotation><xsd:documentation>The container for all information about a single journal and the articles being registered within the journal. journal is the core container for information about a single journal and articles submitted for registration from that journal. Within a journal instance, you may register articles from a single issue, detailed in journal_issue. If you want to register items from more than one issue, you must use multiple journal instances, which can be done within a single batch submission. If you have articles that have not been assigned to an issue, you may register them within a single journal instance. In this case, do not include a journal_issue. You may chose to submit only top level journal_metadata and journal_issue metadata for any journal or issue, allowing you to register DOIs for an entire journal, or any issue or volume within a journal.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="journal_metadata"/><xsd:element ref="journal_issue" minOccurs="0"/><xsd:element ref="journal_article" minOccurs="0" maxOccurs="unbounded"/></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="full_title"><xsd:annotation><xsd:documentation>The full title by which a journal is commonly known or cited. full_title and abbrev_title must both be submitted even if they are identical. Note: In version 4.1.0 and later, this element is allowed up to 10 times to allow for a) journal name changes over time, b) translated journal names (e.g. the Japanese name and the English equivalent), and c) common author mis-spellings of a given journal name.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="255"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="abbrev_title"><xsd:annotation><xsd:documentation>This element contains the common abbreviation or abbreviations used when citing this journal. It is preferred, but not required, that periods be included after abbreviated words within the title. full_title and abbrev_title must both be submitted, and they can be identical. If you do not know the abbreviated title for a specific journal, please supply the full title in the abbrev_title element. Note: In version 4.1.0 and later, this element is no longer required in journal_metadata because some journals do not have abbreviated journal names.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="150"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="issn"><xsd:annotation><xsd:documentation>The ISSN assigned to an entity. The ISSN must consist of eight digits (where the last digit may be an X), or it must consist of eight digits in two groups of four with a hyphen between the two groups. Spaces or other delimiters should not be included in an ISSN. For more information, please see http://www.issn.org:8080/English/pub/getting- checking/checking or http://www.issn.org. The text "ISSN" should not be included in the issn element in Crossref submissions. Crossref validates all ISSNs supplied in deposits, only valid ISSNs will be accepted.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:simpleContent><xsd:extension base="issn_t"><xsd:attributeGroup ref="media_type.atts"/></xsd:extension></xsd:simpleContent></xsd:complexType></xsd:element>
<xsd:element name="coden"><xsd:annotation><xsd:documentation>The coden assigned to a journal or conference proceedings.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="6"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="archive_locations"><xsd:annotation><xsd:documentation>Container element for archive.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element maxOccurs="unbounded" minOccurs="0" ref="archive"/></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="archive"><xsd:annotation><xsd:documentation>Used to indicate the designated archiving organization(s) for an item. Values for the name attribute are CLOCKSS, LOCKSS Portico, KB, DWT (Deep Web Technologies), Internet Archive</xsd:documentation></xsd:annotation><xsd:complexType><xsd:attribute name="name" use="required"><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:enumeration value="CLOCKSS"/><xsd:enumeration value="LOCKSS"/><xsd:enumeration value="Portico"/><xsd:enumeration value="KB"/><xsd:enumeration value="Internet Archive"/><xsd:enumeration value="DWT"/></xsd:restriction></xsd:simpleType></xsd:attribute></xsd:complexType></xsd:element>
<xsd:element name="doi_data"><xsd:annotation><xsd:documentation>The container for elements related directly to a DOI. doi_data contains the doi, timestamp (version) and corresponding resource (URI) data for the doi. Cases of single-resolution (i.e. one DOI with a single corresponding URI) should be tagged with a doi/resource pair in doi_data. If additional resources are to be proved the <collection> element may also be used. The single URL provided in the <resource> is mandatory and serves as the single resolution target for the DOI. Note: A timestamp value placed inside doi_data will override any timestamp value placed in the <head> element.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="doi"/><xsd:element ref="timestamp" minOccurs="0"/><xsd:element ref="resource"/><xsd:element ref="collection" minOccurs="0" maxOccurs="unbounded"/></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="doi"><xsd:annotation><xsd:documentation>DOI for an entity being registered with Crossref. In 2008 Crossref restricted DOI suffix characters to the following: "a-z", "A-Z", "0-9" and "-._;()/" Existing DOIs with suffix characters outside of the allowed set are still supported. For additional information on DOI syntax, see https://0-support-crossref-org.lib.rivier.edu/hc/en-us/articles/214669823</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="doi_t"/></xsd:simpleType></xsd:element>
<xsd:element name="resource"><xsd:annotation><xsd:documentation>The element that contains a URI associated with a DOI. URLs are referred to as resources in the 2.0 Crossref schema because they can be any valid URI. Cases of single-resolution (i.e. one DOI with a single corresponding URI) should be tagged with a doi/resource pair in doi_data. Only one resource is allowed per doi_data, the exception being resource elements within a collection element. Values for the "content_version" attribute are vor (version of record) and am (advance manuscript).</xsd:documentation></xsd:annotation><xsd:complexType><xsd:simpleContent><xsd:extension base="resource_t"><xsd:attributeGroup ref="mime_type.atts"/><xsd:attribute name="content_version"><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:enumeration value="vor"/><xsd:enumeration value="am"/></xsd:restriction></xsd:simpleType></xsd:attribute></xsd:extension></xsd:simpleContent></xsd:complexType></xsd:element>
<xsd:element name="collection"><xsd:annotation><xsd:documentation>A collection is a container for one or more items each holding a doi or a resource (URI) which is related to the DOI in the ancestor <doi_data> element. A collection must be qualified by a property attibute or the multi-resolution attribute. property attributes: list-based: uses an interim page and presents the list of items to the user (via Multiple Resolution) country-based: proxy picks destination based on the country code of the user's location crawler-based: identifies resource to be crawled by the specified crawlers. text-mining: identifies resource to be used for text and data mining unspecified: identifies resource with unspecified usage syndication: identifies resource to be used for syndication link-header: identifies resource to be used as an endpoint The multi-resolution attribute may be used to lock or unlock DOIs for multiple resolution.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="item" minOccurs="0" maxOccurs="unbounded"/></xsd:sequence><xsd:attribute name="property" use="required"><xsd:simpleType><xsd:restriction base="xsd:NMTOKEN"><xsd:enumeration value="list-based"/><xsd:enumeration value="country-based"/><xsd:enumeration value="crawler-based"/><xsd:enumeration value="text-mining"/><xsd:enumeration value="unspecified"/><xsd:enumeration value="syndication"/><xsd:enumeration value="link-header"/></xsd:restriction></xsd:simpleType></xsd:attribute><xsd:attribute name="multi-resolution"><xsd:simpleType><xsd:restriction base="xsd:NMTOKEN"><xsd:enumeration value="lock"/><xsd:enumeration value="unlock"/></xsd:restriction></xsd:simpleType></xsd:attribute></xsd:complexType></xsd:element>
<xsd:element name="journal_issue"><xsd:annotation><xsd:documentation>The container for metadata that defines a single issue of a journal. Special issue numbering information for a journal should be placed in special_numbering. You may register a DOI for an entire issue by including doi_data in journal_issue. The URI should resolve to the table of contents for the issue. contributors is included in journal_issue to allow inclusion of editors of special issues. This element allows linking from a reference such as: R.Glaser, L.Bond (Eds.), Testing: concepts and research, American Psychologist 36 (10-12) (1981) (special issue). You should not include contributors for the regular editors of regular issues.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="contributors" minOccurs="0"/><xsd:element ref="titles" minOccurs="0" maxOccurs="1"/><xsd:element ref="publication_date" maxOccurs="10"/><xsd:element ref="journal_volume" minOccurs="0"/><xsd:element ref="issue" minOccurs="0"/><xsd:element ref="special_numbering" minOccurs="0"><xsd:annotation><xsd:documentation>Issue level numbering for supplements or special issues. Text defining the type of special issue (e.g. "suppl") should be included in this element along with the number.</xsd:documentation></xsd:annotation></xsd:element><xsd:element ref="archive_locations" minOccurs="0" maxOccurs="1"/><xsd:element ref="doi_data" minOccurs="0"/></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="contributors"><xsd:annotation><xsd:documentation>The container for all who contributed to authoring or editing an entity.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:choice maxOccurs="unbounded"><xsd:element ref="organization"/><xsd:element ref="person_name"/><xsd:element ref="anonymous"/></xsd:choice></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="organization"><xsd:annotation><xsd:documentation>The name of an organization (as opposed to a person) that contributed to authoring an entity. If multiple organizations authored an entity, each one should be captured in a unique organization element. If an entity was authored by individuals in addition to one or more organizations, person_name and organization may be freely intermixed within contributors. contributor_role should be set, as appropriate, to author or editor. When a contributor translated a work, set contributor_role to "translator". "chair" should only be used for conference proceedings to indicate a conference chair.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:simpleContent><xsd:extension base="organization_t"><xsd:attributeGroup ref="contributor.atts"/></xsd:extension></xsd:simpleContent></xsd:complexType></xsd:element>
<xsd:element name="person_name"><xsd:annotation><xsd:documentation>The name of a person (as opposed to an organization) that contributed to authoring an entity. Authors with name suffixes should have the suffix captured in suffix, not in surname. Author prefixes such as "Dr.", "Prof.", or "President" should not be included in person_name or any other element. Author degrees (e.g. M.D., Ph.D.) also should not be included in Crossref submissions. contributor_role should be set, as appropriate, to author or editor. When a contributor translated a work, set contributor_role to "translator". "chair" should only be used for conference proceedings to indicate a conference chair.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="given_name" minOccurs="0"/><xsd:element ref="surname"/><xsd:element ref="suffix" minOccurs="0"/><xsd:element ref="affiliation" minOccurs="0" maxOccurs="5"/><xsd:element ref="ORCID" minOccurs="0" maxOccurs="1"/><xsd:element ref="alt-name" minOccurs="0"/></xsd:sequence><xsd:attributeGroup ref="contributor.atts"/></xsd:complexType></xsd:element>
<xsd:element name="given_name"><xsd:annotation><xsd:documentation>A contributor's given name. The given_name, combined with surname, forms the name of an author or editor. given_name may be submitted as either initials or a full name. Do not place given_name within the surname unless it is unclear how to distinguish the given name from the surname, as may be the case in non-Western names. Do not include titles such as "Dr.", "Prof.", or "President" in given_name. These titles should not be submitted to Crossref.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="60"/><xsd:minLength value="1"/><xsd:pattern value="[^\d\?]*"/><xsd:whiteSpace value="collapse"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="surname"><xsd:annotation><xsd:documentation>The surname of an author or editor. The surname, combined with given_name, forms the name of an author or editor. Whenever possible, the given name should not be included in the surname element. In cases where the given name is not clear, as may happen with non-Western names or some societies in which surnames are not distinguished, you may place the entire name in surname, e.g.:<surname>Leonardo da Vinci</surname>If an author is an organization, you should use organization, not surname. Suffixes should be tagged with suffix. Author degrees (e.g. M.D., Ph.D.) should not be included in Crossref submissions.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="60"/><xsd:minLength value="1"/><xsd:pattern value="[^\d\?]*[^\?\s]+[^\d]*"/><xsd:whiteSpace value="collapse"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="suffix"><xsd:annotation><xsd:documentation>The suffix of an author name, e.g. junior or senior. A name suffix, that typically denotes a generation distinction, is tagged with suffix. Author degrees (e.g. M.D., Ph.D.) should not be included in Crossref submissions.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="10"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="affiliation"><xsd:annotation><xsd:documentation>The institution(s) with which a contributor is affiliated. This element may hold the name and location of an affiliation with which a contributor is affiliated. Please note the following points when using this element: 1. A contributor may have up to five affiliations. Each affiliation should be in a unique <affiliation> element. The following is correct: <affiliation>University of New Mexico</affiliation> <affiliation>Sandia National Laboratories</affiliation> The following is NOT correct <affiliation>University of New Mexico; Sandia National Laboratories</affiliation> 2. The name of the institution is required in this element. The location is optional. Both of the following are correct: <affiliation>Harvard University</affiliation> <affiliation>Harvard University, Cambridge, MA</affiliation> 3. Additional address information such as a URL or email address should NOT be deposited in this element 4. Visual linking indicators used in publication to connect authors with their affiliations such as footnote symbols or initials should NOT be included in the <affiliation> element 5. If you have only a single string that has the affiliation for multiple contributors to a work and that string is not broken out into the individual affliations for each author, please do NOT deposit the affilation information. This element is to be used only for affiliation information that is directly connected to the author with whom this information is included within the person_name element.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="512"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="ORCID"><xsd:annotation><xsd:documentation>The ORCID for an author. The schema performs basic pattern validation, checksum validation is performed upon deposit via a system check.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:simpleContent><xsd:extension base="orcid_t"><xsd:attribute default="false" name="authenticated" type="xsd:boolean"/></xsd:extension></xsd:simpleContent></xsd:complexType></xsd:element>
<xsd:element name="titles"><xsd:annotation><xsd:documentation>A container for the title and original language title elements.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:sequence><xsd:element ref="title"/><xsd:element ref="subtitle" minOccurs="0"/></xsd:sequence><xsd:sequence minOccurs="0"><xsd:element ref="original_language_title"/><xsd:element ref="subtitle" minOccurs="0"/></xsd:sequence></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="title"><xsd:annotation><xsd:documentation>The title of the entity being registered. When a title contains a subtitle, it is preferable to capture the subtitle portion in the subtitle element. Only minimal face markup is supported, see https://0-support-crossref-org.lib.rivier.edu/hc/en-us/articles/214532023</xsd:documentation></xsd:annotation><xsd:complexType mixed="true"><xsd:choice minOccurs="0" maxOccurs="unbounded"><xsd:group ref="face_markup"/></xsd:choice></xsd:complexType></xsd:element>
<xsd:element name="subtitle"><xsd:annotation><xsd:documentation>The sub-title portion of an entity title. When possible, it is better to tag a title and subtitle with separate elements. If this information is not available, it is acceptable to submit the title and subtitle all within the title element with punctuation (preferably a colon) used to separate the subtitle from the title. When a subtitle is tagged, the space and punctuation between the title and subtitle text should not be included. The following examples illustrate correct and incorrect tagging practices: Correct and optimal tagging:<title>The Human Brain</title><subtitle>A Handbook</subtitle>Correct but not optimal tagging:<title>The Human Brain: A Handbook</title>Incorrect:<title>The Human Brain:</title><subtitle>A Handbook</subtitle><title>The Human Brain</title><subtitle>: A Handbook</subtitle></xsd:documentation></xsd:annotation><xsd:complexType mixed="true"><xsd:choice minOccurs="0" maxOccurs="unbounded"><xsd:group ref="face_markup"/></xsd:choice></xsd:complexType></xsd:element>
<xsd:element name="original_language_title"><xsd:annotation><xsd:documentation>The title of an entity in its original language if the registration is for a translation of a work. When providing the original language of a title, you should set the language attribute.</xsd:documentation></xsd:annotation><xsd:complexType mixed="true"><xsd:choice minOccurs="0" maxOccurs="unbounded"><xsd:group ref="face_markup"/></xsd:choice><xsd:attributeGroup ref="language.atts"/></xsd:complexType></xsd:element>
<xsd:element name="publication_date"><xsd:annotation><xsd:documentation>The date of publication. In all cases, multiple dates are allowed to allow for different dates of publication for online and print versions. This element was previously called date, but was renamed publication_date to distinguish more clearly from conference_date.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:complexContent><xsd:extension base="date_t"/></xsd:complexContent></xsd:complexType></xsd:element>
<xsd:element name="month" type="xrefMonth"><xsd:annotation><xsd:documentation>Month of publication. The month must be expressed in numeric format rather spelling out the name (e.g.. submit "10", not "October"). The month must be expressed with a leading zero if it is less than 10 (e.g. submit "05", not "5"). When a journal issue has both an issue number and a season, the issue number should be placed in issue. If the month of publication is not known, the season should be placed in month as a two-digit value as follows: Season Value Spring 21 Summer 22 Autumn 23 Winter 24 First Quarter 31 Second Quarter 32 Third Quarter 33 Fourth Quarter 34 In cases when an issue covers multiple months, e.g. "March-April", include only the digits for the first month of the range.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="day" type="xrefDay"><xsd:annotation><xsd:documentation>Day of publication. The should must be expressed with a leading zero if it is less than 10 (e.g. submit "05", not "5").</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="journal_volume"><xsd:annotation><xsd:documentation>The container for the journal volume and DOI assigned to an entire journal volume. You may register a DOI for an entire volume by including doi_data in journal_volume.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="volume"/><xsd:element ref="publisher_item" minOccurs="0"/><xsd:element ref="archive_locations" minOccurs="0" maxOccurs="1"/><xsd:element ref="doi_data" minOccurs="0"/></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="volume"><xsd:annotation><xsd:documentation>The volume number of a published journal, or the number of a printed volume for a book or conference proceedings. A journal volume is contained in the journal_volume element to allow for the assignment of a DOI to an entire journal volume. Do not include the words "Volume" or "vol." in this element. Data may be alpha, numeric or a combination. Roman numerals are acceptable.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="32"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="publisher_item"><xsd:annotation><xsd:documentation>A container for item identification numbers set by a publisher. item_number within publisher_item may also be used to provide an article number when a first_page is not available or applicable. In certain cases it may be deemed in-appropriate to 'misuse' the first_page element to provide a value that has meaning in an on-line only publication and does not convey an form of page number. In these circumstances the attribute <item_number item_number_type="article-number"> will instruct the Crossref system to treat the value of item_number in the same manner as first_page. This value then becomes a critical part of the query process. If both <item_number item_number_type="article-number"> and first_page are present, first_page will take precedence.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="item_number" minOccurs="0" maxOccurs="3"/><xsd:element ref="identifier" minOccurs="0" maxOccurs="10"/></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="item_number"><xsd:annotation><xsd:documentation>A publisher identifier that can be used to uniquely identify the entity being registered. This identifier is a publisher-assigned number that uniquely identifies the entity being registered. This element should be used for identifiers based on publisher internal standards. Use identifier for a publisher identifier that is based on a public standard such as PII or SICI. If the item_number and identifier are identical, there is no need to submit both. In this case, the preferred element to use is identifier. Data may be alpha, numeric or a combination. item_number has an optional attribute, item_number_type. It is assigned by the publisher to provide context for the data in item_number. If item_number contains only a publisher's tracking number, this attribute need not be supplied. If the item_number contains other data, this attribute can be used to define the content. For example, if a journal is published online (i.e. it has no page numbers), and each article on the table of contents is assigned a sequential number, this article number can be placed in item_number, and the item_number_type attribute can be set to "article_number". Although Crossref has not provided a set of enumerated types for this attribute, please check with Crossref before using this attribute to determine if a standard attribute has already been defined for your specific needs. If a dissertation DAI has been assigned, it should be deposited in the identifier element with the id_type attribute set to "dai". If an institution has its own numbering system, it should be deposited in item_number, and the item_number_type should be set to "institution" If the report number of an item follows Z39.23, the number should be deposited in the identifier element with the id_type attribute set to "Z39.23". If a report number uses its own numbering system, it should be deposited in the identifier element, and the id_type should be set to "report-number" The designation for a standard should be placed inside the identifier element with the id_type attribute set to "ISO-std-ref" or "std-designation" (more generic label)</xsd:documentation></xsd:annotation><xsd:complexType><xsd:simpleContent><xsd:extension base="item_number_t"><xsd:attribute name="item_number_type" type="xsd:string" use="optional"/></xsd:extension></xsd:simpleContent></xsd:complexType></xsd:element>
<xsd:element name="identifier"><xsd:annotation><xsd:documentation>A public standard identifier that can be used to uniquely identify the entity being registered. This identifier is a publisher-assigned number that uniquely identifies the entity being registered. This element should be used for identifiers based on public standards. Use item_number for a publisher identifier that is based on a publisher's internal systems rather than on a public standard. The supported standards are: PII - Publisher Item Identifier SICI - Serial Item and Contribution Identifier DOI - Digital Object Identifier</xsd:documentation></xsd:annotation><xsd:complexType><xsd:simpleContent><xsd:extension base="identifier_t"><xsd:attribute name="id_type" use="required"><xsd:simpleType><xsd:restriction base="xsd:NMTOKEN"><xsd:enumeration value="pii"/><xsd:enumeration value="sici"/><xsd:enumeration value="doi"/><xsd:enumeration value="dai"/><xsd:enumeration value="Z39.23"/><xsd:enumeration value="ISO-std-ref"/><xsd:enumeration value="std-designation"/><xsd:enumeration value="report-number"/><xsd:enumeration value="pmid"/><xsd:enumeration value="other"/></xsd:restriction></xsd:simpleType></xsd:attribute></xsd:extension></xsd:simpleContent></xsd:complexType></xsd:element>
<xsd:element name="issue"><xsd:annotation><xsd:documentation>The issue number in which an article is published. Only one issue name should be used for the issue. The issue number takes precedence over any other name. For example, if an issue has only a seasonal name, then the season should be listed in issue. However, if an issue has a number and a season, then only the number should be listed in issue, and the season should be placed in month (see the table in month, below, for proper encoding of the season) if the specific month of publication is not known. Do not include the words "issue", "No" or "number" in this element. When submitting DOIs for journal articles published online ahead of print, you should submit the issue number, when known, even if the pagination information for the entity is not yet known. Data may be alpha, numeric or a combination. Examples: 74(3):1999<journal_issue><publication_date media_type="print"><year>1999</year></publication_date><journal_volume><volume>74</volume></journal_volume><issue>3</issue></journal_issue>Volume 74, Spring 1999<journal_issue><publication_date media_type="print"><year>1999</year></publication_date><journal_volume><volume>74</volume></journal_volume><issue>Spring</issue></journal_issue>Volume 74, issue 3 Spring 1999<journal_issue><publication_date media_type="print"><month>21</month><year>1999</year></publication_date><journal_volume><volume>74</volume></journal_volume><issue>3</issue></journal_issue></xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="32"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="special_numbering"><xsd:annotation><xsd:documentation>Issue level numbering for supplements or special issues. Text defining the type of special issue (e.g. "suppl") should be included in this element along with the number.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="15"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="journal_article"><xsd:annotation><xsd:documentation>The container for all information about a single journal article. A journal article is required to have title and doi_data. All other information is optional. When registering items that do not have titles, use the appropriate heading from the journal section or table of contents (e.g. "Errata") in title. journal_article allows for multiple titles per entity. In some cases it may be helpful to submit multiple titles. For example, if an erratum carries title of the original article a nd the heading "Errata", both should be submitted by using two titles elements.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="titles" maxOccurs="20"/><xsd:element ref="contributors" minOccurs="0"/><xsd:element ref="jats:abstract" minOccurs="0" maxOccurs="unbounded"/><xsd:element ref="publication_date" maxOccurs="10"/><xsd:element ref="acceptance_date" minOccurs="0" maxOccurs="1"/><xsd:element ref="pages" minOccurs="0"/><xsd:element ref="publisher_item" minOccurs="0"/><xsd:choice><xsd:element ref="crossmark" minOccurs="0"/><xsd:sequence><xsd:element ref="fr:program" minOccurs="0" maxOccurs="1"/><xsd:element ref="ai:program" minOccurs="0" maxOccurs="1"/><xsd:element ref="ct:program" minOccurs="0" maxOccurs="1"/></xsd:sequence></xsd:choice><xsd:element ref="rel:program" minOccurs="0"/><xsd:element ref="archive_locations" minOccurs="0" maxOccurs="1"/><xsd:element ref="scn_policies" minOccurs="0" maxOccurs="1"/><!-- cs-3495 --><xsd:element ref="doi_data"/><xsd:element ref="citation_list" minOccurs="0"/><xsd:element ref="component_list" minOccurs="0"/></xsd:sequence><xsd:attributeGroup ref="publication_type.atts"/><xsd:attributeGroup ref="language.atts"/><xsd:attributeGroup ref="reference_distribution_opts.att"/></xsd:complexType></xsd:element>
<xsd:element name="acceptance_date"><xsd:annotation><xsd:documentation>The date a manuscript was accepted for publication.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:complexContent><xsd:extension base="date_t"/></xsd:complexContent></xsd:complexType></xsd:element>
<xsd:element name="pages"><xsd:annotation><xsd:documentation>The container for information about page ranges. When an entity has non-contiguous page information, you should capture the first page range in first_page and last_page. Any additional page information should be captured in other_pages. Punctuation is only allowed in other_pages. It should not appear in first_page and last_page. Page number letter prefixes or suffixes should be included. Roman numeral pages are permitted in both upper case and lower case. Data may be alpha, numeric or a combination.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="first_page"/><xsd:element ref="last_page" minOccurs="0"/><xsd:element ref="other_pages" minOccurs="0"/></xsd:sequence></xsd:complexType></xsd:element>
