architectural design with components (D1.3)
Harvester
- lead: Paul, Cenk
- contributors: Rob & team, Nick
- repository:harvesters
- foreseen as part of prototype in 1st iteration (doc)
Catalogue
- lead: Paul
- contributors: MU, Nick
- repository: pycsw
- most functionality foreseen as part of prototype in first iteration (doc)
Metadata Validation
- lead: MU (first iteration) - MU/Anna + PhD (second iteration)
- contributors: Paul, Thorsten, Cenk, Hugo, WE, Vasilis
- repository:
- foreseen as part of prototype in first iteration (doc)
Transformation & Harmonization
- lead: WE
- contributors: Paul, MU, CREA
- repository:
- foreseen as part of prototype in 1st iteration (doc)
Metadata augmentation
- lead: Paul
- contributors: Beichen, Nick
- repository:
- some functionality foreseen as part of prototype in first iteration (doc)
Knowledge Graph
- most functionality foreseen as part of prototype in first iteration (doc)
- lead: Rob & team, Anna
- contributors: Nick
- repository:
- not foreseen for 1st iteration (doc)
System Usage & Monitoring
- lead: WE
- contributors: Paul
- repository:usage-statistics
- foreseen as part of prototype in 1st iteration (doc)
Storage
- lead: (WE-) Paul - Rob & team
- contributors:
- repository:
- most functionality foreseen as part of prototype in first iteration (doc)
Authorisation
- lead: WE
- contributors: Paul
- repository: Soilwise repo
- not foreseen for 1st iteration (doc)
Metadata authoring
- lead: Paul
WE - contributors: Paul, MU
- repository:
- not foreseen for 1st iteration (doc)
Natural Language Querying
- lead: Rob & team
- contributors: Nick
- repository: natural-language-querying
- not foreseen for 1st iteration (doc)
Map Server
technical repositories not directly linked to a technical component:
- dashboard: only for interaction with stakeholders, SWR intended to integrate in EUSO Dashboard
- development-environment-and-infrastructure: not a technical component, but repository related to WE infrastructure that will be used for SWR (mainly from 2nd iteration and further)
- governance: several issues about governance related to SWR
- Soilwise-credentials: repository containing credentials, logins, passwords used for multiple technical components in SWR; Gopass technology used to manage this
other repositories in the github environment linked to the project:
- SoilWise-documentation: documentation on SWR (Technical components, API's, Infrastructure, Glossary; released for D1.3)
- soilwise-architecture: documentation about architecture (Archimate model)
- Soilwise-Sprint-Backlog: this reposoitory, contains guidelines for the GitHub soilwise-he repositories and the related backlog for the Soilwise project
- Soilwise-userstories: repository to steer the functional requirements of the system, using a user story approach
- Project-management: repository for project management
other repositories in the github environment as inspiration:
- soilinfohub: repository forked from EJP Soil Datahub, a participative effort to collect and maintain a series of descriptions of soil datasets (metadata) in the EU to facilitate discovery of these resources
- demo-zenodo-neo4j-llm-ilvo: demo by ILVO with harvesting Zenodo, ETL to NEO4J graph database and integrated with LLM for search functionality, using Neo4J datascience algorithms for ranking or identifying duplicate datasources
- inspire_soil_gpkg_template: repository hosting the design of a template for a relational database to capture soil data according to the INSPIRE soil data model