# data[].attributes.body
Develop VU-wide infrastructure for sustainable research software and archiving research software. Git-hub?

# data[].attributes.body
Put structural organisation in place to update and improve the RDS portal. Promote the RDS portal as the one-stop-shop for information on RDM

# data[].attributes.body
Document procedures, processes and workflows following the core trust seal standard for digital repositories. This enables functional administration of RDM-tools and possible future certification of VU digital repositories

# data[].attributes.body
Improve and update RDM tool overview and positioning based on available tools and user scenario's. To help researchers find the best possible RDM-solution

# data[].attributes.body
Develop a generic workflow management to handle all RDM related administration and steps in one place. This should avoid double work for researchers and enables the generation of documents needed in the research process (f.i. informed consent, DPIA).

# data[].attributes.body
Provide an online accessible place where researchers and handlers handle the 'paperwork' surrounding research projects. Front-end of the RDM workflow management system

# data[].attributes.body
Integrate decision support tooling into the generic workflow. f.i. storage finder to be integrated in the workflow management system

# data[].attributes.body
Harmonise the current intake and request procedures. Create similar steps for the different RDM-solutions, to make requests and intake easier and more understandable for researchers

# data[].attributes.body
Improve RDM information and requests on AskIT. Helps to improve requests for RDM-tooling

# data[].attributes.body
develop a collaborative knowledge base within the workflow management to improve research support activities. This could contain best-practices, FAQs and how-to-guides

# data[].attributes.body
Develop and provide training on software skills based on the Software Carpentries

# data[].attributes.body
Stimulate sustainable research software by raising awareness. Set up an awareness campaign. Highlight stories of successfully reused research software and demonstrating its advantages

# data[].attributes.body
Create workflow documents or infographics for all RDM-tools that need request and/or intake. Provides overview of tools and better understanding of the process

# data[].attributes.body
Prepare the selection and implementation centrally purchased and supported solution (or, if necessary due to differences between disciplines, a set of solutions): Mapping the potential users, at group level.

# data[].attributes.body
Defining the functional and non-functional requirements and wishes. Special attention is needed here for irreconcilable differences in requirements between groups.

# data[].attributes.body
Set up the (functional) support organisation. Set up agreements for management and ownership and a financing model.

# data[].attributes.body
For solutions that are not yet in use, this means the elaboration of documentation for a process for tendering, selection and implementation of the solution

# data[].attributes.body
Match intended users with possible solutions. Make a first comparison between requirements and wishes and the possibilities of candidates

# data[].attributes.body
Analyse results of 2022 pilot-projects on data-exchange. OSF vs Yoda and SciStor vs Research Drive. Discuss with researchers needs and wishes for data-exchange solutions.  Impact analysis on security issues

# data[].attributes.body
Integration of two storage solutions based on researchers needs and feasibility

# data[].attributes.body
Preparation for Research Cloud implementation.

# data[].attributes.body
Preparation for SRAM implementation. Based on 2-3 pilot-projects to:
shape the functional administration, provide information on SRAM and the use of SRAM, develop training material, determine VU services to be offered via SRAM

# data[].attributes.body
Assess the cross-faculty needs for SaaS that supports specific phases of the research life cycle, e.g. Qualtrics, Castor, automated transcription software

# data[].attributes.body
Facilitate the process of choosing appropriate SaaS and of obtaining and managing contracts for specific SaaS so that they are available in a timely manner for researchers

# data[].attributes.body
Review what SaaS tools are already available at the VU and how they are best used in combination with existing and developing infrastructure

E.g. We have Microsoft Access for creating and managing databases; can Access databases be stored on SharePoint for group access? Can an Access Database be stored on Research Drive?

# data[].attributes.body
Research and review open source SaaS for specific RDM tasks; support training of interested data stewards in the use such open source SaaS so that they can teach researchers

# data[].attributes.body
Investigate making Microsoft Azure services available to researchers, for example, data analytics, VM's etc.