Integrating figshare into our RDM workflow: University of Salford
Download as PPTX, PDF0 likes458 views
The document discusses integrating the data repository figshare into the University of Salford's research data management workflow. It outlines the drivers for improving research data management, including funder requirements. It then details the university's requirements gathering process, which involved auditing current practices, interviewing researchers, and identifying functional needs. Finally, it evaluates figshare as a solution, noting its abilities to enable publishing, discoverability, access control, and integration with other services.
Integrating figshare into our RDM workflow: University of Salford
- 1. David Clay UKSG April 2016 Research Data Management Integrating figshare into your RDM workflow University of Salford
- 2. Drivers RCUK Common Principles 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 requirements and 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. 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
- 5. • Compliance with EPSRC expectations • Enables research data publishing • Facilitates discoverability and re-use of data • Ability to control access to sensitive data • Support for diverse file formats • Simple curation workflow • Large file upload limit • DataCite integration • Arkivum integration Why Figshare?
- 7. • Strong support from 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 and supportive – Positive response to the service Our Experience
- 8. • Pilot Research Data 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