| |
Seven
Registered: Jan 2002
Posts: 202 |
Locked Entries
I'm not sure if this is a bug, or a design flaw =) ...
When I lock a group, others can still add members to it.
Shouldn't it be possible to prevent others from adding anything to that group, be it members or releases or anything else?
Also, it would be useful to lock the releases of a group _with_ the group so I won't have to go through all the releases and set the maintainer? |
|
... 30 posts hidden. Click here to view all posts....
|
| |
Seven
Registered: Jan 2002
Posts: 202 |
I agree, it makes no sense if someone locks everything he adds.
Locking should only be done by people who have a definite grasp on what was/is going on in a group, e.g. people lock their personal entry, group members/leaders lock their own group etc.
Why would I set myself as maintainer for e.g. the Smash Design entry (other than to show them how much I like them ;))?
|
| |
Steppe
Registered: Jan 2002
Posts: 1510 |
My two cents to commander:
You're clearly underestimating the human factor here, with this mass of contributors this database is prone to have lots of errors. The point is not to add information _fast_ but to do it correctly!
I'd therefore als prefer the idea of the maintainer getting notified by e-mail if there was a change to his locked entry in order for him to aprove it. This would make _fast_ adding possible and at the same time ensure correctness. I don't consider the people discussing here to be *too* representative for the whole scene, there might be a lot of lazy MFs out there that just come here only once, add their group, lock it and forget about it for the rest of the year. Does anyone agree on that eventually?
So:
Complete Locking: No, unless the person wishing to completely lock the entry gets approved by the database maintainers and clearly states that the entry is finished, i.e. all the members/credits/releases are complete.
E-Mail Notification to aprove changes _before_ they apply: Yes, if that is practicable and wouldn't be too much of a burden for the NoName guys, that means the notication task can be automated by the database. |
| |
Commander
Account closed
Registered: Jan 2002
Posts: 106 |
Nice idea, Steppe!
|
| |
Perff
Administrator
Posts: 1679 |
I see the need for some changes in the way the maintainer thing works.
I've read what you have to say and have some comments.
It's very easy to notify either by email or the CSDb msg system the maintainers of a record when something is changes, but to make it so that the maintainers need to confirm the change before it is made for real is not so easy.
My sugestion is that people edit like they do now, and then the maintainers can go back and change back if someone make some crap.
Maintainers can then also choose to lock an entry 100% or keep it open (with notifications on edits)
If someone wan't something chaned in a 100% locked entry they should contact the maintainers of that record.
? |
| |
CreaMD
Registered: Dec 2001
Posts: 3057 |
Sounds reasonable to me.
roman |
| |
Moloch
Registered: Jan 2002
Posts: 2928 |
I've locked entries for groups I was never a member of - why? Because I'm one of the only guys entering NTSC (mainly demo group) information. From experience most PAL sceners didn't/don't have a clue about the former NTSC demo scene and I don't want people screwing with information I know is correct.
I was a staff member on nearly every NTSC demo magazine and friends (I use that term loosely - Seven is correct about the attitude issues in the scene) with nearly everyone ever active. Plus, as people that know me can attest, I was a major group hopper - changing groups every couple of months.
I agree with some of the ideas here - the maintainer should have final say and an email system of sorts should be included for information entered by a non-maintainer.
|
| Previous - 1 | 2 | 3 | 4 - Next |
