Ticket #1111 (closed story: wontfix)

Opened 13 years ago

Last modified 12 years ago

First author can disable collaborative authoring

Reported by: hans Owned by: anonymous
Priority: major Milestone:
Component: generic Version:
Keywords: Cc:
Time planned: Time remaining:
Time spent:

Description (last modified by hans) (diff)

Each learning resource, activity and tool has a checkbox "Other users can't edit this resource". This checkbox will be the last one in the additional information (or edit) page. It is displayed only for the first author.

In the content section we should also display help text "This setting will disable assigned groups."

If this checkbox is marked, other users will not see edit link and will not be able to edit the document (even if they know the URL of the edit page). In the content section this checkbox will also set "Assigned group" to "Not assigned to any group" and disable the "Assigned group" radioboxes.

http://lemill.org/trac/attachment/ticket/1111/restrictions.png?format=raw

Attachments

restrictions.png (49.1 KB) - added by hans 13 years ago.

Change History

Changed 13 years ago by hans

comment:1 Changed 13 years ago by hans

  • Description modified (diff)

comment:2 Changed 13 years ago by tarmo

Users will be confused if we just hide the Edit links for some resources. Remember, no hiding, but disabling. We should probably show a page that says something like "This author has decided that this resource does not benefit from collaborative authoring. Contact the author (link) to discuss this."

But in general I think this is a bad idea: Some people will just start using LeMill as their personal storage environment and not allow collaboration at all.

What we should do is decide for each resource type, whether it benefits from collaborative authoring, and use that. For example, Presentations, Tips for Use, and Member profiles aren't collaboratively editable.

comment:3 Changed 12 years ago by hans

  • Status changed from new to closed
  • Resolution set to wontfix

This story is in conflict with current design ideas.

Note: See TracTickets for help on using tickets.