Annotation Spec

{toc}

h3. Used business terms and abbreviations

|| Term || Description ||
| URI | *Uniform Resource Identifier* (*URI*) is a  string of characters used to identify a name or a resource in the Internet |
| Annotation Point (AP) \\ | As an annotation point will be referred any of the following concepts, when displayed on the screen and when no special distinction is required: object record (the root), object statement (Subject, Property, Object), in which the object is either literal or thesaurus value. Each annotation point is a RFD graph node. The object record itself is the root (main node) of the graph, and each field or field value (subject or object) is also a node in the RDF graph. |
| Node | A node may be a URI reference, a literal, or blank node |
| Discussion | A discussion (also known as thread or topic) is a collection of posts, displayed by default from oldest to latest. A discussion is defined by a title, an opening or original post (common abbreviation _OP_) which opens whatever dialogue or makes whatever announcement the poster wished, date and time on which is started as the date and time of the last post. A discussion can contain any number of posts, including multiple posts from the same members, even if they are one after the other. \\
A discussion is contained in a forum. When a member posts in a discussion it will jump to the top since it is the latest updated thread. \\
The following discussion types will be distinguished in the document: |
| Item Discussion | This is type of discussion used as a term in this document. This is discussion directly started on an item -- object record, field or value. This type of discussion has a reference to the data item for which is started. |
| General discussion | This is type of discussion used as a term in this document. This discussion is independent from an object record, it started from the discussions component, but it could contain links to data objects, documents, images, etc |
| Post | A post is a user-submitted message, containing the user's details and the date and time it was submitted. Members are usually allowed to edit or delete their own posts. Posts are contained in discussions. The first post starts the discussion; |
| Main Link \\ | Thus will be called the link between: \\

| Data Layer \\ | Data layer includes factual statements |

* The state chart diagram will be updated after the analysis performed on the next stage.

|| Code || State || Description ||
| OBJPOS | Possible | Active state of a version record \\
This is an informative state of a newly created version of a field value. The researcher may select this status, when he is not sure that the value is correct, but wants to keep it as a reminder for future research, or may want to delete it later. |
| OBJRES | Under Research | Active state of a version record \\
This is also an informative state of a created version. The researcher may select this status together with creating the version or he could change the status of already created version in status Possible to Under Research. This state is created with the purpose of informing other team members, that this value is still not proven. |
| OBJPRO | Proposed | Active state of a version record \\
By changing a version record state to “Proposed” the researches informs his Project Admin, that he has finished his research and he grants that the new version of a record item is correct. |
| OBJDEL | Deleted | End state of a version record \\
The researcher, who created a new version, together with the Project Admin are given the possibility to delete the version in case of mistake due to inadvertence, before the new value is actually approved. \\
Deleted versions are invisible for the project members. |
| OBJREJ | Rejected | End state of a version record \\
After the RS Project Admin receives a proposed value for review he could either approve it or reject it. If he rejects the state of the new version becomes Rejected. Rejected versions of an item are visible fr the project members, but could only be commented on them. \\
The transition to this state will be developed in the next stage of the project. |
| OBJAPI | Approved Internal | Active state of a version record \\
After the RS Project Admin receives a proposed value for review he could either approve it or reject it. If he decides to approve he could select to approve it just internally for the project, but not for publishing to the public web, because of different reasons -- some more clarifications are needed, the research is secret, etc.   \\
The transition to this state will be developed in the next stage of the project. |
| OBJAPP | Approved Publishable | Active state of a version record \\
The RS project Admin could approve proposed value version for publishing. This means that when the publishing procedures are started all values in this status will be published. \\
The transition to this state will be developed in the next stage of the project. |
| OBJPUB | Published | End State of a version record \\
Version records are in this state when published on the web. \\
The transition to this state will be developed in the next stage of the project. |
| OBJORG | Original | End state of a version record \\
All initially loaded/ migrated object record items are in this state. \\
If new object record is created and there is no previous version is status “Original”, when published the items of the record will be in status “Original’. \\
The transition to this state will be developed in the next stage of the project. |


!Object Record Field Status.png|border=1!

Diagram 06.1: Object record item versions State Chart Diagram

The UCs for Data Annotation, Input Editing and Version Comparison are used by the researchers to review data objects and discussions, annotate data objects (or start discussions), create new versions on an objects items.

h4. 06.DAUC01: View Object Record

*Constraints:*
| \\ | 06.DAUC01.R3 | RS3.2 \\ | In RS3 only object records from object type: Painting (P2_has_type rkd-object:painting) will be displayed for review and annotation.   |
* Do Note:* {color:#ff6600}Don't quite understand the constraint - 'Painting'{color}

*Transitions:* No

*Initiating operation/ button:* Link (URI) to Annotation point


*GUI:*
* Object Record Details tab

h4. 06.DAUC02: View/ Sort Versions of AP

*Constraints:*
| \\ | 06.DAUC02.R3 | RS3 \\ | Versions of APs with status “Deleted” from the current project are visible only for the RS and Project Administrators. |
* *

*Transitions:* No

*Initiating operation/ button:* Version Indicator, Version tab


*GUI:*
* Object Record Details tab/ Version Indicator

* Link (URI) to Annotation Point
* Value -- shows the original/new value
* -Research Project- \-the project name, during which the value has been created/changed (not for RS3.2 Iteration)
* Researcher Name - the name of the researcher who created the version
* Date: Time -- the date on which the value version has been updated/changed
* -Status- \-  The status of the version (not for RS3.2 Iteration)
* Discussion Indicator -- discussion indicator here will show that there are/ are not discussions started for this field version, similarly to the discussion indicator, described in DAUC01. If the indicator is selected then will be shown all discussions started for the created field version. The list will be a subset of all existing discussions. The user could start a new discussion for that field version.
* Linked Records Indicator - linked records indicator here will show of there are linked records to each one of the versions. When selected will be opened Linked Records tab. |
| | 06.DAUC02.R7 \\ | RS3.2 | If a version indicator for AP is selected and there are no versions existing then on “Versions” tab is displayed only the original value. |
| | 06.DAUC02.R8 \\ | RS3.2 | If the the version indicator for the object record (the root) is selected, or the Version tab is opened independently when browsing details for an object record - then on Versions tab are listed all existing versions of all APs of the object (if there are no other versions, then only the original versions are displayed). \\ |
| \\ | 06.DAUC02.R9 | RS3.2 \\ | The versions in the Version tab are sorted by default - alphabetically by Link (URI) to Annotation Point and then ascending by version creation date. There is no version number supported. |

| \\ | 06.DAUC02.R13 | RS3.2 | A discussion for field version could be opened or new one started. |
* *

h4. 06.DAUC03: Edit Existing Version

*Preconditions:*
| 06.DANNOTATION.R6 | 06.DAUC03.R1 | RS3.2 | UC “06.DAUC02: View Version of AP” has been performed and “Versions” tab is opened. |
* *

*Constraints:*
| \\ | 06.DAUC03.R2 | RS3 | Version records could be edited only from the researcher who created the version or from the RS Project Admin. |
| | 06.DAUC03.R3 \\ | RS3 | The original value of an AP could not be edited. \\ |
* *

*Transitions:*

\-          Possible >Under Research

\-          Possible >Proposed

\-          Under Research >Proposed

*Initiating operation/ button:* Edit

*GUI:* Versions tab


*Description:*
| \\ | 06.DAUC03.R4 | RS3 | The edit mode for a version will be accessible only for the user who created the version and for the RS Project Admin of the current project. |
| \\ | 06.DAUC03.R5 | RS3 \\ | The edit mode will be accessible only for version records in status Possible or Under Research. |
| \\ | 06.DAUC03.R5 | RS3 \\ | The following information for each version could be edited: |
| \\ | 06.DAUC03.R5-1 | | * -Version Status- (Not for RS3.2 iteration) -- the version status could be updated manually from: \\

| \\ | 06.DAUC03.R6 | RS3.2 | The changes in field version are saved successfully and displayed on the screen. |
* *

h4. 06.DAUC04: Propose New Value

*Preconditions:*
| 06.DANNOTATION.R15-2 | 06.DAUC04.R1 | RS3.2 \\ | UC “06.DAUC02: View Version of AP” has been performed. |
* Constraints:*
| \\ | 06.DAUC04.R2 | RS3.2 \\ | New values could be proposed only for literal or thesauri objects  |
| | 06.DAUC04.R3 \\ | RS3 \\ | New values for compound objects (example Exhibitions) won't be able to be proposed in RS3.2 \\ |
* Transitions:*

\-          New >Possible

\-          New >Under Research

\-          New >Proposed

*Initiating operation/ button:* Propose New Value

*GUI*: Versions tab


*Description:*

h4. 06.DAUC05: Delete Value

*Transitions:*

\-          Possible >Deleted

\-          Under Research >Deleted

\-          Proposed >Deleted

*Initiating operation/ button:* Delete

*GUI:* tab Versions

h4. 06.DAUC06: View and Create Discussions on AP

*Initiating operation/ button:* Link to a discussion, Discussion indicator

*GUI:  *

* Object Record Details/ Discussion tab
* Object Record Details/ Discussion indicator
* Object Record Details/ Version tab/ Discussion indicator
* Object Record Details/ Linked Records tab/ Discussion Indicator

*Transitions:*

*Initiating operation/ button:* Linked Records Indicator

*GUI:  *

\-          Object Record Details/ Linked Records tab

*Constraints:*

*Transitions:*

*Initiating operation/ button:* Add New Relation

*GUI:  *

\-          Object Record Details/ Relations tab

!Count Discussions.png|border=1!


Diagram 06.3 Count Discussions Diagram