Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

3.24.15 Slides, “New Possibilities: Developments with DSpace and ORCID”

2,089 views

Published on

Hot Topics: The DuraSpace Community Webinar Series
Series 11: Integrating ORCID Persistent Identifiers with DSpace, Fedora and VIVO

Webinar 1: “New Possibilities: Developments with DSpace and ORCID”
Tuesday, March 24, 2015

Curated by Josh Brown, ORCID
Presented by: Bram Luyten, Co-Founder, @mire - Andrea Bollini, CRIS Solution Product Manager, CINECA - Michele Mennielli, International Relations Manager, CINECA - João Moreira, Head of Scientific Information, FCT-FCCN - Paulo Graça, RCAAP Team Member

Published in: Technology

3.24.15 Slides, “New Possibilities: Developments with DSpace and ORCID”

  1. 1. March 24, 2015 Hot Topics: DuraSpace Community Webinar Series Hot Topics: The DuraSpace Community Webinar Series Series Eleven: “Integrating ORCID Persistent Identifiers with DSpace, Fedora and VIVO” Curated by Josh Brown, Regional Director Europe, ORCID
  2. 2. March 24, 2015 Hot Topics: DuraSpace Community Webinar Series Webinar 1: New Possibilities: Developments with DSpace & ORCID Presented by: João Moreira, Head of Scientific Information, FCT-FCCN Paulo Graça, RCAAP Team Member Bram Luyten, Co-Founder, @mire Andrea Bollini, CRIS Solution Product Manager, CINECA Michele Mennielli, International Relations Manager, CINECA
  3. 3. Research Information Management: DSpace-ORCID requirements João Mendes Moreira (FCT) Paulo Graça (FCT)
  4. 4. Agenda • Context – PTCRIS (integrated research management ecosystem) – RCAAP (national open access initiative) – PTCRIS & RCAAP & ORCID & DSpace synergies • DSpace-ORCID – Requirements – Compative analysis • XMLUI • JSPUI • DSpace-CRIS • Conclusions
  5. 5. Mission Ensure the creation and sustained development of national integrated information ecosystem (PTCRIS) to support research management
  6. 6. Goals 1. Define the regulatory framework to adopt by the various systems 2. Coordinate FCT’s systems integration in accordance with the standards framework 3. Coordinate external systems integration with FCT (National and International) according to the standards framework 4. Support and promote within community the use of the systems of the PT-CRIS.
  7. 7. The ecosystem CRIS – Current Research Information Systems Academic  expertise Organizations  database Scientific equipment Statistics Funding  database Grant  management Outcomes /  outputs Research news Research ethics Research portal PTCRIS is ecosystem!
  8. 8. Standards Aligned: • H2020 • Digital ERA fórum • RDA PTCRIS Data model Dictionary / Interop. Ontologies Researcher Id Org Id
  9. 9. Roadmap #1 Interoperability An output should be registered only once and reused often! Research  Institutions Publishers Repositori es Prof.  organizations Universiti es Funders
  10. 10. 2. RCAAP Project
  11. 11. Electronic Services Portal RCAAP Institutional Repositories (SARI) Scientific Data (SARDC) Scientific Journals (SARC) Shared Repository Directory Usage Statistics (SCEUR)
  12. 12. Metrics ● 42 Repositories (27 hosted) DSpace JSPUI ● 1 Shared Repository with 38 institutions ● 32 Scientific Journals (9 hosted) ● >200.000 Open Access Items RCAAP - Repositório Cientifico de Acesso Aberto de Portugal
  13. 13. 3. PTCRIS & RCAAP & ORCID
  14. 14. Breaking information silos PTCRIS Academic expertise Org.  database Scientific equipment Statistics Funding  database Grant mng Outcomes / outputs (RCAAP) RI (DSpace) Revistas (OJS) Dados  científicos (CKAN) Research  news Research  ethics Research  portal Identifiers Interoperability
  15. 15. Breaking information silos Outcomes / outputs (RCAAP) RI (DSpace) Journals (OJS) Scientific data (CKAN) Portal RCAAP Identifiers Interoperability
  16. 16. PTCRIS Ecosystem National CV Open Access  Portal
  17. 17. Agenda • Context • DSpace-ORCID – Requirements – Comparative analysis • XMLUI • JSPUI • DSpace-CRIS • Conclusions and recommendations
  18. 18. Requirements sources • COAR Roadmap Future Directions for Repository Interoperability (Fev 2015) • Immediate priorities: – #3 Supporting Author Identification Systems – #7 Supporting additional metadata formats • XMLUI, JSPUI, DSpace-CRIS • Needs RCAAP (national Open Access initiative) • Needs PTCRIS (national CRIS initiative)
  19. 19. Requirements (our view) Author related R1.1 Author’s profile page R1.2 ORCID aware every time the author is displayed R1.3 ORCID authority control R1.4 Search by ORCID identifier Interoperability R2.1 Supporting additional metadata formats  Added value DSpace‐ORCID services R3.1 Add‐to ORCID R3.2 Import/sync from ORCID
  20. 20. Supporting Author Identification Systems • Supporting author identification systems: Author identification systems intend to identify academic authors in a unique way. Different systems are available (ORCID, ResearcherID, AuthorClaim etc.) and can be used in the repository context. “IMHO, a very important extension of current repositories, but relying on external authority data maintained by external systems / staff; needs a lookup service for persons, which can be applied during indexing and searching of data”… “Clearly supports open systems like ORCID instead of proprietary ones”
  21. 21. R1.1: Author’s profile page
  22. 22. R1.2: ORCID Id aware every time the author is displayed
  23. 23. R1.3: ORCID authority control
  24. 24. R1.4: Search by ORCID identifier
  25. 25. R 2.1: Supporting additional metadata formats • DC has strong limitations • Potential formats to be considered (and depending on the purpose) are MODS, METS, MARC, CERIF and others. “Adding more standards when they bring richness and detail is a key step to move forward in the current situation. The complexity of course depends on number and complexity of the new adoptions. DC is no longer useful for advancing in the field.”
  26. 26. R 3.1: add-to ORCID (1/2) RCAAP plug‐in available.
  27. 27. R 3.1: Add to ORCID (2/2)
  28. 28. R 3.2: Import/Sync from ORCID (1/2)
  29. 29. R 3.2: Import/sync from ORCID (2/2)
  30. 30. Requirements analysis Requirement DSpace flavour Author related JSPUI XMLUI DSpace‐CRIS R1.1 Author’s profile page N N Y R1.2 ORCID aware every time the author is displayed N N N R1.3 ORCID authority control N Y Y R1.4 Search by ORCID identifier N N N Interoperability R2.1 Supporting additional metadata formats  DC DC DC, CERIF Added value DSpace‐ORCID services R3.1 Add‐to ORCID N N N R3.2 Import/sync from ORCID N N N Score 0/7 1/7 3/7
  31. 31. Two UIs: Global Adoption 891; 46% 1067; 54% 1,958 “unique”, valid DSpace sites XMLUI JSPUI Source: 2015 DuraSpace Sponsor Summit, Tim Donohue
  32. 32. Priorities (from our perspective) Requirement Author related Priority R1.1 Author’s profile page Max R1.2 ORCID aware every time the author is displayed Min R1.3 ORCID authority control Max R1.4 Search by ORCID identifier Min Interoperability R2.1 Supporting additional metadata formats  Max Added value DSpace‐ORCID services R3.1 Add‐to ORCID Med R3.2 Import/sync from ORCID Max
  33. 33. Agenda • Context • DSpace-ORCID • Conclusions & recommendations
  34. 34. Conclusions • DSpace ORCID integration level varies according with DSpace flavor – DSpace-CRIS appears to be the more complete and DSpace JSPUI the less complete – There are still some important requirements to be fulfilled. • R3.2 ORCID import is key for repositories and OA • The number of DSpace flavors spreads resources and this doesn’t seams to be beneficial (product and community).
  35. 35. Recommendations How can DuraSpace/community help us? Decision towards a unified path for the user interfaces (Mar 2015) – Work with COAR on: • #3 Supporting Author Identification Systems • #7 Supporting additional metadata formats – Follow VIVO Strategic Plan (2015 / 2016) • Goal 2: Promote a more open and networked research ecosystem (ORCID, euroCRIS, CRediT, and CASRAI)
  36. 36. Recommendations How can ORCID help us? – think of a special membership for repositories only purposes How can we help? Members of COAR, CASRAI, euroCRIS, ORCID and DSpace (gold) – Make add-to plug-in available – Integrate a task force to work on DSpace-ORCID integration
  37. 37. Cooperation is power!
  38. 38. ORCID in DSpace 5 University of Missouri - @mire Bram Luyten
  39. 39. OVERVIEW Current offered feature set Implementation use cases
  40. 40. IMPLEMENTED FUNCTIONALITY ORCID and DSpace Authority Control Integration Author lookup for new submissions (UI) Author lookup for edits on items (UI) Author identifiers in Batch CSV editing
  41. 41. WHAT DSPACE ALREADY OFFERED
  42. 42. INTEGRATION String representation of the name in standard Dublin Core metadata enhanced with DSpace compliant authority control id “authority cache” stores extended contributor metadata, including ORCID ID and alternative names
  43. 43. NEW SUBMISSIONS Adding an author with an identifier should ideally be as easy as providing a simple name.
  44. 44. Indicates that author is in DSpace Authority control
  45. 45. Authors in red are in DSpace Authority Control Authors in black are NOT in DSpace Authority Control
  46. 46. Staff enhances contributor string names with ORCID Administrator finalizes by re-uploading edited file Administrator exports existing work metadata Author identifiers in Batch CSV editing
  47. 47. SPREADSHEET EXAMPLE Add ORCID identifier to spreadsheet for batch deposit of metadata into DSpace: “ORCID:dc.contributor.author” Non-ORCID authors can still be imported: “dc.contributor.author”
  48. 48. SPREADSHEET EXAMPLE ORCID authors are retrieved automatically, and the author’s name is displayed in DSpace
  49. 49. CAVEAT: AUTHOR ORDER It is possible to preserve the order of the authors IF all of them have an ORCID ID, or NONE of them has an ORCID ID. Addressing the mixed situation is an important open issue.
  50. 50. IMPLEMENTATION USE CASES Empty new DSpace Repository Existing DSpace without prior usage of the authority control functionality Existing DSpace WITH prior usage of authority control.
  51. 51. RECAP: PRE DSPACE 5 AUTHORITY CONTROL
  52. 52. RECAP: DSPACE 5 ORCID INTEGRATION String representation of the name in standard Dublin Core metadata enhanced with DSpace compliant authority control id “authority cache” stores extended contributor metadata, including ORCID ID and alternative names
  53. 53. Questions? Thank You www.atmire.com
  54. 54. DSpace/DSpace-CRIS and ORCID 1 DuraSpace Webinar: Developments with DSpace and ORCID March 24, 2015 Andrea Bollini Michele Mennielli
  55. 55. • DSpace-CRIS/ORCID: current integrations • DSpace (JSPUI): what’s next? • DSpace-CRIS: what’s next? Agenda www.cineca.it | DSpace/DSpace-CRIS & ORCID | DuraSpace Webinar | March 24, 2015
  56. 56. DSpace-CRIS for euroCRIS It is possible to (public API): • Login through ORCID*; • Claim profile through ORCID; • Register/Associate an ORCID to your own DSpace-CRIS profile First release (part of the 4.3 version) DSpace-CRIS 5.1.0 Release www.cineca.it | DSpace/DSpace-CRIS & ORCID | DuraSpace Webinar | March 24, 2015 * Authentication code is based on the work on DSpace 5 and Dryad project
  57. 57. DSpace-CRIS: importing BIO info www.cineca.it | DSpace/DSpace-CRIS & ORCID | DuraSpace Webinar | March 24, 2015
  58. 58. DSpace-CRIS: importing BIO info www.cineca.it | DSpace/DSpace-CRIS & ORCID | DuraSpace Webinar | March 24, 2015
  59. 59. DSpace-CRIS: importing BIO info www.cineca.it | DSpace/DSpace-CRIS & ORCID | DuraSpace Webinar | March 24, 2015
  60. 60. DSpace-CRIS: importing BIO info www.cineca.it | DSpace/DSpace-CRIS & ORCID | DuraSpace Webinar | March 24, 2015
  61. 61. DSpace-CRIS: importing BIO info www.cineca.it | DSpace/DSpace-CRIS & ORCID | DuraSpace Webinar | March 24, 2015
  62. 62. DSpace (JSPUI): what’s next? Using API ORCID for finding authors with extreme precision during records’ submission and editing phases (including big amounts) – https://wiki.duraspace.org/display/DSDOC5x/ORCID+Integration – http://www.slideshare.net/ORCIDSlides/orcid-ann-campion Porting of the great job done by @mire for the XMLUI into the JSPUI www.cineca.it | DSpace/DSpace-CRIS & ORCID | DuraSpace Webinar | March 24, 2015
  63. 63. DSpace 5  DSpace-CRIS 5 ResearcherPage represents the extention of the cache authority introduced in DSpace 5 Data in ORCID are fully available in DSpace-CRIS: they can be seen, visualised, searched and “activated” When selecting a new record in ORCID a new Researcher Page corresponding to this very record is automatically created www.cineca.it | DSpace/DSpace-CRIS & ORCID | DuraSpace Webinar | March 24, 2015
  64. 64. DSpace-CRIS e ORCID: next steps (1) www.cineca.it | DSpace/DSpace-CRIS & ORCID | DuraSpace Webinar | March 24, 2015 DSpace-CRIS 4.3.1  DSpace-CRIS 5.1.1 (June ‘15) PUSH – services (members API) DSpace-CRIS 5.1.2 (end ‘15) Advanced PULL – services (members&premium API) With the collaboration of The Hong Kong University (HKU) and The Hong Kong Polythecnic University
  65. 65. DSpace-CRIS e ORCID: next steps (2) – Research’s bibliographic data (including the possibility to activate synchronisation for single field) – Publications (with the possibility to chose the publications to sync) – Projects (with the possibility to chose which projects to sync) PUSH local information to ORCID www.cineca.it | DSpace/DSpace-CRIS & ORCID | DuraSpace Webinar | March 24, 2015 PULL extended information from ORCID - Propose to import records in DSpace-CRIS when login-in looking to the Researcher’s ORCID profile Or - Automatically (notification and preferences allowed) when ORCID premium membership is available
  66. 66. Thanks a.bollini@cineca.it m.mennielli@cineca.it March 24, 2015
  67. 67. March 24, 2015 Hot Topics: DuraSpace Community Webinar Series QUESTIONS

×