As an aside. Just in case anyone was wondering about Barrie's comment "raising a task". Believe it ot not, we have a formal "Problem Tracking System" on FreeBMD, this allows members of the FreeBMD Project Team to raise tasks for action by the most appropriate members of the Team. Some of these tasks come from discussions on the FreeBMD-Discuss list or ideas mailed in to members of the Team. Allan Raymond [email protected] http://www.btinternet.com/~allan_raymond/Monarchies_of_Europe.htm FreeBMD - putting birth marriages and deaths on the Internet http://FreeBMD.rootsweb.com/ ----- Original Message ----- From: "Archer Barrie" <[email protected]> To: <[email protected]> Sent: 05 October 2001 09:48 Subject: RE: Syndicate leaders owning data > I tend to agree with Ian - is there some reason why a > transcriber *and* his > or her coordinator can't jointly own data? I am sure Dave M > will correct us > if Ian and I have missed the point, but I wouldn't have a > problem with my > coordinator altering my uploaded files (if he had the time) - > as I see it, it > cuts down the number of people to blame (and I use the word 'blame' > advisedly) when an individual record is wrong! It would also > cut the amount > of time we spend chasing AWOL volunteers. .... > Virginia I have been thinking for a while that a facility like this would be useful. The question of who "owns" the data is a bit philosophical. The files are currently stored in a way that is related to the user id and in that sense the *computer* ownership is with the user id. As such it is relatively easy (in a programming sense) to limit access to that user id. To allow access to selected other user ids (presumably a user who is marked as a co-ordinator for the syndicate that the user belongs to - IYSWIM) would be possible but would take a little thought and effort. I believe it would be important to maintain an audit log for such activities. This would allow us to find out who modified a file and when. This not so much for the usual security reason (finding someone to blame - I am a bit of a security cynic!) but just so we don't have to rely on grey cells when a user asks why one of their files has changed! I think someone should raise a task. Someone who would be prepared to test the facility! Barrie