Skip to end of banner
Go to start of banner

Synapse Discussion Forum

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

There are two use cases for Synapse Discussion Forum: 

  • A discussion forum for each project where collaborators can share thoughts and comments.
  • A Synapse Q&A forum where Synapse technical support answers general questions about Synapse.

In this document, we show the design of the first use case and state the differences for the second use case.

Permissions

Any user with project's Can Read permission will be able to read comments.

Any user with project's Can Comment permission will be able to create a new thread and comments on other's thread. These users can edit their comments, add and remove tags from threads they created.

Any project Admin, in addition to above actions, can also remove threads, comments, and tags in the project. They can also pin a thread so that it appears before other threads.

UI Mockup

The images below were generated using Moqus, and can be viewed here: https://app.moqups.com/Kimyen0816/AnHoFYQWUL/view/page/a56a2940b

Empty Discussion - Can Read

Users who have Read permission to a project will see this if the project does not have any discussion yet.

Empty Discussion - Can Comment

Users with Comment permission will be able to create a new topic or a new question in the discussion tab. The difference between a topic and a Q&A is that users can vote for an answer in a Q&A. Answers will be ordered by number of votes. 

 

Discussion - Can Read

Users with Read permission will see something similar to this. They are not able to write comments yet but can request Comment permission. 

When they click on the expand icon on the bottom right of the topic, they can read more about the comments. 

 

Discussion - Can Comment

This is Kim's view. Since she is the owner of the topic, she will be able to edit her comment.

For users with Comment permission, the expand view will give them the choice to write their comment to the topic they are viewing.

 

Discussion - Admin View

Admin can enter Admin Mode. In the Admin Mode, the admin can choose topic(s) and comment(s) to perform actions to.

For a topic, the admin can add/remove tags, delete topic, and pin/unpin topic. When a topic is pinned, it appears on top of the discussion board. When it is unpinned, it will be order chronologically. 

For a comment, the admin can delete it.

When the admin finishes moderating, he/she can exit the Admin Mode to see how the discussion look with the changes that he/she made.

 

Topic with answers - Can Read

For a topic, comments will be paginated and appear in the order they are written. The UI shows the last few comments. Users can click Load more to read older comments.

 

Q&A with answers - Can Read

For Q&A, comments will be paginated and ordered by number of votes it received.

Users with Read permission cannot vote. Users with Comment permission can vote. 

 

New Topic Editor

When user clicks on New Topic or New Q&A, this widget will pop up. 

To add a tag to the topic, author can simply write #<tag> in the comment body, or use the look up tool to look for existing tags in the project.

Users can press Enter or click Add to add a tag from the look up tool to their topic.

 

New Comment

 

Comments & Suggestions

  1. Provide an Order By button so that users can view Q&A answers either by the votes or by chronological order.
  2. Users should be able to vote on all topics given the above feature.
  3. Users should be able to choose certain topics to follow. Have three panels with paginated content:
    1. Topics pinned by Admin
    2. Topics I follow
    3. Others (order chronologically)
  4. Allow private discussions (like how it works with entity).
  5. Use notation @username, and notify users when their names are mentioned.
  6. In File/Table tab view, if a file or a table has a discussion, give users the link to go to the discussion about that file/table.
  7. As soon as the the feature is out, people will want to search for the content of the comment.
  8. Use case: allowing users to vote on a row in a table. 
    Suggestion: provide a way for user to upload a table, then auto-generate a topic about that table, each row in the table is a vote-able comment. 
  9. How many layers of nesting comments is good?
    1. The advantage of having only one layer of comments/ response is that everything in a topic must be relevant to the topic.
    2. The advantage of having two layer of comments is that user can comment on a specific comment.
  10. Answers by admin should be highlighted and appears first.
  11. Tags should appear separated from the body of the comment in the New Topic window.
  12. Users who have Read permission should be able to vote.

 

 

  • No labels