Basic Course Creation Workflow¶
This page describes the basic workflow for creating new content in Lovelace. All phases are described in more detail in their respective chapters in the guide.
1. Course and Instance Model¶
Lovelace manages courses in two layers:
course instances. Course is the base course which contains basic details such as course code and responsible teacher. The base course is an abstract root node for course instances. A course instance is the equivalent of a course in WebOodi, i.e. it is a singular period of instruction where students can sign up, and typically teachers will have a new one every year.
When teachers manage courses in Lovelace, they usually manage course instances. You can find more details about course instances -- WARNING: BROKEN LINK --here.
2. Opening the Admin Panel¶
Lovelace uses Django Admin Site to manage content. It is a bit crude, but clear enough. Open it from the user menu on the top-right by selecting Teacher tools.
3. Creating a Course Instance¶
You can manage your
course instancesby choosing Course Instances from the admin site menu. For now we're going to disregard the last portion of the form (since we don't have content yet!), and focus on the basic information:
First we need a name for the instance. Course instance names are unique across the entire system. Typically they should be named after the course and include timing information, e.g. "Introduction to Donkeys Autumn 2018" - students will be using this title to figure out which instance they should
enrollto. If the course is only given in one language, remember to use the name_fi field - regardless of the actual language.
After giving your instance a name, link to a course from the course dropdown menu. You can only create instances for courses where you are the
responsible teacher. The rest of the fields are optional but can be filled at this point if you want. The email address here should be the primary contact email for your course (e.g. a list that as all members of the teaching staff as recipients). We're going to leave the
front pageunset for now since there's no content to show.
If start and end times are given, the course instance is considered active within that time span. You can make the course always active by checking "Force this instance active". Starting date is also used for sorting course instances in the Lovelace course index page. You can also choose whether students can see this instance. This is useful for hiding courses that are not set up yet, and also to clean up old instances from the course index.
Finally you can choose whether students can freely sign up for the course, or if they need to be accepted by you from the enrollment management interface.
4. Creating Pages¶
content pagesare called
Lecture pagesin the system. These are pages that are capable of
embeddingother types of pages. Create a new lecture page. When naming pages, two things should be kept in mind: names are unique across the entire system, and Finnish is always the primary field to use if you plan on giving your course in only one language.
Other types of content are linked to lecture pages through links in the page
markup. More information about markup can be found from here. For now let's just write something in the content field. The first page will be your course front page.
You should also create a second page for the next step.
5. Linking Pages to Course Instances¶
Go back to managing your
course instance. You can select your freshly created
front pageas the course front page from the dropdown menu. After that, in the Instance outline section there's a box for selecting
contentswhich should be empty if this is your first course. Click the green plus on the right of the box to create a new content graph - an object that links content pages to your course index. This will open a new window with a form for creating a
The most important field are Content and Ordinal number - the former determines the which content page to show while the latter determines the order of links in the course index. If you choose a Parentnode, the page will be shown in the index as a sub page of the parent page (indented).
You can set a deadline for the entire page. This affects any exercises that have been embedded into the page. If the deadline has passed, students will be shown a message about it with every incompleted exercise on the page. Here you can also choose whether to show this content to students by checking/unchecking the box.
After you press save, the content will be shown in the contents box with its ordinal number and
revision(which should be "newest"). This box will eventually contain more items - including items that may belong to different courses - but only the ones that are selected will actually be linked to the course instance. You can change these selections by clicking while holding down Ctrl.
If you set a front page from the front page field in the course instance form and save the instance, the front page will automatically be added to the contents box with the special ordinal number 0.
6. Creating Pages with Embedded Content¶
Most of the time you want to include pictures, files, videos and of course exercises in your pages. Content is
markupin the page content. An important point to remember is that the embedded content must exist at the time you save the parent content. This is in part due to implementation details, and in part to catch typos in link names. A typical workflow is to write the content in a separate text editor, then create the embedded objects and finally create the parent page.
Embedded contents include the following categories in the admin interface:
- Checkbox exercises
- File upload exercises
- Multiple choice exercises
- Repeated template exercises
- Text field exercises
- Video links
When creating embedded objects, a recommended naming scheme is to include a
course prefix. The amount of embedded content is vastly higher than the amount of pages in courses across the system, and course prefixes help avoid name conflicts. They also make it easier to distinguish between contents of different courses for teachers who have more than one.
Furthermore, when naming files, images and videos it is recommended to use a notation similar to the
slugsthat are generated from page names: all lowercase with all non-alphanumeric characters replaced by dashes. For instance, the course instance explanation image is called
You can find more information about the content model from -- WARNING: BROKEN LINK --here.
Give feedback on this content
Comments about this material