U.S. Department of Energy
Scientific and Technical Information Program

241.1 Web Service Instructions (PDF 960.27 KB) The images below are previews of the AN 241.1 Web Service Instructions PDF. Page 1 Figure 277401: Announcement Notice 241.1 Web Service for STI - Page 1 Announcement Notice 241.1 Web Service for STI - Page 1 ... OSTI's Announcement Notice 241.1Web Service for STIVersion 6.3, August 2020Contents1.0 About1.1 Announcement Notice 241.11.2 OSTI's AN 241.1 Web Service2.0 Using the AN 241.1 Web Service2.1 Credentials and Authentication2.2 POST (Create or Update) and GET (Retrieve)2.3 Response and Notifications2.4 Transmitting Full-Text Products to OSTI3.0 AN 241.1 Web Service Metadata3.1 AN 241.1 Required Fields3.2 Required Fields (Cont):  Access Limitation(s) Attributes and Values3.3 AN 241.1 Optional Fields4.0 AppendicesA.1 Related IdentifiersA.2 Examples of XML 241.1 Metadata RecordsNew in this revision:•  Editorial updates 2411 Webservice Updated Template-01.jpg Printer-friendly version Page 2 Figure 277402: Announcement Notice 241.1 Web Service for STI - Page 2 Announcement Notice 241.1 Web Service for STI - Page 2 1.0   About1.1 Announcement Notice 241.1Announcement Notice (AN) 241.1 provides the Office of Scientific and Technical Information (OSTI) with the information needed to identify, process, announce and disseminate the results of work funded by the Department of Energy (DOE) or performed in DOE facilities (see DOE Order 241.1B (link is external)).   When submitted, the AN 241.1 set of metadata creates a citation/record that is processed by E-Link and then transferred into the appropriate databases for access (see search tools Search Tools).DOE sites can manually submit AN 241.1 metadata a single record at a time through a web interface on E-Link (www.osti.gov/elink) (link is external).  The AN 241.1 Web Service provides an additional option for submitting DOE's scientific and technical (STI) products to OSTI for dissemination.  The STI product will be a full text document, such as a technical report, thesis or dissertation, book, journal literature, conference literature, or a program document.  It could also be a multimedia file.AN 241.1 metadata and products submitted to OSTI, whether through a manual process or an automated process, are subject to the same requirements.  A designated Releasing Official must ensure that each record has been reviewed for any content that would make it appropriate for release to the public.  The Releasing Official is also responsible to ensure that full text documents posted on site or transmitted to OSTI do not contain Personally Identifiable Information (PII) (see https://www.osti.gov/elink/faq.jsp#PII (link is external)).  Use of the AN 241.1 Web Service does not remove these responsibilities from the Releasing Official.STI from DOE's research and development activities is disseminated through OSTI's databases such as OSTI.GOV, through multiagency databases such as Science.gov (link is external), through global databases such as WorldWideScience.org (link is external), and through arrangements with major Internet search engines such as Google. 1.2 OSTI's AN 241.1 Web ServiceOSTI's AN 241.1 Web Service allows a submitting site to send AN 241.1 information in a completely automated manner.  Metadata is generated at the submitting site per the programming set-up by the site's IT developers and POSTed as an output file to OSTI.  The schedule for the POST operation may be multiple times daily, once daily, once weekly, etc. 2411 Web Service for STI Version 6.3 August 2020-02.jpg Printer-friendly version Page 3 Figure 277403: Announcement Notice 241.1 Web Service for STI - Page 3 Announcement Notice 241.1 Web Service for STI - Page 3 Records with unlimited access status and those with limited access can both be transmitted through the secure AN 241.1 Web Service.  DOE organizations may establish a URL link to the unclassified, unlimited STI products on their websites and send the URL in the metadata or they may transmit the full text product to OSTI.  All limited access (Controlled Unclassified Information or CUI) full text are required to be transmitted to OSTI and cannot be posted on the site's public web.The AN 241.1 Web Service provides the ability to submit new Announcement records, edit/update records, or retrieve a record for review.  A user manipulates a record by performing HTTP operations on the web service URL and providing XML metadata.  The POST command/request allows a submitter to create or edit/update AN 241.1 records.  The GET command/request allows a submitter to retrieve a record for review.  Submitters must coordinate with OSTI and submit records to a test environment before POSTing their first XML file for dissemination.  The URL for Test E-Link is https://www.osti.gov/elinktest/2411api.   OSTI's production web service for announcing STI is available at https://www.osti.gov/elink/2411api. 2.0 Using the AN 241.1 Web Service2.1 Credentials and AuthenticationAN 241.1 transactions require an active E-Link user account.  To request personal access to E-Link and obtain an active account, visit https://www.osti.gov/elink/register.jsp.  To obtain an account for your client server to connect to OSTI's web service, contact E-Link Product Manager, Kim Buckner (bucknerk@osti.gov).  Your web service account will be given a login name and password for Test E-Link.  After testing is completed, you will be provided a login and password for production E-Link, as well as a separate password for your site's SFTP.The AN 241.1 Web Service supports HTTP Basic authentication over SSL.  With this method, the client connects to the HTTPS URL for either Test E-Link or, when testing is complete, for production E-Link. The POST and GET verb commands will pass along the standard Authentication HTTP header (base64 encoding). 2411 Webservice Updated Template-03.jpg Printer-friendly version Page 4 Figure 277404: Announcement Notice 241.1 Web Service for STI - Page 4 Announcement Notice 241.1 Web Service for STI - Page 4 2.2 POST (Create or Update) and GET (Retrieve) [Client to OSTI]After successful authentication, the input body of the POST or GET request is read as an XML document, parsed, and loaded appropriately into E-Link.  HTML status codes (200=OK, 401=Unauthorized, 500=System error, etc.) and an XML response, which includes certain metadata fields, are returned by OSTI's server to the client server to notify of either success in loading the record or failure.  The POST command/request is most often used to submit metadata for a new record that is being provided to OSTI for the first time, but it can also be used to edit or update an existing record that has previously been submitted.  Submitters must "tell" the system which of the two activities they intend for a record.  The OSTI ID is key to this.  How and why is explained below:When POSTING to an existing record in order to update it, the OSTI ID must be included in the XML record.  The updated information will then overwrite the previously submitted information.   If the OSTI ID is not included when trying to POST to an existing record, the Web Service believes you are wanting to create rather than update.  It will create a duplicate record, but with a new, different OSTI ID.  This situation always requires correction by logging into E-Link manually and manually deleting the duplicate record.Metadata can be retrieved for any record previously submitted by your organization by using a GET request and supplying the OSTI ID as a parameter in the request.  Authentication is required and is handled in the same fashion as a Create/Update command.  The requested OSTI ID returns that specific XML record.  A GET operation will not update a record, however.                2.3 Response and Notifications [OSTI to Client]OSTI's server makes an immediate response when the client-side server sends a POST or a GET request.  The primary goal of the response is two-fold:  to let the client server "know" if it connected successfully and to provide a status message about the record that was POSTed or retrieved.  The status says SUCCESS if the record correctly transmitted and the metadata loaded into E-Link. The status says FAILURE if the record was unable to load for any reason.  The FAILURE response includes a message indicating the error or problem that kept the record from loading.  Errors leading to a FAILURE response occur when a required metadata field is missing, when a site URL cannot be validated by the automated validation process, when a value is too long for the field it must load into, etc.Note that the successful record returns its newly assigned OSTI ID.  The response for the failed record will not have an OSTI ID since IDs cannot be assigned to records that never actually make it into E-Link. 2411 Webservice Updated Template-04.jpg Printer-friendly version Page 5 Figure 277405: Announcement Notice 241.1 Web Service for STI - Page 5 Announcement Notice 241.1 Web Service for STI - Page 5 E-Link also generates an email containing the SUCCESS or FAILURE information about each submitted record.  The site will be asked to provide to OSTI the names of the people to whom these automated emails will be sent. It is the submitting site's responsibility to review the results of the web service transactions and to correct, then resubmit those records that initially failed.2.4 Transmitting Full-Text Products to OSTIA secure FTP directory is set-up at OSTI for each site utilizing the AN 241.1 Web Service.  A site cannot access any other site's SFTP directory...only the one assigned specifically to it.  The process for providing both a metadata record and its corresponding full text product is as follows: Site submits an XML metadata record to OSTI's E-Link system via the AN 241.1 Web Service. The AN 241.1 Web Service notifies the submitting site that the XML record loaded successfully into E-Link and includes the newly assigned OSTI ID in the notification message.  Notification goes out via server-to-server messaging and via an email to a site's designated distribution list.A "script" written by the site's (client) software developers adds the new OSTI ID to the site's (client) database (records publishing system, review and approval system, etc.).The "script" also reaches out to rename the corresponding full-text product, changing its file name from whatever it was originally to the new OSTI ID number.  Only the number is used as the name, not any part of the OSTI ID text that sometimes prefixes the number.    Example: a file named DOELAB-27834.pdf would be renamed 114073.pdf (if OSTI ID 114073 had been assigned to the corresponding metadata XML record).Another automated command in the submitting site's (client) programming then transmits the file named 114073.pdf to the site's assigned SFTP directory.The metadata record was submitted first and has been waiting in E-Link.  It will not complete processing until E-Link recognizes that a document with the same OSTI ID is now present in the site's assigned SFTP directory. If, on the first night after the XML record's submittal, E-Link does not detect a matching full-text product, the record stays in its "Submitted" state in E-Link.  It will stay that way, as many days as it takes, until the full text product arrives from the site.When E-Link recognizes that a full text product has arrived in the site's (client) directory and that the product has an OSTI ID matching a metadata record from the same site code, a siphon process takes place.  The process attaches the product to the record. 2411 Webservice Updated Template-05.jpg Printer-friendly version Page 6 Figure 277406: Announcement Notice 241.1 Web Service for STI - Page 6 Announcement Notice 241.1 Web Service for STI - Page 6 When E-Link recognizes that a full text product has arrived in the site's (client) directory and that the product has an OSTI ID matching a metadata record from the same site code, a siphon process takes place.  The process attaches the product to the record.After the "marriage," the record and its full text go through a "transfer" process that makes them available in the appropriate database.  CUI records and documents are transferred to Science Research Connection (SRC) (see www.osti.gov/src), a password-protected system available only to DOE and DOE contractors.  Unlimited records will be sent to OSTI.gov, Pages, or other databases.3.0 AN 241.1 Web Service Metadata3.1 AN 241.1 Required FieldsThe following is a list of the required fields for the AN 241.1 Web Service.  These fields are also designated by an asterisk (*).  Records submitted without required fields will fail to load into E-Link for processing.  The other fields available for your use are optional, though some, such as the Abstract/Description, are highly encouraged. NOTE:  The OSTI ID is a required field for all POST requests where the intent is to edit or update records.  The GET request must also include the OSTI ID and will allow retrieval of a record previously submitted by your site.REQUIRED Field NameXML Tag NameAdditional Information1OSTI ID+The OSTI ID is required in all requests intended to edit or update existing records. When POSTing new records to OSTI, no tag is needed in the XML.  E-Link automatically assigns an OSTI ID to each new record successfully submitted.2Record Status*      These tags are required to inform the system of the status of the record being submitted. For new records, only the is needed. For revised metadata or revised/replaced full text products (revprod/), the OSTI ID must be included as an attribute.  See format below.  2411 Webservice Updated Template-06.jpg Printer-friendly version Page 7 Figure 277407: Announcement Notice 241.1 Web Service for STI - Page 7 Announcement Notice 241.1 Web Service for STI - Page 7 Record Status Attributes are needed for revdata tag and revprod tag.(Note the single quote marks around the attribute value) 3Site Code*The site code value is assigned by OSTI to the submitting site and must be present in each XML record.4Product Type*The values are upper case letters. Only one code can be placed in this field. Depending on the code, additional information may be needed. The allowed values are:  CodeDefinitionTRTechnical Report or Workshop Report COConference/Event Paper, Proceedings, or Presentation If product type = CO, the following field is also needed:  Conference Information = Include conference name,conference location, and conference inclusive datesInclude name of conference, location, and inclusive dates. Product Sub-Type CodesCodeDefinitionAConference PaperRConference Presentation (may receive a DOI)OConference Poster (may receive a DOI)PConference Proceedings Example Conference Sub-Type       CO      2411 Webservice Updated Template-07.jpg Printer-friendly version Page 8 Figure 277408: Announcement Notice 241.1 Web Service for STI - Page 8 Announcement Notice 241.1 Web Service for STI - Page 8    FSFactsheet JAJournal Article If product type = JA, the following field is also required:Journal Type data  Allowed values are AC (for announcement citation only), FT (author's early manuscript), or AM (Accepted Manuscript, meaning the final author's version after peer review comments are incorporated).  When FT or AM are the values, the medium code used will be ED (see later in this table). NOTE the requirement to make the Accepted Manuscript available to OSTI andto place AM as the value in data applies to journal articles published October 1, 2014 or later.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .These fields are also needed for JA records:Journal Name       Journal Volume    Journal Issue        Journal Serial ID Page Range            NOTEProvide the page range as p. xx-xx.  If the journal uses article numbers, that value may also be used in this fieldIf you know the DOI that the publisher has assigned to the journal article, please include it also.  The tag for the DOI field is   TDThesis or DissertationPDProgram DocumentBBook/Monograph 2411 Webservice Updated Template-08.jpg Printer-friendly version Page 9 Figure 277409: Announcement Notice 241.1 Web Service for STI - Page 9 Announcement Notice 241.1 Web Service for STI - Page 9    If product type = B, the following field is also needed:Publisher Information Include name of publisher and city, state, and country if other than U.S.ARAccomplishment ReportPPatent If product type = P, the following field is also needed:Patent Assignee 5STI Product Title*Full title of the STI Product.  Include version number, if applicable.6USE THE 6.1 FORMAT BELOW FOR AUTHOR INFORMATION WHEN POSSIBLE6.1Author(s) Preferred format for authors and required in some cases. Note:  Names of collaborations do not go in the author fields. (See Contributing Orgs in section  3.3 AN 241.1 Optional Fields below)      Use the block of tags if you are including ORCID number with any of the authors in the submitted record.When the submitted record has the block of tags, ALL author names MUST be broken out into this block format (even if only one of the names has an accompanying ORCID).NOTE the middle name, email, affiliation, and ORCID parts of the authors "block" format may be left blank if no value is available." 6.2Author(s)* Note:  Names of collaborations do not go in the author fields. (See Contributing Orgs in section  3.3 AN 241.1 Optional Fields below)  Format is Last Name, First Name, MISeparate multiple authors with a semi-colon followed by a space.  Affiliations may be place in square brackets after each author's name.Doe, John [National Tech, Inc.]; Smith, Nancy [Brookhaven National Laboratory] 2411 Webservice Updated Template-09.jpg Printer-friendly version Page 10 Figure 277410: Announcement Notice 241.1 Web Service for STI - Page 10 Announcement Notice 241.1 Web Service for STI - Page 10 7Report/Product Number(s)*  A value in this field is required but the word, None, may be used if no valid report number or product number exists.TR and TD product types should always have valid report numbers.8DOE Contract Number(s)* Use the format of the contract "as is," but remove any preceding "DE". If multiple contract numbers apply, separate with a semi-colon followed by a space.9Originating ResearchOrganization*   For DOE...

DOE Data ID Services Manual (PDF 2.07 MB) The images below are previews of the DOE Data ID Services Manual PDF (DOE Data ID Services Manual.pdf). AN241.6 Web Service Instructions Title Page - Preview Figure 277725: DOE Data ID Services Title Page DOE Data ID Services Title ...Page DOE Data ID ServiceAnnouncing and Registering DOE's Datasets via Announcement Notice (AN) 241.6Manual Version 7.2, January 2021 DOE Data ID Service Manual v7-2 Jan2021-01.png Printer-friendly version AN241.6 Web Service Instructions Table of Contents - Preview Figure 277726: DOE Data ID Services 6 1 02 DOE Data ID Services 6 1 02 Contents DOE Data ID Service Background........................................................................................................... 1 1. About E-Link and AN 241.6................................................................................................................ 1 1.1 Why should I get a DOI?.............................................................................................................. 4 1.2 General Requirements................................................................................................................ 5 1.3 Understanding Key Components.................................................................................................. 5 1.4 The Digital Object Identifier (DOI)................................................................................................. 6 1.5 The Landing Page....................................................................................................................... 8 2. Submitting Metadata to Obtain a DOI................................................................................................ 9 2.1 Scientific Research Datasets 241.6 Web Submission Interface - Single Metadata Record.................... 9 2.2 Application Programming Interface (API) - Multiple Metadata Records.......................................... 10 3. Reserving a DOI............................................................................................................................. 12 4. Editing DOI Metadata..................................................................................................................... 16 5. Searching for a DOI........................................................................................................................ 18 6. Deleting a DOI............................................................................................................................... 20 7. Using Related Identifiers................................................................................................................. 21 8. Versioning: Assigning DOIs to Data Object Versions............................................................................ 30 9. Creating a Unique DOI Infix............................................................................................................. 31 Appendix: DOE Data ID Service API Metadata....................................................................................... 33 Appendix: 241.6 Web Submission Interface Submission Example............................................................. 40 Appendix: Frequently Asked Questions (FAQs)...................................................................................... 45 Appendix: Release Notes.................................................................................................................... 52 DOE Data ID Service Manual v7-2 Jan2021-02.png Printer-friendly version AN241.6 Web Service Instructions Page 1 - Preview Figure 277727: DOE Data ID Services 6 1 03 DOE Data ID Services 6 1 03 DOE Data ID Service BackgroundIn 2011, OSTI joined DataCite to facilitate citing, accessing, and reusing publicly available scientific research datasets produced by DOE-funded researchers. DataCite, an international non-profit organization that registers digital object identifiers (DOIs) with the International DOI Foundation, develops and maintains the metadata schema tailored for describing scientific data and software, and provides infrastructure for allocating DOI prefixes, registering DOIs and associated metadata, and managing DOIs. The U.S. Department of Energy (DOE) Office of Scientific and Technical Information (OSTI), through the DOE Data ID Service, assigns DOIs to datasets announced by DOE and its contractor and grantee researchers and registers the DOIs with DataCite to aid in citation, discovery, retrieval, and reuse. OSTI assigns and registers DOIs for datasets for DOE researchers as a free service to enhance the Department's management of this important resource. OSTI refers to individual data centers at DOE-funded organizations as data clients, and sets up data client accounts to allow for tailored customization of features, which will be detailed in later sections of this manual. 1. About E-Link and AN 241.6 DOE OSTI develops and maintains E-Link, an electronic submission tool for DOE-funded scientific and technical information (STI). E-Link provides Announcement Notices (ANs) or submission tools to submit various types of STI and associated metadata. The E-Link1 AN 241.6, the Scientific Research Datasets AN, allows for the metadata needed to identify/announce datasets resulting from work funded by DOE to be provided to OSTI. The submitted metadata allows the assignment of DOIs to datasets through the DOE Data ID Service. This value-added step of assigning a DOI facilitates visibility, ensures long-term preservation, (re)usability.1 E-Link facilitates the electronic submittal of STI between DOE and its client community including researchers, reviewers, research administrators, and others doing business with DOE. STI deliverables provided to DOE through E-Link are announced, as appropriate, on web products maintained by OSTI, which provide free and convenient public access to full text and bibliographic data of products resulting from DOE-funded research. DOE Data ID Service Manual v7-2 Jan2021-03.png Printer-friendly version AN241.6 Web Service Instructions Page 2 - Preview Figure 277728: DOE Data ID Services 6 1 04 DOE Data ID Services 6 1 04 and supports better linkages between DOE's published research results and the underlying data.The DOE Data ID Service offers three options to submit metadata for DOIs:1. Scientific Research Datasets 241.6 Web Submission Interface - Single metadata recordThe 241.6 Web Submission Interface for manual entry of metadata is a good option for low-volume data clients. Researchers at DOE national laboratories should contact their site's STI Manager2 to arrange for manual submittal.2. Application Programming Interface (API) - Multiple metadata recordsOSTI offers an Application Programming Interface (API) for POST (submit) and GET (retrieval) functions to a communication channel called an endpoint.Testing in the API is required prior to receiving a production account. Please contact OSTI: DOEDataID@osti.gov to set up a test account with credentials.Test E-Link Endpoint: https://www.osti.gov/elinktest/2416apiProduction E-Link Endpoint: https://www.osti.gov/elink/2416apiFor more information about the API, please click here: E-Link 241.6 API Documentation2 Each DOE national Laboratory has a designated point of contact for coordinating submissions of scientific and technical information (STI) to OSTI. DOE Data ID Service Manual v7-2 Jan2021-04.png Printer-friendly version AN241.6 Web Service Instructions Page 3 - Preview Figure 277729: DOE Data ID Services 6 1 05 DOE Data ID Services 6 1 05 Financial Assistance recipients (Grantees) can submit metadata for their individual datasets without log-in credentials using the Scientific Research Datasets (AN 241.6) Submission Interface found at: https://www.osti.gov/elink/2416-submission.jspThe workflow below explains the entire submission workflow from submission to E-Link to display in OSTI's output search products.Dataset Record Submission WorkflowThe user can submit a dataset metadata record to OSTI either through the 241.6 Web Submission Interface (either by logging in for DOE sites or using the Financial Assistance Step-by-Step version for grantees) or the Application Programming Interface (API). If successful, the metadata is submitted to E-Link, OSTI's ingest system. OSTI then sends the metadata record to DataCite to register the DOI. After the record has been processed in E-Link, it will be displayed in both OSTI.GOV and DOE Data Explorer. DOE Data ID Service Manual v7-2 Jan2021-05.png Printer-friendly version AN241.6 Web Service Instructions Page 4 - Preview Figure 277730: DOE Data ID Services 6 1 06 DOE Data ID Services 6 1 06 1.1 Why should I get a DOI?DOIs allow people to more easily discover research and technology objects, access them, and reuse them for verification of the original experiment or to produce new results with the latest methods.DOIs facilitate linkages among outputs - published articles, patents, technical reports, data, software, and other research objects.DOIs are easy to cite in a standardized way to give inventors, authors, or creators the proper attribution.DOIs can be assigned to any digital entity a user wishes to persistently identify, primarily for sharing with an interested user community or managing as intellectual property.DOI links are "persistent". That is, DOIs resolve to a URL that can be updated even if domain names change and/or the domain naming system itself is replaced. This characteristic can be helpful to agencies as they often undergo reorganizations and renaming. A DOI can ensure the long-term integrity of identifiers in these situations.DOIs are cross-disciplinary - used in the humanities, social sciences, physical sciences and in a number of communities that frequently interact with the scholarly literature, such as non-governmental organizations (NGOs), intergovernmental organizations (IGOs), patent systems, and standards bodies.3DOIs help make data FAIR (Findable, Accessible, Interoperable, Reusable). Specifically, DOIs help make data findable, and OSTI makes data accessible, interoperable, and reusable. See the FAIR Data Principles for a more detailed explanation of FAIR. 3 This has been slightly modified from Crossref's persistent identifiers webpage at https://www.crossref.org/blog/global-persistent-identifiers-for-grants-awards-and-facilities/ DOE Data ID Service Manual v7-2 Jan2021-06.png Printer-friendly version AN241.6 Web Service Instructions Page 5 - Preview Figure 277731: DOE Data ID Services 6 1 07 DOE Data ID Services 6 1 07 1.2 General RequirementsGeneral requirements have been established for data registration. The submitter must:Provide the required metadata to enable basic, bibliographic citationHave the authority to make the data public, as the data owner, PI, or other designated submitterGuarantee the persistence of registered dataEnsuring that data are stored and managed for indefinite access and usabilityMaintaining and updating all landing pages/URLs associated with the DOIOSTI DOES NOT CURRENTLY PROVIDE A REPOSITORY TO HOST DATASETS.1.3 Understanding Key ComponentsGranularity is the level of depth represented by the data. More granularity means a very focused detail, the most precision. Less granularity is a summary view of data and transactions.Determining the level at which DOIs are assigned to data is one of the first steps in planning data DOI registration.DOIs can be assigned at varying granularity. The granularity of data can be dependent upon the type of data. Subject matter expertise and knowledge of how researchers use data can help determine the appropriate level of granularity to assign the DOI, as well as intention for reuse, versioning, and how the data is used within journal articles, technical reports, or patents.DOIs can be assigned for a variety of different forms of data, such as instruments, sensor data, time-sensitive data (for example, monthly datasets for a location, with new DOIs each month), supercomputer runtime data, individual samples, grouped samples, supplemental data DOE Data ID Service Manual v7-2 Jan2021-07.png Printer-friendly version AN241.6 Web Service Instructions Page 6 - Preview Figure 277732: DOE Data ID Services 6 1 08 DOE Data ID Services 6 1 08 to a journal article, computer models/simulations, photographs, graphics, interactive resources, and more.1.4 The Digital Object Identifier (DOI)A DataCite DOI consists of a prefix, infix, and suffix. Each OSTI data client receives a numeric prefix from DataCite, which is specific to that data client. A DOI prefix begins with 10.XXXX, where XXXX is a series of numbers. (See Figure Below)Directory: 10Registrant Prefix: XXXXOptional Intelligence: InfixSuffix: OSTI IDThe Infix is optional and can be incorporated by the data client/submitter. The infix can add intelligence to the DOI by incorporating project, user facility, or other specific identification. The infix must contain 3-50 characters. Characters may not be spaces or forward slashes (/) The suffix is assigned by OSTI and is the OSTI ID. Every STI record processed through OSTI receives an OSTI ID Once a DOI is registered, it cannot change, but the URL/landing page associated with the DOI can change or be updated as it is part of the metadata associated DOE Data ID Service Manual v7-2 Jan2021-08.png Printer-friendly version AN241.6 Web Service Instructions Page 7 - Preview Figure 277733: DOE Data ID Services 6 1 09 DOE Data ID Services 6 1 09 with the DOI. DOIs are meant to be persistent, which means submitting organizations should manage and update metadata, including landing pages/URLs as needed for the DOI to properly take the user to the correct page.This can be accomplished by entering a DOI at: https://dx.doi.org/:Or by clicking on the hyperlinked DOI in dataset metadata records found at OSTI.GOV and DOE Data Explorer:The browser will take the user to a web page (URL) associated with that DOI. DOE Data ID Service Manual v7-2 Jan2021-09.png Printer-friendly version AN241.6 Web Service Instructions Page 8 - Preview Figure 277734: DOE Data ID Services 6 1 10 DOE Data ID Services 6 1 10 1.5 The Landing PageA DOI points/resolves to a landing page or URL, which provides information about and access to the dataset. A landing page should contain the following information:Full citation metadata of the data object (including the DOI)Access informationLinks to software needed to open, view, download or analyze the dataUpdate and version informationContact informationBelow is an example of a landing page:The image on this page presents a possible example of a landing page. A table on the left side of the page lists the information about the dataset enumerated prevously. Another section describes the dataset and its relationship to other products. In this case, the dataset was used to generate illustrations for another article. DOE Data ID Service Manual v7-2 Jan2021-10.png Printer-friendly version AN241.6 Web Service Instructions Page 9 - Preview Figure 277735: DOE Data ID Services 6 1 11 DOE Data ID Services 6 1 11 2. Submitting Metadata to Obtain a DOI2.1 Scientific Research Datasets 241.6 Web Submission Interface- Single Metadata RecordThe 241.6 Web Submission Interface for manual entry of metadata is a good option for low volume data clients. Researchers from DOE national laboratories should contact their site's STI Manager to arrange for manual submittal.If a user plans to exclusively submit through the 241.6 Web Submission Interface, then the user does not need to go through Test E-Link first. Work with the Data Liaison by emailing DOEDataID@osti.gov, who will set up a meeting to go through each step of manually submitting.OSTI prepares a new data client for the 241.6 Web Submission Interface by:Creating a site code in E-LinkAssigning a unique DOI prefix to a user's submissionsCreating the account at DataCiteCreating login credentials on Production E-LinkFinancial Assistance recipients (Grantees) can submit metadata for their individual datasets without log-in credentials using the step-by-step version of the Scientific Research Datasets (AN 241.6) Submission Interface found at: https://www.osti.gov/elink/2416-submission.jsp.For more information about manual submission, please refer to the E-Link 241.6 Web Submission Interface Instructions.If users have any questions about the submission process, please contact DOEDataID@osti.gov and a member of the OSTI Data Team will answer as soon as possible. DOE Data ID Service Manual v7-2 Jan2021-11.png Printer-friendly version AN241.6 Web Service Instructions Page 10 - Preview Figure 277736: DOE Data ID Services 6 1 12 DOE Data ID Services 6 1 12 2.2 Application Programming Interface (API)- Multiple Metadata RecordsOSTI offers an Application Programming Interface (API) for POST (submit) and GET (retrieval) functions.Establishing Test CredentialsTo use the production API, users must first submit through Test E-Link before being able to submit in production. In Test E-Link, users can freely practice submissions without the records being shown in OSTI's search products. The Data Ingest Liaison Librarian will work with the user on checking submissions for errors and giving recommendations for improving metadata quality. Once OSTI determines the user has enough experience and a high success rate of submissions, the user will be given production credentials. Before being ready to test submissions to OSTI, the user must obtain the following by contacting DOEDataID@osti.gov: Site Code - The site code associates the user with their metadata and records by associating credentials to those who wish to receive notification emails concerning the account. These automated emails are sent after each submission and inform the user of the new OSTI ID and the DOI of the submitted record.DOI Prefix -The DOI prefix, beginning with 10., is unique to the site code. Every DOI assigned to the user's datasets by the DOE Data ID Service will begin with this prefix.E-Link Account - Finally, OSTI establishes a Test E-Link account. The E-Link API requires the user to include the credentials in the header of the server's transmission file. DOE Data ID Service Manual v7-2 Jan2021-12.png Printer-friendly version AN241.6 Web Service Instructions Page 11 - Preview Figure 277737: DOE Data ID Services 6 1 13 DOE Data ID Services 6 1 13 Confirming Test Credentials - New Client/SubmitterConfirm that the Test credentials are working by:Go to Test E-Link/TEST 241.6 web service: https://www.osti.gov/elinktest/2416apiA...

The AN 241.5 provides OSTI with information required to appropriately identify, process, and/or announce, and disseminate the scientific and technical information (STI) results of classified or unclassified controlled nuclear information (UCNI) work funded by DOE/NNSA or performed in DOE/NNSA facili...ties. Classified and UCNI STI products are submitted securely by originating sites via the Classified E-Link product on the Enterprise Secure Network (ESN). Use the AN 241.5 Fillable Form (PDF 135.50 KB) file and AN 241.5 Instructions as references for submitting classified and UCNI STI to OSTI.  The online version of AN 241.5 and detailed help are available to authorized users of the Classified E-Link product on ESN.For more information regarding classified and UCNI STI submissions, contact OSTI's Classification Officer, David Gottholm, at (865) 576-2623 or gottholmd@osti.gov or your Classified STIP Site Liaison.

The AN 241.6 provides to Office of Scientific and Technical Information (OSTI) the metadata needed to identify/announce datasets resulting from work funded by or performed in DOE facilities. The submitted information also allows OSTI, via the DOE Data ID Service, to assign Digital Object Identifiers... (DOIs) to datasets and register them with DataCite. This value-added step facilitates visibility, helps ensure long-term preservation, and supports better linkage between DOE's published research results and the underlying data.  Visit DOE Data ID Services for more Information. 241.6 Web Services (API) Instructions

The AN 241.3 is required for submission of scientific and technical information (STI) to OSTI in order to ensure proper handling, announcement, and dissemination in accordance with DOE statutory responsibilities. There are basic requirements for metadata fields, however, other optional/non-mandator...y data fields should be included in the AN when possible. The information included in the 241.3 provides information required to appropriately identify, process, and/or announce and disseminate the results of work funded by DOE. It is utilized by DOE Financial Assistance Recipients/Non-Major Contractors and submitted with each STI report or product. An AN 241.3 should be submitted using E-Link (link is external). Required Metadata Elements Specific metadata requirements for Technical Reports, Journal Article - Accepted Manuscript, and Conference Paper/Presentations or Proceedings Required Fields Technical Report Journal Article - Accepted Manuscript Con­fer­ence Papers, Pre­sen­ta­tions, or Pro­ceed­ings DOE Award/Contract Number * Requiredis required for Technical Report * Requiredis required for Journal Article - Accepted Manuscript * Requiredis required for Conference Paper/Presentations or Proceedings Other Identifying Number(s) is optional for Technical Report is optional for Journal Article - Accepted Manuscript is optional for Conference Paper/Presentations or Proceedings Recipient/Contractor Organization (link is external) * Requiredis required for Technical Report * Requiredis required for Journal Article - Accepted Manuscript * Requiredis required for Conference Paper/Presentations or Proceedings STI Product Type * Requiredis required for Technical Report * Requiredis required for Journal Article - Accepted Manuscript * Requiredis required for Conference Paper/Presentations or Proceedings STI Product Title * Requiredis required for Technical Report * Requiredis required for Journal Article - Accepted Manuscript * Requiredis required for Conference Paper/Presentations or Proceedings STI Product Date * Requiredis required for Technical Report is optional for Journal Article - Accepted Manuscript * Requiredis required for Conference Paper/Presentations or Proceedings Author(s) * Requiredis required for Technical Report * Requiredis required for Journal Article - Accepted Manuscript * Requiredis required for Conference Paper/Presentations or Proceedings Contributor Organiza­tion(s) is optional for Technical Report is optional for Journal Article - Accepted Manuscript is optional for Conference Paper/Presentations or Proceedings Report/Product Number * Requiredis required for Technical Report is optional for Journal Article - Accepted Manuscript * Requiredis required for Conference Paper/Presentations or Proceedings Sponsoring DOE Program Office (link is external) * Requiredis required for Technical Report * Requiredis required for Journal Article - Accepted Manuscript * Requiredis required for Conference Paper/Presentations or Proceedings Description/Abstract * Requiredis required for Technical Report * Requiredis required for Journal Article - Accepted Manuscript * Requiredis required for Conference Paper/Presentations or Proceedings Subject Categories (link is external) is optional for Technical Report is optional for Journal Article - Accepted Manuscript is optional for Conference Paper/Presentations or Proceedings Keywords is optional for Technical Report is optional for Journal Article - Accepted Manuscript is optional for Conference Paper/Presentations or Proceedings Intellectual Property/Distribution Limitations * Requiredis required for Technical Report * Requiredis required for Journal Article - Accepted Manuscript * Requiredis required for Conference Paper/Presentations or Proceedings Recipient/Contractor Point of Contact * Requiredis required for Technical Report * Requiredis required for Journal Article - Accepted Manuscript * Requiredis required for Conference Paper/Presentations or Proceedings Media/Format Information * Requiredis required for Technical Report * Requiredis required for Journal Article - Accepted Manuscript * Required*is required for Conference Paper/Presentations or Proceedings Certification(s) * Requiredis required for Technical Report * Requiredis required for Journal Article - Accepted Manuscript * Requiredis required for Conference Paper/Presentations or Proceedings Transmission Information * Requiredis required for Technical Report * Requiredis required for Journal Article - Accepted Manuscript * Requiredis required for Conference Paper/Presentations or Proceedings Releasing Official * Requiredis required for Technical Report * Requiredis required for Journal Article - Accepted Manuscript * Requiredis required for Conference Paper/Presentations or Proceedings Submitter Responsibilities DO NOT encrypt or password-protect STI products.

AN 241.1 Web Version InstructionsMust have an E-Link user account prior to using this method.Identify STI product type to determine whether to provide announcement notice only applicable to copyrighted STI or both announcement notice and full-text document for all full-text documents.Review full-tex...t document for sensitivities listed on AN 241.1 under "Distribution/Access Limitations" and protected personally identifiable information (PII).If copyrighted journal article, conference paper/proceedings, or book, submit only the announcement notice and provide the availability of the publication.If unclassified unlimited full-text document, submit both the announcement notice and the full text.If unclassified unlimited full text and your site is hosting on a public server, provide the announcement notice including the unique uniform resource locator (URL).If protected distribution/access limitation full-text document, submit both the announcement notice and the full text. E-Link provides Secure Socket Layer (SSL) protection.The electronic format is determined based on whether the full-text document is being uploaded or a unique URL is provided.If full-text document is being uploaded, the electronic format options are Searchable PDF or Non-Searchable PDF.If URL is provided, the electronic format options are Searchable PDF or HTML.Ensure all required fields indicated in red and with an asterisk are completed prior to AN 241.1 submission.The STI Releasing Official should:Prior to the submission of the announcement notice and full-text document thru E-Link, verify that all necessary reviews have been completed.Verify that the STI product should be released by OSTI in accordance with the intellectual property/distribution limitation marked on the AN 241.1 and submit.Note:For Unclassified Controlled Nuclear Information, please refer to AN 241.5All *Required Fields must be completed before a document can be attached in Part II.*Site CodeSelect your site code from the drop-down list.*STI Product TypeSelect one product type. Note that these types will open additional fields on the AN 241.1 because they require additional values be selected.Technical/Workshop Report - Identify the type of technical report provided.Conference/Event Paper or Presentation/Proceedings - Provide all available conference information (title, location, and dates, as well as sponsoring organization). An agenda alone is not sufficient for announcement. Also provide any associated journal information for this conference, if applicable.Journal Article - Select one of the following and provide all available journal article information (entering the DOI, if known, will auto-populate many of the metadata fields):Announcement Citation Only - If providing journal citation data, but full-text article is not being uploaded.ManuscriptFinal, Peer-Reviewed Accepted ManuscriptProgram DocumentS&T Accomplishment ReportBook/MonographPatentThesis/DissertationFactsheet*STI Product TitleProvide the title including volume, edition, and similar information.*Author(s)The preferred method for submitting author names is to use the "Enter Each Author" option. This option is formatted to provide the best search, retrieval, and validation of author names and accompanying information, including an author's ORCID number. See About the Addition of ORCID Numbers to E-Link (link is external) for additional 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 plus (+) button.You may change the order of author names by selecting the appropriate "author block" and dragging it.If you wish to delete an author's name that you have already entered, click and drag that author entry to the bottom of the list, then click the minus (-) 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.If you need to use a copy-and-paste method to provide author names, you may use the "Enter All Authors" option. E-Link's parser will then attempt to parse your text string into the designated fields to enable accurate search and retrieval.If using the "Enter All Authors" option:Enter last name, first name, middle initial and additional qualifiers separated by commas. Example: Smith, Richard, T.More than one author may be provided; separate multiple entries with a semicolon and a space. Example: Smith, Richard T.; Jones, John W.Author affiliations should be inside parentheses. Example: Smith, Richard, T. (Office of Scientific and Technical Information)If an email address is entered in the "Enter All Authors" field, it must be preceded with "email:" Example: Jones, John W. email: jjones@osti.gov (Office of Scientific and Technical Information). Note that email addresses will not display in public databases; they are for administrative purposes only.If an author does not exist, the word "None" should be entered.Contributor OrganizationsThe 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.*Report/Product Number(s)This is a unique identifier that you create.Use DOE, an acronym that identifies the awardee, 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 the contract or grant requires more than one technical report, you may use a suffix to identify them.Example:1st report: DOE-YALE-11111-12nd report: DOE-YALE-11111-23rd report: DOE-YALE-11111-3"None" may also be entered in this field when a report number is not appropriate, i.e. when the submission is a journal article.*DOE Contract Number(s)The format should be: two alphabetic characters, two numeric characters, a dash, two-digit year, two alphabetic characters, and a five digit number; or, two alphabetic characters and seven digits.Examples: FG11-96EK82252, FC25-96EU50430, AC02-94RS12345, and SC0001234.R&D Project ID(s)Enter the unique and permanent Project ID assigned to the project itself by the Operations Office, DOE Program Office, laboratory, or other installation to identify a particular research project. Multiples may be provided; separate multiple entries with a semicolon and a space. Sample formats: P/ORNL-2533; TTP/RL439005Work Proposal Number(s), Revision NumberOptional information. Any format and multiple entries are accepted.Work Authorization Number(s), Revision NumberOptional information. Any format and multiple entries are accepted.Other Identifying Number(s)Examples of other identifying numbers that submitters may want to include are:The number assigned by arXiv.org to an author's posting of a paper (arXiv: 1501.00003)The accession number from the submitting site's database (45029 or any format)Any identifying number that may have meaning or retrieval utility to a particular segment of the anticipated user population (any format)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, contract 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.*Originating Research OrganizationProvide the name and location of the organization that performed the research or issued the scientific and technical report/product. More than one organization may be provided; separate multiples with a semicolon and a space. Example: Pacific Northwest National Laboratory, Richland, WA*Publication Issue DateEnter the publication date in mm/dd/yyyy (example: 01/01/2001) or yyyy (example: 1995). If you use the yyyy format, use the drop-down menu to input additional date information.LanguageSelect the name of the additional language(s) in which the information product is written other than English. If language is not provided by the originating organization, the word "English" is the default value.Country of OriginSelect the country of publication. Default value is "United States".*Sponsoring OrganizationSelect the DOE program office (e.g., Office of Science or SC) providing the funding from the list provided. 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. Separate multiple program offices with a semicolon and a space. If you do not know the sponsoring DOE program office, select USDOE.Publisher Name and LocationThis is a required field for Book product type or if different than the Originating Research Organization that issued the document for dissemination.Availability - Refer requests to [if applicable]. For example: A URL with additional help or contact information about this document. This is a required field if the Publisher is the source of availability.Subject CategoriesSelect one or more categories from the list provided. Select them in order of relevance to the product. You can review the list of subject category descriptions on the Authorities Elink page.KeywordsThese 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.Description/AbstractProvide a clear, concise, and publicly releasable English language summary of the information content. The length should be no more than 5,000 characters. To fill this field, you can cut and paste from any word processing file.Related Document InformationInformation useful to include in published announcement record which is not suited for any other field on this notice.*Distribution LimitationsUnrestricted DistributionUnlimited Announcement - The unrestricted, unlimited distribution of the product will be made publicly available. The government assumes no liability for disclosure of such data.OpenNet - STI products declassified and made available for public release will also be announced on the Department's OpenNet Database in accordance with the Department's Openness Initiative and DOE Order 475.2B "Identifying Classified Information."Selecting OpenNet as the distribution requires additional information:Accession Number - For use in indicating additional sources of a document. This number may be used by OpenNet users when requesting a document. The Accession Number is a unique identifier of up to 15 alphanumeric characters only (A-Z, a-z, or 0-9). The transmitting field or program office is responsible for ensuring that the number is unique within its jurisdiction. Document Location - If an electronic copy of the document does not accompany the metadata, this should identify additional sources where the public may go to obtain a copy of the document. At a minimum, this entry would contain a point of contact and enough additional information to enable a user to order a document (e.g., address, phone number, fax number, e-mail address, etc.). Multiple location entries may be provided; separate multiple locations with a semicolon and a space. Field Office Acronym - Use the appropriate acronym provided in OpenNet Declassified Information Database Data Input.Declassification Date - Provide the declassification date for any document that has been declassified and publicly released.Declassification Status - Required for all documents being entered into OpenNet. Check 'Sanitized' for documents with portions deleted for privacy or security reasons and enter a declassification date if the sanitized document is also a declassified document. Check 'Never classified' for documents that have never been classified and are being made publicly available.  The other two options are 'Declassified' and 'Unknown'.OpenNet Document Categories - For information products which will be included in the OpenNet Database, provide the appropriate two level subject categories based on the list in OpenNet Declassified Information Database Data Input Specifications, revised December 15, 1994. The list of OpenNet document categories is also available on the ELink Authories page.Distribution Limitations - Controlled Unclassified Information (CUI): (Note:  Recommendations to restrict access to STI products must have a legal basis or be accompanied by written programmatic guidance.  For questions concerning current laws and guidance, refer to the STIP website or contact at stip@osti.gov)  Copyrighted Material w. Restrictions - 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.Official Use Only - Limitations/Controlled Unclassified InformationOfficial Use Only - OUOExport Controlled Information (e.g. under ITAR/EAR) (FOIA-Exemption 3) - OUOSecurity Sensitive Information (FOIA Exemption 7) - OUOProtected Data - CRADA or OTHER (specify below) - OUOWhen Protected Data is selected, 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.Patent Pending (FOIA Exemption 3) - OUOLimited Rights Data (Proprietary/Trade Secret) (FOIA Exemption 4) - OUOProgram-Determined Official Use Only - (enter exemption number below) - OUOProvide a reference to specific guidance or attach a copy of the specific guidance.Other InformationSpecify other criteria that would necessitate limiting access or restrict announcement of this product.*STI Product Media/Format and Transmission and LocationEnsure the STI product/final technical report does not contain protected Personally Identifiable Information (PII) before you upload the document. Protected PII is defined as an individual's first name or first initial and last name in combination with any one or more of types of information, including, but not limited to, 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, etcSelect one of the medium options provided. Each selection will open additional fields for more information.If "Electronic Document" is selected, first indicate whether the STI document is either posted online, in which case the AN 241.1 record will link to it, or if it is being transmitted to OSTI via the "Upload File" option.For uploaded documents, indicate file format and other requested information. Searchable PDF is the required format for technical reports. Ensure that the document does not contain PII.For documents posted at the originating site, provide the unique URL that links directly to the first page of the STI product. This is required information.If "Audiovisual Material" is selected (typically applicable to conference/event product type), provide the unique URL that links directly to the video, webinar, or audiovisual STI product. This is required information. (Please contact OSTI at (865) 576-6784 if AV material needs to be transmitted to OSTI instead of posted at the submitting site.)Indicate the type of file, such as Audio File, Video File with sound, or Video File w/o sound.Provide the file format of the audiovisual product. Note that the preferred formats are those which can be content-indexed by OSTI's ScienceCinema product. Check the STIP website for detailed information about these formats and what OSTI can and cannot do with them.Provide the length of the video or other audiovisual material as "run time." Example: run time: 01:22:17. This example shows that the run time of the product is one hour, 22 minutes, and 17 seconds. Please use this standard way of reporting run time.When an announcement record only is submitted, select "Announcement Notice Only."Location: Digital Object IdentifierOSTI assigns DOIs to technical reports or obtains correct DOIs for journal articles from CrossRef. If you already know the DOI of the product you are submitting and wish to provide it yourself, you may do so here.*Releasing OfficialThis information is required. Provide the Released By (Name), Date (mm/dd/yyyy), Email, and Phone of the releasing official. You must also select the box verifying that Personally Identifiable Information was not detected in the uploaded STI product.Timing OutThe notice has a time limit of thirty minutes, so if you take more than an hour to fill out the notice, you will receive a timeout message. If you receive a timeout message, you can select the "Back" button on your browser, and resubmit the notice.SubmitWhen the notice is complete, select the "Submit" button. The system will perform several more validations on the fields that you entered. Any errors will be listed at this time, which you can correct. You will find the errors precede each part of the notice in red text, highlighted in yellow. If the information is complete and correct, you will move to a screen with a summary of your input. The summary screen should be printed for your records. 

INSTRUCTIONS FOR Technical/Workshop Report Part I: STI PRODUCT DESCRIPTION *DOE Award/Contract Number 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). Multiples may be entered but MUST be separated with a semicolon and a space. Examples: SC0001234, EE0005432, NT0009876, or FG02-03ER83715, FG52-06NA27489, FC07-99ID55444, and AC02-96CH12345. Other Identifying Number(s) 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 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) The accession number from the submitting site's database (45029 or any format) Any identifying number that may have meaning or retrieval utility to a particular segment of the anticipated user population (any format) 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. *Recipient/Contractor Organization 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. *STI Product Type 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. Final Technical Report - Select this if your award calls for the submission of a "Final" scientific/technical report. Other - Specify type of STI product not listed in the menu of choices. Examples: thesis, patent, book. NOTE: Use the DOE AN 241.4 for software products, not the AN 241.3. *STI Product Title Provide the title that appears on the report or product, including volume, edition, and similar information if applicable. *STI Product Date 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. *Author(s) After entering last name, first name, and middle name or initial in the specified blanks, you may also enter the primary author/creators email address, his or her ORCID number, and his or her affiliation in the remaining three fields of the author section. See About the Addition of ORCID Numbers to E-Link (link is external) for additional information. You may add as many additional authors as needed by clicking the "Add New Author" button. You may change the order of author names by selecting the appropriate author block and dragging it. If you wish to delete an author's name that you have already entered, click and drag that author entry to the bottom of the list, then click the Delete Last Author 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 Organization(s) field. Contributor Organization(s) The name of a Research/Project Collaboration, if applicable, should be entered in this field, not in the author field.  Contributor organizations are not author 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. *Report/Product Number 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 *Sponsoring DOE Program Office Select the name of the specific DOE program office that provided funding for the project described in the STI report/product, 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. Separate multiple program offices with a semicolon and a space. If other agencies also provided funding, you may identify additional funders by inserting funder name(s) in the textbox. Separate multiple names with a semicolon and a space.  If you do not know the sponsoring DOE program office, you may select "USDOE". *Description/Abstract 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. Subject Categories Select one or more categories from the list provided. Select them in order of relevance to the project as described in the report/product. You can review the list of subject category descriptions on the Authorities (link is external) page. Keywords These are words or phrases that describe the project topics as summarized in this report/product. Keywords aid 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. *Intellectual Property/Distribution Limitations 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. 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. 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 *Recipient/Contractor Point of Contact 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. Part II: STI PRODUCT MEDIA/FORMAT AND TRANSMISSION *Media/Format Information 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. *Certification(s) 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. *Transmission 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. Timing Out The notice has a time limit of thirty (30) minutes. After 30 minutes of inactivity (if you take more than 30 minutes to interactively fill out the notice), then you will receive a timeout message. If you receive a timeout message, you can select the "Back" button on your browser, and resubmit the notice. Print You are advised to print a copy for your records. However, note that you will also have an opportunity to print a summary after you select Submit. Please review carefully and print your information before submitting the announcement notice.  You will not be able to view or edit information once the notice has successfully completed submission. Submit When the notice is complete, select the Submit button. If the information is complete (i.e., all required fields are provided and certain validations have been made), you will move to a screen with a summary of your input. This summary screen should be printed for your records. If there are errors or missing data, you will have an opportunity to correct those and then select Submit again. If there are no errors, the process is finished. Upon successful submission of the announcement notice, an email will automatically be sent to your contracting officer notifying them of your submission. *Releasing Official This information is required. Provide the Released By (Name), Date (mm/dd/yyyy), Email, and Phone of the releasing official. You must also select the box verifying that Personally Identifiable Information was not detected in the uploaded STI product. INSTRUCTIONS for Journal Article: Accepted Manuscript (The Accepted Manuscript of a Journal Article) Part I: STI PRODUCT DESCRIPTION *DOE Award/Contract Number 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. Other Identifying Number(s) 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 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) The accession number from the submitting site's database (45029 or any format) Any identifying number that may have meaning or retrieval utility to a particular segment of the anticipated user population (any format) 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. *Recipient/Contractor Organization 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. *STI Product Type Select "Journal Article-Accepted Manuscript" 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) - 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 (link is external) for more information. Volume Issue Serial identifier such as ISSN Page range Journal-associated conference information *STI Product Title Provide the title that appears on the accepted manuscript. Publication/Issue Date 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). *Author(s) 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. See About the Addition of ORCID Numbers to E-Link (link is external) for additional information. You may add as many additional authors as needed by clicking the Add New Author button. You may change the order of author names by selecting the appropriate "author block" and dragging it. If you wish to delete an author's name that you have already entered, click and drag that author entry to the bottom of the list, then click the Delete Last Author 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. Contributor Organization(s) The name of a Research/Project Collaboration, if applicable, should be entered in this field, not in the author field. Contributor organizations are not author 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. Report/Product Number This field is optional for Accepted Manuscripts but can be used to provide a unique identifier that research organization or author placed on the Accepted Manuscripts 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 *Sponsoring DOE Program Office 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". *Description/Abstract 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. Subject Categories Select one or more categories from the list provided. Select them in order of relevance to the project described in the article. You can review the list of subject category descriptions on the Authorities (link is external) page. Keywords These are words or phrases that describe the project as summarized in the article. Keywords aid 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. *Intellectual Property/Distribution Limitations 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. Unlimited 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 also "Certifications" section). *Recipient/Contractor Point of Contact 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. Part II: STI PRODUCT MEDIA/FORMAT AND TRANSMISSION *Media/Format Information For accepted manuscripts, the medium will be an Electronic Document. *Certifications For Journal Article-Accepted Manuscript, there are three certifications that you are required to indicate. 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. 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 journals 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. 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. *Transmission Information For Accepted Manuscripts, you have two options as described below. Indicate in the appropriate fields which way you are providing the accepted manuscript. 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 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. Timing Out The notice has a time limit of thirty (30) minutes. After 30 minutes of inactivity (if you take more than 30 minutes to interactively fill out the notice), you will receive a timeout message. If you receive a timeout message, you can select the "Back" button on your browser, and resubmit the notice. Print You are advised to print a copy for your records. However, note that you will also have an opportunity to print after you select Submit and get a summary. Please review carefully and print your information before submitting the announcement notice.  You will not be able to view or edit information once the notice has successfully completed submission. Submit When the notice is complete, select the Submit button. If the information is complete (i.e., all required fields provided and certain validations made), you will move to a screen with a summary of your input. This summary screen should be printed for your records. If there are errors or missing data, you will have an opportunity to correct those and then select Submit again. If there are no errors, the process is finished. Upon successful submission of the announcement notice, an email will automatically be sent to your contracting officer notifying them of your submission. *Releasing Official This information is required. Provide the Released By (Name), Date (mm/dd/yyyy), Email, and Phone of the releasing official. You must also select the box verifying that Personally Identifiable Information was not detected in the uploaded STI product. INSTRUCTIONS for Conference Papers/Presentations or Proceedings Part I: STI PRODUCT DESCRIPTION *DOE Award/Contract Number 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. Other Identifying Number(s) 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 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) The accession number from the submitting site's database (45029 or any format) Any identifying number that may have meaning or retrieval utility to a particular segment of the anticipated user population (any format) 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. *Recipient/Contractor Organization Provide the name and location of the organization that performed the research or issued the conference paper/presentation or proceedings. More than one may be provided. Separate multiples with a semicolon and a space. *STI Product Type For conference items, select "Conference Paper/Presentation or Proceedings" from the drop-down menu. Then select the appropriate subtype, either (1) Conference Paper/Presentation if an individual conference paper or conference presentation is being submitted or announced or (2) Conference Proceedings if the entire proceedings is being submitted as one compiled document, such as for a workshop. Conference Paper/Presentation Conference Proceedings 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. *STI Product Title Provide the title that appears on the conference item itself, including volume, edition, and similar information if applicable. *STI Product Date 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. *Author(s) 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. See About the Addition of ORCID Numbers to E-Link (link is external) for additional information. You may add as many additional authors as needed by clicking the Add New Author button You may change the order of author names by selecting the appropriate "author block" and dragging it. If you wish to delete an author's name that you have already entered, click and drag that author entry to the bottom of the list, then click the "Delete Last Author" 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. Contributor Organization(s) The name of a Research/Project Collaboration, if applicable, should be entered in this field, not in the author field. Contributor organizations are not author 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. *Report/Product Number(s) 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 *Sponsoring DOE Program Office 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. *Description/Abstract 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. Subject Categories 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 (link is external) page. Keywords 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. *Intellectual Property/Distribution Limitations 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 also "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. 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 *Recipient/Contractor Point of Contact 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. Part II: STI PRODUCT MEDIA/FORMAT AND TRANSMISSION *Media/Format Information The medium will depend on whether it is a conference paper, a conference presentation, or conference proceedings. For conference papers, 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. *Certifications For conference 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 of information:  limited rights data (proprietary data), classified information, protected PII, information subject to export control classification, or other information not subject to release. *Transmission Information 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. Timing Out The notice has a time limit of thirty (30) minutes. After 30 minutes of inactivity (if you take more than 30 minutes to interactively fill out the notice), you will receive a timeout message. If you receive a timeout message, you can select the "Back" button on your browser, and resubmit the notice. Print You are encouraged to print a copy of the notice for your records. You will also have an opportunity to print a summary after you Submit the item. Please review carefully and print your information before submitting the announcement notice. You will not be able to view or edit information once the notice has successfully completed submission. Submit When the notice is complete, select the "Submit" button. If the information is complete (all required fields provided and certain validations made), you will move to a screen with a summary of your input. The summary screen should be printed for your records. If errors are detected, you will have the opportunity to make corrections and then select Submit again. If no errors are found, that completes the process. You will not be able to retrieve or edit the information after this step. Upon successful submission of the announcement notice for conference proceedings, an email will automatically be sent to your contracting officer notifying them of your submission. *Releasing Official This information is required. Provide the Released By (Name), Date (mm/dd/yyyy), Email, and Phone of the releasing official. You must also select the box verifying that Personally Identifiable Information was not detected in the uploaded STI product. INSTRUCTIONS for Datasets Purpose: Announcement Notice (AN) 241.6 provides to the U.S. Department of Energy (DOE) Office of Scientific and Technical Information (OSTI) metadata needed to identify/announce publicly available datasets resulting from work funded by the U.S. Department of Energy (DOE) or performed in DOE facilities. The information allows OSTI to assign Digital Object Identifiers (DOI) to datasets and register them with DataCite (link is external) as a service to researchers. This value-added step facilitates visibility, helps ensure long-term preservation, and supports better linkage between DOE's published research results and the underlying data. See About OSTI's Data ID Service (link is external) for information about the process by which a DOI is assigned to a dataset and the benefits that result. Then, use this page of instructions to help you as you fill in the AN 241.6 or take a look at the STI Announcement Web Service for 241.6 Data manual if you are interested in a more automated submittal method. Who uses this Notice: DOE, DOE Major Site/Facility Management contractors, multi-program and single-program laboratories, other DOE facilities, and DOE grantees/financial assistance recipients may complete AN 241.6 and submit it with a URL for the publicly available location of the data. Contact Information For questions about DOIs and OSTI's Data ID Service, email DOEDATAID@osti.gov.  For general information or assistance with E-Link, Contact Us. AN 241.6 Metadata Details and Requirements *An asterisk indicates required information. 'Tab' between data fields. The 'enter' key assumes you are attempting to submit the notice before entering all required data. Part I: STI Product Description *Dataset Type - This is a required field. Select one choice from the drop-down list that best describes the dataset's main content. Animations/Simulations - Animations and simulations resulting from runs of computer models or similar software. Figures/Plots - A dataset consisting mainly of data diagrams, graphs and charts, diagrams or schematic drawings. Genome/Genetics Data - Information that is numeric or alpha-numeric in nature (such as gene sequences) or that is a specialized mix of text and non-text information conveying results of genetics/genome research Interactive Data Map(s) - A non-static interface and the GIS data and/or shape files that generate it. Multimedia - An example of a multimedia dataset might be a video of an experiment in progress, where the camera monitors change over a number of hours. Numeric Data - Data primarily expressed with numbers; other content is secondary and supporting. Specialized Mix - This "type" may be used to indicate a dataset made up of content that doesn't fit into one of the other "type" categories. The content of a "specialized mix" dataset could have some of everything in this list, for example, but is clearly focused on data and does not have a "format", such as a technical report that is focused on data would Still Images or Photos - A collection of images or photographs that are produced by a scientific instrument or that convey scientific results of experiments. Scientific images that might constitute a data set could be images of cells or molecules that are typically taken with electron microscopes, 3-D structures of proteins or nanomaterials, images captured during an accelerator run, images from astronomy, etc. *Dataset Title - This is a required field. Enter the title exactly as given on the product itself, including part, version, and similar information. *Author(s) [Creator(s)/Principal Investigator(s)] - This is a required field. Enter the name of the person(s) primarily responsible for the dataset, i.e. the person(s) who should be credited with the content of the dataset. 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 (link is external), and his or her affiliation in the remaining three fields of the author section. Email, ORCID number, and affiliation are optional parts of this required author block. The author email is used by OSTI to send creator(s)/PI(s) the Digital Object Identifier (DOI) for the dataset registered with DataCite. Email addresses will not appear in public databases. 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. Related Resource Enter brief citation information (title, author, identifier) for key publication(s) and technical report(s) that the dataset being announced directly supports. *STI Product Identifiers *Dataset Product Number(s) - This is a required field. An identifying number that has been assigned to the dataset by either the originating/submitting organization or by the organization currently hosting the data. If two different organizations have assigned different numbers to the dataset, both are listed here. They should be separated...

The AN 241.1 is required for providing most of DOE's scientific and technical information (STI) to OSTI. It announces non-classified STI products with the exception of datasets (AN 241.6), DOE CODE, or software (AN 241.4).  The information provided by the AN 241.1 ensures proper handling, announceme...nt, and dissemination in accordance with DOE statutory responsibilities. There are basic requirements for metadata fields; however, other optional/non-mandatory data fields should be included in the AN when possible. AN 241.1 in E-Link (link is external) allows manual entry of metadata to create a single record at a time.  DOE Laboratories also have the option of submitting via API.241.1 Web Services (API) InstructionsRequired Metadata ElementsSite CodeSTI Product TypeTypeJournal NameSTI Product TitleAuthor(s) and Contributor(s)Report/Product Number(s)DOE Contract Number(s)DOE Contract Number(s)Originating Research Organization (link is external)Publication/Issue Date or Publication/Issue YearSponsoring Organization(s) (link is external)Media/Format InformationReleasing OfficialOptional Metadata ElementsDescription/AbstractDigital Object IdentifierOther Identifying Number(s)R&D Project ID(s)Related Document InformationSubject Categories and Keywords (link is external)Work Authorization NumberWork Proposal NumberSubmitter ResponsibilitiesDO NOT encrypt or password-protect STI products.DO inform OSTI when permanently removing STI from your site's publicly accessible server.  DO inform OSTI when your site's publicly accessible server, hosting STI products, changes.DO update E-Link metadata when access limitations change for STI products.DO replace full-text STI via E-Link upload for STI products as appropriate.

Fillable Form for AN 241.5 (PDF 135.50 KB) Instructions for DOE Announcement 241.5 Purpose: Announcement AN 241.5 (electronic or paper) provides the Office of Scientific and Technical Information (OSTI) with information required to appropriately identify, process, and/or announce and disseminate the... results of classified or Unclassified Controlled Nuclear Information (UCNI) work funded by the U.S. Department of Energy (DOE) or performed in DOE facilities. When to use this announcement: Submit this announcement with each scientific and technical information (STI) Product. Electronic submission is the preferred method for submitting the announcement record and STI Product. When submitting electronically, use the electronic version of the announcement and submit via ESN. When submitting in paper, input should be typed or printed, not handwritten. Contact Information: For more information, contact the Classified Program Manager, David Gottholm, at (865) 576-2623 or gottholmd@osti.gov, or contact your Classified STIP Site Liaison, Evelyn Gibson, at (865) 576-2590 or gibsone@osti.gov, or Tammy Spencer, at (865) 576-0256 or spencert@osti.gov. Data Fields and Information about DOE AN 241.5 When submitting in paper, the completed announcement for classified documents must be reviewed by a derivative classifier and marked as required by DOE Directives to indicate if it contains classified information. The completed announcement for UCNI documents must be reviewed by a Reviewing Official. DOE and DOE Contractors DOE, DOE Major Site/Facility Management contractors, multiprogram laboratories, single program laboratories, and other DOE facilities should complete the entire announcement. Submit it as a package with the STI product to OSTI for processing in accordance with the requirements of DOE Order 241.1B, Scientific and Technical Information Management. Reporting that may be required under the terms of the contract but which is not appropriate for transmittal to OSTI includes contract proposals, funding status, routine construction or inventory reports, and similar products. Submit the package to the following as appropriate: How to Address Packages Outer Envelope Inner Envelope For Mail Outer EnvelopeU.S. Department of EnergyOffice of Scientific and TechnicalInformation (OSTI)ATTN: Room 554P.O. Box 62Oak Ridge, TN 37831 USA Inner EnvelopeU.S. Department of EnergyOffice of Scientific and TechnicalInformation (OSTI)ATTN: Room 350 INTENDED RECIPIENTP.O. Box 62Oak Ridge, TN 37831 USA For Shipments Outer EnvelopeU.S. Department of EnergyOffice of Scientific and TechnicalInformation (OSTI)Mail Room 5541 Science.Gov WayOak Ridge, TN 37830 USA Inner EnvelopeN/A Classified submissions must be packaged and receipted in accordance with DOE Directives, and OSTI's classified address verified through SSIMS, as required. OSTI ID - Internal OSTI Identification Number RECORD STATUS (Required) - The record status identifies the announcement record or the STI Product as new or revised.  If the record status is not provided, the record is considered "New." Part I: STI PRODUCT DESCRIPTION STI PRODUCT TYPE (Required) - Select one of the following product types that best describes the product. Technical Report - Documents reporting scientific and technical Information (STI). Conference Paper/Proceedings - Select Paper or Proceedings.  Provide all available conference information (title, location, and dates, as well as sponsoring organization).  An agenda alone is not sufficient for announcement.  Also provide any associated journal information for this conference, if applicable. Journal Article - Provide all available Journal Article information. Software Manual - The software manual that accompanies the software package. Provide the actual software package as a separate announcement (see Computer- Related) or indicate availability. Patent/Patent Application - Provide the date filed, the priority date, and the name of the assignee. Drawing - A visual representation of a physical or conceptual object/process. Please include drawing number and scale. Data - Data may be numeric, graphic, or visual. Collection - This product is composed of an assemblage of information objects co- located with each other that can be represented by a common announcement. Computer-Related - Includes software packages. STI PRODUCT TITLE (Required) - Provide the title exactly as given on the product itself, including part, volume, edition, and similar information.  For progress reports, include the period covered.  Classification level and category (if RD or FRD), and any caveats and/or special markings, if applicable, shall be indicated. AUTHOR(S) (Required) - Enter the name(s) of the person(s) responsible for writing the report, performing the research, or credited with the content of the report. The form of entry is the last name, first name, middle initial. If there are authors from other than the ORIGINATING RESEARCH ORGANIZATION, all authors should be listed, with their affiliation after their name separated by a comma.  The names/affiliations should be separated by semicolons. If an author's name is not identified, the word "None" should be entered.Author(s) E-mail Address(es) - Provide the e-mail address for each author. Multiples may be provided; they should be listed in the same order as the authors (Part 1.C.) and should be separated by a semicolon and a space. STI PRODUCT IDENTIFIERS Report/Product Number(s) (Required) - To assist in providing meaningful search results, it is recommended that every product published by the originating organization be assigned a standard product/report number that contains some unique identifier that can be traced to the site of origin. The report number prefix should be formed using the site acronym followed by a unique suffix.  If there are multiple volumes or parts, additional numbers or letters may also be added to the suffix number. Examples: ORNL-1234-Vol.1; LLNL-9876-Suppl.; WHC-4567- Del.Ver. Contract Number(s) (Required) - Enter the DOE or other contract number(s) exactly as provided in the document. Examples: GSFC0200109DNAS501161, FG11-96EK82252, ACO2-94RS12345. If no contract number, enter None. Other Identifying Number(s) - Additional unique identifying numbers associated with the scientific and technical report/product may be provided (e.g., R&D Project ID). More than one identifying number may be provided. Multiple numbers are separated with a semicolon and a space. ORIGINATING RESEARCH ORGANIZATION (Required) - Provide the name and location of the organization that issued the scientific and technical report/product. For non-reports, e.g., subsections of conferences, journal articles, patents, etc., the organization(s)/author affiliation(s) that performed the research should all be listed here, separated by semicolons. PUBLICATION/ISSUE DATE (Required) - Specify the date the document was published, either in format mm/dd/yyyy (ex: 01/01/2001), or in format mm/yyyy (ex: 01/2001) or yyyy (ex: 1995). LANGUAGE (if not English) - Enter language in which the document was written. COUNTRY OF PUBLICATION (if not United States) - Enter country where document originated. SPONSORING ORGANIZATION - Indicate the name of the DOE Program Office (e.g., Office of Defense Programs) providing the funding for the work described in the STI product. 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.  Separate multiple program offices with a semicolon and a space. If DOE funded the work and no sponsoring DOE Program Office is provided, "DOE" will be the sponsor. (See Sponsoring Organization Authority) PRODUCT ORIGIN - Specify if the document is DOE or Non-DOE sponsored. SUBJECT CATEGORIES - Select one or more categories from the Enterprise Subject Category Authority.  Select them in order of relevance to the intellectual content of the STI product.  (See Subject Category Authority (link is external)) KEYWORDS - These are terms or phrases identifying major concepts in the STI product.  Use of the Database Thesaurus as an authority is preferred.  More than one keyword may be entered; separate multiple keywords with a semicolon and a space. To fill this field, you can cut and paste from any word processing file. DESCRIPTION/ABSTRACT - Provide a clear, concise English language summary of the information content of the STI product. The abstract length should be no more than 5,000 characters. To fill this field, you can cut and paste from any word processing file.  Copying or pasting text from any word processing file should be of the UTF8 character set.  If your text includes any special characters please confirm that no erroneous text was added after the pasting. IS STI PRODUCT ACCOUNTABLE? - If the STI product is accountable, indicate with a "yes", and handle in accordance with procedures specified in the current version of DOE M 470.4-4A, INFORMATION SECURITY. RELATED DOCUMENT INFORMATION - Include any other information about the STI product that might be useful but which is not suited for any other field on this announcement. Part II. STI PRODUCT MEDIA/FORMAT AND TRANSMISSION MEDIA/FORMAT INFORMATION Medium of STI Product is (Required) Select the medium of the product being submitted. Note: If the product is not being submitted, mark "No full text" and submit a PDF file describing location of document. If Electronic Document, file format is Select the file format for the product being submitted. If Other is selected, provide the format. This is a required field if the STI product is electronic full text. Size of STI Product Provide the total number of pages, images or other designation which gives an indication of the physical or electronic size of the STI product (Example: 3 pages, 20 images; 5 Megabytes; 1 CD-ROM). If Computer Medium, Video or Audiovisual Material Indicate the quantity and type of medium (Example: 2 videocassettes, 1 magnetic tape). Indicate the machine with which the medium is compatible, i.e., with which it can be used (Example: VHS; PC-compatible, DVD). Enter any other information that would be helpful to the user of the STI product (Example: programming language, file format, sound, etc.). TRANSMISSION INFORMATION (Classified matter and UCNI submitted electronically must be transmitted via ESN!) (Required) STI Product is being transmitted Select one of these options to indicate how the STI product is being transmitted: Electronically via the Enterprise Secure Network (uploaded) or Via mail or shipment. Electronic Information Product File Name Provide file name of transmitted full- text document. Part III. STI PRODUCT REVIEW/RELEASE INFORMATION (To be completed by Releasing Official) (Required) CLASSIFIED ACCESS LIMITATIONS - Enter complete classification (TOP SECRET not allowed) and caveats information for the Classified STI Product. (See Authorities: Classification Level; Classification Category; Caveats) For legacy documents created before implementation of DOE 452.8, the obsolete Sigma Categories 1-5 and 9-13 previously assigned can be used or the "non-Sigma" designation can be used. [Sigmas 1-5 and 9-13 are considered "non-Sigma" unless Sigma(s) 14, 15, 18, or 20 is indicated.] This field is required for classified submissions.  See Appendix A. Enter the most restrictive Programmatic Approval Authority Category Code for the product. For a full list of C-72 subcodes, contact your Classified STIP Site Liaison. UCNI ACCESS LIMITATIONS - If UCNI, check UCNI STI Product and enter/select any other Caveats that apply to the product such as PROP (proprietary), ECI (Export Controlled Information), OUO (Official Use Only), SBIR (Small Business Innovation Research), etc. OTHER CRITERIA LIMITING ACCESS OR RESTRICTING ANNOUNCEMENT OF THIS PRODUCT -  Any other access limitations or announcement restrictions, such as Program Office instructions, limiting the announcement or dissemination of the STI Product, or other information which would help to clarify the limitations entered in A. or B. above. RELEASING OFFICIAL (Required) - Provide the name and additional information of the site's individual(s) responsible for the appropriate review and release of the STI product. Do not forward this announcement or the STI product until after it has been reviewed and released for announcement. TECHNICAL CONTACT - Provide the organization or individual(s) name with corresponding contact information who will be included in the announcement metadata as the point of contact and will respond to external questions about the content of the STI product. APPENDIX A Programmatic Approval Authority Category Codes (reference DOE/OSTI-3679) C-24      Gas Centrifuge Method of Uranium Isotope Separation C-27      Plutonium Isotope Separation C-29      Uranium Atomic Vapor Laser Isotope Separation C-44c    Nuclear Technology-Production Reactor Engineering and Technology C-52      Gaseous Diffusion Process of Isotope Separation C-57      Tritium Production C-65      Plutonium Production C-68      Safeguards and Security C-72      Weapon Data  (IMPORTANT NOTE: For a full list of C-72 subcodes, contact your Classified STIP Site Liaison.) C-73      Nuclear Weapons Effects C-74      Nuclear Weapon-Related Engineering, Instrumentation, and Materials C-74a    Laser and Particle Beam Fusion C-75      General, Miscellaneous, and Progress Reports C-81      Directed Energy Weapon Technology C-82      Special Features of Naval Reactors C-860    Other Isotope Separation Technology C-870    Space and Defense Reactor Power Systems C-880    Arms Control and Nonproliferation

The Announcement Notice (AN) defines a set of metadata, including both required and optional fields, for use in describing the Department of Energy's (DOE) Scientific and Technical Information (STI) products for announcement and availability. An AN includes review and release information, enabling a...nnouncement and searchable online access as appropriate. Review Announcement Notices to learn more about how OSTI collects and preserves information AN 241.1 Lab/Program Offices AN 241.3 Universities and Awardees AN 241.4 Software - Limited DOE CODE Software - Unlimited (Open or Closed Source) AN 241.5 Classified and UCNI Submission AN 241.6 Publicly Available Scientific Research Datasets Please enable JavaScript in your browser if you want to filter the content on this page according to your interests. Choosing an Announcement Notice Show All Submission Tables The submission tool below has been created to help filter the available choices of Announcement Notices. Simply input your affiliation and what you are trying to submit and we will help you figure out what you will need for submission. See Submitting Final Scientific/Technical Reports, STI Reporting Requirements for Financial Assistance Awardees, STI Copyright, Protected STI, and Marking Requirements for additional information. Also, see the DOI Assignment Flowchart (PDF 130.58 KB) for more information on how DOIs are assigned by OSTI.Disclaimers are to be used on all DOE STI products as appropriate. Unclassified or Classified? Select Classification...UnclassifiedClassified What kind of organization are you affiliated with? Select Organization Type...Lab/Site Program OfficeFinancial Awardee/Grantee What type of product are you submitting? Select Product Type...Technical Workshop ReportConference/Event Paper or Presentation ProceedingsAccepted Manuscript of Journal ArticleProgram DocumentScientific and Technical (S&T) Accomplishment ReportBook/MonographPatentThesis/DissertationFactsheetScientific Research DatasetsScientific and Technical Computer Software Showing results for ... ... ... The tables below help identify which tools or resources you will need for submission according to the submitter and the classification and type of STI. See DOE Reporting Requirements, STI Reporting Requirements, STI Copyright, Protected STI, and Marking Requirements for additional information. Classified AN 241.5 More information can be found here. Unclassified - DOE Laboratories, Sites, and Facilities Product Types Submission Method Technical/Workshop Report Submit using AN 241.1. See Attributes to Include. Each DOE laboratory has a site program to manage scientific and technical information produced under the contract and to make it available to DOE's Office of Scientific and Technical Information. Each site's STI Manager is involved in the process; for more information, see the listing of STI Managers. Conference/Event Paper or Presentation/Proceeding Submit using AN 241.1 Each DOE laboratory has a site program to manage scientific and technical information produced under the contract and to make it available to DOE's Office of Scientific and Technical Information. Each site's STI Manager is involved in the process; for more information, see the listing of STI Managers. Accepted Manuscript of Journal Article Submit using AN 241.1 Each DOE laboratory has a site program to manage scientific and technical information produced under the contract and to make it available to DOE's Office of Scientific and Technical Information. Each site's STI Manager is involved in the process; for more information, see the listing of STI Managers. Program Document Submit using AN 241.1 Each DOE laboratory has a site program to manage scientific and technical information produced under the contract and to make it available to DOE's Office of Scientific and Technical Information. Each site's STI Manager is involved in the process; for more information, see the listing of STI Managers. Scientific and Technical (S&T) Accomplishment Report Submit using AN 241.1 Each DOE laboratory has a site program to manage scientific and technical information produced under the contract and to make it available to DOE's Office of Scientific and Technical Information. Each site's STI Manager is involved in the process; for more information, see the listing of STI Managers. Book/Monograph Submit using AN 241.1 Each DOE laboratory has a site program to manage scientific and technical information produced under the contract and to make it available to DOE's Office of Scientific and Technical Information. Each site's STI Manager is involved in the process; for more information, see the listing of STI Managers. Patent OSTI obtains Patents of interest to DOE via special arrangements with the U.S. Patent & Trademark Office (USPTO). Periodic review by Labs and DOE-funded inventors is desirable to ensure that all relevant patents are being included. Each DOE laboratory has a site program to manage scientific and technical information produced under the contract and to make it available to DOE's Office of Scientific and Technical Information. Each site's STI Manager is involved in the process; for more information, see the listing of STI Managers. Thesis/Dissertation Submit using AN 241.1 Each DOE laboratory has a site program to manage scientific and technical information produced under the contract and to make it available to DOE's Office of Scientific and Technical Information. Each site's STI Manager is involved in the process; for more information, see the listing of STI Managers. Factsheet Submit using AN 241.1 Each DOE laboratory has a site program to manage scientific and technical information produced under the contract and to make it available to DOE's Office of Scientific and Technical Information. Each site's STI Manager is involved in the process; for more information, see the listing of STI Managers. Scientific Research Datasets (Announce Only) Submit using AN 241.6 Each DOE laboratory has a site program to manage scientific and technical information produced under the contract and to make it available to DOE's Office of Scientific and Technical Information. Each site's STI Manager is involved in the process; for more information, see the listing of STI Managers. Scientific and Technical Computer Software Submit using AN 241.4. See 241.4 footnote. Submit using DOE CODE. See DOE CODE footnote. Each DOE laboratory has a site program to manage scientific and technical information produced under the contract and to make it available to DOE's Office of Scientific and Technical Information. Each site's STI Manager is involved in the process; for more information, see the listing of STI Managers. Each DOE laboratory has a site program to manage scientific and technical information produced under the contract and to make it available to DOE's Office of Scientific and Technical Information. Each site's STI Manager is involved in the process; for more information, see the listing of STI Managers. Unclassified - Financial Assistance Awardees Product Types Submission Method Technical/Workshop Report Submit using AN 241.3. See Attributes to Include. Conference/Event Paper or Presentation/Proceeding Submit using AN 241.3 Accepted Manuscript of Journal Article Submit using AN 241.3 Book/Monograph Submit using AN 241.3 Patent OSTI obtains Patents of interest to DOE via special arrangements with the U.S. Patent & Trademark Office (USPTO). Periodic review by Labs and DOE-funded inventors is desirable to ensure that all relevant patents are being included. Thesis/Dissertation Submit using AN 241.3 Scientific Research Datasets (Announce Only) Submit using AN 241.6 Scientific and Technical Computer Software Submit using AN 241.4. See 241.4 footnote. Submit using DOE CODE. See DOE CODE footnote. Technical Report Attributes Attributes to include: Cover Page, Page 1: Final Technical Report for DE-XXXXXXXX (Universities and Awardees Only) Title Performing Organization Period of Performance Funding Office Date of Report DOI (if available) Report/Product number (if applicable) Award/Contract/Financial Assistance Number Distribution Statement (if applicable) Page 2: Title Author Abstract Distribution Statement (if applicable) Page 3: Disclaimers are to be used on all DOE STI products as appropriate. Please note that some contracts may include alternative disclaimers for use on STI Products. View Disclaimer. 241.4 Submission AN 241.4 - supports announcement of limited software (Controlled Unclassified Information (CUI), including DOE Official Use Only (OUO) and Export Controlled Information (ECI)) DOE CODE Submission DOE CODE - supports submission and announcement of DOE-funded unlimited availability software (including closed source, proprietary software) /* >