A behaviour of a community is a composition of processes addressing specific scientific concerns. Behaviours are performed by 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. The community behaviours model focuses on Model Overview#ref_minimalset. 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.
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.
The key behaviours of the data acquisition community through the interaction of the community roles include:
Design Experiment: A behaviour performed by a 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.
Data Collection: 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 a Observer, associating consistent time-stamps and necessary metadata.
The roles of the data acquisition community are described in Acquisition Community Roles.
The main behaviours of the data curation community include:
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.
The roles of the data curation community which are described at Curation Roles.
The data publishing community may perform the following behaviours:
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.
The roles of the data publication community are described at Publication Roles.
The following behaviours of the data processing community are modelled:
Describe Service: A behaviour performed by a Service Provider to provide the information needed in order to use a service .
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 Terminology and Glossary for the definitions of these functionalities).
The roles of the data processing community are described at Processing Roles.
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.
User Behaviour Tracking (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 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.
The roles of the data use community are described at Use Roles.