
# The user proposes new value \- {color:#ff6600}This may still require validation from a vocabulary (thesaurus/ authority){color}
* Data entry fields are opened where the user enters the value he proposes and the status of proposed value
* The user browses the list with existing discussions on all versions and either selects an existing discussion and makes a post in it or starts a new discussion.
* The user saves the proposed value
h3. Result
# The version indicator for the selected object item increases
# The discussion indicator for the selected object item, the empty value, increases (either the discussion counter or the post counter, depending on the whether the user started a new discussion or posted on an existing one).
# The discussion indicator for the newly proposed value increases (either the discussion counter or the post counter, depending on the whether the user started a new discussion or posted on an existing one)
# For the newly created version is kept information about: the researcher, who proposed the value, the project , the date and time when it is proposed, the status of the version.
# If a new discussion is started, then it is linked to the proposed value.
# If a new post in an existing discussion is made, then it is linked to the proposed value.
# The newly proposed version is saved and is visible for all team members under the empty value. Only the version indicator indicates that that there are proposed values.
# The newly proposed value becomes visible for external users only after being published.
# Question: Is it possible the newly proposed value, when published, if it is first (there are no other published versions), to become original, with information of course for the researcher, project, organization, etc? {color:#ff6600}NO - the riginal is nothing{color}
h2. Scenario 4: Enter new values in a list
h3. Description
This is the case when a user wants to add new record in a list. For example there is new exhibition in which the painting is placed, and the list with exhibitions must be updated. The user is not changing an original value, he is just adding new valid values. {color:#ff6600}Is this the same as adding a completely new value - above){color}
h3. Performed actions
# The user searches for an object record
# The object record is found and the user opens it
# The user browses the object record and positions to the list with items
# The user captures the required values in the list
* A data entry form is opened, where the user enters the values required for new record in the list
* The user selects the status of the new record. The status is selected once for all values in the list
* The user starts a new discussion where he gives detailed explanations for the new record in the list (Probably it is not necessary to comment, when a brand new value is added in the list).
* The user saves the values
h3. Result
# The status, selected during entering values in the list, though selected once for the whole record is assigned to each individual value.
# For each one of the newly created values in the list is kept information about: the researcher, who entered the value, the project/ organization, the date and time when it is entered, the status of the value.
# The record in the list could be edited and deleted by the author and the project admin before being approved and published.
# The new record in the list is visible only for the team members of the current project before being approved and published.
# After the RS Project Admin approves the newly entered record in the list, and after it is published all values in the record become with status “Original”. This means that this new record in the list becomes part of the original version of the record.
{color:#ff6600}Two more{color}
{color:#ff6600}1. The user adds a completely new field that is available form the template. i.e. the source did not include the field but the field is part of the superset of fields for that record type. The user could add the field and value. Question: Would this be counted as an original. Probably not.{color}
{color:#ff6600}2. The user does not search for the record but gets to it another way, eg a link from a discussion, data basket etc.{color}