Just a suggestion from experience and practical customer applications. Data usually lives longer than a project or could cross many projects/departments. I usually separate my data libraries away from any projects or departments and then assign the security as interest in the data grows (morphs). I document who the owns the data such as using the description to put in business owner name for the folder or library for a quick reference so that I can contact them for approval grants of access of the data and for auditing. If you move the data under projects or departments, you run the risk of lots of duplicate data, stale data and inaccurate reporting, and hard to manage security as well. I just try to think of each data library as like a datamart and treat it as such.
- Data
- library
- library2
-etc
projects (cross dept)
-project
-project2
department (only)
- branch or group
- branch
- project
- project2
... View more