Good day, all. Haven't we been here sometime recently before? I am sure John Pain is also smiling smugly - either that or fuming from the ears. John is my syndicate coordinator and has a record of my submitter ID and my password, which is a password that is so easily broken by those who KNOW me that I never, ever use it in my workplace (for the government). I transcribe and send the files to him as well as uploading them, and he checks against originals for my underscores and asterisks. He then has the facility to correct by replacement on F/BMD the files I uploaded. They do not get loaded twice as that would be most misleading, but the files searchable on the database are as correct as can be with four eyes looking at them. When this was discussed previously we as a syndicate - well, I was at least, and John's responses had the same tone as my thoughts - felt a little put down. We signed up to get the data accessible. This is a truly charitable project and if Dave's reassurances regarding retention of data from *deleted* files is correct then who *@%* gives a care as to who has access to the data if those people are seen by the project to be reliable enough to be syndicate coordinators? I don't really want aan apology from anyone for previous remarks about password security, I can be as paranoid as anyone, but please accept that the previous paranoia was just that. And try asking John if you want a testing of such a system as he and his syndicate already practise!!! Best wishes Anne Cruise Archer Barrie wrote: > > > 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