= Virtual meeting on VLO planning 2017-01-16 = * What? * VLO planning meeting * Who? * Davor, Dieter, Matej, Menzo, Thomas, Twan * When? * 16 January 2017, 14.00 - 16.00 CET (on basis of [http://doodle.com/poll/9bsmid8m9hfpx7qm doodle]) * Where? * [https://hangouts.google.com/call/3kw7karpwvfdnbzjsuithchkfue Hangout] == Documents == * [https://docs.google.com/document/d/1Dn6-U0dUX5ljA_YRBDk5u0DOPiULzzclPXHLSR_Qfbw/edit?usp=sharing Live notes] (Google docs) * [https://docs.google.com/document/d/1oQCWuhuQFidlbombs0AGReStGJZ70-JEu0zK_lRZ_SE/edit?usp=sharing Meeting notes] from [[VLO/Meeting/2016-11-11|last meeting]] * [[Taskforces/CMDI/Meeting20161025-28|CMDI-TF meeting @ CAC2016]] * [attachment:"VLO dynamic mapping workflow.png" Dynamic mapping workflow diagram] * [https://office.clarin.eu/v/CE-2015-0687-CLARIN-PLUS_VLO_workplan.pdf CLARIN-PLUS: VLO Specification] * [https://www.clarin.eu/content/clarin-plus-supplemental-material Virtual Language Observatory testing report] (CLARIN-PLUS D3.2 Usability report appendix) * Milestones * [https://github.com/clarin-eric/VLO/milestone/1 VLO 4.1 milestone] (!GitHub) * [https://trac.clarin.eu/query?status=accepted&status=assigned&status=new&status=reopened&component=VLO+importer&or&status=accepted&status=assigned&status=new&status=reopened&component=VLO+web+app&group=milestone&col=id&col=summary&col=status&col=type&col=priority&col=milestone&order=priority&report=10 Trac tickets]? == Agenda== * Current state * VLO 4.1 * CLAVAS vocabularies * Other issues (long term?) * Planning * Development process == Notes == * Updated national project mapping (of 4.0.2) can be mentioned in an upcoming Centre News mail * Work for supporting [[Collaborations/Europeana|Europeana]] metadata (EDM) in progress, additional licence types need to be supported in the VLO (issues [https://github.com/clarin-eric/VLO/issues/41 41], [https://github.com/clarin-eric/VLO/issues/48 48]) * Some priorities reshuffled in [https://github.com/clarin-eric/VLO/milestone/1 4.1 milestone], also some issues taken off of milestone * Dynamic mapping: parallel implementation of support for external definition files in importer (by the VLO development team) on the one hand and workflow for maintaining mapping vocabularies (by ACDH) on the other hand. We stick with !GitHub despite occasional availability issues. * CLAVAS vocabularies * Stable CLAVAS not yet running in production * Menzo is working on the Organisation vocabulary * A MIME type vocabulary will be bootstrapped from IANA list * A complete vocabulary (including deprecated languages) for language (code)s will be bootstrapped from SIL * Mapping from a (Google) spreadsheet to a CLAVAS vocabulary definition is possible and the procedure can be adopted from CCR which uses the same procedure * (Potential) maintainers/owners of resource type, licence/availability vocabularies will be contacted about this by the Metadata Quality task force * An issue ([https://github.com/clarin-eric/VLO/issues/50 #50]) has been created for the sharing of mapping definitions and logic with applications that are not strictly part of the VLO such as the curation module, FLAT, CMD2RDF * Menzo proposed a [https://docs.google.com/document/d/13wLZM-HZTuBR6gChlepFHI74nOO9YF6poZa5hBfk-XA/edit more precise and robust method of deriving values for the National Project facet], which can be turned into an issue * TODO items * '''Thomas, Davor, Twan''' distribute/assign issues on the 4.1 milestone and start implementing fixes * '''Menzo''' continues work on the Organisation vocabulary * '''ACDH''' implements a workflow for maintaining normalisation/mapping definitions (this can happen in parallel to core VLO development) * '''Davor''' will attempt to make a fresh fork of the VLO repository in the ACDH organisation on GitHub and get it in sync with the curation VLO with a couple of commits to allow for merging and feature sharing in the near future * '''Menzo''' turns [https://docs.google.com/document/d/13wLZM-HZTuBR6gChlepFHI74nOO9YF6poZa5hBfk-XA/edit “National project” facet value retrieval] into a VLO enhancement issue * Remaining Trac tickets are evaluated and migrated to !GitHub if necessary; the remainder gets closed as 'wontfix' in the near future * Planning * Issues will be addressed in order of priority (milestone listing is priority-ordered) * ''Alpha'' release __early March__ * ''Stable'' release __mid-end March__ More details in the [https://docs.google.com/document/d/1Dn6-U0dUX5ljA_YRBDk5u0DOPiULzzclPXHLSR_Qfbw/edit?usp=sharing live notes on Google docs]