uabrc / uabrc/uabrc.github.io

Data lifecycle management

Open
#1,036 0 comments 0 reactions 1 assignee View on GitHub

@wwarriner is already working on this.

Since Aug 12, 2025.

style: article/section 📝 system: data-mgmt 🗃️ system: storage 🛢
Dominant language
Python
Stars
24
Forks
15
Avg merge
10d 3h
Merged PRs (30d)
1

Description

What would you like to see added?

Add an article with the basic outline of data lifecycle management. Add to and cross-link with PI responsibilities.

The following is a tentative outline, this is not a complete list of questions, nor should it necessarily be the final organization.

  • Sourcing data
    • Who owns the data?
    • Who at UAB will be responsible for managing the data?
    • What is the plan for transfer of the data to a new owner if the original owner can no longer take responsibility?
    • What is the storage plan for the data?
    • What is the data management plan for the data?
    • What is the plan for final disposition of the data?
    • Where does the data originate?
    • What licenses, contracts, or data sharing/use agreements will be in force for the data?
    • What security standards or regulations cover the data (e.g. HIPAA, NIST 800-171, etc.)?
    • How is the data classified according to UAB IT policy?
    • How will the data be brought onto UAB storage systems?
  • Data management planning
    • TBD
  • Storing data
    • Who is responsible for the data?
    • Where is the data stored?
    • What grants are attached to the data?
    • Who has access to the data?
    • Who is responsible for granting access to the data?
  • Transferring responsibility
    • TBD
  • Disposing of data
    • Who is responsible for disposition?
    • What method of disposition is required (e.g., destruction, archival, hand-off)?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.