Jisc Research Data Shared Service Open Repositories 2018 24x7
•Als PPTX, PDF herunterladen•
1 gefällt mir•539 views
Jisc Research Data Shared Service 24x7 Slides presented by John Kaye at Open Repositories 2018
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Ähnlich wie Jisc Research Data Shared Service Open Repositories 2018 24x7
Ähnlich wie Jisc Research Data Shared Service Open Repositories 2018 24x7 (20)
Mehr von Jisc RDM
Mehr von Jisc RDM (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Jisc Research Data Shared Service Open Repositories 2018 24x7
- 1. Jisc Research Data Shared Service Looking at the past, looking to the future
- 2. Needs »A better name… “What's in a name? That which we call a rose By any other word would smell as sweet;” Prize available! http://pngimg.com/download/651/?i=1
- 3. This is it! Preservation Systems Multi-tenant administration Discovery User Interfaces and Portals APIs User InterfacesUser InterfacesUser InterfacesTenant User Interfaces APIs Jisc Reporting APIs APIs APIs Tenant Storage APIs Jisc Repository Core Infrastructure APIs Metadata Store Publish Subscribe Messaging Service Cloud Data Storage (Access and Archival) Tenant Repository, CRIS and research systems Scholarly Communications, Service APIs
- 4. Drivers Ben Sutherland – CCBY 2.0 - https://www.flickr.com/photos/bensutherland/2980272613
- 5. RDSS Priorities 5 Alan Levine –CC BY 2.0 - https://www.flickr.com/photos/cogdog/9447421903/
- 6. The… Nick Youngson - CC BY-SA - http://www.thebluediamondgallery.com/handwriting/i/insurance-requirements.html »Scalable »Sustainable »Intuitive
- 7. The…
- 8. Co-Design
- 10. An aside… Why is multi tenanted important? By Steve Cadman (Flickr: The Trellick Tower) [CC BY-SA 2.0 (https://creativecommons.org/licenses/by-sa/2.0)], via Wikimedia Commons
- 11. What’s not quite right… Kevin Dooley, CC BY 2.0, https://www.flickr.com/photos/pagedooley/4662765381
- 12. Multi–tenancy flaw… Photo © N Chadwick (cc-by-sa/2.0)
- 13. Where we are now Preservation Systems Multi-tenant administration Discovery User Interfaces and Portals APIs User InterfacesUser InterfacesUser InterfacesTenant User Interfaces Jisc Reporting APIs APIs Tenant Storage Jisc Repository Core Infrastructure APIs Metadata Store Publish Subscribe Messaging Service Cloud Data Storage (Access and Archival) Tenant Repository, CRIS and research systems Scholarly Communications, Service APIs APIs APIs APIs
- 15. What we’re working on
- 16. Multi-tenant Research Repository What we’re working on
- 17. Part of the Jisc family Submission Acceptance Publication Use SHERPA JULIET SHERPA RoMEO SHERPA REF SHERPA Fact Monitor UK Jisc collections OpenDOAR Publications Router Monitor local CORE IRUS-UK RIOXX Research publication lifecycle Jisc services Report on compliance Deposit in repository Manage costs Check compliance Select Journal Maximise impact Record reach Record impact ORCID support OpenAIRE NOAD Research Data Shared Service Metrics lab experiment
- 18. 3 standard service options End-to-end service Repository service Preservation service Service to be launched in Autumn 2018 All 3 options include: Financial benefits Standards Advisory Network membership
- 19. Records, Archives and Special Collections By Jwslubbock [CC BY-SA 4.0 (https://creativecommons.org/licenses/by-sa/4.0)], from Wikimedia Commons
- 21. Preservation action registries (PAR)
- 22. Jisc national shared research platform Information sources » Publications Router » Publishers » Crossref » ORCID » DataCite » PubMed » Sherpa policy tools University systems » (SingleSign-On, Finance,HR..) Information destinations » Google etc. » Discovery services » Jisc CORE (global OA aggregation) » Jisc Monitor (compliance checking) » Jisc Collections » 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
- 23. What to keep?
Hinweis der Redaktion
- How and why we’ve got to where we are Text and
- How and why we’ve got to where we are Drivers Funder mandates, (more here) Builds on more than £5 million investment over 2 years Open access Also builds on open access serviccs, Jisc MRD work and other related jisc work Sector defined requirements “R@R” co-designchallenge Over half the HEI sector involved - Sector requirements gathering and prioritisation. (over 70 institutions involved To date builds on £5m+ investment in repository and preservation R&D . Costs and risks Risk to research funding -> Reduced income Loss of research data -> Lost value of research work (17% lost key data – DAF survey) Leakage of sensitive data -> Legal threat and cost (Unlimited fines with GDPR) Researcher reputation -> Key staff leave (75% EXPECT HEI to do this) Institution reputation -> Defensible integrity of research, responding to FOI etc. (e.g. Climategate £10m?) Cost and risk of delivery -> Inefficient research and over-expensive IT
- First priority is research data However research data is not good enough on it’s own for research publication the ideal is to store, or link to the complete research package Research output (Article/Thesis etc.) Research data Research software/code Provenance metadata (method) Without this research is often not re-usable or repeatable. But…..we are aware that we are providing preservation systems that are tailored to deal with all kinds of digital objects and data. We are exploring use cases and pilots for objects beyond research data.
- » Scalable multi-tenant repository and preservation infrastructure for multiple content types » Intuitive user experience - automated workflows » Financially sustainable » Multiple storage options » Event based open APIs » Reporting APIs and dashboards
- To do this we need True multi tenant Multi content Shared data model Interoperable Sustainable Much improved user experience
- We worked with a lot of people! How and why we’ve got to where we are Pilots Worked with 16 pilot institutions of various sizes Created a procurement framework Pilots 17 institutions Cross spectrum use cases Large and small Collaborative development Multiple suppliers and solution vendors Drivers More than £5 million investment over 2 years Open access Sector defined requirements “R@R” co-design Over half the HEI sector involved
- How and why we’ve got to where we are Created a multi-tenant core architecture and interoperability framework based on industry standards Technology Multi-tenant core architecture Interoperability framework Industry standards
- Multi–tenancy flaw Why we are developing a new multi tenant repository Why is multi tenanted important? Affordability / Scalability Universal data model Multi content Interoperable Single management interface Multiple view/brands
- 5 developers 5 months could make it work Samvera couldn’t deliver multi-tenancy Dom’s report
- Multi–tenancy flaw Why we are developing a new multi tenant repository Nothing (we found) was truly multi tenanted Separate clusters were needed Existing solutions too much customisation Which leads to… A solution that doesn’t scale nationally Economically unsustainable Not sustainable to run a national service like this
- Where we are now Core Architecture multitenant database Interoperability layer Data model Proof of concept front end API Initial Front end design
- Obligatory slide that cant be read by anyone It wouldn’t be an RDSS presentation without it See Dom if you want to read it data model, apis and reference (example) apis and data available to develop
- Where are we now Multi tenant user interface Workflows Integrations with open access service Core Architecture consisting of multitenant database with tech, descriptive and event metadata. Proof of concept API that shows that we can put a lightweight front end on multi tenant core architecture Begun design of front end development with our Design and User Experience partners Ocasta
- Where are we now Multi tenant user interface Workflows Integrations with open access service Core Architecture consisting of multitenant database with tech, descriptive and event metadata. Proof of concept API that shows that we can put a lightweight front end on multi tenant core architecture Begun design of front end development with our Design and User Experience partners Ocasta
- RDSS working with Universities of Glasgow and Westminster: Preservation use cases for records management University archives University Websites Special collections Other records Recommendations around workflows, systems and future integrations Engage with the community through workshops
- Integrations with active data storage e.g. Institutional storage area network, file sync and share services. Integrations with additional 3rd Party systems Integration with updated DMP Online Integration with Jisc Tiered Storage Certification ISO 9001, 27001, CoreTrustSeal (Data seal of approval) ISO 163634
- Preservation action registries (PAR) Actions = check sums , convert files – for normalization or rendering etc. TIFF to JPEG These act on objects, create AIP Actions are executed by tools = DROID, JHOVE general purpose or disciplinary specific Arkivum, Artefactual, Preservica & Jisc Sharing information on digital formats, actions (e.g. conversion) and tools (e.g. JHOVE) for preservation via APIs Exchange between systems and organisations on preservation policies and solutions Capture best practice and give confidence for preservation actions, accelerate adoption of digital preservation Prototype based on Archivematica’s Format Policy Register and Preservica’s Linked Data Registry as part of the Jisc research data shared service research data network: http://researchdata.network web: https://www.jisc.ac.uk/rd/projects/research-data-shared-service github https://github.com/JiscRDSS
- against
- Evolving field, wicked problem. To help to understand and inform policy and practice, what is needed – integrity, reproducibility and to help define solutions and costs What researchers, research funders, ethics professionals, archivists, research data managers, peer reviewers see as the optimal research data to keep from research projects conducted at UK institutions; Any conditions, such as degree of openness, timescales, etc., associated with the data The reasons behind their opinions, policies, professional practices; are these based on empirical evidence, professional judgements, top-down policies, etc. The extent to which the data is, in fact, known to be kept in line with the conditions and the approaches used to achieve that; The extent to which the data is not, in fact known to be kept in line with the conditions, the reasons for that shortfall, and plans or suggestions to address it. Jisc and Neil Beagrie, running from now until 2019
- Ensuring we have an internal business case Helping users build theirs Collaborating where possible Creating an efficient / cost effective system As open as possible