| Target release | Sept-16 (prefereably June-16) |
|---|---|
| User Story | SWIK-191 Deck editor |
| Document status | DRAFT |
| Date | |
| Document owner | |
| Designer | Klaas Andries de Graaf |
| Developers | Benjamin Wulff |
| QA | |
| Work Package deliverable | D4.3: First stable version of SlideWiki usable, accessible and ubiquitous user interface WP 2, 3, 4 |
Related tasks in JIRA:
Summary
- As a user I want to edit the structure and properties of a presentation deck.
Background and goals
Editing the deck comprises of 2 areas of functionality:
1 Adding and editing meta data associated with the deck
Users need to be able to add the required meta-data (e.g. title, language, author) when creating a new deck and then add or edit metadata once a deck has been created.
2 Changing the structure of the deck by adding or removing slides and sections.
Feedback from Hasanov has highlighted importance for simple and transparent tools for editing the deck structure.
Assumptions
Requirements
| # | Title | Task User Story (As an author... | Importance | Notes | JIRA |
|---|---|---|---|---|---|
| 1 | Edit Meta | When I select a deck, I want to be able to edit the metadata | Must have |
| |
| 2 | Add meta | When I create a new deck, I want to add the required minimum meta data | Must have | ||
| 3 | Add Slide | I want to be able to add a slide to a deck | Must have | Currently implemented in a menu under the slide in the tree view but other means of adding a slide are need to aid discoverability, usability and accessibility |
User interaction and design
Description of fields/input/elements + validation + test scenarios
Proposed properties for a deck
Name | Type | Description |
title | Text | the title of the Deck |
language | Text | ISO-639-1 language codes |
tags | List | a list of tags |
| Category | Number | 6 digist UNESCO nomenclature for fields of science and technology* |
- It can be downloaded from:
Questions
Below is a list of questions to be addressed as a result of this requirements document:
| Question | Asked by | Outcome |
|---|---|---|
| When a deck is translated does the language meta-data stay always as the original language or is it updated? | Abi James | |
| Should the meta-data include historical data on the slides? For example, I a deck is translated (i.e branched) should the creator of the original slides still be included in the meta-data? | Abi James |
Not Doing
| Feature | Status |
|---|---|
Source material for user/stakeholder feedback
Requirements (/user stories) from pilot roadmap:
As a content producer, I need the platform to be easy to handle, e.g. through clear and simple structures, and fast to access. (IKH BIZ)
As a content producer, I would like to have a wizard that guide me to the creation of a content that follow the guidelines for UPV MOOCs.(UPV)
Evaluation/improvements by Farid Hasanov master thesis :
Issue5 - Adding slides. Users were complaining that adding a new slide is time-consuming to find and perform. It takes time to guess that a right click on the slides hierarchy could be performed.
Source. Two users raised this issue, as they experienced slight delays while attempting to increase the number of slides.
Figure 5.13: Slide adding original.[51].
Metrics violated: Ease of use, Friendliness.
Here, the first user made 3 mistakes and carried out a task within 47 seconds. The ease of use is 25%. The second user spent more time and made more errors. The result is only 14%. For the third user it was 34%.
Possible Solution. Since not everyone guesses to right click over the slides, perhaps some note explaining this possibility should be added to the website. However, the best way to solve the slide-adding problem is to provide two small buttons for slide and deck adding. The overall picture looks something like this:
Figure 5.14: Slide adding mockup.
Of course these two buttons will move down each time the amount of slides or decks is increased. This will raise the speed of the user’s interaction with the product since it takes less time than right clicking.
Evaluation at UniBonn :