Editing SV Community Behaviours

A '''behaviour''' of a community is a composition of '''processes''' addressing specific scientific concerns. Behaviours are  performed by [[SV Community Roles|'''SV Community Roles''']]. In the ENVRI RM, the modelling of community behaviours is based on analysis of the common operations of research infrastructures which has resulted in [[Appendix A Common Requirements of Environmental Research Infrastructures|'''Appendix A Common Requirements of Environmental Research Infrastructures''']]. The community behaviours model focuses on supporting a predefined [[Model_Overview#Common_Functions_within_a_Common_Lifecycle|'''minimal set''']] of functionalities. A community behaviour can be either a single function or a composition of several functions from the function list. 

A '''process''' is a collection of '''steps''' taking place in a prescribed manner and leading to an objective. A '''step''' is an abstraction of an action, used in a '''process''', that leaves unspecified the objects that participate in that action. Steps are introduced in the definition because not all the action details need be specified  in the composition.

<p style="background-color: #fcfcfc; border-radius: 5px; border: 1px solid #ccc;  padding: 10px 10px 10px 20px;">
'''Note'''<br>
The Science viewpoint of the ENVRI RM only defines high level behaviours. A behaviour can be refined further by defining its constituting processes and steps, however, this task is left to the actual system designers.
</p>

== <span style="color: #BBCE00"><span id="BehavioursoftheDataAcquisitionCommunity">Behaviours of the Data Acquisition Community</span></span> ==

The key behaviours of the data acquisition community through the interaction of the community roles include:

* <span id="DesignExperiment">'''Design Experiment'''</span>: A behaviour performed by an ''Environmental Scientist'' that designs the scientific experiment which motivates the data acquisition activities.
* '''Design Measurement Model''': A behaviour performed by a ''Measurement Model Designer'' that designs the measurement or monitoring model based on scientific requirements.
* <span id="InstrumentConfiguration">'''Instrument Configuration'''</span>: A behaviour performed by a ''Technician'' that sets up a ''sensor'' or a ''sensor network''.
* '''Instrument Calibration''':  A behaviour performed by a ''Technician'' that controls and records the process of aligning or testing a ''sensor'' against dependable standards or specified verification processes.
* <span id="DataCollection">'''Data Collection'''</span>:  A behaviour performed by a ''Data Collector'' that control and monitor the collection of the digital values from a ''sensor'' instrument or a human sensor, such as a ''Measurer'' or an ''Observer'', associating consistent time-stamps and necessary metadata.

{| class="wikitable" style="width: 80%;"
|-
! style="padding: 10px"| <div style='text-align: left;'>'''Acquisition Community Behaviours'''</div>
|-
| style="background-color:#ffffff;"| <center>[[File:SVAcquisitionCommunityBehaviours.png]]</center>
<div style='text-align: right;'>'''[[Notation of Science Viewpoint Models#Community Behaviours|Notation]]'''</div>
|}

The roles of the data acquisition community are described in [[SV Community Roles#RolesintheDataAcquisitionCommunity|'''Acquisition Community Roles''']].

== <span style="color: #BBCE00"><span id="BehavioursoftheDataCurationCommunity">Behaviours of the Data Curation Community</span></span> ==

The main behaviours of the data curation community include:

* <span id="DataQualityChecking">'''Data Quality Checking'''</span>: A behaviour performed by a ''Data Curator'' that detects and corrects (or removes) corrupt, inconsistent or inaccurate records from data sets.
* <span id="DataPreservation">'''Data Preservation'''</span>: A behaviour performed by a ''Data Curator'' that deposits (over long-term) the data and metadata or other supplementary data and methods according to specified policies, and makes them accessible on request.
* '''Data Product Generation''': A behaviour performed by a ''Data Curator'' that processes data against requirement specifications and standardised formats and descriptions.
* '''Data Replication''': A behaviour performed by a ''Storage Administrator'' that creates, deletes and maintains the consistency of copies of a data set on multiple storage devices.
* '''Data Identification''': A behaviour performed by a ''PID manager'' which provides a unique PID for data and metadata being curated.
* '''Select or Build Local Conceptual Model''': A behaviour performed by a ''Semantic Curator'' which supports the annotation of data and metadata.
* '''Data Annotation''': A behaviour performed by a ''Semantic Curator'' which supports the linking of data and metadata with a local conceptual model.

{| class="wikitable" style="width: 80%;"
|-
! style="padding: 10px"| <div style='text-align: left;'>'''Curation Community Behaviours'''</div>
|-
| style="background-color:#ffffff;"| <center>[[File:SVCurationCommunityBehaviours.png]]</center>
<div style='text-align: right;'>'''[[Notation of Science Viewpoint Models#Community Behaviours|Notation]]'''</div>
|}

The roles of the data curation community which are described at [[SV Community Roles#RolesintheDataCurationCommunity|'''Curation Roles''']].

== <span style="color: #BBCE00"><span id="BehavioursoftheDataPublishingCommunity">Behaviours of the Data Publishing Community</span></span> ==

The data publishing community may perform the following behaviours:

* '''Data Publication''': A behaviour that provides clean, well-annotated, anonymity-preserving datasets in a suitable format, and by following specified data-publication and sharing policies, to make the datasets accessible publicly or to those who agree to certain conditions of use, and to individuals who meet certain professional criteria. 
* '''Semantic Harmonisation''': A behaviour enabled by a ''Semantic Mediator'' that unifies similar data (knowledge) models based on the consensus of collaborative domain experts to achieve better data (knowledge) reuse and semantic interoperability.
* <span id="DataDiscoveryandAccess">'''Data Discovery and Access'''</span>: A behaviour enabled by a ''Data Discovery and Access System'' that retrieves requested data from a data resource by using suitable search technology.
* '''Data Citation''': A behaviour performed by a ''PID Manager'' that assigns an accurate, consistent and standardised reference to a data object, in the same way as researchers routinely provide a bibliographic reference to printed resources. The RI publishing the data can define the citation contents such as authors, and dates for different citation styles.
* '''Metadata Harvesting''': A behaviour performed by a metadata harvester to gather metadata from data objects in order to construct catalogues of the available information. A functionality that (regularly) collects metadata (in agreed formats) from different sources.

{| class="wikitable" style="width: 80%;"
|-
! style="padding: 10px"| <div style='text-align: left;'>'''Publication Community Behaviours'''</div>
|-
| style="background-color:#ffffff;"| <center>[[File:SVPublishingCommunityBehaviours.png]]</center>
<div style='text-align: right;'>'''[[Notation of Science Viewpoint Models#Community Behaviours|Notation]]'''</div>
|}

The roles of the data publication community are described at [[SV Community Roles#RolesintheDataPublishingCommunity|'''Publication Roles''']].

== <span style="color: #BBCE00"><span id="BehavioursoftheDataProcessingCommunity">Behaviours of the Data Processing Community</span></span> ==

The following behaviours of the data processing community are modelled:

* '''Coordinate Service''': A behaviour performed by a ''Service Provider'' to coordinate the actions of distributed applications in order to reach consistent agreement on the outcome of distributed transactions.
* '''Compose Service''':  A behaviour performed by a ''Service Provider'' to combine multiple services which can be achieved by either ''Choreography'' or ''Orchestration''. '''Service Choreography''' is a collaboration between ''Service Providers'' and ''Service Consumers''. '''Service Orchestration''' is the behaviour that a ''Service Provider'' performs internally to realise a service that it provides <nowiki>[</nowiki>[[Bibliography#35|'''35''']]<nowiki>]</nowiki>. 
* '''Customise Processing Environment''': A behaviour performed by a processing environment planner to enable a Data Processing Subsystem to prepare customised infrastructure and service platforms for managing specific data processing applications optimally, including the planning, provisioning and deployment sub-activities.
* '''Describe Service''': A behaviour performed by a ''Service Provider'' to provide the information needed in order to use a service <nowiki>[</nowiki>[[Bibliography#8|'''8''']]<nowiki>]</nowiki>.
* '''Register Service''': A behaviour performed by a ''Service Provider'' to make the service visible to ''Service Consumers'' by registering it in a service registry <nowiki>[</nowiki>[[Bibliography#8|'''8''']]<nowiki>]</nowiki>.

These are general behaviours of a service-oriented computing model. In the context of environmental science research infrastructures, a data processing community will focus on the implementation of domain special services, in particular those supporting '''Data Assimilation, Data Analysis, Data Mining, Data Extraction, Scientific Modelling and Simulation, (Scientific) Workflow Enactment''' (See [https://wiki.biovel.eu/display/ERM/Terminology+and+Glossary '''Terminology and Glossary'''] for the definitions of these functionalities).

{| class="wikitable" style="width: 80%;"
|-
! style="padding: 10px"| <div style='text-align: left;'>'''Processing Community Behaviours'''</div>
|-
| style="background-color:#ffffff;"| <center>[[File:SVProcessingCommunityBehaviours.png]]</center>
<div style='text-align: right;'>'''[[Notation of Science Viewpoint Models#Community Behaviours|Notation]]'''</div>
|}

The roles of the data processing community are described at [[SV Community Roles#RolesintheDataProcessingCommunity|'''Processing Roles''']].

== <span style="color: #BBCE00"><span id="BehavioursoftheDataUseCommunity">Behaviours of the Data Use Community</span></span> ==

The data use community can be divided in two main groups: (1) the behaviours performed by active roles (human actors) and (2) the behaviours performed by passive roles (computer resources). The first group encompass the activities performed by human actors using the RI to interact with the different components of the RI. This can extend to all the actors in all the communities defined in the SV, in addition to the ones in the use community, these behaviours form a specialisation of the use community which can be called community support behaviours (or user support behaviours). The second group corresponds to the behaviours that enable the authorisation, authentication, and accounting of the activities of users, conforming a second specialisation which can be called  AAAI behaviours.

* '''Co-create''': A behaviour in which active roles from all communities participate in the design and planning of activities for the collection, preservation, analysis or publishing of research data.
* '''Collaborate''': A behaviour performed by active roles which entails assisting/participating in some of the phases of the collection, preservation, analysis or publishing of research data.
* '''Contribute''': A behaviour performed by active roles which entails directly collecting, preserving, analysing, or publishing research data held by the RI, according to a predefined protocol.
* <span id="UserBehaviourTracking">'''User Behaviour Tracking</span> (sysnonym: real user monitoring)''': A behaviour enabled by a Data Use Subsystem that to track the Users. User Behaviour Tracking is the analysis of visitor behaviour on a website. The analysis of an individual visitor's behaviour may be used to provide options or content that relates to their implied preferences; either during a visit or in the future visits. Additionally, it can be user to track content use and performance.
* '''User Profile Management''': A behaviour enabled by a ''Data Use Subsystem'' to support persistent and mobile profiles, where profiles will include preferred interaction settings, preferred computational resource settings, and so on.
* '''User Working Space Management''': A behaviour enabled by a ''Data Use Subsystem'' to support work spaces that allow data, document and code continuity between connection sessions and accessible from multiple sites or mobile smart devices.
* '''User Working Relationships Management: A behaviour enabled by a ''Data Use Subsystem'' to support a record of working relationships, (virtual) group memberships and friends.
* '''User Work Group Support''': A behaviour enabled by a ''Data Use Subsystem'' to support controlled sharing, collaborative work and publication of results, with persistent and externally citable PIDs.

{| class="wikitable" style="width: 80%;"
|-
! style="padding: 10px"| <div style='text-align: left;'>'''Use Community Behaviours'''</div>
|-
| style="background-color:#ffffff;"| <center>[[File:SVUseCommunityBehaviours.png]]</center>
<div style='text-align: right;'>'''[[Notation of Science Viewpoint Models#Community Behaviours|Notation]]'''</div>
|}

The roles of the data use community are described at [[SV Community Roles#RolesintheDataUseCommunity|'''Use Roles''']].

[[Category:Science Viewpoint]]