✏️
Alaska Region Interim Data Management User Guide
  • Alaska Region Interim Data Management User Guide
  • Background
    • Why Data Managment?
    • The Big Picture: Integrating Data Management with Project Management
    • Definition of Project and Product (aka Data Resources)
  • Four Fundamental Activities of Data Management
    • Establish Roles and Responsibilities
    • Quality Management
    • Security and Preservation
    • Documentation
  • Alaska Data Management 101
    • Workflow
    • File Organization and Best Practices
      • Best Practices in Naming Conventions
      • Best Practices for Version Control
      • Changelog Best Practices
    • Alaska Regional Data Repository
    • Data Management Policy
  • Plan
    • Why Data Planning?
    • Data Management Plan Templates
      • Data Standards in brief
    • Project & Data Management Integration
    • Considerations for Projects with External Partners
  • ACQUIRE
    • Common Data Types
      • Open Formats
      • Best Practices in Tabular Data
      • Best Practices in Databases
      • Best Practices in Geospatial Data
      • Best Practices with Collections of Similar Types of Data
      • Best Practices with Source Data
    • Quality Management Procedures
      • Incorporating Data Standards
      • Using Unique Identifiers
  • MAINTAIN
    • Update Metadata
  • Access & Share
    • Open Data Requirements
      • Obtaining a Digital Object Identifier (DOI)
      • Obtaining a URL
      • Sharing without a URL
  • Long-term Storage Options
    • Using the Regional Data Repository
    • Public Accessible Repositories
  • Records Schedule & Disposition
  • Data Management Actions Quick Guide
  • Glossary
Powered by GitBook
On this page
  • ServCat
  • ScienceBase

Was this helpful?

  1. Long-term Storage Options

Public Accessible Repositories

PreviousUsing the Regional Data RepositoryNextRecords Schedule & Disposition

Last updated 2 years ago

Was this helpful?

Like the RDR, publicly accessible repositories are organized inventories of data assets. A key difference, though, is that these repositories are accessible to all individuals. Staff, with the assistance of their data manager, can upload their project data to a public-facing repository. The benefit of doing this is twofold:

  1. Archiving your data in more than one repository will lead to redundant storage, greatly reducing the risk of data loss.

  2. Your project data can easily be discovered and accessed by partners and other researchers outside of the Service.

Examples of public repositories--many of which are federally managed--include:

ServCat

ServCat--short for Service Catalog--archives resources generated or created by the Service such as published and unpublished reports, management plans, datasets, photos, audio files, maps, and journal articles. This repository was designed allow project data to be easily discovered and retrieved by Service staff as well as the general public. The system is securely managed and backed up by USFWS data specialists, and files of all types and sizes can be uploaded to ServCat. This repository is well suited for document storage and can be used by all Service staff.

Access ServCat here:

ScienceBase

ScienceBase is a digital repository created by USGS for the long-term storage of finalized science products like datasets, photos, and maps. Data uploaded to this repository can be shared within and without USGS through web services, and metadata can be created and maintained using this tool. ScienceBase also allows researchers to track projects and their data from their inception to completion. This repository is currently only available for Science Application staff.

Uploading project files to public-facing repositories is best accomplished with help from your data manager.

Access ScienceBase here:

ServCat
ScienceBase
AGOL
Landscape Conservation Cooperatives Science Catalog
GeoPlatform
Data.gov
https://ecos.fws.gov/ServCat/
https://www.sciencebase.gov/catalog/