Virtual meeting on VLO planning 2018-03-12

• What?
  • VLO planning meeting
• Who?
  • Wolfgang, Thomas, Menzo, Twan
• When?
  • 12 March 2018, 14.00 - 16.00 CET (on basis of ​doodle)
• Where?
  • ​Zoom

Documents

• ​Value mapping requirements
  • Note: a bit outdated but contains up-to-date examples towards end
• ​Value mapping parameters/scenarios
• ​Description of the current workflow for data import & Identification of possible side effects (Wolfgang)
• ​Potential for reimplementation of VLO post-processors as value mapping cases (Twan)

• Previous meetings
  • ​Nijmegen VLO dev meeting notes
  • ​Vienna curation meeting notes

• Milestones
  • ​VLO 4.4 milestone (GitHub)

Agenda

• Current state
• VLO 4.4
  • Value mapping
  • Other issues
• Other milestones
  • EOSC-hub
• Planning

Notes

• Value mapping (​#93)
  • Ok to always operate on post-processed values for now, but should be documented for curators
  • Value mapping implementation could have a single map per value-map. Wolfgang will change this in the implementation
  • We keep the currently implemented behaviour of any removeSourceValue="true" overriding all cases of "false" among matching target-value-sets
  • Overriding existing values behaviour can be improved and made more predictable by buffering 'override' values and only applying them after all facets have had values mapped to them. Wolfgang will change this in the implementation.
  • CSV to XML transformation could combine source values with same target into commong target-value-sets
• Data provider and national project mapping based on OAI endpoint (​#131)
  • Centre registry does not yet provide national project information via API
  • Record tarballs will include endpoint URI
  • Value maps for endpoint->dataProviderName and endpoint->nationalProject are created from information in centre registry
  • VLO picks these up with rest of VLO mapping
• Planning
  • VLO 4.4 beta testing with value maps starts end of March
  • VLO 4.4 release in week 17 (23~27 april)
  • Wolfgang is on vacation between 26 March and 10 April but will implement the described changes to the mapping logic before leaving