= Virtual meeting on VLO development status 2017-10-24 =
 * What?
   * VLO status meeting for the 4.3 release
 * Who?
   * Dieter, Menzo, Thomas, Wolfgang, Twan (and Matej?)
 * When?
   * 24 October 2017, 14:00 - 15:00 CEST (on basis of [https://doodle.com/poll/axd6ntzun8vikxz7 doodle])
 * Where?
   * [https://hangouts.google.com/call/3kw7karpwvfdnbzjsuithchkfue Hangout] & [https://clarineric.slack.com/messages/G5U69D1MX #vlo-dev Slack channel]

== Documents ==
* Milestone
 * [https://github.com/clarin-eric/VLO/milestone/4 VLO 4.3 milestone] (!GitHub)
* [https://docs.google.com/document/d/1kP8-bzA5WoK960D4a-Qx9MTGtc-KFIPbk9591Lvgtk4/edit?usp=sharing Proposal for CFM requirements] - OLD, superseded by following:
* [https://docs.google.com/document/d/13ShmYq2-YWxmc8u868cCgP9fAv6tNoDAcoDCoIWoh_M/edit?usp=sharing Proposal for value mapping requirements and implementation]

== Agenda==

* VLO 4.3 development status
 * Open issues (see [https://github.com/clarin-eric/VLO/milestone/4 milestone])
  * Cross facet mapping (CFM)
    * Currently implemented feature
    * Specification of requirements and integration with existing mapping and normalisation mechanism
    * See [https://docs.google.com/document/d/1kP8-bzA5WoK960D4a-Qx9MTGtc-KFIPbk9591Lvgtk4/edit?usp=sharing requirements proposal]
  * Solr 6
  * Incremental import
* Planning
    - 4.3 beta release
    - 4.3 production release
* Annual conference recap (see notes from [[Taskforces/CMDI/Meeting20170918|task forces meeting]])
 * Vocabularies and mapping
 * Resource types
 * Licence categories (discussed in CLIC meeting, see excerpt below). 
  * Relation to Licence vocabulary?
  * Also see this [https://github.com/clarin-eric/VLO/issues/104 proposal] for an alternative approach in the VLO
* Planning
 * Real life meeting of VLO dev team (January?) to discuss
  * Fundamental development and maintenance aspects: review/consolidate our mechanisms + distribution of responsibilities
  * Transferral of knowledge
  * Conversion of concrete (pre-filtered) feedback into tasks and priorities
  * Long term planning (in the context of EOSC-hub)
* Other business?

== Notes ==

* CFM
 * We will investigate the options for a unified "value mapping" mechanism that involves a single definition allow for value mapping within and across facets. Twan initiated a [https://docs.google.com/document/d/13ShmYq2-YWxmc8u868cCgP9fAv6tNoDAcoDCoIWoh_M/edit?usp=sharing document to gather requirements and implementation options].
* Releases
 * 4.3 milestone planned to go in beta on 10 November
  * Will include use of stand alone Solr 6.0 - perhaps Solr 7.0 but this can also be postponed to 4.3.1 or 4.4.
 * CFM ([https://github.com/clarin-eric/VLO/issues/93 #93] and depending feature [https://github.com/clarin-eric/VLO/issues/46 #46]) and VTD-XML upgrade ([https://github.com/clarin-eric/VLO/issues/92 #92]) are postponed to [https://github.com/clarin-eric/VLO/milestone/7 VLO 4.4]
* Meetings
 * BoD will meet in November to discuss VLO functionality and report back to us. Among other things representation of licensing and availability in the VLO will be discussed.
 * A curation meeting organised by ACDH will take place in November (more info TBA)
 * A VLO development meeting (see agenda) + knowledge exchange will take place in January in The Netherlands
   * [https://doodle.com/poll/t3cpkbcnv6kgev7r Doodle]

== Excerpt from CLIC meeting at CAC 2017 ==

3. Discussion about VLO:
- There is a confusion between different categories that are either not consistent with the ones in the other communities or not clear even to the people who upload the content:  e.g. public, academic, restricted. Though there are concepts free/open/public, also the dichotomy between academic users versus academic use. We should disambiguate those matters. Overall, we will have to use the wording of open access, also even from simply political views.
- Whatever would be the decision on the procedure how to assign types of data for the new data being added to the VLO, what to do with the legacy data?
- Currently in VLO 80% are of unspecified category! So at least for the new data, the copyright clearance should be the first step, but still the backlog of those legacy datasets is the question to take decision on.