Usability #2053
Delete button in My Publications
0%
Description
If you go into "My Publications", there are "Delete" buttons for each published CO.
Because it's never possible to delete a published CO, maybe it's interesting to replace Delete by Unlink?
Related issues
Associated revisions
History
Updated by Anonymous over 11 years ago
- Priority changed from Normal to Urgent
It should be possible to perform actions on multiple objects (now actions have to be performed one by one) :
- unlink and delete (publication)
- delete
Updated by Stefaan Vanbillemont about 11 years ago
- Project changed from Chamilo LCMS Connect to Repository
- Category deleted (
4)
Updated by Anonymous about 11 years ago
Updated by Anonymous about 11 years ago
- Status changed from New to Needs more info
- Assignee set to Anonymous
About the Unlinking idea... you are in fact in a Publication browser, so you are deleting the publication, not the object... you must be in the actual repository to perform a delete of the object... seems logical to me...
any other opinions?
Updated by Koen Favere about 11 years ago
from a programmer's / experienced user's point-of-view you are right.
from a average user's point-of-view we experienced in our training that it's quite confusing
in the repository there is also the possibility to 'unlink' a content object. in accordance with this 'unlink' might be more appropriate to use the same in the course module?
Updated by Anonymous about 11 years ago
I totally agree with the average users point of view, but when you try to keep a clean line in development, unlinking and deleting a link are two different things. Delete will just remove this one link, while unlinking will remove ALL links to the object.
I think naming the delete method unlink will end up confusing developpers as well as they expect to remove each link instead of this single one... don't know what is best though.
Updated by Stefaan Vanbillemont about 11 years ago
- Status changed from Needs more info to Feature implemented
Fix fill in blanks errors see #2053
- Use a hash of the value (sha1) instead of doing value="my text "