Project

General

Profile

Bug #3270

Document: Dropbox delete file: rename it;

Added by Ludwig Theunis over 8 years ago. Updated over 7 years ago.

Status:
Bug resolved
Priority:
Normal
Assignee:
-
Start date:
17/04/2011
Due date:
% Done:

0%

Estimated time:
Complexity:
Normal

Description

In the dropbox you can set rights to students to be able to add, edit or delete documents.

If you give a student only the right to add something in the dropbox, he still is able to delete the publication trough the repository.

I think this is something for the repository but since it is related to the course I post it here...

History

#1

Updated by Nathalie Blocry over 8 years ago

I don't think this is realy a bug.dropbox is just a publication category in the documents tool. It is logical that a student can delete/remove the publication from the repository since that is the case with all publications.

for handing in assignments without worrying about students deleting them or not having enough disk-quota we should probably focus on the assignment tool and forget about the dropbox.

#2

Updated by Ludwig Theunis over 8 years ago

It's not only a bug in the dropbox, but it's a bug in the documents module of the weblcms. Because you can set rights to each 'folder' or 'file' not only to the 'dropbox'.

But the users can 'override' the right to 'delete' when he or she is the owner. I agree that we don't have to think in terms of 'dropbox' anymore. But the document has now a lot more possibility's in sharing content and setting rights to it.

In my opinion it should not be possible to delete the object from within the repository, when the place where the object is published does not allow that. Otherwise the right has no effect.

Our more in detail: it should not be possible to delete a publication of an object when the location of the publication does not allow that. And then it should not be possible to delete an object if not all publications are deleted....

I think this is a big problem and not that simple to solve.

Perhaps it is better that everything published in a course should be stored in the repository of the course creator. But that also give problems....

#3

Updated by Sven Vanpoucke over 8 years ago

The document owner can always delete his files (the publication owner has ALL the rights on the publication. The delete / edit right are there so you can give other people access to delete / edit your publications). Since we do not have a dropbox anymore it's not an issue since a document owner must have the opportunity to delete his own files at every time. We are creating an assignment module which does the exact things that you need. It hands out the document to the assignment creator and can not be deleted / edited anymore.

#4

Updated by Ludwig Theunis over 8 years ago

In that case the dropbox should be removed from the system because in does not do what the name suggests. You cannot drop a file or something else in the course with this 'dropbox' functionality. You can only show something in a course, and that is not what the dropbox was about in the first place...
Good thing if the assignment tool takes over this kind of interaction of students with the course. Hope that it does just that and also as simple as in the old 'dropbox'.

I can't wait to test this.... ;-)

#5

Updated by Ludwig Theunis over 8 years ago

So the assignment tool will become an extra tool in the weblcms?

#6

Updated by Sven Vanpoucke over 8 years ago

Yes it will be so i think this issue can be closed?

#7

Updated by Ludwig Theunis over 8 years ago

When 'Dropbox' will be removed or renamed to something that makes sense, then it can... ;-)

#8

Updated by Anonymous over 8 years ago

  • Status changed from New to Feature implemented

is this still an issue?

#9

Updated by Anonymous over 8 years ago

  • Status changed from Feature implemented to Needs more info
#10

Updated by Koen Favere almost 8 years ago

  • Subject changed from Dropbox delete file. to Document: Dropbox delete file: rename it;
#11

Updated by Stefaan Vanbillemont over 7 years ago

  • Target version changed from 2.1.0 to Backlog (default)
#12

Updated by Anthony Hurst over 7 years ago

  • Status changed from Needs more info to Bug resolved

Also available in: Atom PDF