From: Benny M. <ben...@gm...> - 2009-11-20 20:58:48
|
2009/11/20 E.Genssmann <eck...@on...>: > > Great idea! I would start using it immediately! > I would recommend to include a role-based security concept, paired with some > basic workflow functionality: > The roles could be Read-only-users ("visitors"), "contributors" and "Owners" > for each database: > Visitors will not be able to change or add, but they should see all the data > (including living people), only "private" data are not visible. A website > (like Narrative website) could handle all the "living-people" privacy issue > for all of the web-users, while people granted read access should be treated > differently. > "Contributors" should be able to add or change. I would prefer that all > those changes would create a notification to the owner. He/she then should > check into the information and hit a button to approve this data (meaning > making those data visible to all). Only those approved data should go into > publishing e.g. in reports, next version of web sites etc. > Only the owner(s) should have the final decision what data will be included > and they need to have the freedom to reject some stuff (before it made its > way into your valuable data, creating some potential damage). > > A more technical concern: It will become much more complex as we then will > see people using all flavours of Linux, UNIX, all versions of Windows, Mac, > all existing web browsers, etc... manipulating the same database ... > > But in general, this solution would be a major step forward! Looking forward > to see it go live hopefully soon. > > Best regards, > Eckhard > Actually, I believe a mail was send here to let us know the present state has been put on the web by Doug and Kathy, as a sort of sneak peak: http://gramps-connect.org/ It even has tab pages as gramps: http://gramps-connect.org/person/NDNT6D8O7D3QRKP07N/#tab-events. Export to sql database via a django setup will be present in version 3.2, but will probably not yet be for the faint of hearted. Benny |