Announcement Notice 241.3 Instructions

The award number must be input accurately first in order to complete and submit the AN 241.3. The format should be either (1) two alphabetic characters and seven digits (for DOE awards granted since 2007), or (2) two alphabetic characters, two numeric characters, a dash, two-digit year, two alphabetic characters, and a five digit number (for awards granted prior to 2007).
Examples: SC0001234; EE0005432; NT0009876; or FG02-03ER83715; FG52-06NA27489; FC07-99ID55444; and AC02-96CH12345.

Examples of other identifying numbers that submitters may want to include are:

• Non-DOE contract numbers (Please do not include these non-DOE contract numbers in the DOE Award/Contract Number field. That field is validated and the record will be rejected if the grant/award/contract number is not a DOE one).
• The number assigned by arXiv.org to an author's posting of a paper (arXiv: 1501.00003)
• Any identifying number that may have meaning or retrieval utility to a particular segment of the anticipated user population (in any format). This may include the numbers assigned by a university or domain area repository.

Note that these other identifying numbers do not typically fit more specific identifier fields available for input, i.e. fields such as product/report number, R&D project IDs, etc. Note also that multiple identifiers may be input here. A semi-colon and a space must be used to separate each identifier from the next one following it.

Enter the Award Digital Object Identifier (DOI) under which work or time was provided. An Award DOI is assigned to awards, contracts, equipment, facilities, grants, prizes, salary awards, and/or training grants. If the research object was produced under multiple awards given by multiple organizations, additional Award DOIs may be entered. Multiple Award DOIs are to be entered using the + to create a new entry. DOIs follow the format: 10.XXXX/XXXXX.

Note: Award DOIs are different than DOIs assigned to the research object currently being announced (submitted) to OSTI. DOIs for the research object may have been assigned by publishers or a repository. If a DOI for a research object has not already been assigned from another source, OSTI may assign a DOI.

Provide the name and location of the organization that performed the research or issued the scientific and technical report/product. More than one may be provided. Separate multiples with a semicolon and a space.

Select one product type from the four choices in the drop-down menu. To submit your final technical report, select that value. If "Other" type of STI is selected from the menu, then an additional subfield will appear.

• Technical Report - Select technical report. Note, if you are submitting a "Final Scientific/Technical Report," as most awards require at closeout, first select technical report, and then select the sub-type of "final technical report."
• Accepted Manuscript of Journal Article - Select this if you are submitting a final, peer-reviewed accepted manuscript for a journal article.
• Other - Specify the type of STI product not listed in the menu of choices. Examples: thesis, patent, book. NOTE: Use DOE CODE for software products and 241.6 for scientific research datasets, not the AN 241.3.

Select a report type.

• Final Technical Report - Select "Final Technical Report" if your award calls for a "Final Scientific/Technical Report."
• Technical Report Other - Select "Technical Report Other" if your award calls for submitting a supplemental report describing the research results. This does NOT replace the final scientific/technical report. "Technical Report Other" should not include progress reports or other types of management reports that would not be typical of scientific and technical information.

Specify the type of STI product not listed in the menu of choices. Examples: thesis, patent, book. NOTE: Use DOE CODE for software products and 241.6 for scientific research datasets, not the AN 241.3.

Provide the title that appears on the report or product, including volume, edition, and similar information if applicable.

Enter the date from the cover of the report in mm/dd/yyyy format (example: 01/01/2014), which is the required format for the final technical report. Typically, this date is an indication of when the report/product was created. Other STI may have an alternate date format, e.g., yyyy (example: 2013) as appropriate for the type of publication. If you use the yyyy format, a drop-down menu appears for you to input additional date information.

After entering last name, first name, and middle name or initial in the specified blanks, you may also enter the primary author/creator's email address, his or her ORCID number, and his or her affiliation in the remaining three fields of the author section.

• You may add as many additional authors as needed by clicking the "Add Author" button.
• You may change the order of author names by clicking the appropriate "Move" button.
• You may edit the author details by clicking the appropriate "Edit" button.
• If you wish to delete an author's name that you have already entered, click the "Remove" button.

Note that organization names or names of collaborations should not be entered into the author fields. Collaboration names and names of contributing organizations are entered into the Contributor Organizations field.

The name of a Research/Project Collaboration, if applicable, should be entered in this field, not in the author field. Contributor organizations are not authors' affiliations, the originating research organization, nor the funding/sponsor organization. They are, instead, any company, institution, or organization to which the submitter wishes to provide recognition and which clearly does not fit into any of the other organization fields. Examples of possible contributor organizations that a submitter may want to list (in addition to listing a collaboration name) include:

• An external organization that provided significant review of the research product.
• An organization that provided site management but was not directly involved in the research/experiment itself.
• An organization that collected data to provide to the originating research organization.
• A data center or repository that is not listed as the originating research organization.

This is a free text field and can hold multiple organizations names. Each different organization should be separated by a semi-colon followed by a space.

This is a unique identifier that you create and place on the report/product itself.

Use DOE, an acronym that identifies the awardee/recipient organization, and the final five to seven characters from your contract or grant number.

Example: For award #AC02-01FE11111, with Yale University, the report number would be: DOE-YALE-11111 or DOE-YALE-FE11111. If more than one STI product is to be submitted, you may use a suffix to identify them individually.

Example:
Final report: DOE-YALE-11111-1
2nd product: DOE-YALE-11111-2
3rd product: DOE-YALE-11111-3

Select the name of the specific DOE program office that provided the project funding from the list provided (e.g., USDOE Office of Science (SC) Basic Energy Sciences (BES)). For projects funded by more than one program office, indicate all sources of the DOE funding in descending order of dollar amount of funding appropriated. You may also input additional funding agencies in the textbox. Separate multiple program offices or funding agencies with a semicolon and a space. If you do not know the sponsoring DOE program office, you may select "USDOE".

You must provide a clear, concise, and publicly releasable English language executive summary of the information contained in the report/product, written in terms understandable by an educated layperson. The length should be no more than 5,000 characters. To fill this field, you can cut and paste from any word processing file.

Select one or more categories from the list provided. Select them in order of relevance to the project described in the product. You can review the list of subject category descriptions on the Authorities page.

These are words or phrases that describe the project as summarized in the report/product. Keywords aide in the online search and discovery of information about the project. More than one keyword may be entered; separate multiple keywords with a semicolon and a space.

Please provide citations for supplementary datasets or other items published with the product you are submitting. You may also provide a citation for any other directly-supporting item for technical reports, conference literature, etc. Or, see the Related Identifiers/DOIs field below.

Select a release date for your report based on the terms of your award for the data protection period allowed. After the release date, the technical report may become available to the public.

Referencing other documents, other datasets, or software applications that relate to the document you are submitting allows the user of the information to follow these vital links and to better understand the scope of your research. You may add DOIs to cross-reference these other items. If you do not have a DOI for one of the items you wish to relate to your document, please put the citation information for that item in the Related Document field. Note that you may find assigned DOIs for DOE technical reports in OSTI.GOV.

This Related Identifier/DOIs field also allows you, for each DOI you reference, to choose a controlled vocabulary term that "explains" the type of relationship between the DOI you enter and the document you are submitting. For additional information about the Related Identifiers controlled vocabulary see the DataCite Metadata Schema 4.3 Documentation in Table 9 on pages 46-51.

Select the appropriate distribution limitation from the choices provided in the drop-down menu. STI products should be written for public accessibility in order to advance science. However, if the report/product contains information that should not be publicly released, the restriction(s) must be indicated.

• Unlimited Announcement - The unrestricted, unlimited distribution of the product will be made publicly available. The government assumes no liability for disclosure of such data. If this is selected for an SBIR/STTR award, your final scientific/technical report is subject to immediate public release.
• Copyrighted Material - A copyright restriction on part or all of the contents of the STI product may affect the reproduction and distribution of the product by DOE/OSTI. Any restriction as retained in the award document must be specified.
• Controlled Unclassified Information (CUI) - (enter specific or basic categories/dissemination controls)*
• Small Business Innovation Research (SBIR) Data - If this is selected, you have chosen to protect your final scientific/technical report. The protection period will be calculated by adding 4 years to the date of submission. If you wish to extend the data protection period, you must submit a final scientific/technical report for a subsequent DOE SBIR/STTR award or certifying that work has been performed that extends the R&D under this award.
• Small Business Technology Transfer (STTR) Data - If this is selected, you have chosen to protect your final scientific/technical report. The protection period will be calculated by adding 4 years to the date of submission. If you wish to extend the data protection period, you must submit a final scientific/technical report for a subsequent DOE SBIR/STTR award or certifying that work has been performed that extends the R&D under this award.
• Security Sensitive Information
• Protected Data - You must also select CRADA or cite the data clause paragraph in your award document which allows trade-secret like protection (e.g. Energy Policy Act (EPAct), clean coal, electric vehicles, steel initiative, etc.). Then, specify the release date which must be no more than five years.
• Patentable Material - Provide all applicable patent information.
• Program-Determined Official Use Only

* For Controlled Unclassified Information (CUI), enter the basic or specified categories along with any limited dissemination controls. The best practice is to enter these using the CUI banner markings on the document. Examples include: "CUI//EXPT" "CUI//NNPI//FEDCON" "CUI//SP-EXPT".

Provide the organization or individual(s) name(s), with corresponding contact information, who will serve as the point of contact for DOE if there are questions about the content of the STI product.

For Final Technical Report, the medium required is an Electronic Document, thus that is the default value. For other type of STI, indicate the medium.

Reports or other products that are electronically uploaded to DOE via E-Link must NOT contain: limited rights data (proprietary data), classified information, protected PII, information subject to export control classification, or other information not subject to release. Protected PII is defined as an individual's first name or first initial and last name in combination with any one or more of the following types of information: social security number, passport number, credit card numbers, clearances, bank numbers, biometrics, date and place of birth, mother's maiden name, criminal, medical and financial records, educational transcripts, etc.

You must self-certify prior to submission (prior to uploading the full-text report or other product) that the item does not contain any of this type information.

For a Final Technical Report, you are required to upload an Electronic Document. Select the Browse button to locate the file on your computer. Also indicate the file format. Valid file formats are: Adobe Portable Document Format (.PDF) or MS Word (.DOC) only. Before you upload the document, you must certify (see Certifications) that the document being uploaded has been reviewed for, and does not contain, any information not subject to release, such as Protected PII.

DOE SBIR/STTR awardees may receive commercialization assistance services either from

1. a vendor that is directly funded by DOE or
2. a vendor(s) selected by the applicant and included as part of their application.

The document or file is publicly available electronically for free, without a login required.

An accepted manuscript is the version of the article that has been accepted for publication by a publisher and includes changes made during the peer-review process, also known as the final peer-reviewed accepted manuscript. It includes the same content as the published article in the journal and may or may not include all of the publisher's form or format. The key criteria for submission of accepted manuscripts to OSTI are (1) that DOE partially or completely funded the research reflected in the article or accepted manuscript, and (2) that the publication has been accepted for publication in a peer-reviewed journal.

• Event-shape fluctuations and flow correlations in ultra-relativistic heavy-ion collisions (accepted manuscript)
• Event-shape fluctuations and flow correlations in ultra-relativistic heavy-ion collisions (published article)
• Weak charge form factor and radius of 208Pb through parity violation in electron Scattering (accepted manuscript)
• Weak charge form factor and radius of 208Pb through parity violation in electron Scattering (published article)
• Structure and Dynamics of Colliding Plasma Jets (accepted manuscript)
• Structure and Dynamics of Colliding Plasma Jets (published article)
• Weak-triplet, color-octet scalars and the CDF dijet excess (accepted manuscript)
• Weak-triplet, color-octet scalars and the CDF dijet excess (published article)
• Environmental indicators for sustainable production of algal biofuels (accepted manuscript)
• Environmental indicators for sustainable production of algal biofuels (published article)
• Ultrafast Optical Microscopy of Single Monolayer Molybdenum Disulfide Flakes (accepted manuscript)
• Ultrafast Optical Microscopy of Single Monolayer Molybdenum Disulfide Flakes (published article)
• A Theoretical Study of Trimethylacetic Acid Adsorption on CeO2(111) Surface (accepted manuscript)
• A Theoretical Study of Trimethylacetic Acid Adsorption on CeO2(111) Surface (published article)
• Helicity evolution at small-x (accepted manuscript)
• Helicity evolution at small-x (published article)
• Reducing communication in algebraic multigrid using additive variants (published article)
• Reducing communication in algebraic multigrid using additive variants (accepted manuscript)
• Three-dimensional imaging of cholesterol and sphingolipids within a Madin-Darby canine kidney cell (published article)
• Three-dimensional imaging of cholesterol and sphingolipids within a Madin-Darby canine kidney cell (accepted manuscript)
• Investigating Radial Wire Array Z -Pinches as a Compact X-Ray Source on the Saturn Generator (published article)
• Investigating Radial Wire Array Z -Pinches as a Compact X-Ray Source on the Saturn Generator (accepted manuscript)
• Spatial tuning of acoustofluidic pressure nodes by altering net sonic velocity enables high-throughput,efficient cell sorting (published article)
• Spatial tuning of acoustofluidic pressure nodes by altering net sonic velocity enables high-throughput,efficient cell sorting (accepted manuscript)

The award number must be input accurately first in order to complete and submit the AN 241.3. The format should be either (1) two alphabetic characters and seven digits (for DOE awards granted since 2007), or (2) two alphabetic characters, two numeric characters, a dash, two-digit year, two alphabetic characters, and a five digit number (for awards granted prior to 2007).
Examples: SC0001234; EE0005432; NT0009876; or FG02-03ER83715; FG52-06NA27489; FC07-99ID55444; and AC02-96CH12345.

Examples of other identifying numbers that submitters may want to include are:

• Non-DOE contract numbers (Please do not include these non-DOE contract numbers in the DOE Award/Contract Number field. That field is validated and the record will be rejected if the grant/award/contract number is not a DOE one).
• The number assigned by arXiv.org to an author's posting of a paper (arXiv: 1501.00003)
• Any identifying number that may have meaning or retrieval utility to a particular segment of the anticipated user population (in any format). This may include the numbers assigned by a university or domain area repository.

Note that these other identifying numbers do not typically fit more specific identifier fields available for input, i.e. fields such as product/report number, R&D project IDs, etc. Note also that multiple identifiers may be input here. A semi-colon and a space must be used to separate each identifier from the next one following it.

Enter the Award Digital Object Identifier (DOI) under which work or time was provided. An Award DOI is assigned to awards, contracts, equipment, facilities, grants, prizes, salary awards, and/or training grants. If the research object was produced under multiple awards given by multiple organizations, additional Award DOIs may be entered. Multiple Award DOIs are to be entered using the + to create a new entry. DOIs follow the format: 10.XXXX/XXXXX.

Note: Award DOIs are different than DOIs assigned to the research object currently being announced (submitted) to OSTI. DOIs for the research object may have been assigned by publishers or a repository. If a DOI for a research object has not already been assigned from another source, OSTI may assign a DOI.

Provide the name and location of the organization that was funded and performed the research described in the accepted manuscript. More than one may be provided. Separate multiples with a semicolon and a space.

Select "Accepted Manuscript of Journal Article" from the choice of four product types. Note: Published versions of journal articles should not be submitted; you must provide the final peer-reviewed accepted manuscript and certify this is true before submission.

Additional subfields will appear on the AN 241.3 based on selection of Journal Article: Accepted Manuscript as the STI product type.

• Journal name - The name of the journal in which the accepted manuscript is to be published (or was published) is required
• Digital Object Identifier (DOI) - Digital Object Identifier (DOI) - Provide if available. If provided, you may then select "Auto Populate Metadata" which will automatically fill in journal information (e.g., journal name, volume, etc.). A Digital Object Identifier (DOI) is a unique character string assigned by a registration agency (such as CrossRef) and used to uniquely identify an object such as an electronic document and provide a persistent link to its location on the Internet. If a DOI exists, you may enter the complete DOI for this STI Product. All DOI numbers begin with a 10 and contain a prefix and a suffix separated by a slash. The prefix is a unique number of four or more digits assigned to organizations; the suffix is assigned by the publisher and was designed to be flexible with publisher identification standards; e.g., a valid format is 10.xxxxxxxxxxxxx/yyyyyyyyyyyyy. See CrossRef.Org [exit federal site] for more information.
• Volume
• Issue
• "Serial identifier" such as ISSN
• Page range
• Journal-associated conference information

Provide the title that appears on the accepted manuscript.

A digital object identifier (DOI) is a unique persistent identifier that references a digital object. DOIs can be assigned to written documents in digital form such as journal articles and other reports as well as data sets. DOIs facilitate the citation and discovery of these digital objects. For example, DOIs in cited references promote reference linking practices and the reuse of information.

For journal articles, publishers will assign a DOI, usually when the article is accepted for publication. If you have an assigned DOI for your submission, you will be able to auto-populate some of the required metadata, including title, author, and publication date. DOIs in cited references promote reference linking practices and the reuse of information.

For data sets that are part of a larger repository, a DOI may be assigned by the repository as part of its referencing schema.

For data that are not assigned a DOI by a repository or other authority, authors may request a DOI from OSTI through the DataID service.

All DOIs begin with 10 and contain a prefix and a suffix separated by a slash. 10 is the directory indicator identifying the string of characters as a DOI. The prefix is a unique number of four or more digits that identify the member organization (for example, the journal or data repository); the suffix is a set of characters that uniquely defines the digital object for which the DOI is assigned.

Example: 10.15121/1136724
10 = indicator that this string of characters is a DOI
15121 = the prefix identifying the member organization (of the registration agency)
1136724 = the suffix created by the member organization to represent a specific object

Enter the publication date in either mm/dd/yyyy format (example: 01/01/2014) or yyyy (example: 2013). If you use the yyyy format, also enter the time period (use the drop-down menu to input additional date information).

After entering last name, first name, and middle name or initial in the specified blanks, you may also enter the primary author/creator's email address, his or her ORCID number, and his or her affiliation in the remaining three fields of the author section.

• You may add as many additional authors as needed by clicking the "Add Author" button.
• You may change the order of author names by clicking the appropriate "Move" button.
• You may edit the author details by clicking the appropriate "Edit" button.
• If you wish to delete an author's name that you have already entered, click the "Remove" button.

Note that organization names or names of collaborations should not be entered into the author fields. Collaboration names and names of contributing organizations are entered into the Contributor Organizations field.

The name of a Research/Project Collaboration, if applicable, should be entered in this field, not in the author field. Contributor organizations are not authors' affiliations, the originating research organization, nor the funding/sponsor organization. They are, instead, any company, institution, or organization to which the submitter wishes to provide recognition and which clearly does not fit into any of the other organization fields. Examples of possible contributor organizations that a submitter may want to list (in addition to listing a collaboration name) include:

• An external organization that provided significant review of the research product.
• An organization that provided site management but was not directly involved in the research/experiment itself.
• An organization that collected data to provide to the originating research organization.
• A data center or repository that is not listed as the originating research organization.

This is a free text field and can hold multiple organizations names. Each different organization should be separated by a semi-colon followed by a space.

This field is optional for AMs but can be used to provide a unique identifier that research organization or author placed on the AM itself.

Suggested format is: use DOE, an acronym that identifies the awardee/recipient organization, and the final five to seven characters from your contract or grant number.

Example: For award #AC02-01FE11111, with Yale University, the report number would be: DOE-YALE-11111 or DOE-YALE-FE11111. If more than one STI product is to be submitted, you may use a suffix to identify them individually, e.g., DOE-YALE-11111-1; DOE-YALE-11111-2; DOE-YALE-11111-3

Select the name of the specific DOE program office that provided the project funding, from the list provided (e.g., USDOE Office of Science (SC) Basic Energy Sciences (BES)). For projects funded by more than one program office, indicate all sources of the DOE funding in descending order of dollar amount of funding appropriated. You may also input additional funding agencies in the textbox. Separate multiple program offices or funding agencies with a semicolon and a space. If you do not know the sponsoring DOE program office, select “USDOE”.

You must provide a clear, concise, and publicly releasable English language executive summary of the information contained in the accepted manuscript, written in terms understandable by an educated layperson. The length should be no more than 5,000 characters. To fill this field, you can cut and paste from any word processing file.

Select one or more categories from the list provided. Select them in order of relevance to the project described in the product. You can review the list of subject category descriptions on the Authorities page.

These are words or phrases that describe the project as summarized in the article. Keywords aide in the online search and discovery of information about the project. More than one keyword may be entered; separate multiple keywords with a semicolon and a space.

Please provide citations for supplementary datasets or other items published with the journal article you are submitting. You may also provide a citation for any other directly-supporting item for technical reports, conference literature, etc. Or, see the Related Identifiers/DOIs field below.

Referencing other documents, other datasets, or software applications that relate to the document you are submitting allows the user of the information to follow these vital links and to better understand the scope of your research. You may add DOIs to cross-reference these other items. If you do not have a DOI for one of the items you wish to relate to your document, please put the citation information for that item in the Related Document field. Note that you may find assigned DOIs for DOE technical reports in OSTI.GOV.

This Related Identifier/DOIs field also allows you, for each DOI you reference, to choose a controlled vocabulary term that "explains" the type of relationship between the DOI you enter and the document you are submitting. For additional information about the Related Identifiers controlled vocabulary see the DataCite Metadata Schema 4.3 Documentation in Table 9 on pages 46-51.

Since by definition an accepted manuscript will appear in a publicly available scholarly journal, the appropriate category to select should be "Unlimited Announcement" - The unrestricted, unlimited distribution of the product will be made publicly available. The government assumes no liability for disclosure of such data. "UNL" is therefore the only value that can be selected. You will also be required to certify that only appropriate information is contained in the product (see "Certifications").

Provide the organization or individual(s) name(s) with corresponding contact information who will serve as the point of contact for DOE if there are questions about the content of the STI product.

For accepted manuscripts, the medium will be an "Electronic Document".

For Accepted Manuscript of Journal Article, there are three certifications that you are required to indicate.

1. The award recipient is responsible for ensuring that content of the accepted manuscript is suitable for public release. Therefore, you must self-certify that it does not contain limited rights data (proprietary data), classified information, protected PII, information subject to export control classification, or other information not subject to release.
2. You must also certify that the accepted manuscript being provided is not the published version of the article (i.e., that it is not a copyrighted reprint of the published article in the journal�s format) and that you understand that DOE Policy calls for the manuscript to be submitted after peer-review and acceptance, but before final formatting by the publisher.
3. You must also certify that, in any Publication and Copyright Agreement made with the journal publisher, rights have been retained to deposit the accepted manuscript with DOE.

For Accepted Manuscripts, you have two options as described below. Indicate in the appropriate fields which way you are providing the accepted manuscript.

1. Provide a persistent link (e.g., a URL or PURL) that is publicly accessible for the full text of the accepted manuscript. (NOTE: If the general public cannot access the manuscript at this location, then you must use option 2.)
   
   OR
2. Upload the full text of the accepted manuscript.

Provide additional information indicated for selected option. For option 1, provide the URL or PURL that will link directly to the specific document. Note: it must be accessible to a member of the general public. For option 2, upload the file by selecting the "Browse" button to locate the file on your computer. Valid file formats are: Adobe Portable Document Format (.PDF) or MS Word (.DOC) only. Before you upload the document, you must certify (in "Certifications" above) that the document being uploaded has been reviewed for, and does not contain, any information not subject to release, such as Protected PII.

The award number must be input accurately first in order to complete and submit the AN 241.3. The format should be either (1) two alphabetic characters and seven digits (for DOE awards granted since 2007), or (2) two alphabetic characters, two numeric characters, a dash, two-digit year, two alphabetic characters, and a five digit number (for awards granted prior to 2007).
Examples: SC0001234; EE0005432; NT0009876; or FG02-03ER83715; FG52-06NA27489; FC07-99ID55444; and AC02-96CH12345.

Examples of other identifying numbers that submitters may want to include are:

• Non-DOE contract numbers (Please do not include these non-DOE contract numbers in the DOE Award/Contract Number field. That field is validated and the record will be rejected if the grant/award/contract number is not a DOE one).
• The number assigned by arXiv.org to an author's posting of a paper (arXiv: 1501.00003)
• Any identifying number that may have meaning or retrieval utility to a particular segment of the anticipated user population (in any format). This may include the numbers assigned by a university or domain area repository.

Note that these other identifying numbers do not typically fit more specific identifier fields available for input, i.e. fields such as product/report number, R&D project IDs, etc. Note also that multiple identifiers may be input here. A semi-colon and a space must be used to separate each identifier from the next one following it.

Enter the Award Digital Object Identifier (DOI) under which work or time was provided. An Award DOI is assigned to awards, contracts, equipment, facilities, grants, prizes, salary awards, and/or training grants. If the research object was produced under multiple awards given by multiple organizations, additional Award DOIs may be entered. Multiple Award DOIs are to be entered using the + to create a new entry. DOIs follow the format: 10.XXXX/XXXXX.

Note: Award DOIs are different than DOIs assigned to the research object currently being announced (submitted) to OSTI. DOIs for the research object may have been assigned by publishers or a repository. If a DOI for a research object has not already been assigned from another source, OSTI may assign a DOI.

Provide the name and location of the organization that performed the research or issued the Conference/Event Paper, Presentation, or Proceedings. More than one may be provided. Separate multiples with a semicolon and a space.

For conference items (workshop, seminar, symposium, lecture, or similar event), select "Conference" from the drop-down menu.

Select the appropriate subtype, either (1) Conference Paper (2) Conference Proceedings (3) Conference Presentation or (4) Conference Poster.

• Conference Paper - a paper presented at a conference
• Conference Proceedings - the compilation of a group of papers from a conference
• Conference Presentation - a recording (provide URL) or slides of an oral presentation given at a conference
• Conference Poster - the presentation of research information in the form of a paper poster displayed at a conference

Provide the title that appears on the conference item itself, including volume, edition, and similar information if applicable.

A digital object identifier (DOI) is a unique persistent identifier that references a digital object and provides long-term access; DOIs remain stable even if the underlying address or URL for the content changes. DOIs for conference papers and proceedings may be provided by the publisher and will always begin with 10.XXXX.

Note that these types will open additional fields on the AN 241.3 because they require additional values be selected as well, including:

• Conference Information (required information, i.e., location, place, and date)
• Conference-associated journal information: Journal name, volume, issue, serial identifier, and page range.

Enter the date of the product in mm/dd/yyyy (example: 01/01/2014) or yyyy (example: 2013). If you use the yyyy format, use the drop-down menu to input additional date information.

After entering last name, first name, and middle name or initial in the specified blanks, you may also enter the primary author/creator's email address, his or her ORCID number, and his or her affiliation in the remaining three fields of the author section.

• You may add as many additional authors as needed by clicking the "Add Author" button.
• You may change the order of author names by clicking the appropriate "Move" button.
• You may edit the author details by clicking the appropriate "Edit" button.
• If you wish to delete an author's name that you have already entered, click the "Remove" button.

Note that organization names or names of collaborations should not be entered into the author fields. Collaboration names and names of contributing organizations are entered into the Contributor Organizations field.

The name of a Research/Project Collaboration, if applicable, should be entered in this field, not in the author field. Contributor organizations are not authors' affiliations, the originating research organization, nor the funding/sponsor organization. They are, instead, any company, institution, or organization to which the submitter wishes to provide recognition and which clearly does not fit into any of the other organization fields. Examples of possible contributor organizations that a submitter may want to list (in addition to listing a collaboration name) include:

• An external organization that provided significant review of the research product.
• An organization that provided site management but was not directly involved in the research/experiment itself.
• An organization that collected data to provide to the originating research organization.
• A data center or repository that is not listed as the originating research organization.

This is a free text field and can hold multiple organizations names. Each different organization should be separated by a semi-colon followed by a space.

This is a unique identifier that you create and place on the paper, presentation or proceedings.

Use DOE, an acronym that identifies the awardee/recipient organization, and the final five to seven characters from your contract or grant number. Example: For award #AC02-01FE11111, with Yale University, the report number would be: DOE-YALE-11111 or DOE-YALE-FE11111. If more than one STI product is to be submitted, you may use a suffix to identify them individually.

Example:
Final report: DOE-YALE-11111-1
Conference paper: DOE-YALE-11111-2
Presentation: DOE-YALE-11111-3

Select the names of the specific DOE program office that provided the funding from the list provided (e.g., USDOE Office of Science (SC) Basic Energy Sciences (BES)). For projects funded by more than one program office, indicate all sources of the DOE funding in descending order of dollar amount of funding appropriated. Other funding agencies may also be indicated by inserting funder name(s) in the textbox. Separate multiple program offices or funding agencies with a semicolon and a space. If you do not know the sponsoring DOE program office, select USDOE.

Provide a clear, concise, and publicly releasable English language executive summary of the information contained in the conference product, written in terms understandable by an educated layperson. The length should be no more than 5,000 characters. To fill this field, you can cut and paste from any word processing file.

Select one or more categories from the list provided. Select them in order of relevance to the project described in the product. You can review the list of subject category descriptions on the Authorities page.

These are words or phrases that describe the content of this product. More than one keyword may be entered; separate multiple keywords with a semicolon and a space.

Please provide citations for supplementary datasets or other items published with the journal article you are submitting. You may also provide a citation for any other directly-supporting item for technical reports, conference literature, etc. Or, see the Related Identifiers/DOIs field below.

Referencing other documents, other datasets, or software applications that relate to the document you are submitting allows the user of the information to follow these vital links and to better understand the scope of your research. You may add DOIs to cross-reference these other items. If you do not have a DOI for one of the items you wish to relate to your document, please put the citation information for that item in the Related Document field. Note that you may find assigned DOIs for DOE technical reports in OSTI.GOV.

This Related Identifier/DOIs field also allows you, for each DOI you reference, to choose a controlled vocabulary term that "explains" the type of relationship between the DOI you enter and the document you are submitting. For additional information about the Related Identifiers controlled vocabulary see the DataCite Metadata Schema 4.3 Documentation in Table 9 on pages 46-51.

For conference papers/presentations, because the information has already been delivered in a public setting and thus has been publicly released, the distribution category should be "Unlimited Announcement." It is the responsibility of the recipient to ensure that the information was appropriate for release.

For conference proceedings that have been prepared under terms of an award, the recipient must indicate the distribution category and provide self-certification (see "Certifications" section).

• "Unlimited Announcement" - The unrestricted, unlimited distribution of the product will be made publicly available. The government assumes no liability for disclosure of such data.
• Copyrighted Material - A copyright restriction on part or all of the contents of the STI product may affect the reproduction and distribution of the product by DOE/OSTI. Any restriction as retained in the award document must be specified.
• Controlled Unclassified Information (CUI) - (enter specific or basic categories/dissemination controls)*
• Small Business Innovation Research (SBIR) Data - If this is selected, indicate phase (Phase I or II or Phase III). Specify the release date which should be no more than four years from the date that the STI product was provided by DOE to OSTI.
• Small Business Technology Transfer (STTR) Data - If this is selected, indicate phase (Phase I or II or Phase III). Specify the release date which should be no more than four years from the date that the STI product was provided by DOE to OSTI.
• Security Sensitive Information
• Protected Data - You must also select CRADA or cite the data clause paragraph in your award document which allows trade secret like protection (e.g. Energy Policy Act (EPAct), clean coal, electric vehicles, steel initiative, etc.). Then, specify the release date which must be no more than five years.
• Patentable Material - Provide all applicable patent information.
• Program-Determined Official Use Only

* For Controlled Unclassified Information (CUI), enter the basic or specified categories along with any limited dissemination controls. The best practice is to enter these using the CUI banner markings on the document. Examples include: "CUI//EXPT" "CUI//NNPI//FEDCON" "CUI//SP-EXPT".

Provide the organization or individual(s) name(s) with corresponding contact information that will serve as the point of contact for any questions DOE may have about the content of the STI product.

The medium will depend on whether it is a conference paper, a conference presentation, a conference poster, or conference proceedings. For conference papers or posters, the medium will be “electronic document.” Then provide the format of the document in the Transmission section.

For conference presentations, which are “Audiovisual” medium, indicate the format as either PPT format for a presentation that will be uploaded, or, if a video posted on publicly accessible website, provide the unique URL that links directly to the video or audiovisual STI product. For a video, the URL is required information. Additional information such as format, file type, and run time may be filled in.

For conference proceedings, select the medium “Electronic Document” and then indicate the file format in the Transmission section.

For papers/presentations, you must self-certify that the item described in the notice has already been presented in a public setting during a conference or similar meeting and therefore has been publicly released and that the content is suitable for public release.

For conference proceedings that are electronically uploaded to DOE via E-Link, you must self-certify at the time of submission that the proceedings do not contain any of this type information: limited rights data (proprietary data), classified information, protected PII, information subject to export control classification, or other information not subject to release.

Indicate the format if the conference paper is 'Electronic Document' or if a conference presentation is PPT, then upload the corresponding file format. Select the 'Browse' button to locate the file on your computer. Valid file formats are: Adobe Portable Document Format (.PDF) or MS Word (.DOC) only for electronic documents or PPT for audiovisual. Other audiovisual formats for conference presentations, such as for videos, cannot be uploaded but can be announced by providing a unique URL location. Before you upload the document, you must certify that the document being uploaded has been reviewed for, and does not contain, any information not subject to release, such as Protected PII.