On Wed, 2010-09-22 at 12:10 +0800, maning sambale wrote: > Any real world cases for this?
Imagine the following scenario: * 50 ~ 70 digitizers * 5 QA * 1 Manager Each QA has 10 digitizers assigned. After all the data is validated, the manager merges it and generates the geodb. All users work against the same DB, most of them linked. This causes disconnections, duplicated data, and lots of random errors. Also, they can't be forced to work on different DB's because they are all working on the same project, at the same time. This is the real scenario of GISWorking (http://www.gisworking.com/), a company we are working with. It would be perfect to have smaller groups (ideally 1 person), working against separated databases, but that can be synchronized with the rest of the data when needed. Then each QA merges data from the people he supervises. After it's validated the manager merges the complete dataset, and generates the final "product". I don't know if this it's the exact same case, but we are working on it with a similar approach. -- Fabio R. Panettieri Lead Software Engineer http://www.xoomcode.com _______________________________________________ Discuss mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/discuss
