Frequently Asked Questions: How to Get a Journal Indexed in AGRICOLA

Thank you for your interest in having your journal indexed in the AGRICOLA family of products. This includes PubAg which contains full-text journal articles authored by USDA researchers and staff. This FAQ describes the process for getting a journal indexed in AGRICOLA. It includes the steps involved in the journal approval process and provides detailed guidance to publishers how they can meet the Library's requirement of providing metadata for articles indexed in AGRICOLA. Metadata contains basic citation information about each article (e.g. author(s), article title, abstract, journal title, volume/issue number, ISSN). Sample records as well as templates are provided for each acceptable metadata format.

Questions may be submitted via email to: AGRICOLAPublishers@ars.usda.gov

General

    1. Publisher emails Chief Collection Development Librarian (AGRICOLAPublishers@ars.usda.gov)  requesting to have its journal indexed in AGRICOLA.  Publisher also indicates in email a willingness to contribute metadata as described in this FAQ.

    2. Journal is evaluated for indexing acceptance in AGRICOLA.  Evaluation criteria includes subject scope of the journal’s content and overall quality of the journal.  All journals must be peer-reviewed, and contain English language titles and abstracts..

    3. The Chief Collection Development Librarian sends an email to the publisher either accepting or rejecting the journal for indexing. If accepted, the publisher is asked to submit at least five sample records in proper XML format for review to assure it can meet AGRICOLA metadata requirements.

    4. Sample metadata is reviewed by NAL’s metadata staff and is either approved, or returned to the publisher to modify and resubmit them.

    5. Once the metadata sample has been approved, an FTP account will be established for the publisher to use to send metadata files as issues are published. The publisher is then emailed an FTP account login ID, along with NAL’s IP address which is needed as part of the FTP process. A separate email will immediately follow containing the account password with no other information in the message. More information about the FTP process is available in the FAQ question "How do I send metadata to NAL?"

    6. NAL staff member Deborah Richardson (deborah.richardson@ars.usda.gov) will work with the publisher to assure that the first transmission of metadata is successful.

Peer-reviewed journal articles and conference presentations by named personal authors that have English language titles and abstracts may be indexed in AGRICOLA.

Articles may have the following publisher-assigned labels:

  • Research article
  • Original paper
  • “Review” or “Review Article”
  • Research note
  • Commentary
  • “Insights”--(Wiley journals)
  • “Opinion”---with bibliographical references (BioMed Central journals)
  • Short communication
  • Teaching case study
  • Case study
  • Case report (BioMed Central journals)
  • Viewpoint (Springer journals)
  • Biographical articles about an individual’s contributions to the profession
  • Plant announcements; taxonomic announcements

    The following types of content are not indexed in AGRICOLA:

    • Abstracts (no associated article)
    • Articles in which the author’s name is a pseudonym
    • Basic biographical information/obituaries
    • Book reviews
    • Editorials--unless it has an abstract and bibliographical references
    • Forewords/Introductions
    • Interviews
    • Letters to the editor
    • Meeting reports
    • Monographs of any size
    • News note
    • Obituaries
    • “Opinion”—no bibliographical references
    • Patents
    • "Research highlight" (Wiley journals)

    Metadata is usually defined as “data about data”.

    In terms of AGRICOLA, metadata is structured data that contains basic citation information about each article (e.g. author(s), article title, abstract, journal title, volume/issue number and date). The structured nature of metadata allows it to be  ingested, processed and displayed in AGRICOLA in a consistent manner.

    Extensible Markup Language (XML) defines a set of rules for encoding documents in a format that is both human-readable and machine-readable.

    Each element markup construct begins with “< >“ and ends with “</>"

    start-tags: <section>
    end-tags: </section>

    A Document Type Definition (DTD) defines the legal building blocks of
    an XML document. It defines the document structure with a list of legal
    elements and attributes.

    An XML Schema is an XML-based alternative to DTD. An XML schema
    describes the structure of an XML document. The XML Schema language is
    also referred to as XML Schema Definition (XSD).

    All metadata must be “well-formed” and “validated” against an XML schema or DTD (Document Type Definition).

    Well formed XML has all metadata tags opened and closed in the proper order and has a declaration (DTD or XML schema) at the top of the file of records, with the proper attributes.

    The purpose of a DTD (Document Type Declaration) or XML Schema is to define the building blocks of an XML document with a list of elements and attributes.

    Example of a DTD:
    <!DOCTYPE ArticleSet PUBLIC "-//NLM//DTD PubMed 2.6//EN" "http://www.ncbi.nlm.nih.gov:80/entrez/query/static/PubMed.dtd">

    Example of an XML Schema:
    <xml version="1.0" encoding="UTF-8"?>
    <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://tempuri.org/po.xsd">

    The XML editor that you use to create your metadata will have a built in validation mechanism.  For example the Oxygen XML editor will display a green box if the record is well formed and validated.

    An XML Editor is used to create records.

    If you have already have access to an XML editor please use it to create records.

    If not, there are a variety of open-source XML editors. Two noted below are:

    A) Komodo Edit

    B)  Microsoft XML Notepad 2007      

    •  Resolve any errors identified on the “error list” in XML Notepad.

    Publishers have the option of submitting metadata in one of the three formats noted below. The “preferred” format is MODS, unless the publisher has already created records in JATS or NLM DTD.  MODS records require the least amount of preprocessing by NAL staff and will be available in AGRICOLA more rapidly than those in either or JATS or the NLM DTD.   Templates and sample records are provided in attachments below.

    Metadata Object Description Schema (MODS)
    Publisher data formatted in MODS will be processed more rapidly.
    http://www.loc.gov/standards/mods/mods-schemas.htm

    Journal Article Tag Suite (JATS)
    JATS Journal Archiving and Interchange Tag Suite Version 1.0 will be accepted as will its predecessor NLM DTD 3.0. However, the current version of JATS is preferred.
    http://jats.nlm.nih.gov

    NLM DTD
    This was the original NLM template for submitting metadata for Medline/PubMed. All Versions of the NLM DTD up to 2.6 will be accepted.
    http://www.ncbi.nlm.nih.gov/books/NBK3828/

    The following metadata elements are required on all records that are indexed. Each element has examples below.

    • Declaration (XML Schema or DTD---is required above the first record)
    • Article title (in English)
    • Personal author(s)/contributor(s); affiliation of the first author
    • Language (if no language is noted, English is assumed)
    • Abstract (in English)
    • Pagination (first page, last page, if noted)
    • Journal title
    • Publisher name
    • ISSN (print and electronic if both are available)
    • Identifier: Digital Object Identifier (DOI) or URL link, if available
    • Extent (First page, last page)
    • Volume number
    • Issue number
    • Date of publication
    • Title (non-English)
    • Abstract (Non-English)
    • Copyright statement

    Some characters have a special meaning in XML.

    If a “less than”( "<" ) character is placed inside an XML element, it will generate an error because the metadata parser interprets it as the start of a new element. 

     It will generate an XML error:
    <abstract> if salary < 1000 then </abstract>.

    To avoid this error, replace the "<" character with an entity reference:

    <abstract> if salary &lt; 1000 then </abstract>

    There are 5 predefined symbols that need to be converted to codes:

    Less than:   <   use     &lt;
    More than:  >   use     &gt;
    Ampersand: &   use     &amp;
    Apostrophe:  '   use     &apos;
    Quotation:    "   use     &quot;

    No other HTML coding will be accepted.

    Subscripts and superscripts are acceptable with no coding. H20

    Scientific notation should not be translated. Submit as is. 9.6 x 104 cfu/ml

    The metadata should be in plain text without coding for italics. Encoding="UTF-8"

    A schema or DTD (Document Type Definition) describes the structure of an XML record as well as the
    relationship of the elements to the application. It must appear at the
    beginning of the first record of a file of records, or at the beginning of each record if a file contains only
    one record. Records without a schema or DTD will be rejected.

    Below are the schema and DTDs for the three metadata formats that can be employed on AGRICOLA metadata records.  

    MODS:
    <?xml version='1.0' encoding='utf-8'>
    <modsCollection
        xmlns:xlink=http://www.w3.org/1999/xlink
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
        xmlns="http://www.loc.gov/mods/v3
        xsi:schemalocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-5.xsd
    <mods version="3.5">

     JATS:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96)Journal Archiving and Interchange DTD v1.1d1 20130915//EN" "http://jats.nlm.nih.gov/archiving/1.0/JATS-archivearticle1.dtd">

    PUB MED:
    ?xml version="1.0" encoding="UTF-8"?>

    < !DOCTYPE ArticleSet PUBLIC "-//NLM//DTD PubMed 2.6//EN" "http://www.ncbi.nlm.nih.gov/corehtml/query/static/PubMed.dtd ">

    MS Word documents
    PDF
    .rar files (an archive format)

    Metadata files are sent to NAL using a File Transfer Protocol (FTP).

    FTP is a standard Internet protocol for transmitting files between computers on the Internet. Like the Hypertext Transfer Protocol (HTTP), which transfers displayable Web pages and related files, and the Simple Mail Transfer Protocol (SMTP), which transfers e-mail, FTP is an application protocol that uses the Internet's TCP/IP protocols. FTP is commonly used to transfer files from your computer to other servers.

    Publishers may only send files via FTP using a static IP address. When a device is assigned a static IP address, it does not change. The device always has the same IP address. Most devices use dynamic IP addresses, which are assigned by the network when they connect. If you cannot provide a static IP address please contact NAL for further assistance:
    deborah.richardson@ars.usda.gov

    When the publisher’s metadata sample has been accepted, the FTP account creation process is as follows:

    1. FTP account is created by NAL staff.

    2. FTP login ID and the NAL IP address are sent to the publisher in an email. The login ID consists of lowercase letters.

    3. A second email containing only the FTP account password is then immediately sent to the publisher. The message will contain the same subject line.

    4. Files can be transferred using open-source FTP software such as WinSCP which is available for download at: http://winscp.net/eng/download.php

    5. In the URL box type in: ftp.nal.usda.gov. Then supply your assigned user ID and password.

    6. NAL IP address is: 199.136.16.185

    7. If you are unable to send files via FTP, they can be emailed to: deborah.richardson@ars.usda.gov

    MODS

    The following elements are required on all MODS records:

    See links to template and sample records below.

    Schema

    An XML schema describes the structure of an XML record.  XML schemas support data types, which allow for ease of defining, converting and validating data.  A reference to an XML schema must appear at the beginning of a set of records, or on each record if a file contains only one record. Records without a schema declaration will be rejected.

    MODS schema:

    <?xml version='1.0' encoding='utf-8'>
    <modsCollection
        xmlns:xlink=http://www.w3.org/1999/xlink
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
        xmlns="http://www.loc.gov/mods/v3
        xsi:schemalocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-5.xsd
    <mods version="3.5">

    Article title:

    The first word, proper nouns, names and the first word of  biological names should be capitalized. All other letters should be in lower case.

    Article titles must be in English. If the title also appears in a second language, it may be added as a translated title, even if it is in the language of the article's text.

    Examples:

    1) Rheological characterization of the fractions separated from pork lards through dry fractionation

    2) Developing a savanna burning emissions abatement methodology for tussock grasslands in high rainfall regions of northern Australia

    3) Susceptibility of developmental stages of Tetranychus uriticae (Acari: Tetranychidae) to infection by Beauveria bassiana and Metarhizium anispoliae (Hypocreales:Clavicipitaceae)

    Titles are formatted as follows:

    <titleInfo>
    <title>Bioactivity of  indigenous medicinal plants against the cotton whitefly, Bemisia tabaci </title>
    <titleInfo>

    <titleinfo xml:lang="eng">Drippers flow disturbances due to application of CO2 for irrigation water</title>
    </titleInfo>

    <titleinfo xml:lang="por" type="translated">
    <title>Disturbios de vazão em gotejadores devido a aplicação de co2 via água de irrigação</title>
    </titleInfo>

    Personal names:

    Last name, first name and middle name should be in tagged elements as required by the format.

    Records will be rejected in which first name, middle name and last name are in one tagged element.

    Diacritics can be included with names.

    Include affiliations for all authors, if possible; affiliations are mandatory for the first named author, if available.

    More than one affiliation per author may be recorded within the affiliation tag. Separate the locations with a period.

    <name type="personal">
    <namePart type="family">Rinovetz</namePart>
    <namePart type="given">Zorica Adina</namePart>
    <affiliation>Theoretical High School "J.L. Calderon", Petalozzi 14, 300115 Timosoara,Romania; email: zorrin@yahoo.com </affiliation>
    <role>
    <roleTerm type="text" authority="marcrelator">author</roleTerm>
    </role>
    </name>

    Type of Resource/Genre:

    <typeOfResource>text</typeOfResource>

     <genre>article</genre>

    Publisher Name:

    The Publisher’s name should be spelled out as it appears on the publication.

    Example:< publisher>Kemerovo Institute of Food Science and Technology</publisher>

    Date of issue:

    Issue date may include day and month, in addition to year, depending on what information appears on the article or journal title page.  Copyright date is optional, but may be added.

    Coding of data is as follows as presented in ISO 8601 (extended format):
    Year: YYYY (2014)
    Year and month: YYYY-MM (2014-07)
    Complete date:YYYY-MM-DD (1997-07-16)

    If the date range covers multiple months, e.g.Jan.-Feb.:( 2014-01)

    Examples:

    <dateIssued encoding="w3cdtf"keyDate="yes">2013-04</dateIssued>
    <copyrightDate encoding="w3cdtf">2012</copyrightDate>

    Example for Spring 2013 (only the year is in keyDate because w3cdtf only allows year-month-day.  The season is added under <relatedItem>
    <originInfo>
    <dateIssued encoding="w3cdtf"keyDate="yes">2013</dateIssued>

    Language:

    For MODS, codes for the "Language" element should be three letters, e.g.“eng” for English. NAL uses the iso639-2b codes. The list is available online at:
    http://www.loc.gov/standards/iso639-2/php/code_list.php>

    Example:
    <language>
    <languageTerm type "code" authority="iso639-2b">eng</languageTerm>
    </language>

     Abstract:

    Abstracts should be transcribed as they appear on the publication.

    An English abstract is required on each record in order for it to be indexed. If an abstract is available in a language in addition to English, that abstract must be in a separate tagged element.

    Example:
    <abstract xml:lang="eng">…</abstract>
    <abstract xml:lang="por">…</abstract>

    Records with multiple languages in one <abstract> element will not be accepted.

    The abstract should be in plain Unicode text. It should not include HTML or other format encoding elements. Please refer to the FAQ "How are entity references coded (symbols that need to be converted to codes)?" for the exceptions.

    Abstracts should follow same capitalization rules as titles. There should be a period (.) at the end of the abstract.

    Journal title:

    The journal title should be spelled out, not abbreviated. Capitalization follows the same policy as the article title.

    Do not include a journal’s subtitle unless it’s needed to clarify the meaning of the main title.

    Example:
    <relatedItem type="host">
    <titleInfo>
    <title>Food and raw materials</title>
    </titleInfo>

    ISSN (International Standard Serial Number):

    Metadata samples will not be approved without an ISSN registered with the ISSN International Centre in Paris. ISSNs can be obtained in each country through the local ISSN Centre, which is usually the national library. For more information see: http://www.issn.org

    All ISSN’s on a journal should be transcribed. This usually means the ISSNs for both the electronic and print versions.

    Example:
    <identifier type="issn">1459-0255</identifier>

    Volume number/Issue number:

    Transcribe volume, issue and number information as it appears on the article. Roman numbers may be used if they appear on the publication.

    "Caption" should include the terminology used on the text, e.g. no., issue, part.

    Example:
    <part>
    <detail type="volume">
    <number>9</number>
    <caption>v.</caption>
    </detail>
    <detail type="issue">
    <number>1</number>
    <caption>no.</caption>
    </detail>

    Extent (e.g. pagination):

    Transcribe the pagination as it appears in the article. HTML created articles do not have page numbers, so don’t include them in records.

    <extent unit="pages">
    <start>47</start>
    <end>52</end>
    </extent>

    Date

    Information in this date element is used to create issue records and keep articles from the same issue together.

    Issue date may include day, month, year, or season, depending on what information appears on the article or journal title page.

    "year" only
    <text type="year">2014</text>

    "year" and "month"
    <text type="year">2014</text>
    <text type="month">04</text>

    "year" "month" and "day":
    <text type="year">2014</text>
    <text type="month>04</text>
    <text type="day>15</text>

    "year" and "season"
    <text type="year">2014</text>
    <text type="season">Spring</text>

     Links to full-text:

    NAL prefers digital object identifiers (DOI) be used to link to online full-text. If DOI’s are not available, URLs may be used. NAL will accept URLs even at the journal level. Numbers as they appear on the publication.

    Examples:
    <identifier type="doi">10.12737/1516</identifier>
    <identifier type="uri">http://world-food.net/download/journals/2011-issue_1/8.pdf</identifier>
    </mods>

    JATS

    The following elements are required on all JATS records.  


    See the links at the end of this page to sample records and a template.


    For additional information see JATS documentation at: http://jats.nlm.nih.gov/archiving/


    DTD:


    A DTD describes the structure of an XML record as well as therelationship of the elements to the application. It must appear at thebeginning of each set of records, or on each record if a file contains onlyone record. Records without a schema or DTD will be rejected.


    JATS schema:


    <?xml version="1.0" encoding="UTF-8"?>< !DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96)Journal Archiving and Interchange DTD v1.1d1 20130915//EN" "http://jats.nlm.nih.gov/archiving/1.0/JATS-archivearticle1.dtd">


    Journal Title:


    The journal title should be transcribed as it appears on the publication.


    The first word, proper nouns and names should be capitalized. All other letters should be in lower case. The first word of biological names should be capitalized.  


    Do not include a journal’s subtitle unless it’s needed to clarify the meaning of the main title.


    If the journal title appears in multiple languages, assign the <journal-title> to the language of the journal's text.  Code titles in other languages with the appropriate language code.


    Examples:<journal-title-group><journal-title>Journal of agricultural and food chemistry</journal-title></journal-title-group>


    <journal-title-group><journal-title>Revista brasileira de agricultura irrigada</journal-title><trans-title-group><trans-title>Brazilian journal of irrigation agriculture<trans-title></trans-title-group></journal-title-group>


    Publisher Name:


    The publisher’s name should be transcribed as it appears on the publication.

    <publisher><publisher-name>WFL Publisher</publisher-name></publisher>


    ISSN (International Standard Serial Number):


    Metadata samples will not be approved without a journal's ISSN being registered with the ISSN International Centre in Paris. ISSNs can be obtained from each country's ISSN Centre, which is often the country’s national library. For more information see: http://www.issn.org


    ISSNs for both the print and electronic versions of the journal should be included on the record, if available.


    Examples:<issn pub-type="ppub">1459-0255</issn><issn pub-type="epub">1459-0263</issn>


    Links to Full-Text:


    NAL prefers DOIs (digital object identifiers) be employed as links from AGRICOLA records to online full-text content. If DOIs are not available, publishers may assign a URL that links to either the specific article or the journal.

    For information about DOIs, please see: http://www.doi.org/faq.htmlURLs may be used to link to either the article or the journal, though linking directly to the article is preferred.


    Examples:<article-id pub-id-type="doi">10.7127/rabi.v8n400213</article-id><article-id pub-id-type="uri"> ">http://world-food.net/download/journals/2011-issue_1/8.pdf</article-id> </article-id>


    Article Title:


    <article-title> must be in English. If the title appears in a second language, it may be added as a translated title, even if it is in the language of the text.  


    The first word, proper nouns, names and the first word of scientific names (taxonomic nomenclatures) should be capitalized. All other letters should be in lower case.


    Examples:a) Rheological characterisation of the fractions separated from pork lards through dry fractionationb) Developing a savanna burning emissions abatement methodology for tussock grasslands in high rainfall regions of northern Australiac) Susceptibility of developmental stages of Tetranychus urticae (Acari: Tetranychidae) to infection by Beauveria bassiana and Metarhizium anisopliae (Hypocreales: Clavicipitaceae)


    Formatted examples:English title only:<title-group><article-title>Bioactivity of indigenous medicinal plants against the cotton whitefly, Bemisia tabaci</article-title><title-group>


    English and Portuguese titles:<title-group><article-title>Drippers flow disturbances due to application of CO2 for irrigation water </article-title></title-group><trans-title-group><trans-title xml:lang="pt">Disturbios de vaz~ao em gotejadores devido a aplicac~ao de CO2 via agua de irrigac~ao</trans-title></trans-title-group>


    Personal Authors/Contributors and their Affiliations:


    Last name, first name and middle name should be transcribed as they appear on the publication.  Names should be tagged as required by the format.


    Records will be rejected in which first name, middle name and last name are in one tagged element.


    Diacritics may be included.


    Include affiliations for all authors, if possible. Affiliation is mandatory for the first named author, if it is noted in the journal article.

    More than one affiliation per author may be recorded within the affiliation tag. Separate information about each affiliation with a period.


    Example: <contrib contrib-type="author"><name><surname>Alves Silveira</surname><given-names>Pedro Rodrigues</given-names></name><aff>Departamento de Engenharia Rural, Escola Superior de Agricultura Luiz de Queiroz, Universidade de S~ao Paulo, Piracicaba</aff><email>prasilve@esalq.usp.br (link sends e-mail)</email></contrib></contrib-group>


    Publication Date:


    Issue date may include day, month, year, or season, depending on what information appears on the article or journal title page.  Date information is provided both in coded form and by elements.


    <pub-date type="pub"><day>03</day><month>01</month><year>2014</year></pub-date>


    <pub-date type="pub"><season>Spring</season><year>2014</pub></pub-date>


    Volume Number/Issue Number:


    Transcribe the volume and issue numbers as they appear on the publication. Roman rather than Arabic numbers may be used if they appear on the publication.



    Examples:<volume>1</volume><issue>1</issue>

    <volume>318</volume><issue>7187</issue>



    Extent (e.g. pagination):


    Transcribe the pagination as it appears in the article. HTML created articles do not have page numbers, so don’t include them in records.


    Example:<fpage>825</fpage><lpage>841</lpage>


    Abstract:

    The abstract should be in plain Unicode text. It should not include HTML tagging or other format encoding elements. Please refer to the FAQ "How are entity references coded (symbols that need to be converted to codes)?" for the exceptions.


    An English abstract is required on each record in order for AGRICOLA subject terms to be assigned. If an additional abstract in a language other than English appears in the article, that abstract may be added in a separate <abstract> element.


    Records will not be accepted with abstracts in multiple languages in one <abstract> element.


    Capitalization rules are the same as in the <journal-title> element.


    There should be a period (.) at the end of the abstract.


    Examples: Abstract only in English<abstract > </abstract>


    Abstract in English and Spanish

    <abstract xml:lang="en"> </abstract><trans-abstract xml:lang="sp"> </trans-abstract> </abstract>

    NLM DTD

    The following elements are required on all NLM DTD records.   For additional help see the National Library of Medicine documentation at: http://www.ncbi.nlm.nih.gov/books/NBK3828/#publisherhelp.Instructions_for_articles

    See the links at the end of this page to sample records and a template.

    DTD:

    A DTD describes the structure of an XML record as well as the relationship of the elements to the application. It must appear at the beginning of each set of records, or on each record if a file contains only one record. Records without a schema or DTD will be rejected. 

    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE ArticleSet PUBLIC "-//NLM//DTD PubMed 2.6//EN" "http://www.ncbi.nlm.nih.gov/corehtml/query/static/PubMed.dtd">

    Journal Title:

    The journal title should be transcribed as it appears on the journal.  Do not use the abbreviated form the title.

    Capitalization guidelines follows the same policy as stated in <ArticleTitle>. Do not include a journal’s subtitle unless it’s needed to clarify the meaning of the main title.

    <JournalTitle>Journal of food, agriculture and environment</JournalTitle>

    ISSN (International Standard Serial Number):

    Metadata samples will not be approved without an ISSN that is registered with the ISSN International Centre in Paris. ISSNs can be obtained in each country through the local ISSN Centre, which is often the country’s national library.

    For more information see: http://www.issn.org

    All ISSN’s appearing on the publication should be transcribed. This usually means ISSNs for both the electronic and print versions.

    Volume Number/Issue Number:

    Transcribe the volume and issue numbers as they appear on the publication. Roman rather than Arabic numbers may be used if they appear on the publication.

    <Volume>9</Volume>
    <Issue>1</Issue>

    Article Title:

    The first word, proper nouns and names should be capitalized. All other letters should be in lower case. Capitalize the first word of biological names. Do not use HTML coding for italics.

    Article titles must be in English. If the title appears in a second language, it may be added as a translated title using the element <VernacularTitle>, even if it is in the language of the text.

    Examples:
    a) Rheological characterisation of the fractions separated from pork lards through dry fractionation
    b) Developing a savanna burning emissions abatement methodology for tussock grasslands in high rainfall regions of northern Australia
    c) Susceptibility of developmental stages of Tetranychus urticae (Acari: Tetranychidae) to infection by Beauveria bassiana and Metarhizium anisopliae (Hypocreales: Clavicipitaceae)

    d)Text is in Portuguese; titles and abstracts in Portuguese and English.

    <ArticleTitle>Drippers flow disturbances due to application of CO2 for irrigation water</ArticleTitle>
    <VernacularTitle>Disturbios de vaz~ao em gotejadores devido a applic~ao de CO2 via agua de irrigac~ao</VernacularTitle>

    Links to full-text:

    Only DOIs (Digital Object Identifiers) may be used with the NLM DTD.  Publishers who wish to use URLs to link records to online content must use either the MODS or JATS metadata formats.

    Example:
    <ELocationID EIdType="doi">10.7127/rbai.v8N400213</ELocationID> 

    Language

    PubMed DTD language code should be "EN" for English, not En-US

    <Language>EN</Language>

    For other language codes, see the link below.
    http://www.iana.org/assignments/language-subtag-registry/language-subtag

    Extent (e.g. pagination):

    Transcribe the pagination as it appears in the article. HTML created articles do not have page numbers, so do not include them in records.

    Example:
    <FirstPage>47</FirstPage>
    <LastPage>52</LastPage>

    If the letter “P” appears with the page number, include it in the metadatda:
    <FirstPage>P47</FirstPage>
    <LastPage>P52</LastPage>

    Publication date:

    <PubDate pubstatus="epublish"> electronic publication
    <Year></Year>
    <Month></Month>
    </Pubdate>

    PubMed DTD:
    <Pubdate pubstatus="ppublish"> print publication
    <Year></Year>
    <Month></Month>
    </PubDate>

    Personal Authors/Contributors and their affiliations:

    Last name, first name or initial, middle name should be in tagged elements as required by the format.

    Records will be rejected if first name, middle name and last name are in one tagged element.

    Diacritics can be included with names.

    Include affiliations of all authors, if possible; affiliation is mandatory for the first named author.
    More than one affiliation per author may be recorded within the affiliation tag. Separate the locations with a period.

    Examples:
    <Author>
    <FirstName>Zorica</FirstName>
    <MiddleName>Adina</MiddleName>
    <LastName>Rinovetz</LastName>
    <Affiliation>Theoretical High School "J.L. Calderon," Pestalozzi 14, 300115 Timisoara, Romania; email:zorrin@yahoo.com (link sends e-mail)</Affiliation>
    </Author>

    <Author>
    <FirstName>Nelmicio</FirstName>
    <LastName>Furtada da Silva</LastName>
    <Affiliation>IF Goiana, Campus Rio Verde</Affiliation>
    </Author>

    Abstract:

    The abstract should be in plain Unicode text. It should not include HTML or other format encoding elements. Please refer to the FAQ "How are entity references coded (symbols that need to be converted to codes)?" for the exceptions.

    An English abstract is required on each record in order for it to be indexed. If an abstract is available in a language in addition to English, that abstract must be in a separate tagged element. The schema used to code the metadata will determine how the multiple language abstracts should be coded.

    Records with multiple languages in one <abstract> element will not be accepted.

    Abstracts should follow same capitalization rules as titles. There should be a period (.) at the end of the abstract.

    Example (in English only)
    <Abstract>…</Abstract>

    Example (In English and Portuguese)
    <Abstract>…</Abstract>
    <OtherAbstract language="pt">…</OtherAbstract>