Data Management

This module takes you through the main steps for developing or refining a Node data management strategy.

A Node data management strategy describes how a Node wants to organise, support and develop data management across its activities and partnerships. It is broader than a Data Management Plan (DMP), which usually focuses on how data will be managed within a specific research project. A Node strategy looks across projects and institutions and considers priorities, responsibilities, services, expertise, resources and longer term development.

It is also different from a data management policy, which typically sets out formal rules or commitments, for example those required by a funder or hosting institution. A Node may already have one or more such policies in place through its hosting institution or partner organisations. A strategy works alongside these policies rather than replacing them, helping to coordinate priorities, activities and responsibilities for data management across the Node.

As you work through the module, you will build the main elements of such a strategy. You can start from scratch, build on existing strategies, policies or plans, or return to individual chapters when a particular question needs attention.

What to expect

Together, these chapters take you from defining the scope of the strategy to putting it into action and keeping it alive as a living document, revisited and updated as your Node’s situation changes.

What makes this challenging in practice

Developing a Node data management strategy is rarely just about writing a document. Questions may arise about mandate, what belongs at Node level and what sits with institutions or other organisations, differences between partners, coordination, expertise, staff time, funding and realistic expectations.

You do not need to solve these before you start. The chapters will help you work through them.

Bring what you already have

Use existing information where you can. This might include strategies, Service Delivery Plans, policies, service descriptions, maturity assessments, surveys, training plans or notes from earlier discussions. Do not wait until everything is complete. Missing information, unclear responsibilities and different views between partners are useful input too.

Do not do it alone

A Node data management strategy usually touches more than one role, institution or service. Involve colleagues who bring different perspectives, for example someone who manages your data infrastructure, someone who leads training, or your institution’s legal or data protection contact. You do not need everyone in every exercise.

Quick check before you start

Take a minute to think about your starting point.

• Do you already have a strategy or related documents? Check with your Node Coordinator, or look for a Service Delivery Plan, an institutional RDM policy or notes from an earlier survey.
• Who else should be involved? Think of specific people rather than just roles, for example whoever manages your repository, your institution’s data protection contact or a researcher who has struggled with data management support.
• Which responsibilities sit with the Node, and which sit elsewhere?
• Is there a current challenge or opportunity that makes this work timely?

How this module was developed

This self-paced module builds on several editions of the ELITMa Node Data Management Strategy training. It draws on presentations, exercises, shared notes, Node portfolios, discussions and examples by participating ELIXIR Nodes.

The first edition was held in Espoo in 2023, followed by a second edition in Tartu in 2025. These sessions helped shape the topics and practical approach used throughout the module. The material will continue to develop through the 2026 Barcelona edition and other future Node discussions and training events.

Key terms used in this module

A few terms are used in a specific way throughout the module:

• Node data management strategy: how a Node wants to organise, support and develop data management across its activities and partnerships.
• Data management policy: formal rules or commitments for data management, for example those required by a funder or hosting institution.
• Node data management strategy: how a Node wants to organise, support and develop data management across its activities and partnerships.
• Data management policy: formal rules or commitments for data management, for example those required by a funder or hosting institution.
• Mandate: whether the Node has the remit or authority to act.
• Node role: what contribution the Node should make.
• Decision owner: who can agree about the direction.
• Priority: an area or direction selected to take forward.
• Action: a concrete step to move a priority forward.
• Action lead: the person or group keeping an action moving.
• Capacity and resources: the people, expertise, time and funding that are available to make progress.
• Maturity: a description of the current situation, not a target or ranking.

Ready?

In Chapter 1, you will look at why a Node data management strategy can be useful and what you want it to help your Node achieve.

Start with Chapter 1

Related events

Upcoming events

Past events