Skip to content

Have some natural order to course actions #8251

Open
@novoselt

Description

@novoselt

To me it seems pretty random and not optimal at the moment. I've tried to think of what I would find convenient without knowing internal details (but with some anticipation of fast start up and copying):

Image

Reasons:

  1. Pretty much every instructor has to export grades. It may not be a very frequent action, but quite possible it happens after every assignment, not just in the very end of the course.
  2. Adding students is also a very common operation. Although I don't see a good reason to NOT catch up a freshly added student right away, even without asking any questions. If that was done, this action would be a no-op.
  3. Terminal commands may not be used by some instructors, but for others they may be very handy and frequently used (a speculation...)
  4. Start/stop all is quite important now, but if starting time is small, it is not needed. Maybe there are still benefits to bulk stopping for freeing up seats...
  5. Resending email invites is somewhat natural, but if students didn't get the first message, chances are they will not get the second one either. And there is no important information there.
  6. Knowing that you have to reconfigure requires extensive knowledge. And if there are clear instructions that something requires reconfiguring, it might as well start automatically.
  7. The
  8. last
  9. three are highly non-intuitive. Why would anyone want to do that? At the moment - for copying an existing course, but it we had a better system/interface for that, these actions are redundant.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions