Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

...

...

...

...

...


Page Properties


Target releaseEpic
User Story

Jira Legacy
serverJIRA (slidewiki.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId497b9b88-e2b8-32ee-be05-4d265f33883f
keySWIK-199

 
Document status

Status

invalidmacro

titleDraft

Document owner
Designer
DevelopersFormer user (Deleted)
QA
Work Package & deliverables 
Related JIRA tasks

SWIK-138, SWIK-230, SWIK-267, SWIK-268, SWIK-269


...

User interaction and design

Search results UI

UI proposed following discussion in SWIK-707 . Mock up below proposes:

  • all search entries are marked up as H3 to provide structure to the content
  • icons are labelled with aria-label

1 entry per deck.- the one with the most recent modification

Below deck title

  • deck description
  • date of the last modification of the deck, preceded by "deck" (covers off inaccessibility of the icon)
  • followed by owner OR by "user" to show who last modified it

On pressing "Other versions" button, user sees other version of the deck. This could include versions in different languages.


1 entry per slide - the one with the most recent modification

Below the slide title:

  • snippet of slide content
  • date of the last modification of the deck, preceded by "slide" (covers off inaccessibility of the icon)
  • followed by owner OR by "user" to show who last modified it

On pressing "Other versions" button, user sees other deck title containing the slide. 


.Image Added

The other UI approach to look at is links below the entry that opens a different set of search results as per Google Scholar:

Image Added


Description of fields/input/elements + validation + test scenarios

...

Requirements (/user stories) from pilot roadmap:

 

Evaluation at UniBonn :  


Project Partners feedback: