✏️
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

Was this helpful?

  1. Background

Definition of Project and Product (aka Data Resources)

The interim plan is focused on projects and their derived products. Projects are discrete efforts on a particular topic with defined objectives or goals. At this time, programs determine which projects (completed, ongoing, or proposed) should undergo data management. For example, use in management decisions and partner needs may be criteria managers could adopt to prioritize projects for data management.

Products (aka Data Resources) are recorded information generated by experiments, models, simulations, observations, analysis, and other activities that create or synthesize data resources. In a new project, anticipated products are identified during the planning stage when the design of sampling and analysis take place in consultation with the program’s biometrician. Determining which products to document is at the discretion of the principal investigator, their supervisor, and any relevant program or branch policies but guided by the principle of reuse.

PreviousThe Big Picture: Integrating Data Management with Project ManagementNextFour Fundamental Activities of Data Management

Last updated 5 years ago

Was this helpful?