Extension: Metadata for Result

Metadata for Results

Motivation

Larger resources may be structured or contain a collection of (sub-) resources. While the EndpointDescription does allow nested resources, the amount of metadata (title, description, languages, institution) is limited. Additionally, too many sub-resources may clutter the view and overwhelm users. (A recommendation for endpoint operators and data providers would be great.) So, search results can not easily provide additional context information like date, author or source of a text fragment which would help users to contextualize results directly in the FCS Aggregator (frontend) without having to rely on optionally provided @pid or @ref links that may provide more information (e.g., landingpage or search result page of the FCS Endpoint).

Proposal

An additional Metadata Data View that should be at the ResourceFragment level of a result record to provide contextual information about the text.

It should have a clearly specified vocabulary to allow FCS Clients (FCS Aggregator) to visualize the information. Supporting multiple vocabularies might be possible to cover different domains.

Examples

TODO

Questions

1. Supported Vocabulary
   • Dublin Core
     • as a kind of catch-all metadata set?
     • What does it not cover?
     • Is it to generic so that some fields are not clear enough for users/endpoints?
     • Restrict to subset of fields?
   • What vocabularies do national libraries use?