Difference between revisions of "Spring minions DHIS2 Discussion forum web app"
(→Forum view) |
|||
Line 19: | Line 19: | ||
===Forum view=== | ===Forum view=== | ||
+ | In short, we wish to achieve a "forum style" view of the interpretations. We believe this is a cleaner and more user friendly presentation format. Do note, though, that this will not attempt to replicate the functionality and architecture of traditional web forums such as phpbb et. al. The underlying data simply don't support this type of structure as there are no categories, no titles etc. | ||
+ | |||
+ | |||
====Front page view with subject, last updated date, last author==== | ====Front page view with subject, last updated date, last author==== | ||
Line 51: | Line 54: | ||
====RSS / Atom==== | ====RSS / Atom==== | ||
− | |||
− | |||
===Search=== | ===Search=== |
Revision as of 13:30, 22 November 2013
Contents
- 1 About
- 1.1 Group members
- 1.2 Requirements
- 1.2.1 Forum view
- 1.2.1.1 Front page view with subject, last updated date, last author
- 1.2.1.2 Comment hierarchy
- 1.2.1.3 Like / dislike
- 1.2.1.4 User rating
- 1.2.1.5 Posts per user
- 1.2.1.6 Avatar for users
- 1.2.1.7 Browsing interpretations by Categories(diagnosis)?
- 1.2.1.8 Attachments
- 1.2.1.9 Moderators
- 1.2.1.10 RSS / Atom
- 1.2.2 Search
- 1.2.1 Forum view
- 1.3 How you are dividing tasks within the group
- 1.4 Screenshots and screen flows
- 1.5 Documented learning during project
- 1.6 Suggested improvements to APIs etc
- 1.7 Time scedule/Mile stones
- 1.8 Resources
About
In vanilla DHIS2 there is a (fairly bare bones) "interpretations" system. In essence, this system allows users to annotate analytical objects such as charts, maps and tables with their interpretation (or other relevant information) of the data. UX-wise, interpretations are browsed through a Facebook-style news feed. Except the ability to comment an interpretation shared by another user, some obvious major features are missing:
- There is no way for a user to actively keep track of an interpretation they find interesting. Over time it will be swallowed by the newsfeed and there is no URL to a specific interpretation supplied to the user.
- There is no functionality to search interpretations for issues/items of particular interest.
In short, the existing interpretations feature set is only usable for posting (fairly) disposable data, and is not fit for encouraging proper discussion and interaction between users.
The task of this group project is to attempt to mend some of these issues through creating a separate web-app for exploring and discussing interpretations utilising the DHIS2 web-api.
Group members
- Thomas Iversen
- Trine Frimannslund
- Halvdan Grelland
- Johannes Akse
Requirements
Below is an (admittedly fairly lacking) list of project requirements.
Forum view
In short, we wish to achieve a "forum style" view of the interpretations. We believe this is a cleaner and more user friendly presentation format. Do note, though, that this will not attempt to replicate the functionality and architecture of traditional web forums such as phpbb et. al. The underlying data simply don't support this type of structure as there are no categories, no titles etc.
Front page view with subject, last updated date, last author
baseurlOrder by date- Angular templates
- Fetch more posts when scrolldown
display type icon
*Fetch name. In Progress: Halvdan, Thomas og Johannes
- Style(css)
Comment hierarchy
- display comment within comment
- show comments
- Style(css)
Like / dislike
User rating
Posts per user
Avatar for users
Browsing interpretations by Categories(diagnosis)?
Attachments
Moderators
RSS / Atom
Search
Text
Users
Analysis item (chart, map, pivot)
Item data elements + indicators + data set
Hononyms / synonyms
How you are dividing tasks within the group
Thomas and Halvdan is doing the Back end (Hibernate search/Lucene) Trine and Johannes is doing the Front end(Forum view)
Screenshots and screen flows
Documented learning during project
Suggested improvements to APIs etc
Time scedule/Mile stones
-
01. nov: Finish wiki-page and make link to repository - 15. nov: First prototype of features
- 30. nov: Finished prototype
- 08. dec: Deliver prototype