compared with
Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (75)

View Page History
Possible to Under Research \\
Under Research to Proposed
* Possible to Proposed \\
(TBD: Will we be able to edit version status, or only the discussion status? Vlado said that the version will have the status of the first post in a discussion started for it? What if more than 1 discussions are started?) |
| \\ | 06.DAUC03.R5-2 | RS3.2 \\ | * Value -- Edit functionality for field values is provided for the reasons of unconscious user mistakes, which could be fixed before the version status is changed to Proposed and is sent to the RS Project Admin for approval. |
*Post-Conditions*
| | 06.DAUC04.R4 \\ | RS3.2 \\ | When the user selects a version indicator next to AP, the Version tab opens and the user could select Propose New Value button \\ |
| | 06.DAUC04.R5 \\ | RS3.2 \\ | There are 3 scenarios when new value is proposed: \\
* Add new value - this is the case when there is no existing original value, and the user wants to fill the gaps in the object record. In this case, when opened, the Versions tab is empty for a selected AP. * Replace old value - this is the case when there is already an existing original value and the user wants to propose new value which he thinks is the correct one. In the Versions tab there is one or more versions for the selected AP. * TBD: New value for cardinality >1 ... |
* Replace old value - this is the case when there is already an existing original value and the user wants to propose new value which he thinks is the correct one. In the Versions tab there is one or more versions for the selected AP.
* TBD: New value for cardinality >1 ... |
| 06.DANNOTATION.R15-2 \\
06.DANNOTATION.R2-1 \\
06.DANNOTATION.R2-2 \\
\\ | 06.DAUC04.R6 | RS3.2 \\ | When the user selects “Propose New Value” an entry form is opened with the following mandatory fields: \\ |
| 06.DANNOTATION.R8-1 | 06.DAUC04.R6-1 | RS3.2 \\ | * New value -- Based on the field type, for which a new value is created the user will be provided with different data entry fields:
** If the field requires the use of thesauri value, then the data entry form will provide a thesauri control for the new value. Auto-complete will be incorporated. A value will not be saved if not found in the thesaurus.
** If the field requires literal value, then the entry will only be validated for the correct format - validate for Date, String, Integer, etc. |
| \\ | 06.DAUC04.R6-2 | RS3.2 | * Discussion post - It is mandatory the user to give reasons for the new value he proposes. There are 2 options:
** Start new discussion - The first option is the user to input the text in the new comment field opened, and thus new discussion will be started.
** Comment in existing discussion - The user could decide to select any of the discussions already existing for this AP and to comment in it. In this case there is a button Select Discussion, which navigates to tab Discussions for this AP. |
| \\ | 06.DAUC04.R6-3 | RS3 | * -Status-  (not for iteration RS3.2)\- the version status is selected from a codelist. The user could select only between “Possible”, “Under Research” and “Proposed” statuses |
| \\ | 06.DAUC04.R7 | RS3.2 | The newly proposed value could be saved only after the user contributes in a discussion and field value is is validated successfully by format. \\ |
| \\ | 06.DAUC04.R67-1 | | * If the user does not save the new value and cancels the entry then the created discussion/ post is automatically deleted. |
| \\ | 06.DAUC04.R6-2 | | * If the user saves successfully the new value then a new version record is created, the discussion/post is linked to the version record, the version indicator is increased with 1 and the discussion indicator is also increased. |
| \\ | 06.DAUC04.R7-2 | | * If the user saves successfully the new value then a new version record is created and the discussion/post is linked to the version record. |
| 06.DANNOTATION.R11 | 06.DAUC04.R78 | RS3.2 | When the version record is saved the following additional metadata are associated: \\
\-          Researcher -- the name of the user who created the new value \\
\-          Research Project -- the project name of the researcher \\
\-          Date -- the date and time (in format yyyy-mm-ddThh:mm:ss) when the version is created \\ |
*Post-Conditions*
| 06.DANNOTATION.R9 | 06.DAUC04.R8 | RS3.2 \\ | A new value is created and is visualized on Versions tab. |
| \\ | 06.DAUC04.R9 | | The version indicator counter increases with 1 |
| \\ | 06.DAUC04.R10 | | The discussion indicator counter is increased with the new discussion and/or the number of new posts in the discussion. |
* *


*Preconditions:*
| 06.DANNOTATION.R15-2 | 06.DAUC05.R1 | RS3.2 \\ | UC “06.DAUC02: View Versions of AP” has been performed and tab Versions is opened. |
* Constraints:*
| \\ | 06.DAUC05.R2 | RS3 \\ | Values could be deleted only if in status “Possible”, “Under Research” and “Proposed”. |
| \\ | 06.DAUC05.R3 | RS3 \\ | Values could be deleted only from the researcher who created the version or the RS Project Admin. |
* *


*Description:*
| | 06.DAUC05.R4 \\ | RS3.2 \\ | There are 2 scenarios that could happen when the user selects Delete button next to a value: \\ |
| | 06.DAUC05.R4-1 \\ | RS3 \\ | * Delete Value: Values could be deleted only if in status “Possible”, “Under Research” and “Proposed” and  only from the researcher who created the value or the RS Project Admin. This is the case when a user has proposed new value and later on realizes that he has made a mistake. There is no need the deletion to be approved by the RS Project Admin. |
| | 06.DAUC05.R4-2 | RS3.2 \\ | * Propose Deletion: A user could propose a value for deletion in case he thinks that such value/event does not exist or is totally wrong. Deletion could be proposed to values from data layer or to values from annotation layer which are proposed from other users. The RS Project Admin should approve the proposal for deletion. \\ |
| 06.DANNOTATION.R15-6 | 06.DAUC05.R45 | RS3\\ | When a value is deleted: |
| \\ | 06.DAUC05.R45-1 | | * The value status changes to “Deleted” |
| \\ | 06.DAUC05.R45-2 | \\ | * The discussion associated with the version is deleted |
| \\ | 06.DAUC05.R4-3 | | * The version indicator decreases with 1 |
| \\ | 06.DAUC05.R5-3 | | * -The version indicator decreases with 1- |
| | 06.DAUC05.R6 \\ | RS3 \\ | When a value is proposed for deletion: \\ |
| | 06.DAUC05.R6-1\\ | | * The value status changes to "Proposed Deletion" |
| | 06.DAUC05.R6-2\\ | | * The user must post a comment giving reasons why he proposes the deletion |
*Post-Conditions*
| 06.DANNOTATION.R15-6 | 06.DAUC05.R57 | RS3 \\ | Deleted value is no more visible in Versions tab for normal users but only for the RS Project Admin. |
* *


*Preconditions:*
| 06.DANNOTATION.R6 | 06.DAUC06.R1 | RS3.2 \\ | UC “06.DAUC01” has been performed, and an object record is successfully displayed |
*Constraints:*

*Transitions:*1*



*Description:*
| | 06.DAUC06.R2 \\ | RS3.2 \\ | Next to each AP on the Object Record details tab is displayed a discussion indicator (D). \\ |
| | 06.DAUC06.R2-1 \\ | | * When coloured in red the discussion indicator shows that there are one or more discussions started on an AP. If the indicator is coloured grey this means that there are no discussions started. |
| | 06.DAUC06.R2-2 \\ | | * When discussion indicator next to AP is selected then the user is navigated to the Discussions tab. In the Discussions tab the list with available discussions will be restricted only to those on the current AP and all its versions. The user could read and comment on any of the existing discussions or to start a new one. |
| | 06.DAUC06.R2-3 \\ | | * If a new discussion is started in this case it will be linked to “Original” version of the record |
| | 06.DAUC06.R2-4 \\ | | * If the user selects the discussion indicator next to the root AP, or opens directly Discussion tab for an object record then are listed all available discussions for all AP and versions for the current object record. |
| \\ | 06.DAUC06.R14 06.DAUC06.R3 | RS3.2 | In the Version tab, next to each value in the list with values there is discussion indicator. Discussion indicator colored in red shows that there are discussion started on this particular value. \\ |
| | 06.DAUC06.R3-1 \\ | | * When coloured in red the discussion indicator shows that there are one or more discussions started on an value. If the indicator is coloured grey this means that there are no discussions started. |
| | 06.DAUC06.R3-2 \\ | | * When a discussion indicator next to version record is selected then user will be navigated to the Discussion tab, where will be listed all discussions only for the selected version of the record.  The user could read and comment on any of the existing discussions or to start a new one. |
| | 06.DAUC06.R3-3 \\ | | * If the user selects the discussion indicator next to the root AP, or opens directly Discussion tab for an object record then are listed all available discussions for all AP and versions for the current object record. |
| | 06.DAUC06.R4 \\ | RS3.2 \\ | In the Linked Records tab, next to each value in the list with values there is discussion indicator. Discussion indicator is always coloured in red, because all links in the tab are extracted from existing discussions. |
| | 06.DAUC06.R4-1 \\ | | * When a discussion indicator next to linked record is selected then user will be navigated to the Discussion tab, where will be listed all discussions started for the current AP in which the respective link is embedded (for outgoing links) or all discussions started for the listed record, in which is embedded the current AP (for incoming links). The user could read and comment on any of the existing discussions or to start a new one. |
| \\ | 06.DAUC06.R17 06.DAUC06.R5 | RS3.2 \\ | When a new discussion is started during creation of new value (see DAUC04: Propose New Value), then: \\ |
| \\ | 06.DAUC06.R17-1 06.DAUC06.R5-1 | | * The discussion name is created automatically, based on the following template; “New value <VALUE> for field <FIELD NAME>”. The user is allowed to change the discussion name. |
| \\ | 06.DAUC06.R17-2 06.DAUC06.R5-2 | | * The discussion is automatically linked to the respective version record. |
| \\ | 06.DAUC06.R18 06.DAUC06.R6 | RS3.2 \\ | If there are no discussions started on any of the APs then the Discussion tab is empty, but the user could open it and select Start New Discussion button. |
| | 06.DAUC06.R7 \\ | | For more details see [SNUC13: View/ Sort Discussions|https://confluence.ontotext.com/display/ResearchSpace/Social+Networking+Reqs#SocialNetworkingReqs-04.SNUC13%3AView%2FSortDiscussions]\\ |
*Post-Conditions*
| \\ | 06.DAUC06.R21 06.DAUC06.R8 | RS3.2 | All discussions linked to an object record are accessible from the Object Record Details screen. |
| \\ | 06.DAUC06.R22 06.DAUC06.R9 | RS3.2 \\ | A new post/ discussion for AP could be started from the Discussions tab. |
\\



h4.
h4. 06.DAUC07: View Linked Records

h4. 06.DAUC08: View Linked Records

*Preconditions:*
| 06.DANNOTATION.R6 | 06.DAUC07.R1 | RS3.2 \\ | UC “06.DAUC01” has been performed, and an object record is successfully displayed |
*Constraints:*


*Description:*
| | 06.DAUC07.R2 \\ | RS3.2 \\ | Next to each AP on the Object Record details tab is displayed a Linked Records indicator (R). |
| 06.DANNOTATION.R10 | 06.DAUC07.R2-1 | | * When coloured in red the linked records indicator shows that there are one or more links to APs, related to the current one. If the indicator is coloured grey this means that there are no related records. |
| | 06.DAUC07.R2-2 \\ | | * When the linked records indicator next to AP is selected then the user is navigated to the Linked Records tab. In the Linked Records tab the list with available links will be restricted only to those on the current AP and all its versions. |
| | 06.DAUC07.R2-3 \\ | | * If the user selects the linked records indicator next to the root AP, or opens directly Linked Records tab for an object record then are listed all linked records to all APs and their versions for the current object record. |
| | 06.DAUC07.R2-4 \\ | | * If a link to record is selected then the respective object record is opened and the user positioned to the selected AP (see UC 06.DAUC01: View Object Records). |
| 06.DANNOTATION.R10 | 06.DAUC07.R3 | | The Linked Records tab is split on 2 section \\ |
| 06.DANNOTATION.R10 | 06.DAUC07.R3 | RS3.2 \\ | The Linked Records tab is split in to 2 sections \\ |
| \\ | 06.DAUC07.R3-1 | | * Outgoing Links: Links to APs which are embedded in discussions started for the current AP. |
| \\ | 06.DAUC07.R3-2 | | * Incoming Links: Links to APs, for which are started discussions and there is link to the current AP, embedded in these discussions |
| \\ | 06.DAUC07.R64 | RS3.2 \\ | For each link in the Linked Records tab are displayed the following values (both for incoming and outgoing links): \\
* Link to the record - when clicked on the link the respective object record is opened and the user is positioned to respective AP
* Discussion Indicator - when selected the discussion indicator the discussion tab opens. In this case in the discussion tab are listed all discussions started for the current AP in which the respective link is embedded (for outgoing links) or all discussions started for the listed record, in which is embedded the current AP (for incoming links). |
| | 06.DAUC07.R5\\ | RS3.2 \\ | If a link to record is embedded in more than one discussions (or posts) then it is displayed only once in the Linked Records tab, and in the Discussions tab could be viewed all discussions. \\ |
| | 06.DAUC07.R6\\ | RS3.2 \\ | The links in the Linked Records tab are sorted alphabetically. \\ |
| | 06.DAUC07.R7 \\ | \\ | TBD: Do we list here also the links to documents, images, external links - embedded into discussion started for the current AP? \\ |
\\

*Post-Conditions*
| 06.DANNOTATION.R10 | | 06.DAUC07.R78 | All items linked to the current object item are counted and listed under linked records indicator. |
*&nbsp;*

h4. 06.DAUC098: View Thumbnails

*Preconditions:*
| \\ | 06.DAUC08.R1 | RS3.2 | UC “06.DAUC01” has been performed, and an object record is successfully displayed |
*&nbsp;*

*Description:*
| 06.DANNOTATION.R17-1 \\
\\ | 06.DAUC08.R2 | RS3.2 \\ | In Relations tab are displayed thumbnails to all images, documents linked to the object record \\ |
| 06.DANNOTATION.R17-2 | 06.DAUC08.R3 | RS3.2 \\ | Thumbnails will provide basic information for an image/document - file size, type, file name and the type of the relation between the image/document and the object record . |
| 06.DANNOTATION.R17-2 | 06.DAUC08.R4 | RS3 \\ | Thumbnails to images will be used as links to Image Annotation tool |
| | 06.DAUC08.R5 \\ | RS3.2 \\ | The user could add new relations by selecting "Add New Relation" button from the Relations tab. \\ |
\\

*Post-Conditions*
| 06.DANNOTATION.R17-1 | 06.DAUC08.R5 | | Thumbnails to all content associated with an object record are displayed in the Relations tab \\ |

h4.


h4. 06.DAUC09: Promote Discussion

*Preconditions:*
| | 06.DAUC08.R1 | RS3.2 | UC “06.DAUC01” has been performed, and an object record is successfully displayed |
*&nbsp;*

*Constraints:*

*Transitions:*

*Initiating operation/ button:* Add New Relation

*GUI: &nbsp;*

\-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Object Record Details/ Relations tab

*Description:*
| 06.DANNOTATION.R17-1 \\
\\ | 06.DAUC08.R2 | RS3.2 \\ | In Relations tab are displayed thumbnails to all images, documents linked to the object record \\ |
| 06.DANNOTATION.R17-2 | 06.DAUC08.R3 | RS3.2 \\ | Thumbnails will provide basic information for an image/document - file size, type, file name and the type of the relation between the image/document and the object record . |
| 06.DANNOTATION.R17-2 | 06.DAUC08.R4 | RS3 \\ | Thumbnails to images will be used as links to Image Annotation tool |
| | 06.DAUC08.R5 \\ | RS3.2 \\ | The user could add new relations by selecting "Add New Relation" button from the Relations tab. \\ |
\\
\\

*Post-Conditions*
| 06.DANNOTATION.R17-1 | 06.DAUC08.R5 | | Thumbnails to all content associated with an object record are displayed in the Relations tab |

h3. Activity Diagrams