Download to read offline
Uploaded byDavid Clay
Research Data Management at the University of Salford
The document summarizes the University of Salford's research data management project. It describes the drivers for the project including funder policies requiring open data. It outlines the requirements gathering and policy development process. It then details the proposed solution architecture including online storage, a data repository, source code management, and support services. Finally it discusses the pilot infrastructure launched in 2015 using Figshare and describes next steps to evaluate scaling up the RDM service.
More Related Content
![Who is doing what, and how do we know? [PEPRS]](https://cdn.slidesharecdn.com/ss_thumbnails/who-is-doing-what-100623032001-phpapp01-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to Research Data Management at the University of Salford
Research Data Management at the University of Salford
- 1. David Clay Jisc Digifest March2016 Research Data Management at the University of Salford
- 2. Project Drivers RCUK CommonPrinciples on Data Policy: ‘Publicly funded research data are a public good, produced in the public interest, which should be made openly available with as few restrictions as possible in a timely and responsible manner’. University Research Strategy aims: ‘to deliver a high quality research base by focusing support and investment on areas of strength and research excellence, supporting growth of a strong research portfolio and delivery of strong outputs and impact’.
- 3. Requirements gathering Functional requirementsand Business case Jan 2015 CARDIO March 2013 UoS Data Audit Survey Jun – Sep 2014 Interview’s with researchers October 2014 Functional Requirements November 2014 Solutions assessment November 2014 Business case January 2015
- 4. RDM Policy • Setsout clear principles for the management of research data • Defines the responsibilities of the University, researchers and research students • Aligned with funder policies • Developed after extensive consultation with researchers and research leaders • Informed the development of our RDM service
- 5. Solution Architecture Client Device WindowsPC, Mac, Linux iOS, Android Online Storage ££ Nearline Storage £ UoS Data RepositoryUoS Institutional Repository DOI Proxy Service Research Data Consumer Data Repository Harvester USDR AdministratorFederated Identity Provider OAI-PMH Interface Research Data Storage Service File Synchronisation Web-based Access Researchers and Collaborators Online Storage ££ File Sync Client DOI Minting Service ORCID Validation External preservation services e.g. CLOCKSS Archive? Web Browser Other Interfaces? Research Project Collaboration Space Project Landing Page Document Collaboration (Async) Real-Time Collaborative Editing Web Conferencing Wiki, Blog Backup £ Metadata Standards Deposit Data External Data Repositories During Project End of Project ISDADS (UoS) Directory UK Access Management Federation Other IdP – Google, Office 365, Facebook, LinkedIn, etc. AuthZ and AuthN AuthZ and AuthN UoS Government Agencies Commercial Organisations Other Universities (UK and Intl) Source Code Repository Source Code in Development Key Existing Service External Service New Service DMPOnline Data Management Plan Creation Research Data Support Service Website Guidance Before Project Catalogue
- 6. Client Device Windows PC,Mac, Linux iOS, Android Online Storage ££ Nearline Storage £ UoS Data RepositoryUoS Institutional Repository DOI Proxy Service Research Data Consumer Data Repository Harvester USDR AdministratorFederated Identity Provider OAI-PMH Interface Research Data Storage Service File Synchronisation Web-based Access Researchers and Collaborators Online Storage ££ File Sync Client DOI Minting Service ORCID Validation External preservation services e.g. CLOCKSS Archive? Web Browser Other Interfaces? Research Project Collaboration Space Project Landing Page Document Collaboration (Async) Real-Time Collaborative Editing Web Conferencing Wiki, Blog Backup £ Metadata Standards Deposit Data External Data Repositories During Project End of Project ISDADS (UoS) Directory UK Access Management Federation Other IdP – Google, Office 365, Facebook, LinkedIn, etc. AuthZ and AuthN AuthZ and AuthN UoS Government Agencies Commercial Organisations Other Universities (UK and Intl) Source Code Repository Source Code in Development Key Existing Service External Service New Service Solution Options 1. Syncplicity – on-premise or hosted 2. MS OneDrive for Business – on- premise or hosted 3. Janet File Sync & Share Framework supplier e.g. Box 4. Cloud Service with Linux client support e.g. Dropbox 5. FOSS solution e.g. Dropoff 1. SharePoint/Office 365 2. Lync or Jabber for real time video/audio 3. Figshare 4. Formalise use of commonly used Cloud services e.g. Google Docs/Hangouts Strategic option to develop ‘Community Portal’ platform, adding DB, Big Data, Visualisation, etc. 1. GitHub Enterprise 2. Mercurial with web front-end 3. MS TFS on Azure 4. etc. 1. Another backup product/license 2. Distributed replication rather than traditional backup 1. Figshare – cloud or on-premise 2. Existing repository (FOSS or COTS) e.g. Eprints, Dspace 3. SharePoint with bespoke development 4. Shared Service/Partner with another HEI 5. Other CMS e.g. TikiWiki CMS used by the BBC 1. EMC isilon scale-out NAS with Smartdedupe and Smartpools 2. Amazon S3 3. MS Azure 1. EMC Isilon 2. Amazon S3 3. MS Azure 1. Nothing if online storage is cheap enough 2. EMC Isilon (with Smartpools) 3. Arkivum – cloud or on-premise 4. Amazon Glacier 1. Federation Services 2. Avoid through developing Accman self-service provisioning
- 7. Pilot Infrastructure • LaunchedNovember 2015
- 8. • Compliance withEPSRC expectations • Enables research data publishing • Facilitates discoverability and re-use of data • Ability to control access to sensitive data • Support for diverse file formats • Large file upload limit • DataCite integration • Arkivum integration • Simple curation workflow Why Figshare?
- 9. Data Publication Process Publication Process ExistingMeta Data inc DOI Add Public Research Data to Meta Data Record Full Research Data Openly Accessible Add DOI to article Add DOI to & write up Data Access Statement Discoverable Data End Yes No Yes No Yes No RDM.BP06: Research Publication Process + Closed Embargoed Externally Hosted Define Date Range Upload Data Flag as Closed Upload Data End End Create Meta Data Only Create Meta Data inc Reserve DOI Yes Figshare Boundary Externally Hosted Data Backed up to Arkivum Backed up to Arkivum ProvideLink to External Data Meta Data Only Yes No Embargo Ends Publicly Available Data Unavailable(to Public) Data Yes No End Unavailable (to Public) Data
- 11. RDM Support Service www.salford.ac.uk/rdm EnquiryService E: researchdata@salford.ac.uk P: 0161 295 6707 @OpenDataSalford
- 12. • Strong supportfrom Senior Management • Excellent Researcher engagement and culture change • Bringing together skills and expertise from across the university • Good vendor engagement – Responsive and flexible to changing user needs – Knowledgeable – Supportive • Positive initial response to the new service Our Experience
- 13. • Pilot ResearchData Management Service • Evaluate and develop business case for scaling service up and rolling it out across the University • Learning, developing, growing! • New territory for the University but an exciting opportunity Next steps
Editor's Notes
- #11 Hannah This is our Figshare homepage image – we asked our creative team to design something which represented the diversity of research occurring at Salford, and I thought it’d be nice to share it with you. Obviously, the next step is to get some datasets uploaded which will appear here as well, but we did only go live on Monday!
- #13 I’m just going to mention our experience of our research data management project and the implementation of Figshare. As David has already mentioned, we’ve had strong support from Senior Management. We’ve worked really hard to engage our researcher’s right from the start of the project and it’s been really valuable time spent interacting with researchers on a 1:1 basis, making sure we’re listening to their needs and challenges. It’s been a really great feeling to be able to go back to them and say, here’s what systems and support we’ve put in place for you. It’s been important to keep them informed throughout and to manage their expectations, especially as we’re piloting the infrastructure with a small group initially. We couldn’t have achieved as much as we have without the involvement of departments from across the university – in particular IT Services, but also Research and Enterprise, Information Governance, Finance, and our Quality and Enhancement Office. Also, the RDM community within the UK has been, and still is, incredibly interactive and helpful, and I’m sure many of you will share this opinion. We’ve had great vendor engagement - our needs did change a bit as we progressed through implementation of Figshare but it wasn’t a problem, and they were responsive and flexible. They’ve also been knowledgeable and supportive throughout. So since Monday, we’ve had a positive response to the new service and already academics beyond the scope of our pilot Service are knocking on the door wanting to access these systems. I met with our Acoustics team yesterday and they were really impressed with the Service, even to the point where they independently offered to migrate data from personal Dropbox accounts to our systems! Some people have mentioned a few concerns around ethics and commercially funded research for example, but they are practical about it and they understand the benefits and impact it can have.