diff --git a/articlemeta/export_crossref.py b/articlemeta/export_crossref.py
index a1d9d3a..ef417fb 100644
--- a/articlemeta/export_crossref.py
+++ b/articlemeta/export_crossref.py
@@ -25,9 +25,9 @@ def transform(self, data):
}
el = ET.Element('doi_batch', nsmap=nsmap)
- el.set('version', '4.4.0')
- el.set('xmlns', 'http://www.crossref.org/schema/4.4.0')
- el.set('{http://www.w3.org/2001/XMLSchema-instance}schemaLocation', 'http://www.crossref.org/schema/4.4.0 http://www.crossref.org/schemas/crossref4.4.0.xsd')
+ el.set('version', '5.3.1')
+ el.set('xmlns', 'http://www.crossref.org/schema/5.3.1')
+ el.set('{http://www.w3.org/2001/XMLSchema-instance}schemaLocation', 'http://www.crossref.org/schema/5.3.1 http://crossref.org/schemas/crossref5.3.1.xsd')
return data, el
diff --git a/tests/xsd/scielo_crossref/common5.3.1.xsd b/tests/xsd/scielo_crossref/common5.3.1.xsd
new file mode 100644
index 0000000..be7fc42
--- /dev/null
+++ b/tests/xsd/scielo_crossref/common5.3.1.xsd
@@ -0,0 +1,1606 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The following are basic data types for face markup. Face markup that appears in the title, subtitle, and original_language_title elements should be retained when depositing metadata. Face markup in other elements (e.g. small caps in author names) must be dropped. Face markup support includes bold (b), italic (i), underline (u), over-line (ovl), superscript (sup), subscript (sub), small caps (scp), and typewriter text (tt). See https://support.crossref.org/hc/en-us/articles/214532023
+
+MathML may also be included using the 'mml' namespace prefix.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ content is "Inline" except that anchors shouldn't be nested
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Publisher generated ID that uniquely identifies the DOI submission batch.
+
+
+
+
+
+
+
+
+
+
+ An integer representation of date and time that serves as a version number for the record that is being deposited, used to uniquely identify batch files and DOI values when a DOI has been updated one or more times.
+
+
+
+
+ Information about the organization submitting DOI metadata to Crossref
+
+
+
+
+
+
+
+
+
+
+ Name of the organization registering the DOIs.
+
+
+
+
+
+
+
+
+
+
+ e-mail address to which batch success and/or error messages are sent.
+
+
+
+
+
+
+
+
+
+
+ The organization responsible for the information being registered.
+
+
+
+
+
+
+
+
+
+
+
+ The chapter, section, part, etc. number for a content item in a book. Unlike volume and edition_number, component_number should include any additional text that helps identify the type of component.
+
+
+
+
+
+
+
+
+
+
+ The edition number of a book. edition_number should include only a number and not additional text such as "edition". For example, you should submit "3", not "third edition" or "3rd edition". Roman numerals are acceptable.
+
+
+
+
+
+
+
+
+
+
+
+ The issue number or name in which an article is published. 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.
+
+
+
+
+
+
+
+
+
+
+
+ The container for elements related directly to a DOI.
+
+
+
+
+
+
+
+
+
+
+
+
+ The URI associated with a DOI.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Container for item elements containing non-primary URIs associated with the item being registered. Collections are supported for the following (defined in the property attribute):
+
+ - list-based: Multiple Resolution, more info: https://www.crossref.org/education/content-registration/creating-and-managing-dois/multiple-resolution/
+ - country-based: more info: https://www.crossref.org/education/content-registration/creating-and-managing-dois/multiple-resolution/#00130
+ - crawler-based: for Similarity Check URLs, more info: https://www.crossref.org/education/similarity-check/participate/urls-for-new-deposits/
+ - text-mining: supply specific URLs for text and data mining, more info: https://www.crossref.org/education/retrieve-metadata/rest-api/text-and-data-mining-for-members/
+ - unspecified: can be used for additional URLs
+ - syndication: identifies resources to be used for syndication
+ - link-header: identifies resources to be used as an endpoint
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ A container used to associate a URI with the DOI being registered.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ NOTE: not currently supported.
+ Use to flag references for distribution. "none" is the default and follows current protocol - references are only distributed to everyone if the prefix level permission is set, otherwise reference distribution is limited to the DOI owner. Setting the value to "query" releases references to anyone making a query request (this overrides any established prefix level permission). Value "any" allows bulk distribution to anyone (using a Crossref query account) using the OAI-PMH protocol, and also releases references to anyone making a query request.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ DOI for an entity being registered with Crossref.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The ISBN assigned to an entity.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The ISSN assigned to the title being registered.
+
+
+
+
+
+
+
+
+
+
+
+
+ The volume number of a published journal, or the number of a printed volume for a book or conference proceedings.
+
+
+
+
+
+
+
+
+
+
+
+ A list of articles, books, and other content cited by the item being registered
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ citation is used to deposit each reference in the reference list of the item for which the DOI is being deposited. For details see:
+ https://www.crossref.org/education/metadata-stewardship/maintaining-your-metadata/add-references/
+
+
+
+
+
+
+
+
+
+
+
+
+ Used to assign a unique ID to each reference that is deposited. We use this key value to track the specific reference query and will return this value along with the DOI in your query results.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ A citation to an item that is not structured with the Crossref citation model. 'unstructured_citation' supports deposit of references for which no structural information is available.
+
+
+
+
+
+
+
+
+
+ Journal title in a citation.
+
+
+
+
+ Book series title in a citation.
+
+
+
+
+ Book volume title in a citation.
+
+
+
+
+ First author in a citation.
+
+
+
+
+ Year of publication in citation.
+
+
+
+
+ Article title in a citation.
+
+
+
+
+ article identifier or e-location id of the item
+
+
+
+
+
+
+ Container element for CrossMark data.
+
+
+
+
+
+
+
+
+ Some publishers encourage broad third party hosting of the publisher's content. Other publishers do not. And still others vary their policy depending on whether a particular article has been published under an OA policy or not. This boolean flag allows the publisher to indicate whether the Crossmarked content will only legitimately be updated on the Crossmark domain (true) or whether the publisher encourages updating the content on other sites as well (false).
+
+
+
+
+
+
+
+
+
+
+
+ A DOI which points to a publisher's CrossMark policy document. Publishers might have different policies for different publications.
+
+
+
+
+
+ Container element for crossmark_domain. A list of domains where the publisher maintains updates and corrections to their content. Minimally, one of these should include the Internet domain name of the publisher's web site(s), but the publisher might also decide to include 3rd party aggregators (e.g. Ebsco, IngentaConnect) or archives with which the publisher has agreements to update the content
+
+
+
+
+
+
+
+
+
+ This should be a simple Internet domain name or subdomain name (e.g. www.psychoceramics.org or psychoceramics.org). It is used to identify when a referring URL is coming from a Crossmark domain. A "crossmark_domain" is made up of two subelements; a "domain" and a "filter". The filter is only needed for use in situations where content from multiple publishers/publications is on the same host with the same domain name (e.g. an aggregator) and one needs to use the referrer's URI "path" to further determine whether the content in a crossmark domain.
+
+
+
+
+
+
+
+
+
+
+ A domain name or subdomain name (e.g. www.psychoceramics.org or psychoceramics.org). It is used to identify when a referring URL is coming from a Crossmark domain.
+
+
+
+
+ The filter element is used to disambiguate content in situations where multiple publishers share the same host (e.g. when on an aggregated platform). It should contain a substring of the path that can be used to uniquely identify a publisher's or publication's content. For instance, using the string "alpsp" here would help the CrossMark system distinguish between ALPSP publications on the ingentaconnect host and other publications on the same host.
+
+
+
+
+
+ A document might provide updates (e.g. corrections, clarifications, retractions) to several other documents. When this is the case, the DOIs of the documents that are being *updated* should be listed here.
+
+
+
+
+
+
+
+
+
+ The DOI of the content being updated (e.g. corrected, retracted, etc.) In the CrossMark Terms and Conditions "updates" are defined as changes that are likely to "change the reader’s interpretation or crediting of the work." That is, *editorially significant* changes. "Updates" should not include minor changes to spelling, punctuation, formatting, etc.
+
+
+
+
+
+
+ This attribute should be used to list the update type. Allowed update types are:
+ - addendum
+ - clarification
+ - correction
+ - corrigendum
+ - erratum
+ - expression_of_concern
+ - new_edition
+ - new_version
+ - partial_retraction
+ - removal
+ - retraction
+ - withdrawal
+
+
+
+
+
+
+ The date of the update will be displayed in the CrossMark dialog and can help the researcher easily tell whether they are likley to have seen the update.
+
+
+
+
+
+
+
+
+ Publishers are encouraged to provided any non-bibliographical metadata that they feel might help the researcher evaluate and make better use of the content that the Crossmark record refers to. For example, publishers might want to provide funding information, clinical trial numbers, information about the peer-review process or a summary of the publication history of the document.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ An assertion is a piece of custom, non-bibliographic metadata that the publisher is asserting about the content to which the Crossmark refers.
+
+
+
+
+
+
+
+ If the publisher wants to provide a further explanation of what the particular "assertion" means, they can link to such an explanation by providing an appropriate url on the "explanation" attribute.
+
+
+
+
+ This is the human-readable form of the "group_name" attribute. This is what will be displayed in the group headings on the Crossmark metadata record dialog.
+
+
+
+
+ Some assertions could be logically "grouped" together in the CrossMark dialog. For instance, if the publisher is recording several pieces of metadata related to funding sources (source name, percentage, grant number), they may want to make sure that these three assertions are grouped next to each-other in the CrossMark dialog. The group_name attribute is the machine-readable value that will be used for grouping such assertions.
+
+
+
+
+ This is the human-readable version of the name attribute which will be displayed in the CrossMark dialog. If this attribute is missing, then the value of the assertion will *not* be displayed in the dialog. Publishers may want to "hide" assertions this way in cases where the assertion value is too large or too complex to display in the dialog, but where the assertion is nonetheless valuable enough to include in API queries and metadata dumps (e.g. detailed licensing terms)
+
+
+
+
+ This is the machine-readable name of the assertion. Use the "label" attribute to provide a human-readable version of the name.
+
+
+
+
+ The publisher may want to control the order in which assertions are displayed to the user in the CrossMark dialog. All assertions will be sorted by this element if it is present.
+
+
+
+
+
+
+
+
+ A wrapper for designators or other primary identifiers for a standard.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Designator or other primary identifier for the standard being deposited.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Provides for defining a DOI for a broad grouping of standards.
+
+
+
+
+
+
+ Provides for defining a DOI for a set of standards (sometimes know as truncated form).
+
+
+
+
+
+
+
+
+
+
+
+
+ Provides for defining a DOI for a group of closely related standard documents (undated form is a stem for any dated form)
+
+
+
+
+
+
+
+
+
+
+
+
+ Designator for standard being replaced by the standard being deposited.
+
+
+
+
+ Designator for standard from which the current deposit is adopted.
+
+
+
+
+
+ Designator for the previous revision of the standard being deposited. (note: use alt_as_published for revisions within designators having common stem)
+
+
+
+
+
+ A wrapper for standards body information.
+
+
+
+
+
+
+
+
+
+
+ Name of the standards organization / publisher.
+
+
+
+
+ Acronym for standards body.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ A wrapper for Scholarly Sharing Network (SCN) policy information
+
+
+
+
+
+
+
+
+
+
+
+ A group of related SCN policies
+
+
+
+
+
+
+
+
+
+
+
+ An individual SCN policy
+
+
+
+
+
+
+
+
+
+
+ Media / mime types for component format. For mime types refer to http://www.iana.org/assignments/media-types/
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Language attributes are based on ISO 639
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ First page number of an item.
+
+
+
+
+
+
+
+
+
+
+ Last page number of an item.
+
+
+
+
+
+
+
+
+
+
+ When an item has non-contiguous page information, capture the first page range in first_page and last_page. Any additional page information should be captured in other_pages.
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/tests/xsd/scielo_crossref/crossref5.3.1.xsd b/tests/xsd/scielo_crossref/crossref5.3.1.xsd
new file mode 100644
index 0000000..f16a7ec
--- /dev/null
+++ b/tests/xsd/scielo_crossref/crossref5.3.1.xsd
@@ -0,0 +1,2065 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Top level element for a metadata record submission. This element indicates the start and end of the XML file. The version number is fixed to the version of the schema.
+
+
+
+
+
+
+
+
+
+
+
+ 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 triggered during submission processing.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Container for the main body of a DOI record submission. While it is possible to include records for multiple journals, books, conferences, or other types of content in a single submission, it is not possible to mix content types within a single DOI submission.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Container for all information about a single journal and the volumes, issues, and articles being registered within the 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 within your XML file.
+
+
+
+
+
+
+
+
+
+
+
+ Container for metadata that defines a journal.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The full title by which a journal is commonly known or cited.
+
+
+
+
+
+
+
+
+
+
+
+ Common abbreviation or abbreviations used when citing a journal. It is recommended that periods be included after abbreviated words within the title.
+
+
+
+
+
+
+
+
+
+
+
+ Container for metadata that defines a single issue of a journal.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ 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.
+
+
+
+
+
+
+
+
+
+
+
+
+ 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.
+
+
+
+
+
+
+
+
+
+
+ Container for all information about a single journal article.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Container for all information about a single conference and its proceedings. If a conference proceedings spans multiple volumes, each volume must be contained in a unique conference element.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ A container for all information that applies to a conference event. event_metadata captures information about a conference event. Data about conference proceedings is captured in proceedings_metadata.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The official name of the conference, excluding numbers commonly provided in conference
+
+
+
+
+
+
+
+
+
+
+ The theme is the slogan or special emphasis of a conference in a particular year. It differs from the subject of a conference in that the subject is stable over the years while the theme may vary from year to year. For example, the American Society for Information Science and Technology conference theme was "Knowledge: Creation, Organization and Use" in 1999 and "Defining Information Architecture" in 2000.
+
+
+
+
+
+
+
+
+
+
+ The popularly known as or jargon name (e.g. SIGGRAPH for "Special Interest Group on Computer Graphics"). Authors commonly cite the conference acronym rather than the full conference or proceedings name, so it is best to include this element when it is available.
+
+
+
+
+
+
+
+
+
+
+ The sponsoring organization(s) of a conference. Multiple sponsors may be given if a conference is hosted by more than one organization.
+
+
+
+
+
+
+
+
+
+
+ The number of a conference. conference_number should include only the number of the conference without any extra text
+
+
+
+
+
+
+
+
+
+
+ The location of the conference. The city, state, province or country of the conference may be provided as appropriate.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The start and end dates of a conference event. conference_date may be used in three ways:
+ 1. If publishers that do not have parsed date values, provide just text with the conference dates. The date text should be taken from the proceedings title page.
+ 2. If publishers have parsed date values, provide them in the attributes.
+ 3. If both parsed date values and the date text are available, both should be provided. This is the preferred tagging for conference_date. For example:
+ Jan. 15-17, 1997
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Container for all information that applies to a non-series conference proceeding.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Container for all information that applies to a specific conference proceeding that is part of a series.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The undifferentiated title of a conference proceeding.
+
+
+
+
+
+
+
+
+
+
+ The subject of the conference proceeding, e.g. "Computer Graphics" is the subject matter of SIGGRAPH.
+
+
+
+
+
+
+
+
+
+
+ Container for all information about a single conference paper.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Container for all information about a single book.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ A container for all title-level metadata for a single book that is not part of a series or set.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ A container for all information that applies to an individual volume of a book series.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ A container for all information that applies to an individual volume of a book set.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ A segment of a book, report, or standard for which a DOI is being registered. Most commonly used for book chapters.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Container for metadata about a series publication.
+
+
+
+
+
+
+
+ The abstract element allows depositors to include abstracts extracted from NLM or JATS XML in Crossref deposits. The jats: namespace prefix must be included.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ When a book consists of multiple volumes that are not part of a serial publication (series), set_metadata is used to describe information about the entire set.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The series number within a specific published conference discipline.
+
+
+
+
+
+
+
+
+
+
+ The part number of a given volume. In some cases, a book set will have multiple parts, and then one or more volumes within each part. The part number of a given volume should be deposited in this element.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ dissertation is the top level element for deposit of metadata about one or more dissertations.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ report-paper is the top level element for deposit of metadata about one or more reports or working papers.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Container for the metadata related to a Technical Report or Working Paper.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Container for the metadata related to a Technical Report or Working Paper that is part of a series.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ standard is the top level element for deposit of metadata about standards developed by Standards Development Organizations (SDOs) or Consortia.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Container for the metadata related to a Standard that is not part of a series.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ database is the top level element for deposit of metadata about one or more datasets or records in a database.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ database_metadata contains metadata about the database.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ dataset is used to capture information about one or more database records or collections.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Used to define a publication (book, journal, etc) for pending publication content. A title must be supplied, as well as an ISSN, ISBN, or title-level DOI
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Member's custom statement of intent to publish content for which a pending publication DOI has been created
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The peer_review content type is intended for assigning DOIs to the reports and other artifacts associated with the review of published content.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Required attribute. First submission defined as revision round zero
+
+
+
+
+
+
+
+
+
+
+ Statement of competing interest supplied by a review author during the review process.
+
+
+
+
+
+
+
+
+
+
+
+ Running numbers to specify the various reports (ex: RC1 to RC4)
+
+
+
+
+
+
+
+
+
+ Container for 'pending publication' metadata. Pending publication DOIs are used to create a DOI for a content item that is not yet available online or in print.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Container for posted content metadata.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Posted content may be organzed into groupings within a given publisher. This element provides for naming the group. It is expected that publishers will have a small number of groups each of which reflect a topic or subject area.
+
+
+
+
+
+
+
+
+
+
+
+ Container element for information about an institution or organization associated with an item.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The full name of an institution.
+
+
+
+
+
+
+
+
+
+
+ Identifier for an institution or organization (currently supported: ROR, ISNI, Wikidata). Identifiers must be included as a URI
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The acronym of the institution.
+
+
+
+
+
+
+
+
+
+
+ The primary city location of the institution. institution_place gives the primary city location of the institution. When the location is a major city (e.g. New York, Amsterdam), no qualifying country or U.S. state need be given. If the city is not a major city, the appropriate country and/or state or province should be added.
+
+
+
+
+
+
+
+
+
+
+ The department within an institution.
+
+
+
+
+
+
+
+
+
+
+
+
+ The degree(s) awarded for a dissertation.
+
+
+
+
+
+
+
+
+
+
+ The contract number under which a report or paper was written.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The container for all who contributed to authoring or editing an item.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The name of an organization (as opposed to a person) that contributed to an item. If an item was authored by individuals in addition to one or more organizations, person_name and organization may be freely intermixed within contributors.
+
+
+
+
+
+
+
+
+
+
+
+ The name of a person (as opposed to an organization) that contributed to an item.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ A contributor's given name.
+
+
+
+
+
+
+
+
+
+
+
+
+ The family_name of a contributor.
+
+
+
+
+
+
+
+
+
+
+
+
+ The suffix of an author name, e.g. junior, senior, III.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The ORCID iD for an author.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Container for component metadata if the component is being registered after the parent record/DOI is created.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Container for a group of components
+
+
+
+
+
+
+
+
+
+ Container for component metadata. Supplemental materials, figures, tables, and other items that can be considered a citeable part of a registered item may be registered as components.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ A container for the title and original language title elements.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The title of the item being registered.
+
+
+
+
+
+
+
+
+
+ The title of an item in its original language if the registration is for a translation of a work.
+
+
+
+
+
+
+
+
+
+
+ The sub-title portion of a title.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ 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.
+
+
+
+
+ Day of publication. The should must be expressed with a leading zero if it is less than 10 (e.g. submit "05", not "5").
+
+
+
+
+ Year of publication.
+
+
+
+
+ Container for key dates in the life of a database or dataset.
+
+
+
+
+
+
+
+
+
+
+
+ The date a database or dataset item was created.
+
+
+
+
+
+
+
+
+
+ The date a piece of content was created.
+
+
+
+
+
+
+
+
+
+ The date a pre-print was posted to a repository.
+
+
+
+
+
+
+
+
+
+ The date a manuscript was accepted for publication.
+
+
+
+
+
+
+
+
+
+ The date a dataset or database was last updated.
+
+
+
+
+
+
+
+
+
+ The date of publication. Multiple dates are allowed to allow for different dates of publication for online and print versions.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The date a review was published to a repository.
+
+
+
+
+
+
+
+
+
+
+
+ The date on which a dissertation was accepted by the institution awarding the degree, a report was approved, or a standard was accepted.
+
+
+
+
+
+
+
+
+
+ Basic data types for date parts.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The container for information about page ranges.
+
+
+
+
+
+
+
+
+
+
+
+
+ Identifies books or conference proceedings that have no ISBN assigned.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The coden assigned to a journal or conference proceedings.
+
+
+
+
+
+
+
+
+
+
+ A container for item identification numbers set by a publisher.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ A publisher-assigned number that uniquely identifies the item being registered.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ A public standard identifier that can be used to uniquely identify the item being registered.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ A container for information about the publisher of the item being registered
+
+
+
+
+
+
+
+
+
+
+
+
+
+ publisher_place gives the primary city location of the publisher. If the city is not a major city, the appropriate country, state, or province should be added.
+
+
+
+
+
+
+
+
+
+
+ The name of the publisher of a book or conference proceedings. This name may differ from that of the organization registering or maintaining the metadata record.
+
+
+
+
+
+
+
+
+
+
+
+ A narrative description of a file (e.g. a figure caption or video description).
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ A narrative description of a component's file format and/or file extension.
+
+
+
+
+
+
+
+
+
+
+
+ Container element for archive information
+
+
+
+
+
+
+
+
+
+ Used to indicate the designated archiving organization(s) for an item.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+