Are you looking for an alternative to (1)ESRI's versioning, (2)ESRI's disconnected editing, or a mix of both (3)git like? the scenario that you described first was more like (2), but this one fits (1).
I would love to see something like (3), but truth of the matter, AFAIK, there is nothing like that implemented for geo (yet). On Sep 22, 2010, at 9:00 AM, discuss-requ...@lists.osgeo.org wrote: > 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. > _______________________________________________ Discuss mailing list Discuss@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/discuss