Organization of your Data / Dataset Hierarchy?

Computer Hardware & Server Infrastructure Builds
1

Hello,

at the moment I am on the definition of the structure of my datasets and how to organize my data for the private family NAS. For this I am trying to follow the approach to have top-level datasets depending on their data priority.

However, it is hard to find a good concept and at the moment I am struggling with the question on how to handle different users in the folder/dataset structure.
For example, should I place photos inside
/tank/ds_prio1/photos/user1 and /tank/ds_prio1/photos/user2
or would it be better to have something like
/tank/ds_prio1/user1/photos and /tank/ds_prio1/user2/photos?

Could you, maybe, give some examples of your dataset structure and how you handle different users in your dataset/folder structure?

If there are family photos stored, how to handle photos all users shall have access to? From the content a single ‘family_photos’ dataset would fit best and sharing this dataset via SMB with all family members. However, if everyone has read/write access to store & view the photos there is a chance that a user deletes/modifies photos by fault. For sure, after a fault we can use snapshots and backups to recover the data, but is there any other good practive on how to handle datasets on which multiple users shall have read/write access?

I would really, really be interested on details on how you organize the datasets/folders on your servers.

Thanks a lot,

Thomas

2

For myself I am the only one with access to my NAS so the structure is very simple.

├── LTS_Video
│   ├── Build_Proxy_Clips.sh
│   ├── Channel_Assets
│   ├── Cloud_data_responeability.mov
│   ├── CNWR_Building_Tour.mov
│   ├── Convert_MP4_to_MOV_PCM.sh
│   ├── Create_Random.sh
│   ├── Editing_Installers
│   ├── LTS_April_2023.drb
│   ├── Production
│   ├── Shorts
│   ├── Studio_Computer_OBS
│   ├── test
│   ├── test.mov
│   └── VMWare_Alternatives.mov
├── LTS_Video_Archive
│   ├── Archive
│   ├── Music
│   └── Rusty_Test
└── Tom_Computer_Backup
    ├── Create_Random.sh
    ├── DebianXO.ova
    ├── Duplicity
    ├── Emu
    ├── Googletakeout-20221229T134405Z-001
    ├── ISO_Storage
    ├── OLD_Duplicity
    ├── Old_Marcus_Comptuer_Stuff_Oct_2022
    ├── Random
    ├── test
    ├── WIndows_10_Feb_2022.ova
    ├── WIndows 10.ova
    └── WIndows_XP_Feb_2022.ova

For my business it’s structured based on the data purpose. We have a dataset for XEN hypervisor storage and then sub datasets for each type, production, lab, VDI, backups.

For photos I use Synology Photos.