1 / 14

CERIF Reference Implementation

CERIF Reference Implementation and Compatibility Testing Jan Dvorak, CERIF TG Leader Nikos Houssos , Arch TG Leader Valerie Brasse , Projects TG Leader Miguel-Angel Sicilia, LOD TG Leader. CERIF Reference Implementation. Aims to be:

madge
Download Presentation

CERIF Reference Implementation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CERIF Reference Implementation and Compatibility TestingJan Dvorak, CERIF TG LeaderNikos Houssos, Arch TG LeaderValerie Brasse, Projects TG LeaderMiguel-Angel Sicilia, LOD TG Leader euroCRIS membership meeting, Bonn, 14 May 2013

  2. CERIF Reference Implementation • Aims to be: • An open system available for any interested party to study and understand CERIF down to the implementation level • Indicative implementation to clearly demonstrate the CERIF concepts • An open component of the CERIF compatibility testing system euroCRIS membership meeting, Bonn, 14 May 2013

  3. CERIF Reference Implementation Will not be: A full-fledged CERIF-CRIS product (or a first step to a future full-fledged implementation of a CERIF-CRIS software offering by euroCRIS) An implementation aiming to be the best of breed in terms of development details euroCRIS membership meeting, Bonn, 14 May 2013

  4. CERIF Reference ImplementationArchitecture euroCRIS membership meeting, Bonn, 14 May 2013

  5. CERIF Reference ImplementationArchitecture • The CERIF database. A native CERIF database, fully populated with fabricated (but realistic-looking) data that covers the entire CERIF model. The entire data of this reference CERIF database is publicly available for download in CERIF XML. • The REST API wrapper. A layer over the CERIF database that exposes its contents over a REST API in CERIF XML format. • The CERIF Export functional element. This element handles the transformation of CERIF database data to standard CERIF XML. • Another functional element (persistence layer) for general persistence functions might be needed - depends on the implementation technologies and architecture. euroCRIS membership meeting, Bonn, 14 May 2013

  6. CERIF Compatibility Testing System • Aim: • To ensure the quality and homogeneity of use of CERIF by systems claiming to be CERIF-compliant euroCRIS membership meeting, Bonn, 14 May 2013

  7. CERIF Compatibility Testing • Scenario A CERIF-CRIS software platforms (e.g. PURE, CONVERIS, Symplectic Elements, Research in View, etc.) • Scenario B Individual operational CERIF-CRIS systems currently in production, for example institutional, national or international CRIS (e.g. OpenAIREplus, EuroRIs-Net+) euroCRIS membership meeting, Bonn, 14 May 2013

  8. CERIF Compatibility Testing • Use case to be tested: Point-to-Point CRIS data exchange in CERIF XML • Ability of a CRIS system to provide information in standard CERIF-XML through a basic REST API. euroCRIS membership meeting, Bonn, 14 May 2013

  9. CERIF Compatibility Testing System • Components: • CERIF Reference Implementation (described before) • Compatibility Checker module, which performs queries against the system under test, retrieves the results and validates them, using, when appropriate, also information that it retrieves from the CC_REFIM. • The CRIS system under test – two types: • an operational CRIS system currently in production (e.g. institutional, national or international CRIS) • a specific testing installation of a particular CRIS software platform / product made available by the CRIS platform provider for the purpose of testing by the euroCRIS CERIF Compatibility Testing euroCRIS membership meeting, Bonn, 14 May 2013

  10. CERIF Compatibility Testing Scenario A euroCRIS membership meeting, Bonn, 14 May 2013

  11. CERIF Compatibility Testing Scenario B euroCRIS membership meeting, Bonn, 14 May 2013

  12. REST API • Minimal to allow straightforward implementation • Two types of mandatory operations: • Get the identifiers of all instances of a particular type of entity (e.g. get a list of all projects – however only the identifiers are returned for each project). The identifier returned for each entity instance must be adequate to allow retrieval of the full information about the particular project. Format of call: http://api.eurocris.org/{Entity}/ • Get all information about a particular instance of a particular type of entity (e.g. get information about project with id: 123456789). The information returned must contain the full record of the entity instance, including plain data fields, multi-lingual fields and 1st level of linked entities (in embedded mode). • Format of call: http://api.eurocris.org/get/{Entity}/{id} euroCRIS membership meeting, Bonn, 14 May 2013

  13. REST API invocation examples http://api.eurocris.org/project/123456789 (get information of project with id 123456789) http://api.eurocris.org/get/project/123456789 (get information of project with id 123456789) http://api.eurocris.org/project (get list of identifiers of all projects in the CRIS system) http://api.eurocris.org/get/project (get list of identifiers of all projects in the CRIS system) euroCRIS membership meeting, Bonn, 14 May 2013

  14. Thank you! euroCRIS membership meeting, Bonn, 14 May 2013 Questions / comments?

More Related