✏️
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. Four Fundamental Activities of Data Management

Security and Preservation

PreviousQuality ManagementNextDocumentation

Last updated 5 years ago

Was this helpful?

Establishing a single archive folder for each project prevents data loss and ensures data integrity. The archive folder for a project, comprised of the recommended file structure (Appendix B) and described in section, will be placed in the Regional Data Repository. See for details on setting up an archive folder for your project.

The will have write permissions to all folders in the archive folder. The and will have write permissions to an “incoming” folder and read-only permissions to all other folders. All other staff in the Region will have read-only access to the entire folder. The incoming folder allows project personnel to contribute products and associated metadata records to the archive folder. The is responsible for reviewing these files and the is responsible for moving them from the incoming folder to the appropriate folder in the archive folder.

Anyone with access to the Regional Data Repository can copy an archive folder to their local hard drive and maintain the files on their hard drive in whatever manner they choose, but only project personnel may move things into their project's archive folder via the incoming folder.

File Organization and Best Practices
File Organization and Best Practices
Data Custodian
Project Manager
Data Originators
Data Steward
Data Custodian