New facet "coverage"

[herold@bbaw.de]

Saarland University staff request a new facet "coverage" for temporal and spacial coverage of a resource.

Original report below:

<coverage>. Diese Information ist leider im Moment nicht in den Facetten enthalten. Ein Nachfolger des VLO

[herold]

I think it'll be useful to establish a separate facet for temporal coverage so you can see which time period a resource covers. I'd oppose to an indiscriminate mixture of temporal and spacial coverage.

[knappen]

Sigh, my comment was lost due to the server problems ...

I think it is good to have two facettes for temporal and spatial coverage in the VLO user interface.

But Dublin Core uses the same tag, coverage, for both of them. So the VLO needs some efforts to separate temporal and spatial coverage. This can be done by pattern matching (everything matching an ISO 8601 time or time range as temporal coverage, matching a terms from the TGN as spatial coverage, also matching ISO country codes as spatial coverage).

References:

​http://dublincore.org/documents/dcmi-terms/ Best Practice for Dublin Core

​http://www.getty.edu/research/tools/vocabularies/tgn/ Thesaurus of Geographical Names

[twagoo]

Needs to be reflected in the web app but primarily an importer matter

[Jörg Knappen]

There is now a VLO task force proposal for the handling of Time Coverage,
see https://trac.clarin.eu/attachment/wiki/%20VLO%20Taskforce/time_coverage.pdf

[Sander Maijers]

I suppose if something is to be done with the ticket it should be reassigned to someone working on the VLO at this time. Twan, can you triage it?

[teckart@informatik.uni-leipzig.de]

The VLO taskforce/working group has decided to use a new facet "temporal coverage" which is now supported by the importer in trunk (r5932). Still need a postprocessor to normalize values and then to find a sane way to use these values in the Web app (maybe a dual slider?). Closing this ticket and creating a new one for the postprocessor + Web app support.