Table 1. shows the requirements that we have extracted from the experts’ responses.
The color-coding indicates the importance of each requirement according to the number of responses that signified it.
| ID | Requirements | doamin experts |
|---|---|---|
| R01 |
The ENVRI-KMS should include all prospective RIs, datasets, repositories, best practices, service catalogs, and design
decisions in its search space. |
54.29% |
| R02 |
Contact lists of people in charge of specific tasks (authors, researchers, developers, etc.) must be provided by the ENVRI-
KMS. |
54.29% |
| R03 |
The ENVRI-KMS is required to employ a set of assessment criteria, such as FAIRness criteria, to evaluate search space
entities. |
85.71% |
| R04 | Private, public, open-source, or premium search space entities should be indicated in the ENVRI-KMS. | 37.14% |
| R05 |
Documentation, technical solutions, configurations, and compatible combinations should all be recommended by the
ENVRI-KMS. |
34.29% |
| R06 | The ENVRI-KMS should provide technical discussions through Q&A forums and invite domain experts to participate. | 45.71% |
| R07 | Ontologies and semantic search should be supported by the ENVRI-KMS. | 60.00% |
| R08 | Multilingual inquiries should be supported by the ENVRI-KMS. | 8.57% |
| R09 | The ENVRI-KMS should be able to search for source code and provide suitable solutions to technical issues. | 14.29% |
| R10 | The contents of the RI websites have to be searchable through ENVRI-KMS (similar to what Google search engine does.) | 60.00% |
| R11 | The user interface (UX/UI) of the ENVRI-KMS should be similar to typical search engines. | 57.14% |
| R12 | The ENVRI-KMS should be able to connect to endpoints and support SPARQL queries. | 28.57% |
| R13 | High performance and availability have to be two essential quality attributes of the ENVRI-KMS. | 68.57% |
| R14 | APIs for connecting to virtual research environments (ENVRI-HUB) should be available through the ENVRI-KMS. | 34.29% |
| R15 | Automated knowledge ingestion should be possible with the ENVRI-KMS. | 28.57% |
| R16 | The outcomes and contents of the ENVRI-KMS should be visualized. | 48.57% |
| R17 | The ENVRI-KMS should be able to search numerous image categories (plots, etc.) and support image search. | 42.86% |
| R18 | Domain experts must be able to analyze the contents of the ENVRI-KMS using assessment techniques. | 48.57% |
| R19 | The ENVRI-KMS should support manual knowledge ingestion. | 11.43% |
| R20 | The knowledge base of the ENVRI-KMS should always be kept up-to-date. | 31.43% |
| R21 | One of the search criteria in the ENVRI-KMS should be the geolocation of datasets. | 48.57% |
| R22 | The metadata of the search space entities, such as datasets and APIs, should be available through the ENVRI-KMS. | 20.00% |
| R23 | Continuous integration and continuous delivery (CI/CD) should be supported by the ENVRI-KMS. | 28.57% |
| R24 |
Different user groups, such as researchers, knowledge curators, developers, and high-level managers, should receive
suggestions from the ENVRI-KMS. |
17.14% |
| R25 | The ENVRI-KMS should categorize and classifies its knowledge base contents. | 37.14% |