Confluence Retirement

Due to the feedback from stakeholders and our commitment to not adversely impact USGS science activities that Confluence supports, we are extending the migration deadline to January 2023.

In an effort to consolidate USGS hosted Wikis, myUSGS’ Confluence service is targeted for retirement. The official USGS Wiki and collaboration space is now SharePoint. Please migrate existing spaces and content to the SharePoint platform and remove it from Confluence at your earliest convenience. If you need any additional information or have any concerns about this change, please contact Thank you for your prompt attention to this matter.
Skip to end of metadata
Go to start of metadata


Data Release WorkBench

  • A quick tour of the Data Release Workbench (phase 1), developed to illustrate the general steps needed for releasing data in USGS
  • Questions to consider:
    • Do you see benefits to workflows that actually tie the tools together?
    • If you are using a system other than ScienceBase for your data releases in your Center/Program, do you see the Workbench useful?
    • Are there patterns in your workflows that would benefit from some automation?
  • Will data releases in ScienceBase automatically go to the Science Data Catalog?
    • We are working on the connection right now so that the workflow can be easier.
    • Users will be able to manage choose if they want to send their metadata from ScienceBase to the Science Data Catalog. 
  • Are Data Management Plans (DMPs) going to be deposited with the dataset? 
    • Currently it is up to the centers/programs to figure out how to manage DMPs
    • As of now it is not required to have DMPs made public. This is helping with progress tracking at the center level. 
    • We might add the DMP component to the Data Release Workbench
    • Dave Govonni comment - A tight linkage to a uniform plans structure would be necessary here. At some point we are going to go from DMP creation requirements to DMP enforcement. At the OMB level they are thinking about this. Having a look back that allows you to update the plan. Tracking what you promised and tracking what happened is something that is coming. 
  • Nicole from USDA - Is the metadata that has been added to the Workbench been validated? Or does the workbench validate for you? 
    • The workbench is a simple checklist right now and does not validate the metadata. 
    • When metadata are being stored on a government server, the hope is that the metadata has already been reviewed and validated through the USGS review and approval process. 
  • Heather  - Before you upload the metadata, wouldn't you need the repository to be established first, and the DOI needing to be created to go into the metadata? Questioning the linear layout in the workbench.
    • Yes there is a chicken and egg for some of these processes. This order is not linear and the order displayed in the Workbench is not prescriptive (you can start with any component). 

Differences between USGS Science Data Catalog and ScienceBase 

Science Data Sharing agreements - JC Nelson (UMESC)

JC has been working on drafting Data Sharing Agreements at USGS to guide centers/programs when they are working with collaborators/funders. These agreements cover who receives the data after the end of the project, which agency is responsible for releasing/preserving the data, etc. Contact JC to view a copy of the draft Data Sharing Agreement. 


  • Dave Govonni - Suggest adding a clause to assure that data associated with our publications are handled in a way that also meets our OSTP public access requirements.
    • JC - that is the reason for this to ensure data associated with the authors meets the requirements. We talked about generalizing data for data coming in. Money going in and going out will have specific details. You will be able to pick either one of those templates so that up front it is known that agency x will have to make the data available or USGS will have the authoritative copy, etc. 
  • Dave Govonni - will this language have the same force as language that is being added to our Grants program? Want to make sure that the two have the same effect and legal force. Suggest talking to Keith Kirk to provide the current language
    • JC - hoping so that it will have full legal backing. Will look into it.
  • Once you get the template approved by OPA for the centers to be used, if the centers use then modify the template will they have to go through OPA for approval each time they do a data sharing agreement?
    • JC - hoping centers wont have to go through OPA for their agreements but that decision has not been made yet. Stay tuned.
  • Do you have a timeline to get this done?
    • JC - hoping to get done by end of July. 
  • Next steps is to get this advertised
    • Suggest the Public Access Plan monthly forum to make an announcement once completed
    • Suggest we alert the Dept of Interior larger activity "Data as a strategic asset" initiative led by Tim Quinn and Jerry Johnston. It is important to let other bureaus know how they can work better with USGS under these new requirements for USGS. 
      • JC will reach out to Tim Quinn
    • John Faundeen - this is  great. We usually work with FEMA to gather data for them. Then the data are still here with USGS. This will be useful.
  • Could centers take the template and use interchangeable text?
    • JC - we wanted interchangeable text for centers to pick and choose but OPA wanted more fixed text for centers to use. 
  • When will these agreements be in place during the course of a project lifecycle?
    • JC - recommend typically after the project is funded and you are working out the details with the collaborator. When you are doing the interagency/cooperative agreement, it is this stage where we are pushing the data sharing agreement. It could be in other parts of the lifecycle (e.g. proposal phase) depending on the center.

WG Updates/Discussions:



-       JC is on detail for Ecosystem Mission Area to help with data release. If any Ecosystems centers need help, contact JC.