Your SlideShare is downloading. ×
0
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

The SONEX Workgroup for the Analysis of Repository Interoperability-Related Issues: a Summary of Activities

705

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
705
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  1. El Grupo de Trabajo SONEX para elanálisis de cuestiones relativas a la interoperabilidad de repositorios: resumen de actividades Pablo de Castro, GrandIR – pcastro@grandir.com Peter Burnhill, EDINA National Data Centre – p.burnhill@ed.ac.uk
  2. Estructura de la presentación• Cinco secciones con pausas intermedias para Q&A y discusión1. Una breve historia del Grupo SONEX, con énfasis en la incorporación de contenidos a los repositorios2. Algunos proyectos de interés relacionados con SONEX y financiados por el JISC3. Cómo el modelo de análisis de SONEX se extiende a la gestión de datos de investigación – con referencias a algunos proyectos en curso4. Cómo el modelo de análisis de SONEX se extiende a las componentes de servicio del proyecto UKRepositoryNet+5. Cuestiones abiertas/Open issues - Cuál es el valor archivístico de la Copia Final de Autor? - Hacia la hegemonía de la Vía Dorada? - Datos suplementarios/supplementary files y más
  3. http://sonexworkgroup.blogspot.com/
  4. How it all started:Institutional Repositories Workshop (IRW’09)
  5. http://repinf.pbworks.com/Repository-handshake
  6. SONEX are…As of Nov09 the workgroup coordinator Pablode Castro changed affiliation from SpanishNational Research Council (CSIC) to Carlos IIIUniversity Madrid, and Richard Jones(Symplectic Ltd) became a member of thegroup in Apr10 replacing Jim Downing.
  7. How SONEX fits into the JISC Deposit Programme
  8. SONEX: Scholarly Output Notification and Exchange• The goal: populating (then) nearly-empty repositories - focus onresearch papers (the multi-authored, multi-institution default case study)• The procedure: an international think-tank with own institutionalactivity in the area and international connections to running projects - Identifying deposit opportunities as deposit use cases - The group philosophy: not a coding project (not even a project) - "no power, no responsibility" - because of that we had influence and language
  9. SONEX: Scholarly Output Notification and Exchange• Dissemination and networking - abig workgroup objective: - OR10, - DL.org, - COAR WG2…
  10. The SONEX paper:deposit-related interoperability in a nutshell http://hdl.handle.net/10016/9257
  11. A bit of archaeology: the deposit landscape at SONEX start time11 ‘A summary of ongoing deposit-related projects’, http://bit.ly/c6OCi5
  12. SONEX usecase-based interop analysis
  13. SONEX usecase scenario I: publisher-driven deposit OA-RJ workflow PEER workflow
  14. SONEX usecase scenario I: publisher-driven deposit
  15. SONEX usecase scenario II: CRIS/IR integration (from: “KE CRIS-OAR [publication metadata] interoperability project” presentation, CRIS2010 Aalborg, Denmark, June 2-5, 2010)
  16. SONEX usecase scenario II: CRIS/IR integration
  17. SONEX usecase scenario III: Funder-mandated deposit• Meeting funder mandates• Subject-based repositories as a potential document source SONEX usecase scenario IV: Deposit via personal software • Direct ingest from author’s desktop • Strongly relying upon Sword-based workflow
  18. (Potential) SONEX usecase scenario V:are IRs a proper target for research data deposit?
  19. Summing up: Section 1 on SONEX work• Began with interoperability deposit opportunity as the priority• Take the multi-authored, multi-institution research paper as default• Review existing deposit projects• Develop use case analysis• Key was think not have to do the work ourselves: think tank thathelped form framwork and language• JISC then acted to commission a set of deposit projects alongSONEX identified deposit worklines
  20. March 2010: JISC Deposit call released
  21. JISC Deposit call projects: DepositMO
  22. JISC Deposit call projects: RePosit
  23. JISC Deposit call projects: JISC DURA http://jisc-dura.blogspot.com/2010/08/ir-cris.html
  24. JISC Deposit call projects: JISC DURA http://www-library.ch.cam.ac.uk/open_access_publishing
  25. JISC Deposit call projects: Kultivate http://lanyrd.com/2011/kultivate-july-2011/sfpqw/
  26. Measuring success of strategies to promote deposit • Measuring success for particular deposit strategies: much harder than getting a general picture • Specific questions should be asked to repository managers, such as: - was any given automated deposit strategy used for content ingest purposes? - could an approximate amount of items thus ingested be estimated as a percentage of total item input? http://www.rsp.ac.uk/grow/measuring-success/
  27. And in the meantime, outside JISC Deposit programme… http://grandirblog.blogspot.com.es/2012/03/creciente-adopcion-de-cerif-como.html
  28. SHERPA RoMEO involved in CRIS End of section 2: Deposit projects
  29. SONEX Extension toResearch Data Mgt
  30. SONEX Extension to Research Data Mgt• SONEX commissioned by the JISC to perform a similar analysis on RDM• Same JISC programme architecture: the JISC MRD Programme
  31. SONEX Extension to Research Data Mgt
  32. What SONEX does for JISC MRD• Reporting on meetings, activities,new approaches the SONEX way:with a focus on internationalconnections and connecting theanalysis to previous work• Joint SONEX-Sword work foranalysis of Dataset deposit use cases• Providing a conceptual frameworkto Research Data Management• Examination of specific issues: areIRs suitable for research data storageand management?
  33. What SONEX does for JISC MRD
  34. What SONEX does for JISC MRD
  35. A final reflection on RDM/Open Data and Open Access (are we wrt Open Data where OA was 10 yrs ago?)OPEN DATA <> OPEN ACCESS(“shared” vs “repositories”, © PMR)BUT:- Berlin Declaration shows shared goals- Same workteams on both arenas- Open movements feed back each other- Synergies seeked and needed
  36. Activities around SUNCAT, Union Catalogue for Serials in UK Published Serials (Journals etc) D-journals E-journals Print journals OpenURL Library as Custodian & Library as Customer Router Usage for Articles Custodian – Licensing – Stewardship Entitlements SUNCAT UKRR / Keepers Registry PECAN / KB+ ‘Volume holdings’ 37
  37. Project to build infrastructure to support operation of repositories in UK
  38. Landscape: Actors, Agency & Relationships for Report, Deposit & Access teacher editor Licensed/ Publisher monograph tollgate student Academic referee access to Publisher’s researcher Final Copy journal (PFC) P.I. author(s) Subject Deposit of metadata/text of Repository SWORD Authors’ Final Copy (AFC)Research UKPMC reader Digital metrics LibraryAward EUreporting Eval Research Outcomes Institutional NORA Repository CERIF curation micro - services UKCoRR RCUK Wellcome EU stewardship budgets Trust ARMA UK Research Library Funder CRIS Research Excellence HEI [OA mandate] Framework Institution [OA mandate] HEFCE, SFC …
  39. Library View (Without Repositories) Publisher monograph Publisher’s <DOI> Final Copy (PFC) journal author(s) Publisher’s Platform Licensed / $ tollgate Customer access Library University
  40. Researcher View (Without Repositories)Principal Investigator (PI) Publisher monograph Publisher’sleads research team Final Copy researcher (PFC) journal P.I. author(s) Research Award reporting about Outcomes <AwardID> Research Funders £ University <AwardID>
  41. General Landscape (Without Repositories) Publisher monograph Publisher’s Final Copy researcher (PFC) journal P.I. author(s) Research Publisher’s Award reporting Platform about Outcomes Licensed / tollgate $ access Customer LibraryResearch Funders University
  42. Landscape With Green OA Repositories Added Publisher monograph Publisher’s Final Copy <DOI> (PFC) researcher journal P.I. author(s) Licensed/ tollgate Subject access Deposit of metadata/text of Repository Authors’ Final CopyResearch (AFC) <DOI> SWORD DigitalAward <AwardID> Libraryreporting Research Outcomes Institutional Repository <AwardID> CERIF RCUK Wellcome EU Trust Custodian Customer Library Research Funders HEI [OA mandate] Institution HEFCE, SFC … <AwardID> [OA mandate]
  43. Landscape: Actors, Agency & Relationships for Report, Deposit & Access teacher editor Publisher monograph student Academic referee Publisher’s Final Copy researcher (PFC) journal P.I. author(s) Subject Repository Deposit of metadata/text of SWORD Authors’ Final CopyResearch (AFC) <DOI> Digital reader LibraryAwardreporting Research Institutional Licensed Outcomes Repository / CERIF tollgate Custodian access RCUK Wellcome EU Trust Customer <DOI> Library Research Funders CRIS HEI [OA mandate] Institution [OA mandate] HEFCE, SFC …
  44. A Simpler View of Repository Landscape Monograph Teacher Article Journal Reader Academics Publishers Author P.I. Subject Repository Open Acces Institutional Repository s Funders Repository Research Research Informatio CRIS Library Awards n Faculty Institution Funders s Managem Research Grant Office ent
  45. High-Level Plan Plan toKey DeliverablesJISC-funded Project with Build an Infrastructure2011 2012 2013Aug Oct Jan Apr Jul Oct Jan Mar JISC Programme Outputs & Dependencies (Scholarly Comms, Research Information Management, etc.) WP1: Project Management & Reporting Core Project Major Review Re-plan Checkpoint Re-plan Checkpoint Final Documents Checkpoint Report WP2a: Scope Production Environment Scoping Study WP2b: Develop and Maintain Production Environment Initial Production Environment (PE) & Description Production Environment Service Desk WP3: Scope Components: Tools & Services Component Catalogue Blueprint Processes Gap analysis & use cases WP5a: Develop Service Suite Phase 1 Phase 1 Shortlist WP5b: Develop Shared Service Suite Phase 2 Phase 1 Components in PE Phase 2 Shortlist Phase 2 Components in PE Partnership Arrangements Phase 1 Partnership Arrangements Phase 2 WP4: Foster Partnerships Consumers & Service Providers for Service Components Stakeholder Analysis & Communications Plan Engagement Strategy WP6: SDPR* *SDPR = Service Development Process Re-engineering Component Lifecycle Model & Processes for Embedding WP7: Service Sustainability Market Analysis Sustainability Options Component Business Cases Sustainability Plan
  46. Stakeholder EngagementInstitutional view Repository managers Research administrators (on research reporting) Researchers??Research funders RCUK, Wellcome TrustPublishers Green and Gold
  47. Stakeholder Analysis: what we learnedValidated the Repository Landscape Proved initial understanding correct Reassurance that there were no gaps in understanding or landscape mappingHow to take this forward ? Concentrate on use cases based on functional areas, eg publisher deposits, PIs, IR manager benchmarks, funder requires statisticsNeeded to sketch the vision of what can be provided in order to extract user requirements within and beyond what is done by existing components in the functional areas
  48. Components for Wave 1Classification and Recommendations
  49. 12 Components from (6) Owners: by functional area OpenDOAR ROAR REPUK RoMEO University of Innovation Southampton University of Nottingham Juliet UKOLN Open Depot ORI IRS IRUS-UK CORE Linked data/mobile RJ Broker Open University NAMES2 EDINA MIMAS Aggregation, Text mining & Search Benchmarking, Statistics and Report Constructing Relevant Registries Deposit Tools Enhancing Metadata Quality
  50. Summary of Components by Functional AreaA: Aggregation, Text mining & Search Aggregated set of metadataREPUK for development D: Deposit Tools Search, aggregation, full-textCORE mining for OA repositories RoMEO Publisher policies Search, aggregation, data- on OA depositIRS mining for all IRs Juliet Research funders’ policies on OAB: Benchmarking, Statistics and Report Open Redirect facility to OA IRs, Depot and default OA repository Centralised service for collection of OAIRUS-UK usage statistics M2M direct for multi- RJBroker authored works to OA repository(ies)C: Creating Relevant Registries OpenDOAR Authoritative, manually curated registry E: Enhancing Metadata Quality of OA repositories, combined with Naming Authority for the UK harvested metadata NAMES2 assigning identifiers to Registry of OA repositories compiled with organisations and individuals ROAR statistics in mind engaged in research Organisation based with information ORI on repositories
  51. The purposes and functions of OpenDepot.org are two-fold:1. a repository function to ensure that all researchers can do Open Access – whether or not they belong to an institution with a repository2 a discovery/re-direct function to help populate Institutional Repositories (IRs) The Repository Junction Broker is used in OpenDepot.org for re-direct and has been developed as separate middleware
  52. Sketch of RepositoryNet Infrastructure & Components Funders’ Subject Institutional Repositories Repositories Repositories * Hosted by consumers universities Service Desk Service Support Service Directory hacks … Rapid Service components / Innov. … … curation … Hosted by RepNet Innovation micro-services Remote* Zone RepositoryNet Production Environment
  53. Gracias!More info on Sonex: http://sonexworkgroup.blogspot.com/ Pablo de Castro, GrandIR – pcastro@grandir.com Peter Burnhill, EDINA National Data Centre – p.burnhill@ed.ac.uk

×