Note 1: See list of standardized
XML tag names for use in output file.
Note 2: See allowed
formats for the publication date.
Note 3: See details
of the OSTI-to-Site TAPping process.
Required Metadata for OSTI-to-Site TAPping (formerly “harvesting”)
|
Required Metadata for a Citation to go into E-Link |
Must site always include in its XML output file? |
Can OSTI insert this field and/or a default value into the citation as it is TAPped and processed? |
Where does the information in this field display in
the |
|
Access Limitation |
No |
Yes, and is always UNL for harvesting |
It doesn’t. Info is stored in E-Link. |
|
STI Product Title |
Yes, field with a value is always required from site. |
No |
TITLE |
|
Author(s) |
Yes, field (with or without a value) is required. |
No, but OSTI will default an empty tag set to “None Available” |
CREATOR/AUTHOR |
|
Country of Publication |
No |
Yes and will default to US |
COUNTRY OF PUBLICATION |
|
DOE Contract Number (s) |
No |
Yes, if site specifies the default contract number |
DOE CONTRACT NUMBER |
|
Language |
No |
Yes and will default to 'English' |
LANGUAGE |
|
Originating Research Organization |
No |
Yes and will default to input site's name |
RESEARCH ORG |
|
Publication Date (see allowed formats) |
Yes, field with a value is always required. |
No |
PUBLICATION DATE |
|
Released By (Releasing Official's Name) (See Note B below) |
Site may include or OSTI will insert. |
Yes, if site wishes and indicates name to be inserted. |
It doesn't. Info is stored, maintained in E-Link. |
|
Released Date |
Site may include or OSTI will insert. |
Yes and will default to citation's TAP date. If site does not want to use default, however, site may put any specific date here, and it will not be changed by the date of TAPing. |
It doesn't. Info is stored, maintained in E-Link. |
|
Releasing Official's Email or Releasing Official’s Phone |
Site may include or OSTI will insert. |
Yes, if site wishes and indicates email address to be inserted. |
It doesn't. Info is stored, maintained in E-Link. |
|
Report Number(s) |
Yes, site must include field, with or without value. Note “if” statement: Value must always be present for TR product types. |
No, but OSTI will default to “None” when tag set is empty. |
REPORT NUMBER(S) |
|
STI Product Type |
Yes field with a value is always required from site. |
No |
RESOURCE TYPE |
|
Conference Information (See Note A below) |
Yes, field with a value if product type is Conference. Value may be minimal, if necessary, such as “To be presented at xxxx Conference” * |
No |
RESOURCE RELATION |
|
Journal Name (See Note C below) |
Yes, field with a value is required for Journal product type. Value may be minimal, such as “Submitted to xxxx Journal” * |
No |
RESOURCE RELATION |
|
Site URL |
Yes, field, with a value is required if product type is technical report, thesis/dissertation, or any product with full text. |
No |
Serves as a link to the full text |
|
Publisher Information |
Yes, field, with value required if product type is Book. |
No |
PUBLISHER |
|
Unique record identifier assigned by site |
Yes, field with a value is always required. |
No |
It doesn't. Sites' accession numbers are maintained in E-Link. |
Note A: Conference Information:
Conference information may be minimal when an
announcement is first harvested, but it is expected that the citation will
update through the reharvest process when more information is available.
Citations for conference documents should also include a URL indicating the
location of the full text, unless those documents are in copyrighted
“Proceedings.” In that case, publisher information for the Proceedings
should be provided.
Note B: Releasing Official Name: This is also the site Point of Contact (POC) for records provided to OSTI that refer to external publications (journals, books, etc.)
Note C: Journal Name: Journal information may be minimal when an announcement is first harvested, particularly if the announcement is based on a preprint. If the preprint is available as full text and the URL is in the citation, the minimal information continues to be acceptable. In the case of “announcement only” journal citations, it is expected that a minimal piece of information such as “Submitted to xxx Journal” will be updated through the reharvest process after publication information is available.
Optional Metadata for OSTI-to-Site TAPping
|
Optional Metadata |
Must site always include in its XML output file? |
Can OSTI insert field or default value into the citation as it is processed? |
Where does this information display in the |
|
Authors' email addresses |
No. |
No |
It doesn't. Information is stored, maintained in Elink. |
|
Availability information |
No |
No |
AVAILABILITY |
|
Authorization Revision Number |
No |
No |
OTHER IDENTIFYING NUMBERS |
|
Abstract |
No, but highly desirable |
No |
DESCRIPTION/ABSTRACT |
|
DOI (Digital Object Identifier) |
No |
No |
Serves as a link to full text |
|
File Format of STI Product |
No |
Yes and will default to correct value |
FORMAT |
|
Serial Identifier (such as ISSN or CODEN) |
No |
No |
OTHER IDENTIFYING NUMBERS |
|
Journal Volume |
Not in initial TAPed record but expected to come in updated record later. |
No |
RESOURCE RELATION |
|
Journal Issue |
Not in initial TAPed record but expected to come in updated record later. |
No |
RESOURCE RELATION |
|
Keywords |
No, but highly desirable |
No |
RELATED SUBJECT |
|
Other Identifying Numbers |
No |
No |
OTHER NUMBER (S) |
|
Patent Assignee |
No |
No |
RIGHTS |
|
Patent File Date |
No |
No |
RESOURCE RELATION |
|
Patent Priority Date |
No |
No |
RESOURCE RELATION |
|
Product Size |
No, but highly desirable |
No, but OSTI can default the word 'pages' so that site only has to put a number in this field |
FORMAT |
|
Proposal Revision Number |
No |
No, but OSTI can insert “Proposal Revision Number” as a prefix to help identify the number to users. |
OTHER IDENTIFYING NUMBERS |
|
R&D Project IDs |
No |
No, but OSTI can insert “R&D Project ID” as a prefix to help identify the number to users. |
OTHER IDENTIFYING NUMBERS |
|
Sponsoring Organization |
No |
Yes, if site wishes |
SPONSORING ORG |
|
Subject Category Codes |
No, but highly desirable |
No |
SUBJECT |
|
Work Authorization Number |
No |
No, but OSTI can insert “Work Authorization Number” as a prefix to help identify the number to users. |
OTHER IDENTIFYING NUMBERS |
|
Work Proposal Number |
No |
No, but OSTI can insert “Work Proposal Number” as a prefix to help identify the number to users. |
OTHER IDENTIFYING NUMBERS |
Note 1: Standardized
Tag Names
These are the XML tag names that OSTI requests TAPing sites to use in their output files.
<accession_no>
<author>
<author_emails>
<conference_information>
<country_publication_code>
<description>
<doe_contract_nos>
<doi>
<keywords>
<language>
<journal_name>
<journal_issue>
<journal_serial_id>
<journal_volume>
<other_identifying_nos>
<product_type>
<publication_date>
<publisher_information>
<rd_project_ids>
<report_nos>
<related_doc_info>
<research_org>
<released_by>
<released_by_phone>
<released_by_email>
<released_date>
<product_size>
<sponsor_org>
<subject_codes>
<title>
<site_url>
Note 2: Date Formats Allowed in
TAPped Records
1. mm/dd/yyyy
2. yyyy
3. yyyy followed by
either month, season, or quarter text as follows:
(a) yyyy and month text, e.g. 2000
January, 2004 March (month always fully spelled out)
(b) Seasons: e.g, 2000 Winter , 1999 Spring, 2006 Summer,
2008 Fall
(c) Quarters: e.g., 2000 1st Quarter
(CY)
Quarter must be one of the
following:
Calendar Year:
1st Quarter (CY)
2nd Quarter (CY)
3rd Quarter (CY)
4th Quarter (CY)
Fiscal Year:
1st Quarter (FY)
2nd Quarter (FY)
3rd Quarter (FY)
4th Quarter (FY)