Introduction
Academic institutions are generating vast amounts of research data across numerous disciplines. In the spirit of open science and promoting the highest levels of research integrity, institutions develop policies and procedures to clarify the requirements of researchers for data management, but also to guide them in meeting these. Like all such governance frameworks, they are only as good as the manner in which they are implemented and used. It has become common practice to make mandatory training a part of employment, and most researchers will complete this training on induction and then conduct annual refreshers or undertake new training modules as required.
Research Data Management Plans (RDMPs) are the cornerstone of good research practice, and all institutions require them (; ). There are abundant reasons why RDMPs are best practice and should be developed and used, but whilst some believe they are mandatory, they are not prescribed under any legislation. In Australia, the National Health and Medical Research Council (NHMRC) sets out the responsibilities institutions have with respect to responsible behaviour in the Australian Code for the Responsible Conduct of Research (), ‘the Code’ (). Whilst this is not a statute, since it is also endorsed by the Australian Research Council and Universities Australia, it acts as a de facto requirement for all institutions that receive federal funding. In practice, no academic organisation in Australia would not comply with it. The Code sets out a series of principles expected of institutions, although there is no mechanism in place to verify that they obey the principles.
The Code requires institutions to have policies for managing research data and primary materials, in addition to providing guidance and training to assist researchers applying the principles. The Code’s principles cover data ownership, stewardship and control of research data and primary materials, although the Code does not provide explicit guidance on how this should be delivered—allowing a broad range of interpretations. The NHMRC has instead published supporting guidance for the Code in a supplementary guide (Univ. Australia et al.). The NHMRC strongly encourages the development and use of a management plan for each research project, but does not mandate this. To complement the Code, the NHMRC has also published an ethical guidance document called the National Statement (NS) on Ethical Conduct in Humans (2007, as amended in 2018- the NS).
Like the Code, the NS is not a legal instrument, but it intersects with some activities that require its use that are under legislation, such as the Therapeutic Goods Act (1989) for clinical trial activities and the various Commonwealth, State and Territory and private sector data privacy legislation. Like the Code, the NS also describes the need for RDMPs as best practice, particularly in the creation of research databanks, but does not mandate their usage. The Code and the NS are guidelines that act at a national level and are signed up to by all universities. Given their importance, there may be an expectation that there was some level of standardisation in their implementation and operation across Australia.
Environmental Scan
Given the importance of Research Data and Primary Material (RD+PM) management plans, and as we were about to embark on a refresh of the QUT RD+PM policy and procedure, we sought to understand how it was currently being done, what researchers thought of it and how they thought it might be improved. We undertook a review of the QUT approach to managing RDMPs through the evaluation of the existing policies, procedures, related websites and any work instructions or departmental guidance. The QUT library was primarily responsible for managing RDMPs and had constructed a website with an online tool. Whilst the library reported a high level of utilisation, it was revealed that as it was not a structured database, it could not be analysed for content, and there was no record of how the plans were actually being used or monitored.
In addition to our review of our own activity, we examined the various approaches to Research Data Management (RDM) across 20 Australian Universities through an examination of their online policies, procedures, guidance material and forms. We have not presented all of the findings of that review here, as the content rapidly changes, and several have been undertaking their own reviews and enhancement of their processes. However, we found that several of the websites did not provide clear guidance material, and there was practically no consistency between them in terms of an approach.
Undertaking an Internal Consultation Process to Identify the Unmet Need
Like all QUT policies, the RDM policy is subject to cyclical review every three years, and the Office of eResearch was charged with the responsibility of performing a review. We formed the Research Data Management Strategy-Implementation Group (RDMS-IG), which comprised representative key academics across science, biomedical science and the humanities, in addition to the Office of eResearch and the Office of Research Ethics and Integrity. The IG met virtually on a monthly basis to provide guidance to the QUT eResearch team working on revisions to the policy and procedure (P&P). The RDMS-IG identified collectively and through extensive one-on-one interviews with a range of academic and professional staff, that, like many institutional policies and procedures, the DMP was not widely known amongst their colleagues, and they did not refer to it on a regular basis. Instead, they noted that staff and students were required to make themselves aware of and to abide by the relevant P&P, and that a number of internal processes were in place to ensure that this happens. Through this stakeholder engagement, it was agreed that Primary Material management plans should be included.
Whilst the knowledge and application of institutional policies is a requirement of employment compliance, they are regarded as a chore that must be done at the start of employment or enrolment—and can be largely forgotten about in between annual mandatory training requirements. This formal compliance requirement has had an unfortunate effect, moving researchers into a ‘compliance-mentality,’ motivated largely by the need to check off a box, rather than approaching RDM+PM management as an important core component of conducting research itself. It should be noted that this is observed in related areas such as ethical review, where the need to ‘get ethical approval’ has replaced the primary notion of being ethical and making sure that the research project itself is intrinsically ethical ().
However, it was clear that whilst Policies and Procedures (P&Ps) related to Occupational Health and Safety (OHS), and other key compliances had mandatory training through an Learning Management System (LMS), the DMP webpage was not seen as essential, and a review of content indicated that there was a need for a refresh. Indeed, a key finding from the IG activity was the need to tailor the content of a DMP to the type of research being conducted. A DMP for law would necessarily be quite different to one for earth sciences or civil engineering.
Anecdotally, it was revealed to us that a lack of mandatory requirements for DMPs. together with a-less-than-friendly user process meant that DMPs were not taken as seriously as the university would like. We also found that in each institution, there was not one person with responsibility for its oversight, and the majority of senior people, while committed to the ideals and objectives of responsible research practice, felt they were under-resourced to deliver training to their staff and students and monitor how RDM was being conducted in everyday situations.
We responded by developing an institutional framework for RDM+PM management, taking a different co-design approach. Importantly, we adopted the approach to include PM, not just RDM. We sought to explore how we could create policy and guidance material for RDM and PM that fulfils the principles set out in the Australian Code for the Responsible Conduct of Research and in other international consensus policies such as the FAIR principles ().
We recognised that there is a natural alignment, especially for a number of disciplines, and RDM and PM plans can come in different forms. To deliver to this approach, we developed an online RDM+PM checklist to support and direct researchers. This checklist currently asks seven questions, taking into consideration the different needs of disciplines spanning Arts, Law, Business, Humanities, Health, Environment and STEM. In this manuscript, we provide an overview of the checklist tool, its inherent ability to enhance the engagement between researchers, their research students and all key stakeholders across the institution, including: research grants, ethics, facilities management, audit and risk, faculties, schools and research centres. The checklist captures real-time business intelligence (BI) statistics that allows us to: i) understand key blockers for any given researcher need and identify stakeholders to engage with to resolve them; ii) continuous feedback on the policy and guidance material; and iii) the ability to capture real-time BI data that can be used to define a metric to quantify an institution’s maturity in managing research data, which we refer to as its Data Quotient™.
Methods: The Approach to Devising the RDM+PM Checklist Tool
In providing simplified guidance to researchers, we ask seven questions at the outset of their research projects around the following topics: do you understand your obligations as per the university RDM+PM policy?; does your research involve humans and animals?; are you creating, collecting or receiving digital data?; are you creating, collecting or receiving physical (primary) materials?; will the data be available for publishing?; and are there any limitations to sharing your research data?
We decided to implement an online tool to ask these questions. We summarise that the aim of the RDM+PM Checklist is to: i) direct researchers so they can have relevant conversations with QUT Subject Matter Experts, depending on the nature and content of their specific research project; ii) create a skeleton or framework for the creation of RDMPs, relevant to the evolving requirements of their project; iii) provide researchers and research supervisors with a tool to identify, monitor, and report on the specific areas of data and primary materials governance that their project requires; and iv) establish a repository of checklists that will facilitate the usable reporting of research activities across the institution and the ability to share these with researchers external to the institution. Figure 1 outlines the process we followed.
Development Principles
The tool is written as a responsive web application with a React frontend and a stateless API backend. Frontend and backend components are written in JavaScript and leverage cloud native apis to service storage, authentication, authorisation and monitoring requirements. The following principles guided the development of the tool:
- High availability: the tool will be available for use outside of scheduled maintenance periods
- Accessible: the tool is accessible to all university users. Usability is reviewed against university guidelines and audited by external third parties
- Low cost: the tool is low cost to run, and the cost of the provisioning, running, and maintaining the tool will not incur a cost barrier to the tool owners or its users
- Self-service: users are able to perform all required interactions with minimal training, rather than a formal onboarding process
Architectural Design of the RDM+PM Checklist
Figure 2 provides an overview of the architectural design implemented in Amazon Web Services. Each of the architectural components are described in Table 1.
REF | BUILDING BLOCK | CHARACTERISTICS |
---|---|---|
AC-01 | WAF | Web Application Firewall: protects application and AC-06, AC-08 and AC-11 from common web attacks. |
AC-02 | CDN | Content Delivery Network: Fast transfer of statics assets and protects against common malicious attacks AC-01 |
AC-03 | Front-end Distribution | Static website resources fronted by AC-02, not directly accessible. |
AC-04 | Front-end Access Logs | Web Application Logs. Records access to frontend distribution resources. |
AC-05 | Cognito | AWS Cognito: Integrates with AC-06, applies access control and user pools |
AC-06 | IDP | IDP: Integrates with AC-05 and AC-07, provides university standard Single Sign-On capabilities |
AC-07 | API Gateway | API Gateway: Integrates with AC-07, reviews authorisation token to allow checklist access to approved users |
AC-08 | Checklist API | Checklist API: Integrates with AC-09, AC-11, AC-12, retrieves researcher details, ORCID ID, and registered project/application details from PURE (AC-09, AC-11). Saves checklist responses (AC-12) |
AC-09 | Pure API Secrets | AWS SSM: Pure API Secrets are stored encrypted and are restricted by AWS IAM access control policies |
AC-10 | API Access Logs | AWS Cloudwatch; Records access to Checklist API endpoints |
AC-11 | Pure API | PURE Rest APIs: Restricted endpoint access. Access keys and secrets stored in SSM (AC-09) |
AC-12 | Checklist Storage | AWS Dynamodb: Storage engine for checklist responses |
Results and Discussion
Summary of key findings from consultations
As part of our review to revise the policy and procedures for RDM, we asked standard questions including:
- Should every research project have institutional project data storage space created by default?
- What should be the standard storage environment?
- How do we identify and highlight restricted technology use as part of the Checklist, e.g. Clustered Regularly Interspaced Short Palindromic Repeats (CRISPR) policy, etc.
For the top 20 Australian universities, we examined whether they had a current policy, who is responsible for its implementation and management, what resources are available for help with developing plans, how compliance was monitored and how plans integrated with research ethics and integrity (where applicable). We also examined whether they used any online tools to capture plans and whether these were able to provide a means to find data. The findings are summarised in Table 2. Finally, we explored whether institutions provided support, such as running courses in how to develop RDM or PM plans for undergraduates and staff, and whether this was required as part of policy compliance. Based on our analysis, we then focused our desktop review on each QUT faculty. The findings are summarised in Table 3.
AUS.RANK | GLOBALRANK | UNIVERSITY | DATA MANAGEMENT POLICY | DATA MANAGEMENT PLAN | GUIDANCE/TRAINING | TOOL(Y/N) | CHECKLIST(Y/N) | WHO MANAGES DM POLICY & DMP | ||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
HAS A DATA MANAGMENT POLICY (Y/N) | CURRENT | YEAR | REQUIRESRDMP(Y/N) | WEBSITE | ||||||||
1 | 29 | Australian National University (ANU) | No | Refers to its Code of Research Conduct | Yes | Sep–20 | Yes | Yes | DMPTool | No | Library | |
2 | 38 | University of Melbourne | Yes | https://policy.unimelb.edu.au/MPF1242 | No | Nov–13 | Yes | Yes | yes | no | Library | |
3 | 42 | University of Sydney | Yes | https://www.sydney.edu.au/policies/showdoc.aspx?recnum=PDOC2013/337&RendNum=0 | No | 2014 | Yes | Univeristy of Sydney Research Dashboard (DashR) | yes | yes | no | Library |
4 | 43 | University of New South Wales (UNSW) | Yes | https://research.unsw.edu.au/research-data-management-unsw | Yes | 2022 (requires login?) | Yes | ResToolkit | yes | yes | no | Library |
5 | 47 | University of Queensland (UQ) | Yes | https://ppl.app.uq.edu.au/content/4.20.06-research-data-management | No | 2016/Updates Mar–21 | Yes | Research Data Manager | Yes | yes | no | Library |
6 | 58 | Monash University | Yes | https://publicpolicydms.monash.edu/Monash/documents/1935815 | No | Effective date 112–17, review date 2–12–20 | No | – | Yes | No | Yes | Library research infrastructure manager/librarian |
7 | 86 | University of Western Australia (UWA) | No | Part of Research Integrity Policy | Yes | 10–May–21 | Yes | Part of the Toolkit | Yes | Yes | No | Policy Office |
8 | 106 | University of Adelaide | Yes | https://www.adelaide.edu.au/policies/4043/?dsn=policy.document;field=data;id=7345;m=view | Yes | 4–Aug–21 | Yes | Research Data Planner | Yes | Yes | No | Library |
9 | 140 | University of Technology Sydney (UTS) | No | Part of Reearch Data Management Procedures & Research Policy | Yes | 16–Feb–21 | Yes | UTS | No | Yes | No | Library |
10 | 207 | University of Newcastle, Australia (UON) | No | Part of the Research Data & Primary Materials Management Procedure | No | 25-Mar-2021 | Yes | Data Management Dashboard | Yes | Yes | No | Library in partnership with Research office and IT |
11 | 212 | University of Wollongong | Yes | https://documents.uow.edu.au/about/policy/uow116802.html | No | Feb–19 | Yes | RedBox | Yes | No | No | Research Service Office |
12 | 224 | Queensland University of Technology (QUT) | Yes | http://www.mopp.qut.edu.au/D/D_02_08.jsp | Yes | 21–Sep–20 | Yes | QUT Data Management Plan | Yes | Yes | No | Research and innovation division, research services office |
13 | 230 | Curtin University | Yes | https://s30991.pcdn.co/about/wp-content/uploads/sites/5/2022/12/Research_Data_and_Primary_Materials_Policy.pdf | Yes | Dec–21 | Yes | https://libguides.library.curtin.edu.au/c.php?g=202401&p=1333108 | Yes | Yes | no | Library |
14 | 237 | Macquarie University | Yes | https://policies.ma.edu.au/document/view.php?id=300 | Yes | 7–Sep–21 | Yes | Online Portal | Yes | No | No | Ditutally Enabled Research |
15 | 238 | RMIT University | No | Refers its Research Policy & Research Data Management Procedure | Yes | 1–Jun–21 | Yes | Word doc templates for staff and student | No | No | No | Library |
16 | 271 | Deakin University | No | Research Data Management Procedure | No | Review Date 2– Mar–22 | Yes | yes | Yes | Yes | Deakin Research Development/Library | |
17 | 274 | University of South Australia | https://i.unisa.edu.au/policies-and-procedures/university-policies/research/res-17/ | Yes | MyDMP | Yes | Library | |||||
18 | 291 | University of Tasmania | Yes | https://www.imas.utas.edu.au/__data/assets/pdf_file/0009/782118/IMAS-Data-Management-Policy-2015.pdf | Yes | Research Data Portal | Yes | No | Yes | Library | ||
19 | 320 | Griffith University | No | Resource Sheet | Yes | Oct–19 | Yes | Template document | Yes | Yes | No | Policy Office |
20 | 377 | James Cook University (JCU) | No | Management of Data and Information in Research Procedure | – | – | Yes | Research Data JCU Platform | Yes | No | No | Library |
FACULTY | FINDINGS |
---|---|
Engineering |
What? Architectural and building models; Machinery; Robots; Design products; Biomaterial samples; Rock samples; Laboratory books. Where? Stored at numerous facilities, depending on the nature of research activities (multiple sites). How? Storage requirements are determined by the research supervisor, who consults the faculty Laboratory and Technical Services Manager or Facilities Management for guidance. |
Health |
What? Human tissue; Animal tissue; Cell lines; Consent forms; Survey forms; Medical devices; Laboratory books. Where? Stored at multiple sites and other QUT facilities, depending on the nature of research. Some lab books and paperwork stored in storerooms and offices. How? Storage requirements are determined by the research supervisor, who consults the faculty Laboratory and Technical Services Manager, or Facilities Management for guidance. |
Science |
What? Human tissue; Animal tissue; Biomaterial samples; Chemicals; Soil and rock samples; Laboratory books. Where? Stored on site in laboratories or at specialist facilities. How? Storage requirements are determined by the research supervisor, who consults the faculty Laboratory and Technical Services Manager, the faculty Physical Spaces Representative, or Facilities Management for guidance. |
Business and Law |
What? Consent forms; Survey forms; Hardcopy documents; Hardcopy images. Where? Stored in locked cabinets, offices and storerooms on site and off site. How? Storage requirements are determined by the Research Supervisor, who consults the faculty Laboratory and Technical Services manager or Facilities Management for guidance. |
Creative Industries, Education and Social Justice |
What? Consent forms; Survey forms; Hardcopy documents; Hardcopy images; Industrial Design outputs; Creative artefacts. Where? Stored in locked cabinets, offices and storerooms on site and off site. How? Storage requirements are determined by the research supervisor, who consults the faculty Laboratory and Technical Services Manager or Facilities Management for guidance. |
Faculties store research project data on either: institution-provided project space; personal OneDrive folders; or a specialist storage area (on or off site), if it is a requirement of the project.
From this review, we identified there were significant gaps in stakeholder engagement and no consistent approach across faculties. We wanted to ensure that higher degree students and their research supervisor understood the data and primary material needs of their research project; enable a process for ongoing dialogue to address any items that needed extra attention; and be comfortable to ask their supervisor for assistance or contact the responsible university department.
Common themes that emerged during the discussions with stakeholders included:
- Everyone has a commitment to robust data management and all institutions have policies.
- However, what do these data management policies actually deliver in practice?
- How are they used?
- Who monitors them?
- Are they worth the paper they are written on?
- Is there redundancy from requirements elsewhere?
- Who teaches students about the relevance/importance of these?
To develop a research data management plan, it was identified as important to:
- clarify and describe the specific research data needs of their project;
- engage with relevant policies, guidelines, resources, services and contacts;
- share their plan with their supervisor (if they are an HDR student) or collaborators;
- attach an exported copy of their plan as supplementary documentation for grant or ethics applications;
- communicate project data requirements to external and industry partners.
To facilitate this, we implemented an online RDM+PM checklist.
RDM+PM Checklist
The Office of eResearch at QUT has designed a web-based Research Data Management + Primary Materials (RDM+PM) checklist to support and direct researchers, taking into consideration the different needs of disciplines spanning Arts, Law, Business, Humanities, Health, Environment and STEM. The solution conception, design and development has been driven by the end-users, relying on the co-development cohort for iterative feedback and enhancement throughout. The tool utilises QUT Single Sign-On for authentication and tiered user access controls; HDRs, supervisors, and other researchers can all use the same platform for different use cases. The checklist tool will be open sourced.
Once logged in, researchers (HDR or career) can create a checklist specific to their project. The interactive checklist will present the user with simple questions, dynamically updating the question list and directing researchers towards relevant conversations with QUT Subject Matter Experts, depending on the nature and content of the answers they provide. The checklist is shown in Figure 3.
Key functional features in the current version of the Checklist are shown in Table 4.
FEATURE | DESCRIPTION |
---|---|
Web-based | Available to any web accessible device |
Device dynamic | Display dynamically reacts to type of device used for readability |
Tiered Access | User groups are assigned appropriate roles, and read/write access levels are customised to appropriate groups |
SSO integration | Integration with institution Single Sign-On capabilities |
User Groups | Multiple types of User are defined in groups, with appropriate access/feature set applied |
Customised Branding | System is able to be branded to institution specifics |
Metadata capture | All checklists produce relevant metadata per project, as defined by the institution |
Customised Questions | All questions are customisable to institution preferences |
Customised Links | All informational direction links are customisable to institution preferences |
Email trigger | Directional link can trigger email to appropriate group if required |
Accessibility Standards | Platform meets Australian Accessibility standards |
Active Directory connection | System connects to institution active directory for pre-fill fields |
API integration | System is able to use API to connect to other institution systems, e.g. PURE |
Predefined list | System is able to offer predefined answers for fields (as opposed to open text) |
Prefill | System can prefill metadata based on other API integrations (e.g. SSO, PURE) |
Form widgets | Platform offers web-form widgets for customisation of questions, e.g. calendar, short field, check box, radio button etc. |
Create | User is able to create a new checklist |
Save | User is able to save a checklist |
Revert | User is able to revert answers to previous save |
Edit | User is able to edit an existing checklist |
Print to PDF | User is able to print checklist as PDF |
Delete | User is able to delete existing checklist |
Supervisor linkage | User is able to link checklist to their supervisor |
Collaborator Linkage | User is able to link checklist to collaborator |
Search – User | Admins are able to search all users and checklists in system |
Monitoring | System creates monitoring logs for performance maintenance |
Login/Logout | User is able to securely login and out of system |
Search – Filter | User is able to use filter search to narrow view of existing checklists |
Import | System can import data from other systems (e.g. PURE) |
Conditional Rendering | Questions are dynamically displayed based on field input of user |
Realtime analytics | Admin are able to view real-time analytics of checklist data and usage |
Data export for analytics | Admin are able to export all data from platform for detailed analytics |
Supervisor management view | Supervisors can view all checklists they have been linked to |
Collaborator management view | Collaborators can view all checklists they have been linked to |
As part of our extensive stakeholder engagement and piloting of the checklist, we obtained the following feedback from users, as outlined in Table 5.
‘I like the simple look and feel of the checklist.’ | ‘This will help guide researchers to ask the right questions at the start of their projects.’ |
‘An easier-to-use tool like this will make researchers want to use it.’ | ‘This will make it easier for me to track what my HDR’s haven’t completed.’ |
‘It will make the data management planning process more understandable for researchers.’ | ‘This will make planning the data and primary materials management on my projects easier.’ |
‘I like the simplified approach, providing guidance but allowing researchers to decide what the DMP for their project will look like.’ | ‘This is a great start to improving research data and primary material management at QUT.’ |
‘I would like to be involved in future developments and testing of this tool.’ | ‘This will be a great improvement on the Data Management Planning tool.’ |
‘Clean, smooth and easy to use, can’t wait for the launch.’ | |
Researchers can use the tool as a skeleton or framework for the creation of RDM+PM plans, relevant to the evolving requirements of their project. HDR supervisors can use the tool to review student progress in their data management and spark meaningful discussions around data and primary material storage. HDR supervisors are trained with the tool and are expected to ensure all HDR students use the checklist as a mandatory process when initiating projects—complementing the training researchers receive as part of their induction certificate in checklist usage.
The RDM+PM checklist provides researchers and research supervisors with a tool to identify, monitor and report on the specific areas of data and primary materials governance that their project requires. The RDM+PM checklist has been made mandatory for all HDR students to complete from the launch date.
Business intelligence can be obtained in real-time. Since August 2022, the checklist became mandatory for new HDR students. At the time of taking this data snapshot, as shown in Table 5, the compliance rate was very high, which involved a new cohort of 142 HDR students who used the tool. We have developed training on RDM as part of their induction, in addition to access to a self-service training video. Only a small number of students have not answered particular questions, and these can be drilled down to assist particular students and if necessary, revise the guidance material for students. From Table 6, if we simply average the percentage answered across the seven questions, we arrive at 97%. This high percentage not only demonstrates the usefulness of the tool, but also provides a mechanism to ultimately measure the institution’s maturity with regards to RDM and PM management. We refer to this measure as an institution’s Data Quotient, and this will be detailed in a subsequent publication. Within the checklist, there is functionality to enable the analysis of data in real-time (analytics), as shown in Figure 4. A range of graphical and tabular representations are dynamically available.
QUESTION | YES | NO | UNANSWERED | TOTAL STUDENT | PERCENTAGE ANSWERED |
---|---|---|---|---|---|
Do you understand your obligations as per QUT MOPP D/2.8 on the Management of research data and primary materials? | 129 | 6 | 7 | 142 | 95% |
Does your research involve humans? As defined by the National Statement on Ethical Conduct in Human Research (2007). | 87 | 52 | 3 | 142 | 98% |
Does your research involve animals? As defined by the Australian code for the care and use of animals for scientific purposes. | 3 | 136 | 3 | 142 | 98% |
Are you creating, collecting or receiving digital data? | 127 | 11 | 4 | 142 | 97% |
Are you creating, collecting or receiving physical materials? | 34 | 105 | 3 | 142 | 98% |
Will the data be available for secondary usage (publishing)? | 101 | 37 | 4 | 142 | 98% |
Are there any limitations with regards to sharing your research data? These could include: trade controls, contractual requirements, copyright, or intellectual property issues | 42 | 95 | 5 | 142 | 96% |
As data management needs vary widely between projects depending on their discipline and scope, the checklist provides a dynamic solution that adapts to fit the need of the researcher in real-time. Crucially, the checklist offers guidance for both data management and primary material management. It is simple to use and understand and includes links to all relevant Subject Matter Experts (SMEs) to ensure that correct guidance for specific management practices is provided. It will be integrated into the early stages of the researcher lifecycle to ensure information is understood in a timely manner. The checklist aligns to the objectives of FAIR and data sharing programs that aim to minimise waste, allow for the re-purposing of data, facilitate reproducibility tests, and so forth. Importantly, the checklist can also foster collaboration across institutions, where the key seven questions can be customised for individual institutional needs, socialising the opportunity to arrive at a ‘common’ set of RDM and PM questions, while promoting best practice and sharing knowledge.
The approach devised by QUT has been acknowledged nationally through both external research infrastructure funding and by shifting the narrative for institutions to guide researchers in research data management planning, rather than providing a single data management planning tool that is not fit for purpose for many research disciplines ().
The questions posed by the checklist have been designed to directly reflect the current policy and for the first time, provide a systematic approach to guide researchers. Importantly, statistics are immediately available in real-time to enable managers to begin measuring the institution’s preparedness for RDM. It is envisaged that a score can be devised, which can provide weightings on the answers to specific questions and identify opportunities though ongoing feedback where checklist functionality can be enhanced.
At the time of writing this manuscript, it is mandatory for PhD student projects to use the checklist, and we believe this is a strong representative basis. This was a university-wide decision as an extension of the mandatory induction and onboarding training material for students. The derived benefits include: As PhD projects are diverse in nature, the checklist needs to be ‘fit for purpose’; the checklist promotes RDM+PM skills literacy and training at an early career stage, as well as ensuring supervisors’ responsibility in understanding RDM+PM policy. This is reflected in the high compliance results already captured with the tool. Updates to the tool are underway; the checklist is being scoped to support the development of RDM plans, and feedback is obtained, as the tool is currently undergoing customisation for deployment at another institution. This approach enables an agile iterative refinement of the tool through the sharing of best practice between institutions. Further extensions the tool’s functionality is through the automated provisioning of digital and data storage and analytic tool environments to support specific research projects.