Requirements
| 04.SOCIALNET.R1 | RS3.4 | Social networking (or Collaboration) tools are applications within the CMS system. |
| 04.SOCIALNET.R2 | RS3.4 | The following social networking tools will be supported during RS Stage 3: - Wikis - Blogs - Discussions |
| 04.SOCIALNET.R3 | RS3.4 | When posts (contributions) are made within a social networking tool, the information should be stored in the RDF store if that information enriches the store of cultural heritage data and information stored there. |
| 04.SOCIALNET.R4 | RS3.4 | During RS Stage 3 when scholars are contributing to a general discussion, they should have the opportunity of saving the whole blog, discussion or wiki as an annotation with the appropriate associations or relationships in the RDF store |
| 04.SOCIALNET.R5 | RS3.4 | The social networking tools will be integrated with the Search engine and each team member will be able to search in all blogs, wikis and discussion forums |
| 04.SOCIALNET.R6 | RS3.4 | The social networking tools will be integrated with the ResearchSpace toolbar - providing navigation application launch capability |
| 04.SOCIALNET.R7 | RS3.4 | The social networking tools will be integrated with the RS Data Basket – a mechanism for managing data to and from the social networking tools. |
| 04.SOCIALNET.R8 | RS3.4 | The social networking tools will be integrated with the Research Tools – which are launched from the CMS environment and which interface with the CMS environment through the data basket. |
Use Cases not developed in RS3.2
04.SNUC04: Edit Comment
Preconditions:
| 04.SNUC04.R1 | There is an existing comment, which to be edited. |
Constraints:
| 04.SNUC04.R2 | Only the user who created the comment could edit it. |
Initiating operation/ button: Edit
GUI:
- Forum/ Topic/ Comment/ Edit
Description:
| 04.SNUC04.R3 | When the user selects Edit button the comment becomes editable and the user could edit the text and links into the comment. | |
| 04.SNUC04.R4 | If a link to data object or data object statement is deleted, and the discussion is from type AP discussion then the information on Linked Records Tab should be updated (See [UC View Linked Records|../../../../../../../../../../display/ResearchSpace/Annotation+Spec#AnnotationSpec-06.DAUC07%3AViewLinkedRecords||\||]) | |
| 04.SNUC04.R5 | After the user finishes editing the comment, he has to save changes. |
Post-Conditions
| 04.SSUC04.R6 | The comment is saved |
04.SNUC05: Delete Comment
Preconditions:
| 04.SNUC05.R1 | There is an existing comment, which to be deleted. |
Constraints:
| 04.SNUC05.R2 | Only the user who created the comment, or the project administrator, could delete it. | |
| 04.SNUC05.R3 |
Only a comment to which there are no replies could be deleted. |
Initiating operation/ button: Delete
GUI:
Description:
| 04.SNUC04.R4 | When the user selects Delete button the comment is permanently deleted from the discussion. | |
| 04.SNUC04.R5 | If a link to data object or data object statement is deleted and the discussion is from type AP discussion, then should be updated the information in Linked Records tab, for the respective records (see [Linked Records|../../../../../../../../../../display/ResearchSpace/Annotation+Spec#AnnotationSpec-06.DAUC07%3AViewLinkedRecords||\||]) |
Post-Conditions
04.SNUC12: Add Disposition
Preconditions:
| 04.SNUC12.R1 | This UC extends use case 04.SSUC03: Reply Comment and could not be executed without it to be started. |
Constraints:
Initiating operation/ button: Add Disposition
GUI:
Description:
| 04.SNUC12.R2 | With Add Disposition functionality, the user flags his comment/reply as: (C) - Comment (?) - Question (A) - Advice (Y) - Agree (or icon for thumb up) (N) - Disagree (or icon for thumb down) |
|
| 04.SNUC12.R3 | When the user selects Add Disposition button, a list with values opens where the user could select his agreement, disagreement, etc. with the comment he is replying to. |
|
| 04.SNUC12.R4 |
If no disposition is explicitly selected then the reply is flagged by default as Comment. |
|
| 04.SNUC12.R5 | The disposition flags are displayed in front of each comment. |
Post-Conditions
| 04.SNUC12.R6 | A disposition is successfully inserted into the comment. |
04.SNUC13: View/ Sort Discussions
Preconditions:
Constraints:
| 04.SNUC13.R1 | A user could view only general discussions to which he has access. | |
| 04.SNUC13.R2 |
The access rights on item discussions could not be managed separately and inherit the access rights on the object records |
Initiating operation/ button:
GUI:
- For general discussions*:* Project Dashboard/ Forum/ Discussions
- For item discussions: Object Record Details/tab Discussions
- For document discussions: Document Details/ tab Discussions
Description:
| 04.SNUC13.R3 | For each discussion will be displayed the following items in the list with discussions: |
- Discussion name - the column will display the Link to the discussion - If the link to discussion is selected then the discussion is opened with all its posts.
- Annotation point - the column will display the Link to the Annotation point (URI) for which the discussion is started – If the link is selected then the user is positioned to selected node on the Object Record area. This field could be empty for general discussions.
- Researcher – the name of the user who has started the discussion,
- Date: Time/ Researcher – the date and time of the last post in the discussion and the name of the researcher who last commented on the discussion
- Number posts per each discussion |
04.SNUC13.R4 In Project Dashboard/ Forum/ Discussions are displayed all general discussions plus the promoted item discussions. (TBD: See UC: Promote Discussion - where the administrator could promote an item discussion as general - then it becomes visible in the list with general discussions). The item discussions are displayed with different icon than the general discussions.
04.SNUC12.R5
In Object Record Details/ tab Discussions are displayed all discussions started for the selected annotation point.
- If the user selects the root then will be visible all discussions started for the object record and all its annotation points
- If the user selects an annotation point then he would be able to see all discussions started only for this annotation point. |
04.SNUC12.R6 By default discussions are sorted by Date: Time of last post, thus the recent discussions are always on the top. 04.SNUC12.R7 The discussions could be sorted in ascending/ descending order by different criteria by clicking on the respective column name.
For example if the user selects once the column Researcher - the discussions will be sorted alphabetically in ascending order by researcher name. If the user selects the same column twice the discussions will be sorted alphabetically in descending order by researcher name.
Use Cases RS3.5
The use case diagram below represents the functionality that should be developed in RS in place of the existing functionality for discussions in Nuxeo. In iteration RS3.2, when social networking was planned for development, it was supposed that for general discussions will be reused the existing Nuxeo functionality. After RS UI redesign in RS3.4 this functionality has been decided to be redeveloped.
04.SNUC14: Start New Discussion
| R1 | Each user could start a new general discussion from Forum tab |
| R2 | When the user clicks on Start new discussion, a window opens where the user enters:
|
| R3 | For each discussion, when created is kept additional information about:
|
04.SNUC15: Open Discussion
| R1 | In the Forum tab are visible all discussions started in the RS – the discussions started from all possible tools - image annotation tool, data annotation tool and general discussions |
| R2 | The discussions from different tools are flagged differently, so the users could recognize them visually |
| R3 | The discussions are organized in pages, with the latest modified discussions on the top. |
| R4 | For each discussion in the Forum tab is visible:
|
| R5 | If a user clicks on the discussion name the discussion is opened in the Forum tab with all its comments and the user could review it. |
| R6 | For each discussion generated from data annotation or image annotation tools, when opened is provided link to the discussion in the respective tool. The user could select the link and open the discussion together with the object it is annotating in the tool for more detailed review. |
04. SNUC16: Reply
| R1 | When the user opens a discussion he could post his reply to it. |
| R2 | Only one level of replies is supported – this means that user could reply only to the top level comment, and cannot reply to other users replies. |
| R3 | When user saves his reply on a discussion, then the Last modified date and Last contributor metadata are updated. Also the replies counter is increased with 1. |
04. SNUC17: Sort/ Filter discussions
| R1 | The discussions in the Forum tab are sorted by default by Last Modified date |
| R2 | The user could sort discussions by each one of the following criteria, both ascending and descending:
|
| R3 | The user could filter discussions in the Forum tab, using the following criteria:
|
| R4 | After user enters the filtering criteria, the system displays only the items in the data basket, which satisfy the criteria |
| R5 | The user could filter by more than one criteria at the same time and to sort the result. |
| R6 | The user should be able to clear the filtering criteria, if he wants to browse all discussions again. |
Labels:
None