E. Extended Guidance and Specific Products
- E.1 Peer-Reviewed Journal Submissions
- E.2 Data
- E.2.1 What are some examples of a dataset and a database?
- E.2.2 What are the requirements related to planning and conducting data collection and research?
- E.2.3 What Federal Government policies require the release of scientific data and how does the USGS intend to meet these requirements?
- E.2.4 How do I reference and cite the data supporting my publication?
- E.2.5 What is a USGS author's obligation when data collected by an outside source are used (with permission) in a USGS scientific information product and have not been publicly released by the data collector, and who is responsible for releasing the data?
- E.2.6 If a non-USGS lead author does not release data collected using Federal funds, is the USGS coauthor responsible for providing public access to those data?
- E.2.7 How is ownership determined for data collected during research or produced as a scientific information product? [updated July 2021]
- E.2.8 What outlets are available for releasing data?
- E.2.9 How are raw data handled?
- E.2.10 What about using non-Federal data repositories to provide or host the required public access to my data?
- E.2.11 What are the recordkeeping requirements regarding research activities?
- E.2.12. What data qualify as USGS funded scientific data and therefore are subject to USGS open data requirements and must be released to the public? [updated July 2021]
- E.2.13. What data responsibilities need to be included in cooperators/collaborators agreements or contracts? [added July 2021]
- E.2.14. Can tables, graphs, and other illustrations showing data that support the scholarly conclusions in a publication with USGS authors qualify as a data release? [added July 2021]
- E.2.15. What requirements apply to USGS data made available in non-USGS acceptable digital repositories?[added July 2021]
- E.2.a Data Management Planning
- E.2.A.1 What are data management plans or DMPs and why do I need to create them?
- E.2.A.2 What information is included in a DMP?
- E.2.A.3 What is the relationship between a project work plan and a DMP?
- E.2.A.4 Where can I find some DMP examples?
- E.2.A.5 What tools are available to help me create my DMP?
- E.2.A.6 Can a Science Center-wide plan be leveraged for my project-specific DMP?
- E.2.A.7 What if I do not know all the details of how my data will be managed?
- E.2.A.8 Who is responsible for ensuring that DMPs are developed and implemented for each project within a center or office? [updated June 2020]
- E.2.b Metadata
- E.2.B.1 What are metadata?
- E.2.B.2 Why do we need metadata for data?
- E.2.B.3 What do metadata records look like?
- E.2.B.4 How do I create metadata?
- E.2.B.5 What is a metadata review, and who can perform it? [updated June 2020]
- E.2.B.6 When do I create metadata?
- E.2.B.7 I have a lot of data packaged in different datasets and databases. For what packages of data do I produce a metadata record?
- E.2.B.8 Are metadata records required for any size dataset?
- E.2.B.9 Are metadata records needed for scientific datasets and databases that are provided by non-USGS authors and are subsequently included in USGS datasets, databases, or publications?
- E.2.B.10 Are the output data generated by a model simulation also subject to the metadata requirement?
- E.2.B.11 Do summary data tables in scientific information products such as USGS publication series products or outside publications (for example, journals) need metadata?
- E.2.B.12 Is USGS SPN editing required for metadata records?
- E.2.B.13 Where do the metadata records go once we have created them?
- E.2.B.14 If my data are associated with a publication, where does the DOI pointing to that publication get placed in the metadata?
- E.2.B.15 If I cannot explain how the data were created in the metadata record, where do I place the URL or DOI for the product that describes the data creation process?
- E.2.B.16 Where can I find additional guidance or information about metadata?
- E.2.B.17 Why must metadata records be cataloged in the USGS Science Data Catalog if the data are already available in an acceptable digital repository? [added July 2021]
- E.2.c Data Products
- E.2.C.1 What are the review and approval requirements for releasing scientific data to the public? [updated March 2021]
- E.2.C.2 What outlets are available for releasing data?
- E.2.C.3 Can I login and enter data into the USGS ScienceBase before those data have been approved for release?
- E.2.C.4 Where do I get a DOI for USGS data that has been approved for release?
- E.2.C.5 Where can I find additional guidance related to releasing USGS scientific data?
- E.2.C.6 What Federal Government policies require the release of scientific data, and how does the USGS intend to meet these requirements?
- E.2.C.7 Who may review data and metadata? [added February 2020]
- E.2.C.8 May I obtain a Digital Object Identifier (DOI) for historical USGS data created before October 1, 2016, when the USGS public-access requirements went into effect? [added February 2020]
- E.2.a Data Management Planning
- E.3 Restricted-File Federal Interagency Report (RFFIR) series (formerly Administrative Report series)
- E.4 Other Products
- E.5 Reporting of Project Progress
- E.6 Software
- E.7 Publications Warehouse
Aggregated data received from an analytical laboratory for field samples or measurements made directly during fieldwork are both examples of datasets. If a number of datasets are combined together into a searchable product or defined system, this product or system is an example of a database regardless of whether a formal database management system is used. A geologic map has a geospatial dataset, and when this dataset is combined with other regional datasets, the result is another example of a database. The National Water Information System (NWIS) is a database. Data retrieved from NWIS (such as a table of data) are a dataset.
USGS data collection and research activities are governed by work plans that are reviewed by appropriate experts and approved at some level higher than the project chief, generally by the Science Center Manager or equivalent. A work plan, which can be a component of a proposal, is handled through the Bureau planning process. Proper documentation is required to ensure that scientific goals are achievable and are appropriate to the mission of the USGS, and that research can be interpreted appropriately. Data collection and research activities are carried out in a consistent, objective, and replicable manner that has been vetted through a vigorous and open process of peer review (refer to SM 502.2). Scientific information products resulting from data collection and research activities, regardless of the outlet in which they are published, must follow the appropriate requirements for review, approval, and release.
The OSTP's February 22, 2013, memorandum Increasing Access to the Results of Federally Funded Scientific Research requires that all Federal Government agencies with a research budget greater than $100 million must develop and implement a plan to support increased public access to the results of federally funded research. Agencies must ensure that the public can read, download, and analyze, in digital form, final peer-reviewed manuscripts or final published documents within a timeframe that is appropriate for each type of research conducted or sponsored by the agency. Further, OSTP requires digitally formatted scientific data resulting from unclassified research supported wholly or in part by Federal funding to be stored and publicly accessible to search, retrieve, and analyze. Also refer to SM 502.8, which describes the requirements for review and approval of USGS scientific data prior to release. Additionally, the OMB's May 9, 2013, memorandum M-13-13, Open Data Policy—Managing Information as an Asset requires agencies to collect or create scientific information in a way that supports downstream information processing and dissemination activities, including using machine-readable and open formats, data standards, and common core and extensible metadata for all new scientific information creation and collection efforts. The Bureau's web page Public Access to Results of Federally Funded Research at the U.S. Geological Survey provides information related to how the Bureau meets these OSTP and OMB requirements and includes a link to the USGS Public Access Plan. The USGS Public Access Plan requires that digital data, upon which scholarly conclusions in USGS funded publications are based, be made available no later than the time of publication of those scholarly conclusions in conformance with applicable USGS data management policies.
Include a complete bibliographic citation for the data source in the references section of the publication. Example data citations are available on the USGS Data Management web site in the section titled "Citing Your Data." Cite the data source in the body of the report the same way you cite other references.
E.2.5. What is a USGS author's obligation when data collected by an outside source are used (with permission) in a USGS scientific information product and have not been publicly released by the data collector, and who is responsible for releasing the data?
Data used in USGS science information products should be made widely available to help ensure the accuracy, validity, and reproducibility of the scientific results. USGS scientists must ensure that the data associated with their research have proper acknowledgment regarding how the data were collected, where the data will reside, who will release the data, and how the data will be released. This information about data release must be described in data management plans (DMPs) that are included in associated research project plans (refer to guidance on developing DMPs). If the party collecting the data is another Federal agency, that agency has the primary responsibility for releasing the data according to their specific requirements. Refer to Guide to Data Releases With or Without a Companion Publication for six scenarios that describe data release obligations according to roles of USGS scientists and project funding arrangements.
Provisions for handling proprietary data and information, that is, data that cannot be released to the public for specific reasons, are found in SM 502.5. The author must ensure discussion about data release takes place with the data collector prior to signing any cooperative or collaborative agreement to use proprietary data, and decisions about these data releases should also be reflected in the DMP.
Data that are part of a USGS science data information product or used in interpretive work are subject to Freedom of Information Act (FOIA) requests. If the data are considered Federal records, we must comply with requirements related to responding to FOIA requests. Contact the USGS FOIA Officer for additional guidance.
The OSTP and OMB requirements for open data apply to data collected using Federal funds. Regardless of authorship, if the research was federally funded, then the funding agency is responsible for providing public access to those data. If the research is not federally funded, then the non-USGS lead author is not required to but has discretion to release the data to the public. It is common practice throughout the scientific publishing community to release the data upon which scholarly conclusions are based. Major publishers including Science, Nature, American Geophysical Union, Elsevier, and Wiley require access to the data upon which scholarly conclusions are based as a condition for publication.
E.2.7. How is ownership determined for data collected during research or produced as a scientific information product? Data collected by USGS employees, students, emeritus and other volunteers, and contractors on behalf of the USGS or using USGS funds, are owned by the USGS and not to the individual who collected the data. Data collected by a USGS employee or other affiliates, but funded by a cooperator, are considered owned by the cooperator. The agreement or contract with the cooperator/collaborator and the USGS project DMP should specify the data ownership, the distribution rights for USGS use of the data, the data preservation responsibilities, and who is responsible for providing the data to the public (refer to SM 502.6, guidance on developing DMPs, and FAQ E.2.13).
The preferred path for USGS data release is through USGS data repositories or portals, such as Science Base, NWIS, or BioData. The goal is to ensure that the USGS maintains the authoritative copy of the data it releases. The USGS has guidance available on acceptable digital repositories for releasing USGS data at Standards for Establishing Trusted Repositories for USGS Digital Assets. This guidance includes a list of repositories that will be updated as additional repositories are deemed acceptable.
"Raw data" refers to digital and nondigital data that are unprocessed and unverified. Examples include field observations and unaltered output from sensors. Retention of raw data is important in support of reproducible science and for recovering from processing errors. Raw data must be archived according to the USGS records disposition schedule and can be released as either provisional or approved data according to the USGS policy on data release (SM 502.8). Raw data may also be subject to FOIA requirements. In the event such data are requested, contact the USGS FOIA Officer for additional guidance.
Use of non-Federal repositories is acceptable as described at Standards for Establishing Trusted Repositories for USGS Digital Assets. The authoritative copy of the data, however, must be hosted on USGS servers or a federally maintained data service (refer to SM 502.9). For established agreements with the USGS, these arrangements, including a hosting agreement, need to be clearly spelled out in the DMP. In all cases, a metadata record, as described in SM 502.7, must be included in the USGS Science Data Catalog that includes a DOI link back to the data source, regardless of where the data reside or are hosted.
Documentation and recordkeeping requirements associated with data collection and research activities are found in the USGS Mission-Specific Disposition Schedules and General Records Disposition Schedules.
USGS-funded scientific data are those data collected with federally appropriated funds provided directly to the USGS as part of the congressionally-enacted USGS budget and therefore are subject to USGS requirements for data release (refer to SM 502.8). Data collected by USGS scientists with funding from another Federal or a non-Federal cooperator/collaborator are not considered USGS funded data (refer to E.2.13).
The agreement or contract with the cooperators/collaborators should clearly specify data ownership responsibilities, including expectations for curation and release. This information should also be included in the USGS project DMP (refer to SM 502.6). All final scientific data must include complete metadata (refer to SM 502.7) and be reviewed as described in SM 502.8 prior to being released by the USGS or provided to research partners under cooperative/collaborative agreements (refer to E.2.12).
No. Representations of data in tables, graphs, plots, maps, and other illustrations in such publications cannot qualify as a data release because they do not comply with open data requirements described in the USGS Public Access Plan.
For USGS data products stored in non-USGS repositories, review, approval, release, and preservation requirements apply as described in SM 502.8 and SM 502.9. A copy of the metadata record that describes the data asset and includes a resolvable Digital Object Identifier (DOI), must be added to the USGS Science Data Catalog, using the individual metadata upload page. The metadata record should accompany data stored in an acceptable non-USGS digital repository. These metadata should be maintained and updated as necessary (refer to SM 502.7).
A DMP is a document that outlines the data management considerations of a given project. A DMP describes intended actions for acquiring, processing, analyzing, preserving, publishing/sharing, describing, managing the quality of, backing up, and securing USGS data holdings. The document describes where and how you will acquire data, what standards you will use, and how data will be handled and protected during and after the completion of the project. The DMP is created before the project begins and is updated throughout the research process, as needed, to reflect the reality of project activities (SM 502.6). The USGS has a responsibility to steward its data to meet OMB open data requirements for managing Federal Government scientific information as an asset throughout the lifecycle. USGS researchers must create DMPs to help meet this responsibility. This planning enables Bureau management to anticipate the need to provide infrastructure and other support for scientific data.
A DMP includes information about the data and metadata standards to be used and intended actions for acquiring, processing, analyzing, preserving, publishing/sharing, describing, managing the quality of, backing up, and securing data holdings. The DMP captures the point of contact for the project and its data, and assigns roles to people who will be responsible for data management, updating the DMP, and generating metadata and other documentation. Descriptive information about the expected data input and output from the project is also important to include in the DMP, such as the estimated volume of the data and the format of the data and the accompanying metadata. With regard to length, the DMP should be as long as it needs to be to fully describe the data management activities on a given project. Once a project proposal has been accepted and the project is underway, the DMP is expected to be updated throughout the length of the project.
The overall project work plan of every research project (as discussed in SM 502.2) must include a DMP. Project work plans are broad in scope and cover all aspects of a project including project purpose, significance, methodology, staffing, budget, timelines and deliverables. DMPs are focused on the data-related aspects of the project. Both project and data management plans are essential and should be maintained as project documents.
The USGS Data Management website provides guidance on developing DMPs and understanding data management best practices. The Data Management Planning Considerations Checklist can be used to help ensure that all issues that may affect your data have been addressed in your DMP. Additionally, the USGS has partnered with the DMPTool to develop a DMP template. The DMPTool is a free, web-based application that is also used by several Federal agencies including the National Science Foundation and the National Institutes of Health. The tool presents each section of a DMP and allows you to save, preview, and export your plans as well as share your DMPs with collaborators.
Yes. A number of centers have developed guidance for how their scientists should be managing their data. Any center-specific information on how data are managed should be considered when writing your DMP. Every project is unique and will have particular data management requirements, however, so it is important that those project-specific details are captured in the DMP. No single, center-wide plan will be completely applicable for every project within a Science Center.
A data management plan is just that, a plan to get all the various actors in your program or center thinking about and committed to data management responsibilities before a project begins. You may need to get data management input from the principal investigator, co-investigators, data collectors, data analysts, information technology (IT) staff, modelers, geographic information systems (GIS) staff, and metadata experts, as each party involved may bring certain expertise related to specific aspects of the plan. If data management details change, your DMP should be updated to reflect those changes.
Science Center Directors or their designees ensure compliance with data management requirements for data produced in their centers or offices and consult with their ADs, RDs, Managers (program and project), scientists, and others on their staff as needed with regard to carrying out data management activities, including ensuring the development of DMPs. They also assign or ensure the assigning of data managers to oversee or steward the lifecycle activities of their respective data products (SM 502.6). Science Center Director responsibilities related to data management plans are summarized in the Training Module USGS FSP Science Center Director Responsibilities.
The term “metadata” refers to documentation of important aspects of data that describe where, when, and why the data were collected; who collected the data; what types of data were collected; what processes were used to create the data; what quality assurance controls were used; and where the collected data are located. Metadata are provided in a human-readable form as well as in a format that is machine readable (for example, XML) for automated use.
Metadata enable users to find, understand, and reuse the data, thus extending the life of the data. In addition, a metadata record is required by the USGS for including data in the Science Data Catalog. Federal Government mandates (including Executive Order 12906 and OMB Circular A-16) and USGS policy SM 502.7 require metadata as an integral part of data released to the public.
Examples of metadata for data include those found at https://archive.usgs.gov/archive/sites/sofia.usgs.gov/metadata/index.php.html and other examples on the USGS Data Management web page at https://www.usgs.gov/datamanagement/describe/metadata.php#hide-FGDC-CSDGM-Standard-Metadata-Examples.
Various tools for creating metadata are available on the USGS Data Management metadata web page. For example, the Online Metadata Editor (OME) helps you create a valid FGDC metadata record by compiling the answers you provide to common questions about your data. The OME tool can be used to start new records, upload and edit existing records, and save completed or ongoing records to the database or directly to your desktop.
A metadata review includes both checking for compliance with metadata standards by using a recommended metadata validation tool and performing quality checks. A minimum of one metadata review by a qualified reviewer is required for all USGS scientific data prepared for release. The role of the metadata reviewer is to evaluate the accuracy, completeness, and usability of the metadata. The metadata review can be conducted as part of the peer review (SM 502.3) or data review (SM 502.8), or it can be conducted separately as appropriate. Science Center management determines who serves as qualified metadata reviewers for the data produced by authors in their Centers. A metadata checklist that provides guidelines to reviewers is available. Additional information on metadata reviews is available on the USGS Data Management Metadata web page. A written report of all metadata reviews (reviewer comments and how they were reconciled) must be included in the internal IPDS review package that is submitted for Bureau approval as described in SM 502.7. Science Center Manager responsibilities for ensuring compliance with metadata requirements are also outlined in the FSP training module entitled USGS FSP Science Center Director Responsibilities.
A metadata record needs to be finalized and disseminated when the data are ready to be released to others. Authors should develop an approach for compiling the metadata record at the data-management planning stage as described in SM 502.6. Metadata are collected, used, and revised as a living resource throughout the data lifecycle. Therefore, metadata creation should be started as soon as the project begins. When recorded throughout the lifecycle of data, the metadata information is likely to be more accurate and will require less effort than if it is recorded at the end of the project. The metadata information must be updated periodically to document any changes to the data, such as corrections or additions.
It depends on how the data will be used. You need a metadata record that describes the data package that will be cited, which is generally also the package that will be searched for in the Science Data Catalog and public search engines. Additional metadata records might be needed for separate parts of data packages that have different creation or processing details.
There is no established size for a dataset that prescribes when a metadata record is required. A separate metadata record may not be needed if only a few sample results are presented in their entirety in a published table. However, if the table contains analytical or summary results, or a larger set of data is used from which a small number of records are extracted to create a table for a USGS series or outside publication, then it is appropriate to also have a metadata record for that larger dataset. When data are released, they must be accompanied by a metadata record. If a product uses a subset or summary of separately released data, no additional metadata record is needed.
Generally, yes, because these items become part of USGS scientific information products. When incorporated into USGS information products, these datasets or databases from non-USGS sources need to comply with USGS data release requirements, including review and approval of data and documentation of the source data. This is important because metadata records establish the provenance of incorporated data and include a link to the original source data. If sufficient metadata do not exist, record(s) should be created and included as part of the new information product's data package or cited in the metadata for the new USGS data product.
Yes, model simulation data that will be made publicly available through the data release process need metadata. Source data used for the model should be well documented and cited in the metadata to allow the work to be understood and replicated by others.
No. The data behind the summary table, however, if not also presented in the body of the product, will need metadata and will need to go through the data release process.
No, an SPN editorial review is not required, but Science Centers have the option of obtaining such a review as described in SM 1100.2 for any product as they deem appropriate.
A copy of the metadata record must stay with its associated data. Upon formal release of the data, copies of metadata records for all USGS data-related products, including non-geospatial data, must also be placed in the USGS Science Data Catalog. For more information about how to include metadata in the Science Data Catalog.
The DOI for the associated publication should be placed in the “Cross-referenced: Citation: Online Linkage:” element of the metadata record. To be an actionable link within the metadata record, the DOI must follow this format example: https://doi.org/10.3133/sir20155010.
This information should be added to the “Supplemental Information:” element of the metadata record. To be an actionable link within the metadata record, the DOI, if used, must follow this format example: https://doi.org/10.1029/2005WR004455.
Additional guidance on metadata creation, quality control and content review, tools, and best practices is available on the USGS Data Management Metadata web page.
Various Federal directives require agencies to manage data as assets and make those data publicly available, open, discoverable, and usable. The USGS Science Data Catalog (SDC) meets these Federal requirements by serving as the authoritative source for the USGS to provide its metadata to data.doi.gov, data.gov, and the Office of Management and Budget. Additionally, the SDC serves as the official data inventory of the USGS. To be compliant with these Federal requirements, metadata records must be cataloged in the SDC to identify USGS data assets distributed by USGS Trusted Digital Repositories (TDR) and by non-USGS repositories. Most USGS TDRs provide metadata to the SDC as a part of the data release process and repository owners should be consulted for guidance as needed. For other USGS and non-USGS repositories, the SDC tool for uploading individual metadata records may be used.
Data intended for public release are subject to USGS FSP review, approval, and release requirements. These requirements include one data review and one metadata review followed by Bureau approval documented in the IPDS as described in SM 502.8. A comprehensive data review checklist is available for conducting the data review. Data are never placed in the IPDS—only the documentation of the required metadata review and data review and any necessary reconciliation are placed in the IPDS as part of the approval package. Data are approved for release by Science Center Directors or their designees. USGS scientific data are considered noninterpretive; however, the scholarly publications associated with the data that describe the process used to create data, if interpretive and previously unpublished, must be peer reviewed and are approved by BAOs in the OSQI (refer to SM 205.18). Additional information about USGS scientific data is available at Distinctions between New Research or Interpretive Information Products, Previously Published or Noninterpretive Information Products, and Scientific Data. Science Center Director responsibilities for ensuring IPDS and FSP compliance and approval authorities are outlined in the USGS FSP Training Module entitled USGS FSP Science Center Director Responsibilities.
The preferred path for USGS data release is through USGS data repositories or portals, such as ScienceBase, NWIS, or BioData. The goal is to ensure that the USGS maintains the authoritative copy of the data it releases. The USGS has guidance available on acceptable digital repositories for releasing USGS data at Acceptable Digital Repositories for USGS Scientific Publications and Data. This guidance includes a list of repositories that will be updated as additional repositories are deemed acceptable.
Yes. Under the manage option in ScienceBase, users can enter data and keep the data private, that is, available only to them and others within the USGS. Data can be added to ScienceBase at any time and can be used as a resource during the data review process prior to release. Once the data are approved for release, the same manage option can be used to make the data public.
For specific guidance on DOIs, refer to Data Management Preserve.
The OSTP's February 22, 2013, memorandum Increasing Access to the Results of Federally Funded Scientific Research requires that all Federal Government agencies with a research budget greater than $100 million must develop and implement a plan to support increased public access to the results of federally funded research. Agencies must ensure that the public can read, download, and analyze, in digital form, final peer-reviewed manuscripts or final published documents within a timeframe that is appropriate for each type of research conducted or sponsored by the agency. Further, the OSTP requires digitally formatted scientific data resulting from unclassified research supported wholly or in part by Federal funding to be stored and publicly accessible to search, retrieve, and analyze. Also refer to SM 502.8, which describes the requirements for review and approval of USGS scientific data prior to release. Additionally, the OMB's May 9, 2013, memorandum M-13-13, Open Data Policy—Managing Information as an Asset requires agencies to collect or create scientific information in a way that supports downstream information processing and dissemination activities, including using machine-readable and open formats, data standards, and common core and extensible metadata for all new scientific information creation and collection efforts. The Bureau's web page Public Access to Results of Federally Funded Research at the U.S. Geological Survey provides information related to how the Bureau meets these OSTP and OMB requirements and includes a link to the USGS Public Access Plan. The USGS Public Access Plan requires that digital data, upon which scholarly conclusions in USGS funded publications are based, be made available no later than the time of publication of those scholarly conclusions in conformance with applicable USGS data management policies.
Data and metadata reviews are distinct and differ from peer reviews required for other USGS information products because data are considered noninterpretive. Peer review for interpretive information products must meet the requirements as described in SM 502.3, but data, however, do not follow these requirements. Although data release is often done at the same time as journal article publication, it is a distinct process that has different policy requirements.The intention is to have a qualified person who is familiar with the data/metadata perform the review, and this commonly is an individual on the project team. For example, a supervisor may be a data or metadata reviewer, or an individual on the project team supervised by the principal investigator may be the best person to perform these reviews. The same qualified individual may conduct both the data and metadata reviews, or different individuals may conduct the separate reviews. In both selection and number of reviewers, science center directors have authority to impose stricter requirements than the FSP required minimum.
Yes, you may obtain a DOI for these data. However, two circumstances must be considered, depending on the nature of the data — (1) data that have been previously published and released on a Science Center website prior to October 1, 2016, or available in print or other media and (2) unpublished (not previously released) data. For previously published data, no additional FSP review and approval documentation in IPDS is required because those data are grandfathered and exempt from the current requirements that went into effect October 1, 2016, as part of the USGS Public Access requirements. If there is an existing DOI, that DOI should be used. If no DOI exists, a DOI must be obtained using the USGS DOI Creation Tool. A metadata record about the data and containing that DOI is submitted to the Science Data Catalog. These data need to be available digitally from a landing web page to which the DOI is assigned and accessible from a USGS trusted or acceptable repository. Conversely, for unpublished data, the review and approval requirements as described in SM 502.8 must be followed prior to the data being released.