A research data management (RDM) strategy sets out how your organisation supports good data management, and links its services and policies to a clear vision and mission. As a data steward, you often prepare the strategy or help write it, whether for an ELIXIR Node or a small support team.
The sections below are in the order in which you build a strategy, from groundwork to review. In a federated set-up with several partner organisations, each step takes longer because all partners have to agree, and the strategy should add to what partners already do (see this example from ELIXIR Germany).
Lay the groundwork
Before you write, find out who should be involved and where your organisation stands now.
Set up a team and get a mandate
Don’t write the strategy alone. A small group works better, for example a coordinator who knows the organisation’s priorities and someone from support or training who hears what researchers ask for. Also find a manager who backs the strategy, and agree early on who approves it.
Define your scope
Decide who your RDM activities serve. Researchers in one institute need a different strategy than researchers across a whole country.
Then list the policies your organisation has to follow at local, national and international level, such as funder requirements and your institution’s data policy. You can look up funder and journal policies in FAIRsharing. Their goals often shape your vision and mission.
In Canada, funders require a strategy, so institutions have published more than 200 of them.
Take stock of where you are
Map the people and infrastructure you have, and what you still need. This also helps when you plan budgets. Collect what already exists, such as service plans, policies and earlier user surveys.
Then use the Handbook’s maturity indicators as a self-assessment. Pick the areas that matter most to you and compare the level descriptions with your situation. The gaps you find are input for your goals.
Write the strategy
Turn your groundwork into a vision and concrete goals.
Write a vision and mission
The vision describes the state your organisation wants to enable, at a set point in time. For example: “Our researchers apply good data management practices, so their research outputs are available to the global research community according to the principles of Open Science, reproducible research and FAIR.”
The mission defines the objectives needed to reach the vision, and how you’ll reach them. You can have more than one mission statement. ELIXIR Sweden wrote theirs in a workshop when the team grew from two to five people.
Set goals and plan activities
Write each goal so you can check it later. “All new PhD candidates attend an RDM course in their first year” is easier to measure than “improve RDM skills”. For each goal, decide which activities deliver it and who is responsible for them. Activities can include support services, policies, documentation, software, outreach, training and guidelines.
Keep it focused
Aim for one or two pages that people read, and put the details in an action plan. You don’t have to cover everything. The Global Open Research Commons (GORC) model lists the elements a strategy can cover, such as human capacity or sustainability, so you can pick the ones that matter most to you. The NBIS Data Management Strategy shows what this looks like for an ELIXIR Node.
Keep the strategy separate from policies and data management plans (DMPs). A policy sets formal rules, and a DMP covers one research project. Your strategy looks across projects and points to those documents for the details.
Put it into practice
A strategy only helps if people know it and you check whether it works.
Share the strategy
Publish the strategy where all staff can find it, for example on your intranet or website. Present it at a team meeting, and add it to onboarding for new staff who work with data. Include a communication plan in the strategy itself. In a distributed ELIXIR Node, plan extra communication and regular check-ins between partners.
Monitor and review
Track progress with key performance indicators (KPIs) linked to your goals, for example the number of DMPs your team reviews per year. Review the strategy once or twice a year, and sooner after a big change such as new funding or staff leaving. Make sure more than one person owns the review. Otherwise the strategy disappears when that person leaves.
External resources
| Category | Resource | Description |
|---|---|---|
| External | ELITMa – Node data management strategy module | Online module with exercises for writing a data management strategy for an ELIXIR Node. |
| External | Global Open Research Commons (GORC) International Model, version 1.1 | Research Data Alliance (RDA) model of the elements a research data commons can cover, useful to decide what your strategy includes. |
| External | NBIS Data Management Strategy | Published strategy of the data management team at NBIS, the Swedish ELIXIR Node. |
| External | Published institutional RDM strategies (Canada) | Strategies published by Canadian universities and research hospitals, useful as examples when you write your own. |
| External | FAIRsharing – Policies | Searchable list of data policies from funders, journals and institutions. |