Required Metadata for Harvesting
|
Required Metadata for a Citation to go into E-Link |
Site must always include in its XML output file: |
OSTI can insert into the citation as it is processed: |
Business rule change? |
Where does this information display in the Dublin Core database? |
|
Access Limitation |
No |
Yes, and is always UNL for harvesting |
No |
It doesn’t. Info is stored in E-Link. |
|
STI Product Title |
Field with a value |
No |
No |
TITLE |
|
Author(s) |
Field (with or without a value) |
No, but will default an empty tag set to “None Available” |
No |
CREATOR/AUTHOR |
|
Country of Publication |
No |
Yes and will default to 'U.S.' |
No |
COUNTRY OF PUBLICATION |
|
DOE Contract Number (s) |
No |
Yes, if site specifies the default contract number |
No |
DOE CONTRACT NUMBER |
|
Language |
No |
Yes and will default to 'English' |
No |
LANGUAGE |
|
Originating Research Organization |
No |
Yes and will default to input site's name |
No |
RESEARCH ORG |
|
Publication Date |
Field with a value |
No |
Yes, see note below |
PUBLICATION DATE |
|
Released By (Releasing Official's Name) |
Site may send or OSTI will insert. |
Yes, if site wishes and indicates name to be inserted. |
Yes, added to harvesting See note below. |
It doesn't. Info is stored, maintained in E-Link. |
|
Released Date |
Site may send or OSTI will insert. |
Yes and will default to citation's harvested 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 harvesting. |
Yes, added to harvesting |
It doesn't. Info is stored, maintained in E-Link. |
|
Releasing Official's Email or Releasing Official’s Phone |
Site may send or OSTI will insert. |
Yes, if site wishes and indicates email address to be inserted. |
Yes, added to harvesting |
It doesn't. Info is stored, maintained in E-Link. |
|
Report Number(s) |
Field, with or without value |
No, but OSTI will default to “None” when tag set is empty. |
No |
REPORT NUMBER(S) |
|
STI Product Type |
Field with a value |
No |
Yes, the MI product type will now be disallowed. |
RESOURCE TYPE |
|
Conference Information (required if product type is CO and if link to full text is not available) |
Field with or without a value. Note “if” statement. Value may be minimal, such as “To be presented at xxxx Conference” * |
No |
Yes, added requirement to harvesting See note below. |
RESOURCE RELATION |
|
Journal Name (required if product type is JA and if link to full text is not available) |
Field with or without a value. Note “if” statement. Value may be minimal, such as “Submitted to xxxx Journal” * |
No |
Yes, added requirement to harvesting See note below |
RESOURCE RELATION |
|
Site URL (required if product type is TR or TD or if any product is full text) |
Field, with or without a value. Note “if” statement. |
No |
No |
Serves as a link to the full text |
|
Publisher Information, if other than originating research organization |
Field, with or without a value. Must have value if document type is Book and no link to full text is available |
No |
Yes, added requirement to harvesting |
PUBLISHER |
|
Unique record identifier assigned by site |
Field with a value |
No |
No |
It doesn't. Sites' accession numbers are maintained in the harvesting files. |
Publication Date Note: This field is being “relaxed” to allow sites to submit text format if a date is not available. Text options include month or a year. OSTI will then generate a date to enable range searching but will allow the document’s text-only date of publication to display in the database. The standard text options are to be determined.
Conference Information Note: 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. A CO citation will be rejected if there is nothing in conference information, unless a URL is provided.
Releasing Official Note: This is also the site Point of Contact (POC) for records provided to OSTI that refer to external publications (journals, books, etc.)
Journal Name Note: 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. A JA citation will be rejected if there is nothing in the Journal Name field, unless a URL is provided.
Optional metadata for harvesting
|
Required Metadata for a Citation to go into E-Link |
Site must always include in its XML output file: |
OSTI can insert into the citation as it is processed: |
Business rule change? |
Where does this information display in the Dublin Core database? |
|
Authors' email addresses |
No |
No |
No |
It doesn't. Information is stored, maintained in Elink. |
|
Availability information |
No |
No |
No |
AVAILABILITY |
|
Authorization Revision Number |
No |
No |
No |
OTHER IDENTIFYING NUMBERS |
|
Abstract |
No, but highly desirable |
No |
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 |
Yes, no longer required from site |
FORMAT |
|
Serial Identifier (such as ISSN or CODEN) |
No |
No |
No |
OTHER IDENTIFYING NUMBERS |
|
Journal Volume |
No, but highly desirable |
No |
No |
RESOURCE RELATION |
|
Journal Issue |
No, but highly desirable |
No |
No |
RESOURCE RELATION |
|
Keywords |
No, but highly desirable |
No |
No |
RELATED SUBJECT |
|
Other Identifying Numbers |
No |
No |
No |
OTHER NUMBER (S) |
|
Patent Assignee (but becomes a required field if site intends to submit patent data through harvesting) |
No |
No |
No |
RIGHTS |
|
Patent File Date (but becomes a required field if site intends to submit patent data through harvesting. |
No |
No |
No |
RESOURCE RELATION |
|
Patent Priority Date |
No |
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 |
No |
FORMAT |
|
Proposal Revision Number |
No |
No, but OSTI can insert “Proposal Revision Number” as a prefix to help identify the number to users. |
Yes, new field in E-Link |
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. |
No |
OTHER IDENTIFYING NUMBERS |
|
Sponsoring Organization |
No |
Yes, if site wishes |
No |
SPONSORING ORG |
|
Subject Category Codes |
No, but highly desirable |
No |
No |
SUBJECT |
|
Work Authorization Number |
No |
No, but OSTI can insert “Work Authorization Number” as a prefix to help identify the number to users. |
Yes, new field.in E-Link |
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. |
Yes, new field in E-Link |
OTHER IDENTIFYING NUMBERS |