Opened 8 years ago

Closed 8 years ago

#857 closed task (fixed)

Facet definitions for availability/license/accessInfo

Reported by: Twan Goosen Owned by: Twan Goosen
Priority: critical Milestone: VLO-3.4
Component: VLO importer Version:
Keywords: Cc: teckart@informatik.uni-leipzig.de, davor.ostojic@oeaw.ac.at, go.sugimoto@oeaw.ac.at, matej.durco@oeaw.ac.at, Twan Goosen

Description

As described in #852, the situation with respect to facets relating to license/availability information changes in VLO 3.4. Therefore the existing descriptions and definitions (stored in facetConcepts.xml), as phrased by the VLO-WG of CLARIN-D, need to be reconsidered.

Current (VLO 3.3) definitions:

  • availability
    • Description: The usage conditions for the resource or tool
    • Definition: A rough description of the conditions under which the resource or tool can be used.
  • license
    • Description: The licensing conditions for the resource or tool
    • Definition: The name of the license or a very brief description of the licensing conditions under which the resource or tool can be used.

Proposed new definitions (tentative):

  • availability (facet)
    • Description: The category of conditions under which the resource or tool can be accessed
    • Definition: One of the three availability categories PUB/ACA/RES depending on whether access requires no identification, proof of academic affiliation, or has to be granted on an individual basis.
  • license (field)
    • Description: The license under which the resource or tool is made available
    • Definition: An identifier or the exact name of the license under which the resource or tool can be used.
  • accessInfo (field, multi-valued)
    • Description: Usage or access condition for the resource or tool
    • Definition: A description of a condition that applies to the usage or accessibility of the resource or tool.

Change History (4)

comment:1 Changed 8 years ago by DefaultCC Plugin

Cc: Twan Goosen added

comment:2 Changed 8 years ago by Twan Goosen

Excerpt from a mail I sent around concerning this ticket:

On 25/01/16 10:08, Twan Goosen wrote:

Although the actual task itself is rather trivial, I think in a way it is also pivotal as the exact usage of/mapping to these facets should be rooted in these definitions. So if you could all have a look and please comment on the new descriptions and definitions I proposed, as they really only are first attempts. You may not even agree with the direct I'm going with some of these, in which case it's good if we find out as soon as possible :)

Some clarification: the facet/field description is used in a tooltip in the application. The definition is not used at the moment, but could be used (maybe in the updated UI) e.g. in a detailed info pop-up.

comment:3 Changed 8 years ago by Twan Goosen

Definitions updated in ed661. Keeping this ticket open because we may want to revise the definitions based on feedback during the beta stage.

comment:4 Changed 8 years ago by Twan Goosen

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.