DeckEdit / DeckView
- Abi James
Summary
DeckView: To display information and metadata about a deck
DeckEdit: To edit the contents on the deckview.
Background and goals
The information that is displayed in the DeckView is created either
- when a deck is added to the SlideWiki (see Add a deck)
- by editing the DeckView data. This is access through the deck settings dialog.
There is a description of when the deckview is displayed and when it could be edited as a user creates a deck in Deck Structure and actions
Assumptions
Requirements
| # | Title | User Story | Importance | Notes | JIRA |
|---|---|---|---|---|---|
| 1 | Display deck info | As a user I wish to see an overview of a deck. | The deckveiw should display:
| ||
| 2 | Deck sample slides | As a user I wish to see thumbnails of the most popular slides and be able to open that slide when I select it | must have | Below the deck view, display thumbnails of a selection of slides. These slides to be display could be selected from:
Initially we should display the first 3-4 slides of the deck. In the future this could have a carousel control to allow users to expose additional thumbnails. This should use the Thumbnail component SWIK-147 - Getting issue details... STATUS
| |
| 3 | Deck edit | As the owner of a deck I wish to edit the information in the deckview | must have | The form for editing the deckview is accessed through the settings button. This opens a modal window with the fields from the Add a deck form (see mockup below). | |
| 4 |
User interaction and design
Design for the deckview. This mockup has placed the deckview contents and thumbnails within a container with a height of 450px to match the proposed size of the slide area. The HTML for this mockup is available at https://drive.google.com/open?id=0B-oEnszZrEaMY3kxY3ZtVGVSN0E (drop the HTML file into custom-semantic-ui\examples before opening). The example has been marked up for accessibility.
Description of fields/input/elements + validation + test scenarios
Questions
Below is a list of questions to be addressed as a result of this requirements document:
| Question | Asked by | Outcome |
|---|---|---|
| Is the DeckEdit form the same form for entering metadata for new decks? | Abi | The deckedit form is a modal windows based on the upload form. |
| Do we limited the metadata to a stored scheme (using autocomplete or a drop-down) or allow free text to be added? Selecting from a schema may be better for support different languages as this could be populated after the user selects the language for the deck | Abi | |
Not Doing
| Feature | Status |
|---|---|
Source material for user/stakeholder feedback
Requirements (/user stories) from pilot roadmap:
Evaluation/improvements by Farid Hasanov master thesis :
Evaluation at UniBonn :
Project Partners feedback: