This document discusses best practices for supporting open science. It recommends adopting existing solutions where possible rather than developing new ones. It also suggests engaging with researchers, incentivizing open practices, allowing for innovation and failure, collaborating with peers, and keeping service delivery options open. The document concludes by inviting attendees to a workshop on delivering research data management services.
Developer Data Modeling Mistakes: From Postgres to NoSQL
Do & don't of supporting Open Science
1. www.geant.orgwww.geant.org1 |
Click to edit Master title style
• Click to edit Master text styles
• Second level
• Third level
• Fourth level
• Fifth level
29/09/2020 1
The do’s and don’ts of
supporting Open Science
www.geant.org
Sarah Jones
EOSC Engagement Manager
sarah.jones@geant.org
Twitter: @sarahroams
4TUResearchData 10th anniversary celebration,
29th September 2020
3. www.geant.orgwww.geant.org
10 years ago a new repository was launched…
3 |
• Over 900 data collections
deposited in 10 years
• Top 10 have between
2500-8500 views
• Open to deposits beyond
4TU consortium in science,
engineering and design
• 3TU 4TU ?
Image courtesy of Kevin Ashley, DCC
6. www.geant.orgwww.geant.org
Adopt > Adapt > Develop
If community already has a solution (or there is an emerging one), ADOPT
If necessary, ADAPT it to suit user needs
Only as a last resort DEVELOP an entirely new solution
Why?
• Existing services are established, adopted, mature, more sustainable…
• New development is expensive, costly to support, often inferior…
Don’t reinvent wheels!
6 |
9. www.geant.orgwww.geant.org
• Partner
• Be responsive
• Tailor to user needs
• Fit in with research workflows
• Co-located support staff with researchers
e.g. data stewarship roles, research
software engineers, observational studies
Engage in a meaningful way
9 |
10. www.geant.orgwww.geant.org
• Pressure to publish is still noted as major stressor for PhDs
• Recognise and reward open practices
- Make it part of promotion criteria
- Ask for examples in grant application CVs, research assessment etc
• Professionalise data roles
• Example of Research Software Engineers p49 doi: 10.2777/1524
• RDA group on professionalising data stewardship
Incentivise the culture change you want to see
10 |
11. www.geant.orgwww.geant.org
• If you want to find approaches that work well, you need to
be able to experiement, fail, change-course…
• Adopt some aspects from the corporate / business approach
• Constantly monitor landscape and users to know needs
• Objectively evaluate and decide when to fund (or not!)
• Increase flexibility in workplans to respond to changes
Allow for innovation – and failure!
11 |
12. www.geant.orgwww.geant.org
• Don’t all go it alone – do we really need thousands of
generic institutional data repositories?
• Share lessons – be open about experiences
• Skills sharing akin to datacurationnetwork.org
• Sector-wide procurement to broker better deals e.g. Jisc
data repository framework
Collaborate with peers and work as a sector
12 |
13. www.geant.orgwww.geant.org
• Open source / open infrastructure
• Bespoke internal services
• Commercial tools
• Self-hosted
• Partnerships
• Run by third-parties
• National services
• Brokering / procurement
Ensure we keep service delivery options open
13 |
What?
How?
14. www.geant.orgwww.geant.org
• Procurement pain points
• Open Source business models / open infrastructure
• Partnerships / national models for delivery
Mon 2nd – Fri 6th November 2020
https://events.geant.org/e/rdmservices
Workshop on Delivering RDM services
14 |