Virtual meeting on VLO planning 2019-03-28

• What?
  • VLO planning meeting. Follow up of 2019-03-21 meeting
• Who?
  • Can, Dieter, Matej, Menzo, Tariq, Thomas, Twan, Wolfgang
• When?
  • Thursday 28 March 2019, 13:00 - 14:30 CET
• Where?
  • ​Zoom

Documents

• ​EOSC-hub roadmap

• Milestones (GitHub)
  • ​VLO 4.7 milestone
  • ​Other milestones
  • ​EOSC-hub related issues

Agenda

VLO 4.7

Mono-lingual resource filter

See issue ​#212.

Thomas to first carry out an evaluation of value distribution and accuracy. Any new insights?

Link checker data integration

See document: ​Link checker - VLO integration (issue ​#220)

Decisions thus far:

• Functional
  • Show link status only for problematic cases (broken or requiring authn)
  • Show for each individual link on the record page
  • Option to filter results to show only 'the good stuff': records with public access and available resource(s)
  • Ranking penalty for records with inaccessible linked resources

• Implementation
  • An API is to be designed and implemented for providing access to the resource status information.
    • Working title: Resource Access Status API (RASA)
    • Methods to be defined on basis of requirements from VLO and Curation Module (see ​document)

• Software maintenance
  • Alternative/enhanced solution (partially) based on 3rd party components to be investigated by ACDH. Development for 4.7 releases takes priority.

Notes

Repository ​resource-availability-status-api created.

• Can will create java interfaces based on design in ​document
• then index updater can be implemented on VLO side on basis of interfaces
• Can will implement Mongo based implementation later (to be completed ~mid March)

Planning

• Finish design and requirements: late March
• Curation module 3.0: Early April
• Implementation of Resource Availability Status API for Mongo: mid April
• Completed Implementation of 4.7 milestone: Late April
• VLO 4.7.0 beta release: early May
• VLO 4.7.0 stable release: mid May