Article on data access authorization and responsibility

.pre-commit-config.yaml

@@ -8,7 +8,7 @@ repos:
     hooks:
       - id: mkdocs-build
         name: Build documentation
-        entry: conda run -n mkdocs mkdocs build --strict
+        entry: "conda activate mkdocs && mkdocs build --strict"
         language: system
         always_run: true
         pass_filenames: false

docs/data_management/data_responsibilities.md

@@ -51,21 +51,11 @@ What hazards can cause data loss?
 - Accidental file deletion.
     - Example: mistakenly deleting the wrong files when using the [shell command](../workflow_solutions/shell.md#delete-files-and-directories-rm-rmdir) `rm`.
     - Files deleted with `rm` or any similar command can not be recovered by us under any circumstances.
-    - Please restore from a backup.
 - Natural disasters.
     - Examples: tornado; hurricane.
     - All of our data sits in one geographical location at the UAB Technology Innovation Center (TIC).
     - Plans to add geographical data redundancy are being considered.
-    - Please restore from an offsite backup.
-- Unusable backups.
-    - Examples: backup software bug; media destroyed; natural disaster at offsite location.
-    - Regularly test data restoration from all backups.
-
-How can I ensure data integrity?
-
-- Regularly back up your (and your lab's) data in an offsite location.
-- [S3 based long-term storage (LTS)](lts/index.md) can be used for short-term onsite backup.
-- Crashplan licenses are available for automatic offsite backups, please contact [Support](../help/support.md) for more information.
+If you have backup needs, we can discuss options based on your use case. We want to engage in a conversation. please send us a support ticket via <[email protected]>.
 
 ## Security Exceptions for Accessing Former UAB Personnel Data
 
@@ -75,8 +65,14 @@ To request access to data of former UAB user, the first step is to fill out the
 
 If the owner of the data was your student or staff in your lab, then the first choice is probably best (two-levels up supervisor). If the data owner was in a different department or special approval is required (for example a professor in the dept of medicine wanting access to data from a student in the school of engineering), select "Dean, C-level, or Trusted Designee" for the "Approval Type" field. If written approval can be provided directly by the former personnel, you can bypassed completing the form for request.
 
-To simplify data access and management, it is recommended to store critical research data in shared storage areas that are accessible to or owned by the responsible PI. If you need help with data management process, please send a support ticket via <[email protected]>, and we will guide you through these steps.
+To simplify data access and management, it is recommended to store critical research data in shared storage areas that are accessible to or owned by the responsible PI, with ownership transfer initiated as needed. If you need help with data management process, please send a support ticket via <[email protected]>, and we will guide you through these steps.
 
 ## User responsibilities with UAB-IT policies
 
-All PIs, Core directors, researchers, students, users of UAB-owned computer systems, including Research Computing system, are responsible for adhering to the data and computing infrastructure policies set by UAB-IT, such as [Overall IT policy page](https://www.uab.edu/it/home/policies), [Acceptable Use Policy (AUP)](https://secure4.compliancebridge.com/uab/portal/getdoc.php?file=300), [Data Protection and Security Policy](https://secure4.compliancebridge.com/uab/portal/getdoc.php?file=302), [Data Access Policy](https://secure4.compliancebridge.com/uab/portal/getdoc.php?file=301), and [Data Classification](https://www.uab.edu/it/home/policies/data-classification/classification-overview).
+All PIs, Core directors, researchers, students, users of UAB-owned computer systems, including Research Computing system, are responsible for adhering to the data and computing infrastructure policies set by UAB-IT.
+
+- [Overall IT policy page](https://www.uab.edu/it/home/policies).
+- [Acceptable Use Policy](https://secure4.compliancebridge.com/uab/portal/getdoc.php?file=300).
+- [Data Protection and Security Policy](https://secure4.compliancebridge.com/uab/portal/getdoc.php?file=302).
+- [Data Access Policy](https://secure4.compliancebridge.com/uab/portal/getdoc.php?file=301).
+- [Data Classification](https://www.uab.edu/it/home/policies/data-classification/classification-overview).

docs/data_management/res/cheaha_project_directory.csv

@@ -7,7 +7,9 @@ Hardware capital expenses,beyond default quota,,,up to default quota
 Periodically check group membership,Yes ✔️,Yes ✔️,,
 Grant access to users to a specific folder,Yes ✔️,Yes ✔️,,
 Oversee and update access controls,Yes ✔️,Yes ✔️,,
-"Data Management and Storage:<br>&nbsp;  - Administrative (authorization and access) <br> &nbsp; - Technical (encryption, firewall, etc.) <br> &nbsp;  - Physical(locks, cameras, sign-ins, etc.)", <br>Yes ✔️,,,<br><br>Yes ✔️ <br>Yes ✔️
+"Data Management and Storage: <br> Administrative (authorization and access)",Yes ✔️,,,
+"Data Management and Storage: <br> Technical (encryption, firewall, etc.)" ,,,,Yes ✔️
+"Data Management and Storage: <br> Physical (locks, cameras, sign-ins, etc.)" ,,,,Yes ✔️
 Request a project directory,Yes ✔️,,,
 Obtaining security exceptions when required,Yes ✔️,,,
 Creating and maintaining metadata,Yes ✔️,,,