FInding and managing services in multiple service catalogs

Home » Eosc Service And Research Product Catalogues » Post » FInding and managing services in multiple service catalogs

Jos Vanwezel's picture
13 Sep 2020

FInding and managing services in multiple service catalogs

  • By Jos Vanwezel

Dear all,

The project EOSC Pillar is discussing the use of service catalogs in national context and plans to deploy a pilot. This activity may have consequences for the operation of EOSC. For this thread I focus on the technical consequences. Together with Luciano Gaido and Leonardo Candela, who are leading project tasks to implement a functional services catalog we started thinking how the Pillar catalog could interact with the EOSC-hub catalog and for that matter with others, since we must assume other (existing) catalogs want to join as well.

The construction of a federation of catalogs or similar seems useful and I like to understand what activity is already undertaken to make that possible. What work was done on standardisation of (service) descriptions so they can be exchanged easily, similarly regarding the communication between catalogs? Are there solutions we can borrow from the experience with data catalogs? Have you already worked on describing processes and indicating roles and actors in the context of services management. Where does FitSM fit in? What projects are involved  and could this IG help to channel the discussion?

Your input is much appreciated.



  • Andrea Mannocci's picture

    Andrea Mannocci

    Date: 24 Sep, 2020

    Dear Jos, (and Luciano, and Leonardo),

    Thank you for starting this discussion in EOSC-Pillar and for bringing that here; this IG is indeed a good place to channel this discussion, gather feedback and hopefully take this further.
    Summarising, to date, new SDTs have been designed (v3.0) to accommodate service and resource registration in EOSC. Similarly, the EOSC Onboarding process has been revised and it is currently in beta testing here,

    About information exchange, and your observations about integration of catalogues, APIs are being tested in beta too,
    As you can see, it would be possible to register providers and resources programmatically (POST and PUT methods).
    However, this leaves out third-party resource catalogue harvesting, i.e. automated pull of information into EOSC from external catalogues, which is still an open discussion, as far as I know.

    Regarding your question about FitSM, I reckon Owen could massively contribute to this point.

Leave a Reply