2. knowledge

[BerkvensNick]

The Triple store will be extended with links to knowledge assets from external resources, for the 1st iteration extracted from CORDIS. To a user, the knowledge will be made available, among others, based on interlinked metadata, i.e., metadata linked to relevant projects and project deliverables.  

Origin: D1.3 Repository architecture

• triple store hosting knowledge graph (KG)
• KG structure implementing the chosen SWR metadata schema
• KG structure implementing linkages between resources
• CORDIS resources metadata + links to knowledge integrated in KG (link to harvester component)
• Explicit links from CORDIS to OpenAire/Zenodo integrated in KG (link to harvester component)
• OpenAire/Zenodo resources metadata + links to data and/or knowledge integrated in KG (link to harvester component)
• Bonares resources metadata + links to knowledge integrated in knowledge graph (link to harvester component)
• integrated UI visualisation of data and knowledge resources (link to UI component)
• UI visualisation of (explicitly) linked data and knowledge (link to UI component)

---

With acceptance criteria:

• Triple Store Hosting Knowledge Graph (KG)

• The triple store must be set up and running on the designated server.

• It should support SPARQL queries and provide an endpoint accessible to authorized users.

• It must store and manage triples effectively, ensuring data integrity and consistency.

• The performance of the triple store should be tested to handle the expected volume of data and queries without significant lag.

• KG Structure Implementing the Chosen SWR Metadata Schema

• The KG must correctly implement the chosen SWR metadata schema.

• All required entities, properties, and relationships defined in the metadata schema should be present and correctly structured.

• The KG should pass validation tests against the schema to ensure compliance.

• Sample data should be inserted and queried to demonstrate correct implementation.

• KG Structure Implementing Linkages Between Resources

• The KG should include defined linkages between various resources as specified.

• These linkages must be navigable through SPARQL queries, demonstrating connections between resources.

• The linkages should be tested to ensure they reflect the relationships accurately and consistently.

• Visualization tools should display these linkages clearly to users.

• CORDIS Resources Metadata + Links to Knowledge Integrated in KG (link to harvester component)

• CORDIS metadata should be harvested and integrated into the KG.

• All relevant metadata fields must be accurately mapped and stored in the KG.

• Links to knowledge (e.g., project deliverables) should be established and verified.

• Queries and visualizations should correctly reflect the integration of CORDIS metadata.

• Explicit Links from CORDIS to OpenAire/Zenodo Integrated in KG (link to harvester component)

• Explicit links between CORDIS resources and Zenodo should be established within the KG.

• These links should be navigable and correctly represented in the KG.

• Test cases should confirm that users can traverse from CORDIS resources to corresponding Zenodo entries.

• The linkage data should be visualized correctly in the UI.

• OpenAire/Zenodo Resources Metadata + Links to Data and/or Knowledge Integrated in KG (link to harvester component)

• OpenAire/Zenodo metadata should be harvested and integrated into the KG.

• All relevant metadata fields must be accurately mapped and stored in the KG.

• Links to associated data and/or knowledge should be established and verified.

• Queries and visualizations should correctly reflect the integration of Zenodo metadata.

• Bonares Resources Metadata + Links to Knowledge Integrated in KG (link to harvester component)

• Bonares metadata should be harvested and integrated into the KG.

• All relevant metadata fields must be accurately mapped and stored in the KG.

• Links to knowledge resources should be established and verified.

• Queries and visualizations should correctly reflect the integration of Bonares metadata.

• Integrated UI Visualization of Data and Knowledge Resources (link to UI component)

• The UI should integrate visualizations for all data and knowledge resources within the KG.

• Visualizations must be clear, interactive, and user-friendly.

• Users should be able to filter, search, and navigate the data and knowledge resources easily.

• Performance tests should ensure that the UI loads and responds quickly even with large datasets.

• UI Visualization of (Explicitly) Linked Data and Knowledge (link to UI component)

• The UI should clearly visualize explicitly linked data and knowledge.

• Users should be able to see the relationships and linkages between different resources.

• The UI must provide intuitive navigation through these links.

• Tests should confirm that the visualized links correspond accurately to the data in the KG.