Hi all, Still thinking about deletion of a user vs. keep user forever.
The reason I wanted to delete a user on a platform but keep its content is mainly so login names can be reused and having a users list not becoming to long so it is workable. Keeping all users on the platform would mean the users list would get bigger every year. But if I think about it perhaps it is better to keep the user information, and still preventing the userlist to get bigger and release the username. This could be achieved with an additional users status: 'Archived'. Switching a user to this status will automatically, change the username of the user to for example 'Archive'+ the user_id, so the username becomes free for reuse. And additional al user accounts with status 'archived' never to be visible in de userslist for teachers etc. The platform admin can search this users in the users admin, then reactivate the account and choose a new user/login name. This way perhaps it is not necessary to delete users, because these users aren't visible any more, the username's are not taken for ever and become available, all objects are kept, and you can see who published it.... Greetings, Ludwig 2011/4/2 Frederik Questier <frede...@questier.com> > Dear devs, > > I (and without a doubt many others) certainly need the option of > keeping all content when students or teachers leave the organisation. > How many arguments do you want? ;) > > 1. In current modern education we ask students to create products that > are to be used and extended by next generations of students. > > 2. It's important to remember the name of the authors of these > products, for e.g. copyright reasons. (Even all creative commons > licenses now require attribution). > > 3. Quality monitoring rules demand that universities and colleges keep > the materials that students have produced during x years, to show them > when quality commissions visits the organization. > > 4. With lifelong learning it's becoming more and more likely that > students return to the learning institution. It's nice if you can just > reactivate their account. > > 5. Keeping teaching materials when teachers leave the organisation, > that's a no brainer for everybody, I guess. > > Like I see on some other platforms, I want to see deactivated users as: > Name (deactivated user) > where relevant, e.g. in the author field of their contents. > > If others want a full delete, we should provide optional choices: > - deactivate user > - delete user with it's content (warning: this can corrupt forum > discussions, wiki's, ...) > > And maybe an admin script "delete contents from users deactived since > [show date picker]" > > Kind regards > > -- > Prof. dr. Frederik Questier > http://questier.com > Vrije Universiteit Brussel > > > > Message: 2 > > Date: Fri, 01 Apr 2011 18:46:08 +0200 > > From: Hans De Bisschop <hans.de.bissc...@ehb.be> > > Subject: Re: [chamilo-dev] Deleting Users > > To: Chamilo dev list <dev@lists.chamilo.org> > > Message-ID: <4d960150.2060...@ehb.be> > > Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" > > > > Hi Ludwig, > > > > I doubt one scenario has to exclude the other. Both should be able to > > coexist. The reason I'm in favour of also implementing complete deletion > > is because of the simple fact that it will no doubt be a necessity in > > some environments. For us at Erasmus I'm leaning more towards > > deactivation instead of plain deletion, but there might be issues with > > that on other levels ... something for the "other people" to determine. > > > > Best regards, > > Hans > > > > On 1/04/2011 9:30, Ludwig Theunis wrote: > >> Hi all, > >> > >> I'me a little bit worried about that deleting a user would also imply > >> that also all his objects will be deleted. > >> > >> Because this would give problems, depending on how things are organized. > >> > >> For example if you have a course, on which two teachers, course > >> administrators, are working to getter, both deliver content to the > >> course. As I understand the system, the object published in a course > >> is originated in the repository of the user creating them. > >> At some point one of the course administrator leaves, (he is retiring > >> or even worse, he died in an accident :-), I think its only normal > >> the user will be delete from the platform. So everything he ever > >> contributed will be deleted??? > >> > >> Is this correct... > >> > >> I think when a user is deleted the repository of the user would have > >> to stay, only, the reference to the user would have to be deleted. > >> > >> For us this is an very importing behavior because we use the platform > >> to let users collaborate. Users can contribute to the system at a lot > >> of places, he/she write's an evaluation of an particular event for > >> example; So it can be used in the future. When the user is deleted the > >> infor should stay. > >> > >> keeping all users for ever on the platform is also a concept I don't > >> like, because than at one point you will get out of readable login > >> names that students can keep in there minds. > >> > >> regards, > >> > >> Ludwig > >> > >> 2011/4/1 Hans De Bisschop <hans.de.bissc...@ehb.be > >> <mailto:hans.de.bissc...@ehb.be>> > >> > >> Hi all, > >> > >> Pure looking at things structurally when deleting a user the > >> following should happen: > >> > >> 1. Unlink all his objects > >> 2. Delete all his objects (perhaps take a CPO export of his > >> entire repository beforehand as a final backup?) > >> 3. Contact all applications / packages with a request to delete > >> all references to user x (which isn't all that unsimilar > >> from the object unlink) > >> > >> If and when all that has been implemented everywhere, the user > >> itself could be deleted and there shouldn't be any problems. > >> > >> Practically speaking it's a loooooooooot of checks that need to be > >> executed and even more statements that need to be executed to > >> actually make it all happen. Te easy way out is to not actually > >> delete the user but deactivate him. That might work in some cases, > >> depending on your company's policy, but it does not remove the > >> need for an actual delete in those cases where it is explicitly > >> needed and/or requested. > >> > >> Best regards, > >> Hans > >> > >> > >> On 01/04/2011 08:56, Sven Vanpoucke wrote: > >>> Hello All > >>> > >>> I would like to discuss the deletion of a users in chamilo 2.0. > >>> At this point the user his content objects are NOT removed > >>> because they would cause a lot of issues where the content > >>> objects are published or used in other content objects. It's > >>> important that we define some kind of procedure that should > >>> happen when a user gets deleted. What happens with his content > >>> objects, what happens with the references to the user id's in all > >>> the other tables (tracking, subscriptions etc...).? > >>> > >>> At this point i'm pretty sure that when you delete a user, the > >>> system will break on some places because of the display for the > >>> username without the check if the user still exists. I > >>> implemented a new function in the userdatamanager which gets the > >>> user's fullname by user id which returns the fullname if the user > >>> exists and User unknown if the user doesn't exist anymore but i > >>> didn't have the time / resources yet to change this feature on > >>> the entire platform. If you are developing new features i would > >>> ask you to now use this function, or at least check if the user > >>> still exists in the platform to avoid breakage. > > _______________________________________________ > Dev mailing list > Dev@lists.chamilo.org > http://lists.chamilo.org/listinfo/dev >
_______________________________________________ Dev mailing list Dev@lists.chamilo.org http://lists.chamilo.org/listinfo/dev
