Virtual meeting on VLO planning 2017-04-10

• What?
  • VLO planning meeting
• Who?
  • Dieter, Matej, Menzo, Thomas, Twan
• When?
  • 10 April 2017, 14.00 - 16.00 CET (on basis of ​doodle)
• Where?
  • ​Hangout

Documents

• Annotated version of CLARIN+ VLO work plan​ (green = implemented, yellow = unimplemented feature)
• ...

• CMDI-TF meeting @ CAC2016
• ​CLARIN-PLUS: VLO Specification
• ​Virtual Language Observatory testing report (CLARIN-PLUS D3.2 Usability report appendix)

• Milestones
  • ​VLO 4.2 milestone (GitHub)
    • Also see ​issues that are not on a milestone (yet)
  • Trac tickets?

Agenda

• Current state
  • Curation workflow?
• VLO 4.2
• CLAVAS vocabularies
• Other issues (long term?)
• Planning
  • Release end of June 2017 (CLARIN+ deliverable due, document for approval mid June)
• Development process

Notes

Situation and planned work @ ACDH

Situation at ACDH: two java developers (~130% full time combined) will start 1 May, filling up for Davor (Parthenos + CLARIN). At least one of them be present at the upcoming centre meeting in Utrecht, along with Matej.

Matej and team will pick up the work on further implementing the curation workflow (distributed work on normalisation maps etc), starting in May (before the centre meeting, after work on assessment).

Matej and team will look at: ​#46, ​#68. Not considered blocking for 4.2.

TODO: create ticket for cross-facet mapping (​#46 depends on this)

Incremental import

We will try to implement incremental imports to complement incremental harvesting. This work is covered by issue #34. Menzo will deliver a delta to the developers; the exact details and requirements are to be worked out.

Some considerations:

• import logic is not strongly affected
• processing of untouched records may be skipped/reduced
• look at interaction with 'rentention time' (the 7 days after which unseen records are removed)
• look at interaction with changes in mapping (any change should lead to re-processing all present records)

Planning

While it is not strictly necessary to have 4.2 available in production at the time of the delivery milestone, this is desirable and we will aim for it. It is not required to have the full VLO CLARIN+ specification implemented, but all 'promised' features are to be mentioned and reflected upon in the context of development/discussion during CLARIN+.

• Week of meeting (14/4): all review tickets in ​https://github.com/clarin-eric/VLO/milestone/3 and self-assign issues. Remaning issues are discussed and likely taken off the milestone
• Early June (~2/6): draft of CLARIN+ deliverable (document describing VLO work during CLARIN+)
• Early-mid June (~9/6): Deployment of 4.2.0-beta
• Mid june (~16/6): Final draft of deliverable (version for approval)
• End of June (~30/6): Release and deployment of 4.2.0, submission of deliverable

Twan will initiate the writing process for the deliverable document.