Reservation/

From Dokeos

Jump to: navigation, search

The reservation-system that we will create will add a complete reservation-toolset to Dokeos. You must see reservations in a wide variety. It is not only for making appointments but it can also be used to reserve classrooms, multimedia equipment, computers, etc. Our aim is to make our tool as FURPS (flexible, usable, reliable, performance & secure) as possible. The tool will be platform-based and not course-based (CMS-system). At the bottom we list a few possible expansions which we have been thinking about so far. Feel free to contribute other suggestions.


Contents

User Perspective

One of our main priorities is making the system as user-friendly as possible. This means that the user will not have to go through a bunch of chaotic steps before his subscription is actually done. It must be simple and practical.

The user will have to follow a simple path to reserve a certain item. He has to go to “My Reservations" where he can select a category (eg. “classrooms") and then select the item (eg. “classroom number 20") he needs. Finally the available reservations for that item will be visible and the user can select one (eg. “from 14:30 till 15:30u on the 23th of March 2006") that fits his time-shedule.

Next to categories, the “My Reservations"-page also lists all “item+subcription"-pairs which are reserved by the user and are not over. Those pairs also have a “accepted-status". If the admin has accepted the subscription or if auto-accept is on for the reservation, the accepted-status will be “accepted", otherwise it will be “waiting for approval".

Admin Perspective

The admin should off course get the same amount of “easiness" as a regular user but his task is more profound. There are 3 admin-sections: an item manager, a category manager and a reservation manager.

The category manager and item manager will, in the first release, only be accessible for the platform-admin. The item manager will work with a new rights-system that will bind groups (“class")+ rights to the items. A group can consist of a few teachers that may create reservations for the item.

An item consists of a name, a description and a category . The platform-admin will have the possibility to add, edit and erase items.

A category is a general description for a group of items. Eg. “classrooms" is a category but “classroom number 20" is an item. The platform-admin will have the possibility to add, edit and erase categories.

Reservations are active until the “end date" or “subscribe until"-date has passed or until the maximum amount of subscribers (default = 1) is reached. The user with sufficient rights may select an item and set up a reservation for it.

Expansions

  • Linking items to courses if needed.
  • Rights on category-level. (eg. that certain groups may only create items in a certain category – and not that only the platform-admin can add new items like now)
  • Mail subscribers on “action". (delete reservation, decline/accept subscription, …)
  • Recurrence.
  • “blackout time"-concept: making items unavailable for a certain amount of time.
  • Set a minimal amount of users for reservations.
  • Make it possible for users to reserve items via “My Agenda".
  • See your personal item-subscriptions in “My Agenda".

Use Cases

You can find the use cases here

Personal tools