Hey folks.
I am getting a small taste of data management in an enterprise GIS environemtn. one of the issues is how a large geodatabase can be structured to keep data organized instead of a simple laundry list of coverages.
I am interested to know if anyone has attacked this in a GRASS data structure.
I am thinking a similar approach as is done is ArcSDE might be the most straight forward. have each datasource (eg topographic 1:250K dataset) as a seprate user. so if you had 7 seprate sources of similar data then you would have 7 diferent mapsets.
The next question is now that I have 7 different mapsets or user spaces can I apply seprate permissions to each? Eg Read, Write, Delete. If so is this set within grass or per user account. Do I need 7 linux user accounts and manage permissions by owners and groups? Some good resources for understand this part better would be good.
Essentialy I am looking to develop a network of users that access a GRASS dataset and can read from multiple users but only write to their own mapsets or a common group mapset.
If this is mentioned in the GRASS Manual please provide page numbers as I did not see this covered, but I could be thinking incorectly.
Anyhow if there are any white papers on best data management practices in GRASS let me know.
Cheers