Skip to main content
U.S. flag

An official website of the United States government

Dynamic Data Release

By ScienceBase Instructions and Documentation

Dynamic data release can facilitate continuous collection, processing, quality control, and publication of data. It requires that the data, metadata, and all processing steps be reviewed and approved prior to the initial release.

The standard process for releasing data in ScienceBase, as described on the ScienceBase Data Release (SBDR) instructions page, is not always a good fit for projects that are continuously collecting data. There is often a benefit to having these data released as they are ready, in order to meet a particular science or management need. There are three options for releasing data for these types of projects: 

Venn Diagram of Provisioned, Versioned, and Dynamic data releases and their processes
Sources/Usage: Public Domain. View Media Details
 

Versioned Data Releases 

Versioned data releases require that the author go through the same steps as the standard data release process (USGS review and approval, and finalization by the SBDR Team). This approach works well for projects in which data collection is continuous, but processing and quality control steps are completed in discrete intervals (e.g., on a quarterly basis). Learn more about versioning a data release here.

Provisional Data Releases 

Provisional data releases are made publicly available before official USGS review and approval. These data releases include disclaimer statements to ensure that users are aware that these are not finalized data. Authors do still need to receive approval from the relevant approving officials to release provisional data. The authors will release a final, static data release at the conclusion of the project. Provisional data releases work well when data are continuously collected and processed but not continuously quality controlled. There is usually an immediate need for access to the data. For example, provisional data releases can be appropriate in cases of natural disasters. 

Dynamic Data Release 

Dynamic data releases require that the data, metadata, and the processing and quality control steps be reviewed and approved before initial release. This approach is a good fit for data that are continuously processed and quality controlled as they are collected. The released data are in their final form and no final static release is planned. Survey Manual Chapter 502.8, section 7 outlines requirements for the review, approval and maintenance of USGS-owned online databases and web data services. 

The process for releasing dynamic data releases is as follows and is subject to change: 

  1. Authors finalize and document their procedures for data collection, processing, and quality control 
  2. Center Directors (or designated approving officials) approve the reviewed data, metadata, and maintenance processes 
  3. Authors send the SBDR Team written approval from their approving official to release data as a dynamic data release 
  4. Authors develop a scripted approach to making updates to their ScienceBase data release 
    1. See below for fields that will need to be updated
    2. Contact the SBDR Team at sciencebase_datarelease@usgs.gov for an example script
  5. The SBDR Team finalizes and publishes the landing page and DOI, but the authors retain edit permissions to the landing page
  6. Authors use their script to automatically update the data, metadata, and change log as data are ready for release. 

Dynamic data releases require a lot more initial work compared to a standard data release or a versioned data release. Authors should not use this type of data release as a path to bypass data and metadata reviews.  

Landing Page Updates

  • Title: include the date of last update
  • Citation: include the date of last update
  • Last Update: include the date of last update in the Dates section with date type 'Last Update'
  • Change Log: indicate what has been added or changed

Metadata Updates

  •  <title> include date of last update​
  • <edition> include date of last update​
  • <metd> include date of last update​
  • <enddate> updated based on data​
  • <progress> “In work” or “Planned” changed to “Complete”​ if the project comes to a close and new data will not be added
  • <update> “Continually”, “Daily”, “Weekly” etc. changed to “None planned”​ if the project comes to a close and new data will not be added

Other details of the metadata should stay the same because data structure and processing steps should not change in a dynamic data release.

Identifier Updates

Digital Object Identifier (DOI)

  • Title: include the date of last update
  • Date: include the date of last update with date type 'Updated'

Metadata Persistent Identifier (PID)

  • Title: include the date of last update