The following communities have been identified as being involved in the provision of DARIAH activity IKC

  • Data Creation Community: The Data Creation Community is involved in the DARIAH activities at different levels and different in-kinds contributions, especially in the “Development of Software” and “Creating resources in-kinds”. This community creates the research data, which in the DARIAH case are represented by digitised cultural objects, as well as training resources.
  • Data Management Community: also in this case, this community is involved in different DARIAH activities, especially in the DARIAH “Consulting” in-kinds. The Data management community has two main aims: on the one hand, it makes sure that the data quality is as high as possible. It also administers and curates the research data.
  • Data Provision Community: It’s involved in the DARIAH activities, especially at the level Consulting and Coordination. The ultimate goal of the DARIAH Coordination is that of making the data and services in DARIAH recognised among the research community. Similarly, as part of the Consulting Activity, the main aim might be that of making the DARIAH resources and activities well known and accessible.

Activity Provision Community Roles

The following roles are identified in the Activity community

  • Activity Provision Subsystem (passive role): the community component representing the activity provision community
  • Activity Owner (active role): the agent (individual or institution) who owns, and is ultimately responsibility for, the owned activity.
  • Activity Provider (active/passive role): different from the activity implementer, the agent (individual or institution) that performs a certain action in the context of DARIAH.
  • Activity Implementer (active role): the agent that executes a certain action on behalf of the activity provider.
  • Activity Consumer (active role): the agent (individual/ institution) that receives, consumes or experiences the outputs created during an activity.
  • Activity Manager (active role): has a day to day overview of the running of the activity. This role is also the point of contact for issues with the expected running of the activity
  • Activity Management System (passive role): the community component representing the activity management system
  • Activity Support (active role): agent who provides support for the planning and running of an activity. This can be represented by a service (link to service here).

Activity Provision Community Behaviours

The following Activity Provision behaviours have been identified:

  • Activity Management: the behaviour undertaken by the Activity Manager, who overviews the running of the activities on a daily basis.
  • Activity Support: the behaviour of the Activity Support agent, offering support for the planning and running of an activity.
  • Activity Execution: the behaviour of a number of agents (Activity Provider, Activity Implementer) performing certain actions in the context of an activity.