Data Query Response GUI

[KathiSchleidt]

Requirements to the Query Response:

• Provide an overview page for the search results. Includes:
  • short overview (title, preview image, start abstract, type, organization, geographical scope, certain statistics in overview, e.g. number of citations...)
  • information on scale, spatiotemporal resolution, usage constraints, provenance, uncertainty, accessibility, validated, downloaded, completeness, contact, endpoint existence Note: think some of this should go to the detailed record page
  • Link to map preview
  • Ability to tailor content of overview to specific communities
• Differentiate between overview page and detailed record page. On detailed record page, include:
  • FAIRness…
  • TBD
• Provide access to additional filters (filter options not yet used) in result page
• Prioritized results depending on highest alignment with filters
  • When searching multiple concepts, response should indicate extent to which concept fits to which response Note: not sure what sorts of search are envisioned. I'd expect responses to fit to all filters
• Provide a link to the record in SoilWise or original source
• When response includes links to other resources, make these actionable

[pvgenuchten]

Would be nice to have some prioritization in these properties, also important to understand that many properties will not be populated by the platform which provided the record, our backend can extract some properties from context, but not the full 100%

can you provide some context to: "Ability to tailor content of overview to specific communities"

"Prioritized results" is usually referenced to as 'search ranking', ranking is a typical aspect of Full text search. Although could also be implemented separately. It's certainly high on the wish list.

Data fairness... FAIR fits well in the domain of academic publications, but it is a less fit to the domain of real time sensing. Considering the variety of options in FAIR, it will be hard to establish an automated test to assess the level of FAIRness, especially if the resource has access constraints:

• Findability
  • Metadata describes the resource in a rich way
  • Metadata has a unique persistent identifier (URL/DOI)
  • Data (snapshot) has a unique persistent identifier (URL/DOI)
• Accessibility
  • Protocol is shared and universally implementable
• Interoperability
  • (Meta)data in a format which is formal, accessible, broadly applicable
  • Using common vocabularies
  • References to other metadata
• Reusability
  • Clear usage license
  • Rich provenance
  • (Meta)data meet domain relevant community standards