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

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

Documents containing classified or controlled unclassified information (CUI) should be marked according to their respective guidance and directives. The links listed here provide resources to help ensure documents are appropriately marked.Identifying and Protecting Official Use Only Information, DOE... O 471.3 Chg 1 (Admin Chg) (link is external)Manual for Identifying and Protecting Official Use Only Information (link is external)Identification and Protection of Unclassified Controlled Nuclear Information, DOE O 471.1B (link is external)Identification and Protection of Unclassified Controlled Nuclear Information, 10 CFR 1017 (link is external)DOE CMPC Marking Resource (link is external)DOE O 475.2B, Identifying Classified Information (link is external)

Recommended Characteristics of STI Technical ReportsDOE reporting requirements for financial assistance recipients are specified as scientific/technical reporting deliverables on the Federal Assistance Reporting Checklist (DOE F 4600.2).  Other awardees', such as Non-major Site/facility Management C...ontractors, technical reporting requirements are identified in Section J, List of Attachments, of the contract as part of the Performance Work Statement/Statement of Work, or as a separate attachment.Each required Scientific/Technical Report deliverable is to be submitted to DOE in electronic format as indicated in the award instrument/contractual agreement. Electronic documents should be submitted in one integrated file that contains all text, tables, diagrams, photographs, schematic, graphs, and charts and the file size should not exceed 120 MB.The report deliverable should be submitted via the Announcement Notice 241.3, Announcement of U.S. Department of Energy Scientific and Technical Information for Use by Financial Assistance Recipients and Non-major Site/facility Management Contractors. The Web-based AN 241.3 and instructions are available on the DOE Energy Link (E-Link) System.A username and password are not needed to submit the AN 241.3; however, it is imperative that your contract number is accurate. Below are basic instructions and other helpful information related to the scientific/technical reporting deliverable.Recommended Characteristics of STI Technical ReportsFront MatterAttributeTypical Placement on STI ProductExplanatory CommentAbstractPlacement on STI Product:Title PageComment:Briefly informs of purpose, scope, and findingsAcknowledgementsPlacement on STI Product:Follows Title PageComment:Credits substantial contributors to the work who are not authorsAuthorPlacement on STI Product:Cover and Title PageComment:Includes primary author and all contributing authorsAvailability StatementAttributeTypical Placement on STI ProductExplanatory CommentAward/Contract/Financial Assistance NumberPlacement on STI Product:Cover, inside front cover, and title pageComment:DOE funding agreementClassification Level/ CategoryPlacement on STI Product:Refer to DOE M 471.2-1C, Classified Matter Protection and Control ManualComment:Classification level and category of informationControl Markings/CaveatsPlacement on STI Product:Refer to DOE M 471.1-1, Identification and Protection of Unclassified Controlled Nuclear Information Manual; DOE M 471.2-1C, Classified Matter Protection and Control Manual; DOE M 471.3-1, Manual for Identifying and Protecting Official Use Only Information; DOE O 5610.2, Control of Weapon Data; and DOE M 452.1-1A, Protection of User Control Vulnerabilities and DesignComment:Markings that identify special handling or dissemination requirementDatePlacement on STI Product:Cover or title pageComment:Month and Year of releaseDisclaimerPlacement on STI Product:Inside front or back coverDistribution StatementPlacement on STI Product:Cover or title pageComment:Outlines restrictions or limitations on distributionFunding OfficePlacement on STI Product:Cover, inside front cover, title pageComment:Specifies the DOE office funding work productList(s) of Figures and TablesPlacement on STI Product:Follows Table of ContentsComment:Lists 5 or more figures or tables or any combination thereofPerforming OrganizationPlacement on STI Product:Cover, title page, outside back coverComment:Name and address of the performing or research organization and/or site of originReport/Product numberPlacement on STI Product:Cover, title page or outside back coverComment:Report number unique to releasing company/laboratory/agencyReport Documentation PagePlacement on STI Product:Before title pageComment:Used by federal agencies for database buildingReporting PeriodPlacement on STI Product:Included in title on cover or title page and first page of textComment:Month/year of reporting periodTable of ContentsPlacement on STI Product:Follows Title PageComment:Outlines organization and scope of a reportTitlePlacement on STI Product:Cover and Title PageComment:A brief title and if necessary, subtitleTitle PagePlacement on STI Product:First page of productComment:Provides information for description and bibliographic informationText BodyAttributeTypical Placement on STI ProductExplanatory CommentConclusionsPlacement on STI Product:Final paragraph of text (prior to Summary)Comment:Presents substantiated findings, discusses their implications and presents author's optionIntroductionPlacement on STI Product:1st page of textComment:States subject, purpose, scope and plan for developing reportReferencesPlacement on STI Product:Citations within the text or footnotesComment:Cites sources of information used by author(s) of reportsSummaryPlacement on STI Product:Follows Lists of Figures and Tables and/or Table of ContentsComment:Summarizes problem, results, conclusions, recommendationsBack MatterAttributeTypical Placement on STI ProductExplanatory CommentAppendixesPlacement on STI Product:Follows BibliographyComment:Contains supplemental information not essential to the textBibliographyPlacement on STI Product:Follows AcknowledgementsComment:Lists additional sources of information not cited in the text of a reportDistribution ListPlacement on STI Product:Last page of productComment:Gives permanent record of initial distribution of report

The AN 241.5 provides the Office of Scientific and Technical Information (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) wo...rk funded by DOE/NNSA or performed in DOE/NNSA facilities or predecessor agencies. Classified and UCNI STI products are submitted securely by DOE and DOE contractors via the Classified E-Link product on the Enterprise Secure Network (ESN).The Atomic Energy Act of 1954, as amended (link is external), and Executive Order 13526 (link is external) serve as the basis for identifying classified information generated by the Department.  Classified information is defined as certain information that the United States Government has determined requires protection against unauthorized disclosure for reasons of national security (i.e., Restricted Data, Formerly Restricted Data, Transclassified Foreign Nuclear Information, and National Security Information).  The unauthorized dissemination of UCNI is prohibited under Section 148 of the Atomic Energy Act of 1954, as amended (link is external).  UCNI is identified and controlled as directed in DOE Order 471.1B, Identification and Protection of Unclassified Controlled Nuclear Information (link is external); and Title 10, Code of Federal Regulations, Part 1017, Identification and Protection of Unclassified Controlled Nuclear Information (link is external).Classified and UCNI STI products transmitted to OSTI are to be properly marked with the appropriate announcement and/or access limitations on the accompanying announcement notice. Caveats and special control markings are placed on documents to identify special handling or dissemination requirements, or to assist in describing the type of information involved.  Refer to CMPC Marking Resource (link is external) for marking examples.DOE Order 475.2B, Identifying Classified Information (link is external), requires organizations to submit bibliographic information and, if available, an electronic version of the document to OSTI for every document that is declassified and determined to be publicly releasable. This ensures that it gets included in the Department's OpenNet (link is external) product. To ensure access to the appropriate audience, originating sites are further required to send classification change notices to OSTI for all declassifications, classification upgrades, and classification downgrades of STI products.  STI documents that have been declassified, in accordance with requirements prescribed in DOE Order 475.2B, Identifying Classified Information (link is external) may not automatically be released to the public. Information contained in the declassified document may still be exempt from public release based on one or more of the Freedom of Information Act exemptions. Classified information products that have been declassified should also be reviewed by the originating site for controlled unclassified information and official results submitted to OSTI.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.

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z A | Top A2EDAP Atmosphere to Electrons Data Archive and Portal AEC Atomic Energy Commission ALCF Argonne Leadership Compu...ting Facility AM Accepted Manuscript AMES Ames Laboratory AN Announcement Notice ANL Argonne National Laboratory ANSI American National Standards Institute API Application Programming Interface ARM Atmospheric Radiation Measurement User Facility AV Audio-Visual B | Top B&R Budget and Reporting BAPL Bettis Atomic Power Laboratory BNL Brookhaven National Laboratory C | Top CAF Controlled Access File CE-Link Classified Energy-Link CFR Code of Federal Regulations CI-SFA Critical Interfaces Scientific Focus Area CIMS Classified Information Management System CMPC Classified Matter Protection and Control CRADA Cooperative Research and Development Agreement CRD Contractor Requirements Documents CUI Controlled Unclassified Information CXIDB Coherent X-ray Imaging Data Bank D | Top DDE DOE Data Explorer DOE United States Department of Energy DOE-GDR US Department of Energy Geothermal Data Repository DOI Digital Object Identifier DRPOWER Data Repository for Power system Open models With Evolving Resources DTIC Defense Technical Information Center E | Top ECI Export Controlled Information EMSL Environmental Molecular Sciences Laboratory ERDA Energy Research and Development Administration ESN Enterprise Secure Network ESS-DIVE Environmental Systems Science Data Infrastructure for a Virtual Ecosystem ETTP East Tennessee Technology Park F | Top FNAL Fermi National Accelerator Laboratory FOIA Freedom of Information Act FRD Formerly Restricted Data FT Full Text G | Top GFO Golden Field Office GPO Government Printing Office H | Top HQ Headquarters HTML Hypertext Markup Language I | Top IAEA International Atomic Energy Agency IDF International DOI Foundation INIS International Nuclear Information System INL Idaho National Laboratory IPAR Individual Procurement Action Report J | Top JGI Joint Genome Institute JLAB Thomas Jefferson National Accelerator Facility K | Top KAPL Knolls Atomic Power Laboratory KCP Kansas City Plant L | Top LANL Los Alamos National Laboratory LBNL Lawrence Berkeley National Laboratory LDRD Laboratory Directed Research and Development LLNL Lawrence Livermore National Laboratory M | Top M&O Management and Operation MHKDR Marine and Hydrokinetic Data Repository MOU Memorandum of Understanding N | Top NARA National Archives and Records Administration NASA National Aeronautic and Space Administration NEA Nuclear Energy Agency NERSC National Energy Research Scientific Computing Center NETL National Energy Technology Laboratory NETL-EDX NETL's Energy Data eXchange NGEE-Arctic Next Generation Ecosystem Experiments - Arctic NGEE-Tropics Next Generation Ecosystem Experiments - Tropics NIH National Institutes of Health NISO National Information Standards Organization NLLC DOE National Laboratory Library Coalition NNDC National Nuclear Data Center NNPI Naval Nuclear Propulsion Information NNSA National Nuclear Security Administration NPTO National Petroleum Technology Office NREL National Renewable Energy Laboratory NSF National Science Foundation NSI National Security Information NTIS National Technical Information Service NTK Need to Know O | Top OECD Organization for Economic Cooperation and Development OLCF Oak Ridge Leadership Computing Facility ORAU Oak Ridge Associated Universities ORISE Oak Ridge Institute for Science and Education ORNL Oak Ridge National Laboratory OSS Open Source Software OSTI Office of Scientific and Technical Information OSTP Office of Science and Technology Policy OUO Official Use Only P | Top P.L. Public Law PDF/A Portable Document Format - Level A Compliance PDOUO Program Determined Official Use Only PNNL Pacific Northwest National Laboratory POC Point of Contact PPPL Princeton Plasma Physics Laboratory Q | Top QA Quality Assurance QC Quality Control R | Top R&D Research and Development RD Restricted Data RD&D Research, Development, and Demonstration RSICC Radiation Safety Information Computational Center S | Top S&T Scientific and Technical SBIR Small Business Innovative Research SIMS Security Information Management System SLAC SLAC National Accelerator Laboratory SNL Sandia National Laboratories SRC Science Research Connection SREL Savannah River Ecology Laboratory SRNL Savannah River National Laboratory SRS Savannah River Site STI Scientific and Technical Information STIP Scientific and Technical Information Program STRIPES Strategic Integrated Procurement Enterprise System STTR Small Business Technology Transfer Program T | Top TAP Tagged Acquisition Protocol TES-SFA Terrestrial Ecosystem Science Scientific Focus Area TIO Technical Information Officer TJNAF Thomas Jefferson National Accelerator Facility U | Top U.S.C. United States Code UCNI Unclassified Controlled Nuclear Information URL Uniform Resource Locator USQCD US Lattice Quantum Chromodynamics Collaboration W | Top WCH Washington Closure Hanford WFO Work for Others WTR-SFA Watershed Function Scientific Focus Area X | Top XML Extensible Markup Language Y | Top Y-12 Y-12 National Security Complex

DOE Elements are first-tier organizations at Headquarters and in the field, as described in the Correspondence Style Guide, Office of the Executive Secretariat (link is external)Heads of Departmental Elements at Headquarters, including NNSA, per DOE O 241.1B:Ensure that the objectives and requiremen...ts are incorporated into their program planning, management, contract administration, and performance-based management activities.Ensure that program-issued documents or other types of STI are appropriately reviewed and released and made available in acceptable electronic formats to OSTI, with corresponding Announcement NoticesInstruct initiators of procurement requests for M&O and site/facility management contracts to specify whether the CRD for this Order applies in the award resulting from the procurement request and any special instructions for applying the Contractor Requirements Document of DOE Order 241.1B.Instruct initiators of procurement requests for R&D contracts other than site/facility management contracts to specify the required scientific and technical deliverables, the form of delivery, and the requirement for the accompanying "Announcement of DOE Scientific and Technical Information" in the statement of work or any special instructions for applying the Contractor Requirements Document of DOE Order 241.1B.Instruct initiators of procurement requests for financial assistance instruments to specify the required scientific and technical deliverables, the form of delivery, and the requirement for the accompanying "Announcement of DOE Scientific and Technical Information" on the Federal Assistance Reporting Checklist.Designate senior officials to address STI policy issues as needed.For programs that fund projects that generate STI or staff offices that affect STI policies, appoint and officially inform OSTI of the formal STI points of contact (i.e., Technical Information Officer) to participate in the Department's Scientific and Technical Information Program (STIP), coordinate STI management activities, and serve as or designate an STI Releasing Official(s).Appoint and officially inform OSTI of formal STI points of contact (i.e. Technical Information Officer) to participate in the Department's Scientific and Technical Information Program (STIP) and serve as or designate an STI Releasing Official(s).

DOE Programs fund research and other scientific endeavors. For those activities where the STI is not submitted by National Labs, major sites, or through financial assistance awards, it should be submitted by the DOE Program.  DOE Programs have the option to provide metadata via the Announcement Noti...ce 241.1 on E-Link. The metadata-based announcement notice generated and supplied by DOE and contractors for unclassified STI products includes metadata elements that provide identification of and attribution for DOE's STI.  It also includes key identifiers; descriptive elements, review and release information, and medium, format, and location elements. Some elements are required, while others are optional.  Submitters must provide required information and are highly encouraged to include optional information wherever possible.Steps Required to Provide STI to DOE:Apply for E-Link Access. Questions about E-Link should be directed to OSTI @ 865-576-4070.Identify STI product type and check the AN 241.1 instructions or Submission Basics to determine which business rules apply to your submission. If the product you are submitting is a journal article, be sure to check the requirements for including the author's accepted, peer-reviewed manuscript.Review full-text document for sensitivities and protected Personally Identifiable Information (PII).The STI Releasing Official should: Prior to the submission of the announcement notice and full-text document through 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.Program Offices also have the option to send STI directly to OSTI via STI submission at STIP@OSTI.GOV.  An OSTI staff member will work with the Program to ensure appropriate submission.

A Principal Investigator is designated by a research organization to have an appropriate level of authority and responsibility for the proper conduct of the research, the use of funds, and administrative requirements, including the submission of scientific and technical information to the agency. Wh...en an organization designates more than one PI, they must share the authority and responsibility for leading and directing the research, intellectually and logistically.  For submission information, reference Submitting STI.Principal Investigators and Authors at DOE National Laboratories should follow the procedures provided at the lab/site.  For more information, contact the STI Manager.

OSTI coordinates the STI Program (STIP), a complex-wide collaboration across DOE programs, field offices, national laboratories, and contractors to disseminate and preserve the Department's STI. In addition to text, OSTI recognizes the growing need to capture scientific research in emerging formats,... such as data and software, and pursues this mission responsibility. OSTI builds on existing partnerships and seeks strategic alliances across a wide range of communities, including DOE, interagency, international, and private sector, to increase access to the Department's research and development results.Responsibilities include: Ensuring appropriate transparency of and open access to DOE's STI to advance science and technology as well as preservation of a permanent DOE STI repository.Collaborating with stakeholders to establish STI requirements and responsibilities to ensure optimal availability of Departmental STI to the varied customer segments, within applicable laws and Departmental requirements.Maintaining information management systems and web-based databases to enable full use of DOE-funded STI and provides a suite of web products and services for publicly releasable STI, as well as systems to manage protected categories of STI as appropriate. Managing domestic, interagency, and international STI exchanges to ensure DOE and U.S. access to national and global scientific and technical advances.Supporting program-specific STI management efforts by offering special support services upon request to DOE organizations that provide funding to cover incremental costs of the requested service(s).Responsibilities of OSTI STIP LiaisonThe STIP Liaison within the Office of Assistant Director for Acquisition and Information Programs at OSTI serves as the representative and advocate for the STIP community.  The Liaison is normally involved in activities or discussions concerning:STIP collaboration businessCross-cutting STIP issue resolutionsSTI order and guidePerformance objectives and measuresSTI policies and proceduresSTIP special focus teamsE-Link submission and reportingSTIP planning and reportingThroughout its history, OSTI has worked with representatives across the agency-in laboratories, field offices, Headquarters-to facilitate access to information and to promulgate policy and best practices for STI management. OSTI will work to broaden its complex-wide collaboration by increasing communications beyond the designated STI points of contact and engaging others across DOE in projects that advance STIP goals.For more information, contact an OSTI-STIP Liaison.

STI ManagersTechnical Information OfficersSTI Releasing OfficialsContract Officers and Contract SpecialistDepartment of Energy national laboratories and other sites and facilities have designated representatives to serve as technical information officers (TIOs) and STI Managers in the Scientific and... Technical Information Program (STIP).STI Managers The role of STI Managers is to stay abreast of the requirements of DOE's STI Program and coordinate the implementation of STIP related requirements. They serve as the main POC for their respective site/facility and participate in various STIP activities.  Normally, one STI Manager is appointed at each contractor site.  While roles and responsibilities may vary from site to site, depending on the specific language of DOE contracts, the STI activities of STI Managers generally are the same.Roles and ResponsibilitiesSTI Managers provide oversight and coordination of contractor compliance with the CRD portion of DOE O 241.1B, Scientific and Technical Information Management (link is external)  and other applicable DOE directives with related requirements (i.e., regarding sensitivity reviews, etc.).STI Managers provide oversight and coordination of contractor application of the agreed to best practices set forth on the STIP website.STI Managers ensure that an appropriate sensitivity review process of STI is implemented at their respective site and that all STI is appropriately reviewed and marked before it is released outside of their jurisdiction of their site prior to release to OSTI or Web posting.Related to the sensitivity reviews of STI, STI Managers should serve as the releasing official or at least coordinate designation and maintain awareness and provide official approval and notification to OSTI of the designation.STI Managers ensures that STI resulting from R&D and other scientific and technical endeavors that have undergone institutional review is made available to OSTI along with appropriate announcement notice information provided through one of the several STI announcement options.STI Managers ensure that OSTI is notified of any removal, replacement, or new marking or STI, per appropriate STIP channels.STI Managers participate in bi-monthly STIP teleconferences, annual STIP Working Meetings, and special STIP working groups normally chaired by OSTI.STI Managers provide general liaison with OSTI and the TIOs.STI Managers prepare contractor responses to STI-related action items received from their respective DOE Office and OSTI.Technical Information OfficersTechnical Information Officers (TIO) serve as the principal DOE Office POC and assistant to, and liaison with, the DOE Office of Scientific and Technical Information (OSTI) that serves as the Department's office charged with the Scientific and Technical Information Program (STIP). The TIOs are to be familiar with the STI Programs within their DOE Office (given they have contracting financial assistance and/or acquisition activities) and for their major site/facility management contractor(s) STI Program to discern compliance with the DOE O 241.1B. They must maintain an up-to-date knowledge-base of the STI Program activities and provide timely feedback on issues as they emerge. While roles and responsibilities may differ, each major DOE element shall designate a TIO to perform STI-related activities.Roles and ResponsibilitiesTIOs coordinate with the major site/facility management contractor(s) STI Manager(s) activities as they pertain to STI to ensure compliance with the CRD portion of DOE O 241.1B, Scientific and Technical Information Management (link is external).TIOs ensure that an appropriate sensitivity review process of STI is implemented by their DOE contracting/acquisitions group and appropriate guidance is provided to DOE contractors and financial assistance recipients. In addition, they should ensure that the STI generated by their financial assistance recipients, non-major site/facility management contractors, and major site/facility management contractors is appropriately reviewed and marked before it is released outside of the jurisdiction of the sites and prior to release to OSTI or Web posting.Related to the sensitivity reviews of STI generated from financial assistance and non-major site/facility management contractors, TIOs should serve as the releasing official or at least coordinate designation and maintain awareness and provide official approval and notification to OSTI of the designation.TIOs are responsible for ensuring the STI generated by financial assistance recipients and non-major site/facility management contractors is submitted to OSTI according to appropriate submission processes via E-Link. TIOs ensure the DOE contracting officers and contract specialists within their organization are aware of the status and trends related to the sensitivity reviews and timely submission of STI deliverables to OSTI.TIOs participate in preparing official DOE Office responses to STI-related action items relevant to their respective DOE and major site/facility management contractors.TIOs serve as the DOE Office representatives and advocates to ensure that STI objectives and requirements are incorporated as appropriate into the DOE Office strategic plans, DOE management information plans, DOE contractor information architecture plans, life-cycle management plans and procedures, contractor-developed institutional plans, and contract language for new or modified contracts and grants.TIOs are responsible for coordinating and communicating DOE STI goals and objectives and initiating the promotion/education of STI and STIP-related activities at the DOE Office and provide assistance as appropriate to their respective major site/facility management contractor sites. This includes the progression of timely and acceptable electronic formats of announcement records and STI.TIOs represent their organization's STI objectives/perspectives by staying informed of their in-house STI activities and those of their major site/facility management contractors. Also, TIOs represent their DOE Office by participating in the various STI-related activities and meetings such as Meet-Me Calls, Annual STIP Working Meetings, and special working groups. Active participation in the STIP collaboration is vital and beneficial when contributing to the best practices for a successful STI management program.TIOs participate in rewrites of directives as appropriate, provide updates to the STIP Home Page, and communicate the requirements and best practices to DOE and DOE major site/facility management contractors.Through STIP, TIOs recommend the need for new or revised policies and comment on the new or revised policies put forth. They also ensure that implementation procedures for the new or revised policies are put in place by DOE and coordinate as needed with major site/facility management contractors.STI Releasing OfficialsReleasing Officials have responsibility for ensuring that STI has undergone appropriate sensitivity reviews and that subsequent recommendation to OSTI is made via established systems regarding release of STI in the public domain (i.e., unlimited announcement) or the application of DOE-approved access limitations, as well as other laws, policies, and schedules.Contract Officers and Contract SpecialistA Contracting Officer is the DOE official authorized to execute awards on behalf of DOE and is responsible for the business management and non-program aspects of the financial assistance process. They are responsible for ensuring that the receipt of required interim and final scientific/technical reporting deliverables as identified on DOE F 4600.2, Federal Assistance Reporting Checklist, and in the contract are monitored and provided to DOE/OSTI.

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.

A disclaimer is to be used on all DOE STI products as appropriate. The following is a standard disclaimer to be used as appropriate. Please note that some contracts may include alternative disclaimers for use on STI Products.Full Legal DisclaimerThis work was prepared as an account of work sponsored... by an agency of the United States Government. Neither the United States Government nor any agency thereof, nor any of their employees, nor any of their contractors, subcontractors or their employees, makes any warranty, express or implied, or assumes any legal liability or responsibility for the accuracy, completeness, or any third party's use or the results of such use of any information, apparatus, product, or process disclosed, or represents that its use would not infringe privately owned rights. Reference herein to any specific commercial product, process, or service by trade name, trademark, manufacturer, or otherwise, does not necessarily constitute or imply its endorsement, recommendation, or favoring by the United States Government or any agency thereof or its contractors or subcontractors. The views and opinions of authors expressed herein do not necessarily state or reflect those of the United States Government or any agency thereof, its contractors or subcontractors.Acceptable AlternativeThis work was prepared under an agreement with and funded by the U.S. Government. Neither the U. S. Government or its employees, nor any of its contractors, subcontractors or their employees, makes any express or implied:warranty or assumes any legal liability for the accuracy, completeness, or for the use or results of such use of any information, product, or process disclosed; orrepresentation that such use or results of such use would not infringe privately owned rights; orendorsement or recommendation of any specifically identified commercial product, process, or service. Any views and opinions of authors expressed in this work do not necessarily state or reflect those of the United States Government, its contractors or subcontractors.Trademark DisclaimerReference herein to any specific commercial product, process, or service by trade name, trademark, manufacturer, or otherwise, does not necessarily constitute or imply its endorsement, recommendation, or favoring by the United States Government or any agency thereof or its contractors or subcontractors.See additional standards that provide information on recommended practices as well as guidance for Departmental elements and others in the preparation of 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...