1. SWR catalogue/dashboard

[BerkvensNick]

The SWR Catalogue will be powered by a GIT repository, relational database and triple store containing standardised metadata of external data/knowledge resources. Standardised means a unified structure despite various input metadata structures from the underlying repositories, such as CORDIS, INSPIRE Geoportal, Zenodo, BonaRes, OpenAire, etc. https://github.com/soilwise-he/Soilwise-userstories/issues/17

Origin: D1.3 Repository architecture

• catalogue
• dashboard (JRC-ESDAC will use EUSO dasboard, keep to minimum only for project demonstrations with stakeholders)
• search function
• metadata store
• standardised metadata (=unified structure)
• metadata of datasets
• metadata of knowledge
• data from EUSO
• data from INSPIRE Geoportal
• data from Zenodo
• data from Cordis
• data from BonaRes
• data from OpenAire

---

With acceptance criteria:

• Catalogue

• Visibility: Users can see a list of all available documents.

• Accessibility: The catalogue is accessible via a clear and intuitive menu on the homepage.

• Sorting: Users can sort the catalogue by various criteria (e.g., date, relevance, title).

• Filtering: Users can filter the catalogue based on predefined categories (e.g., source, date range, document type).

• Pagination: The catalogue supports pagination for easy navigation through large datasets.

• Dashboard

• Search Function

• Relevance: The search function returns relevant results based on user queries.

• Speed: Search results are displayed within a few seconds.

• Filters: Users can apply filters to refine search results (e.g., by date, document type, source).

• Advanced Search: Advanced search options are available for more precise queries (e.g., Boolean operators, exact phrases).

• Result Sorting: Users can sort search results by relevance, date, or title.

• Metadata Store

• Central Repository: All metadata is stored in a centralized repository.

• Scalability: The metadata store can handle a large volume of metadata entries.

• Accessibility: Metadata is accessible via the search function and the catalogue.

• Integrity: Metadata entries are accurate and consistently formatted.

• Security: The metadata store is secure from unauthorized access.

• Standardized Metadata (Unified Structure)

• Consistency: All metadata follows a standardized structure.

• Interoperability: Metadata is interoperable with other systems and standards.

• Validation: There are validation rules in place to ensure metadata conforms to the standardized structure.

• Documentation: Clear documentation is provided for the metadata structure.

• Ease of Use: The standardized metadata is easy to use and implement by developers.

• Metadata of Datasets

• Completeness: Metadata for datasets includes all necessary information (e.g., title, description, date, source).

• Accuracy: Metadata entries accurately reflect the content and details of the datasets.

• Searchability: Dataset metadata is searchable through the platform's search function.

• Linkage: Metadata entries link to the actual datasets for easy access.

• Updates: Metadata is updated regularly to reflect any changes in the datasets.

• Metadata of Knowledge

• Relevance: Metadata captures key information about knowledge documents (e.g., articles, reports).

• Comprehensiveness: All essential details are included in the metadata (e.g., author, publication date, keywords).

• Accessibility: Knowledge metadata is accessible and searchable via the platform.

• Categorization: Metadata entries are properly categorized for easy filtering and retrieval.

• Regular Updates: Metadata is kept up to date with the latest knowledge documents.

• Data from EUSO

• Integration: Data from EUSO is successfully integrated into the central database.

• Accuracy: EUSO data is accurately reflected in the platform.

• Searchability: EUSO data is searchable via the platform's search function.

• Metadata: EUSO data includes standardized metadata entries.

• Access: Users can easily access and retrieve EUSO data through the platform.

• Data from INSPIRE Geoportal

• Integration: Data from INSPIRE Geoportal is integrated into the central database.

• Accuracy: INSPIRE Geoportal data is accurately captured.

• Searchability: Users can search for INSPIRE Geoportal data using the platform's search function.

• Metadata: Standardized metadata is provided for all INSPIRE Geoportal data entries.

• User Access: Users can access INSPIRE Geoportal data easily through the platform.

• Data from Zenodo

• Integration: Data from Zenodo is seamlessly integrated into the central database.

• Accuracy: Zenodo data is accurately represented in the platform.

• Searchability: Zenodo data is searchable via the platform's search function.

• Metadata: Zenodo data includes standardized metadata entries.

• User Access: Users can access Zenodo data easily through the platform.

• Data from Cordis

• Integration: Cordis data is integrated into the central database.

• Accuracy: Cordis data is accurately reflected in the platform.

• Searchability: Cordis data is searchable via the platform's search function.

• Metadata: Standardized metadata is provided for all Cordis data entries.

• User Access: Users can easily access and retrieve Cordis data through the platform.

• Data from BonaRes

• Integration: BonaRes data is successfully integrated into the central database.

• Accuracy: BonaRes data is accurately represented.

• Searchability: BonaRes data is searchable using the platform's search function.

• Metadata: BonaRes data includes standardized metadata entries.

• User Access: Users can easily access and retrieve BonaRes data through the platform.

• Data from OpenAire

• Integration: OpenAire data is seamlessly integrated into the central database.

• Accuracy: OpenAire data is accurately reflected in the platform.

• Searchability: OpenAire data is searchable via the platform's search function.

• Metadata: Standardized metadata is provided for all OpenAire data entries.

• User Access: Users can access OpenAire data easily through the platform.

[pvgenuchten]

EUSO above, is that meant as ESDAC?

[BerkvensNick]

@tomreznik , do you have an answer to the above question of Paul?

[tomreznik]

Yes, ESDAC is a part of the EUSO (at least, I am convinced that Panos Panagos mentioned that explicitly).

[pvgenuchten]

It is important to understand the difference between euso and esdac, to my knowledge the esdac team facilitates the euso community, which is thus wider then esdac itself. The swr aims to become the data and knowledge facility of euso, it makes sense it will harvest esdac, not itself

[roblokers]

I think indeed the ESDAC, but also the EUSO and dashboard part require some clarification (at least for me).

• will ESDAC (now containing among others a "catalogue" and search function on soil data, maps documents etc) remain an independent part of EUSO? And what does that mean for SWR and for ESDAC? E.g. will ESDAC remain having it's own metadata search?
• Does data from EUSO exist as a separate datasource? Or is that actually the data from ESDAC?
• EUSO currently already has a dashboard, and I think we were instructed stay away from dashboarding as that lies with JRC, so how much time should we spend in the first interation on including the dashboard functions mentioned above?

[tomreznik]

These questions are the best to be answered directly by the JRC. As far as I understand it:

• EUSO is a broader concept than ESDAC (ESDAC is a part of the EUSO), as indicated by Paul.
• The current ESDAC lacks a catalogue (unless we understand https://esdac.jrc.ec.europa.eu/resource-type/datasets as a catalogue). We should fix this situation with the SWR Catalogue the JRC will adopt.
• I don't know whether the EUSO has some more data than ESDAC. I would say so for the computation of soil health indicators. However, these data are not publicly available.
• I confirm that EUSO already has a dashboard, and the JRC explicitly mentioned several times they will manage that dashboard by themselves. Let's spend only time on the dashboard in the first iteration that is needed to show the SWR functionality. Let's be pragmatic.

[pvgenuchten]

what is EUSO? See soilwise-he/governance#10
Challenges of harvesting ESDAC? See soilwise-he/harvesters#5

[KathiSchleidt]

Question to Standardized Metadata (Unified Structure), any outlook what will be used? I'm asking because we recently had discussions on this between projects working on the Green Deal Data Space (GDDS), our current working conclusion is that we try and align the various metadata approaches selected by our projects (ISO 19115 and STAC) to GeoDCAT as a common semantic core. Think that would make sense here also