Building a National Data Service Open Repositories 2018
•Als PPTX, PDF herunterladen•
0 gefällt mir•361 views
Introductory slides
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Ähnlich wie Building a National Data Service Open Repositories 2018
Ähnlich wie Building a National Data Service Open Repositories 2018 (20)
Mehr von Jisc RDM
Mehr von Jisc RDM (15)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Building a National Data Service Open Repositories 2018
- 1. Building a National Data Service Open Repositories 2018 – Montana State 04/06/2018
- 2. Agenda » 09:00 -9:30 - Intros, Intro to Jisc Research Data Shared Service RDSS and Demo » 09:30 – 10:30 - Data Modelling –With excercise » 10:30-11am -Tea/Coffee » 11:00-12:00 – System Integration Architecture Overview » 12:00-12:30 -Vendor experiences of RDSS » 12:30-13:00 - Lunch » 13:00-14:30 – Interactive session in Groups:Workflows, events and adapters » 14:30-15:00 –Tea Coffee » 15:00 – 16:00 – Figshare ORCiD integration » 16:00 – Close –Wrap-up + Chance to talk about Jisc Samvera development 04/06/2018 Building a National Data Service 3
- 3. Intros »John Kaye – RDSS Product Lead– Jisc (UK) »Dom Fripp – Repository product manager – Jisc (UK) »Joel Simpson – Analyst – Artefactual Systems (CA) »DanValen – Figshare »Alan Mackenzie – Chief Architect – Digirati (UK- Remote) »Round the room (Brief intros, systems you work with and are interested in) 04/06/2018 Building a National Data Service 4
- 4. Notes and Resources »Shared Google doc – feel free to add anything during the day »http://bit.ly/2LWmq2r 04/06/2018 Building a National Data Service 5
- 5. Who we are 04/06/2018 Building a National Data Service Jisc is the UK higher, further education and skills sectors’ not-for-profit organisation for digital services and solutions Operate shared digital infrastructure and services Provide trusted advice and practical assistance for universities, colleges and learning providers We… Negotiate sector-wide deals and conditions with IT vendors and commercial publishers 6
- 6. Jisc Digital Futures 04/06/2018 Building a National Data Service Store services Playlists Diagnostic tool builder Curation and remix Learner Analytics Services Digital capability Learning analytics Digital launchpad Apprentice workforce development Digital leadership Summer of student innovation Analytics academy Analytics labs Qualification verification App and content store Research data discovery Research data usage metrics Equipment data Repository and preservation platform Research data shared service ? 7
- 7. Why a Shared Service? There is no single “solution” easily available and that meets requirements for Universities to enable better management of research data research data network: http://researchdata.network web: https://www.jisc.ac.uk/rd/projects/research-data-shared-service github https://github.com/JiscRDSS 04/06/2018 Building a National Data Service 8
- 8. University Pilot Institutions 04/06/2018 Building a National Data Service 9
- 9. Service workflow summary 10 Repository Messaging Preservation service Reporting and analytics Archival data storage National research data aggregation Or 1.a. Researcher deposits data 2. Data added to aggregation 3. Data is automatically preserved 4. Use of data and service is monitored 7. Data stored long term 6. Researchers find and reuse data Institutional or external services 5. Other services are updated 04/06/2018 Building a National Data Service 1.b. Record of data external deposit Layer
- 10. Pilot Alpha MVP 04/06/2018 Building a National Data Service 11
- 11. RDSSTop level architecture multi-tenant administration Discovery User Interfaces and Portals API s User InterfacesUser InterfacesUser InterfacesTenant User Interfaces APIs Jisc Reporting API s API s Scholarly Communications, Service APIs Tenant Repository, CRIS and research systems API s Tenant Storage API s Jisc Repository Core Infrastructure APIs Preservation Systems Archivematica Preservica DataVaultMetadataStore Tenant User Interfaces Publish Subscribe Messaging Service Cloud Data Storage (Access and Archival) 04/06/2018 Building a National Data Service 12
- 12. Jisc Repository Jisc Repository Initial design https://marvelapp.com/36ggde2 04/06/2018 Building a National Data Service 13
- 13. Jisc national shared research platform 04/06/2018 Building a National Data Service 14 Information sources » Publications Router » Publishers » Crossref » ORCID » DataCite » PubMed » Sherpa policy tools University systems » (Single Sign-On, Finance, HR..) Information destinations » Google etc. » Discovery services » JiscCORE (global OA aggregation) » Jisc Monitor (compliance checking) » JiscCollections » Funders systems » OpenAIRE + for EU Preservation services Reports and dashboards University X repository Open Access publications Research datasets University Y repository Open Access publications Research datasets University Z repository Open Access publications Research datasets
- 14. 15
- 15. 16
- 16. 17
- 17. 18
Hinweis der Redaktion
- More effective Research Data Management must happen to comply with Funder Mandates, ensure data is not lost, and to realise a whole range of positive benefits A shared service (provided by Jisc) seems to offer a number of benefits: Cost savings and efficiencies Common approaches and practice – do this together Research system standardisation and interoperability ( do it once rather than many times! , & also address it across essential systems so we can key once and share) Address market gaps
- How and why we’ve got to where we are Text and
- * This year, the University of Westminster will be piloting RDSS within their existing information infrastructure. * Since 2013, the University has been using Haplo Research Manager as their Virtual Research Environment. * As well as CRIS, postgraduate research workflows and research ethics functions, it provides the University's repository, integrating REF and Open Access management. * It has excellent buy-in from researchers, as a "one stop shop" for research information with an compelling user experience. * This is their current setup, with a custom hybrid Haplo/EPrints repository. * Information flows from University systems into Haplo. * Researchers self-deposit outputs into the Haplo Repository module, and a workflow helps them work with the metadata team to prepare their outputs for publication. * When published, outputs are pushed to EPrints which provides the public view of the repository. * The researcher's full research profile, including publications, is pushed to the corporate web site.
- * By August 2018, Westminster will be using an "all Haplo" Repository. * EPrints will be retired, * and Haplo will provide the public interface of Westminster repository. * The project is lead by the Research and Scholarly Communications team based in Library and Archives at UoW in collaboration with University of Westminster academics * The move is motivated by a desire to use a standard repository, using the Haplo core product with a small amount of local configuration on top. * Haplo Repository provides many "building blocks", and Westminster have selected the ones most appropriate for their research. * In particular, collections workflow, support for practice-based research, and REF & OA reporting * Westminster are working with two other institutions to define common workflows and reporting, aiming to launch their new repositories at roughly the same time.
- * By the end of the year, Westminster will be using RDSS services for preservation. * Haplo already has initial support for the RDSS message bus. * The Haplo developers like the RDSS because a single interface allows integration with many different research data components: "we get many integrations for the price of one" * The flexibility of the RDSS allows Westminster to pick the components they need, and easily integrate into their research information infrastructure.