Lernanta Workflow (outdated)
NOTE: THIS PAGE IS OUTDATED
Lets try to summarize some ideas about the future Lernanta's workflow. This is a really preliminary draft, so feel free to improve it.
If there have never being a course like the one you want to run, you will need to start by creating a private draft. This initial step will allow you to start preparing the course content without announcing it to the world. A private draft will not be listed anywhere, but it will be associated with a private, non-obvious url that you can share in order to obtain opinions, and collaborate with a limited number of people. The existence of private drafts fulfills the secondary role of providing a sandbox for new users.
Once you feel comfortable enough with the course prototype or draft that you have created, you can allow more people to contribute by making the draft public. Public drafts will be listed in the web site so anyone can find them.
If you consider that the course prototype is ready to be run by someone (who will be probably yourself the first time) you will publish it as a ready course prototype.
Any course prototype (ready course prototypes, public drafts or even a private draft if the author sends you the link) can be used as the starting point for the preparation of another course. When you clone a prototype it will automatically become a new private draft. In the future we could include ways to import content from a course prototype into another so it will be possible to prepare a course based on the prototypes of several P2PU courses.
Ready course prototypes can be used to create a course instance, which is how one actually runs a course. Unlike a course prototype, course instances are associated with the list of people participating in the course, and the date in which the course instance will start to run. In order to allow participants to interact with the course content and continually reshape it, the course instance will be associated with a ready course prototype cloned from the original prototype that was used to create the course instance. Course instances are essentially subclasses of the course prototypes, wrapping them in additional metadata.
When a course instance is initially cloned in order to be run, it will be set to status upcoming. It will be listed along with other upcoming courses for people browsing the website.
When a course start date arrives, its status is changed to running. This indicates to people that the course is active and "in session".
Sometimes course organizers will want to open a course for sign up right away, and other times they will want to open sign up on a specific day. Similarly, once a course is running, course organizers might or might not want to allow new sign ups. No matter if a course is upcoming or running, it may be either open for signup or closed for sign-up.
When a course is complete, its status is changed to archived. In this state the course is still accessible for people to browse, but not for adding new content.