2017.4 meeting #9 2019-01-17

• Contractors have developed the new ATS/ETS for MD TG 2.0, View Services (WMS and WMTS) and SOS:
  • ATS/ETS are available on Github (in our workspace) under different branches, in draft status (they may still change)
    
  • ATS/ETS are currently under testing from the JRC on sandbox instances provided by Contractors
  • ATS/ETS for WCS will be developed at a later stage
    
• JRC is still evaluating to setup a test instance of the ETF validator, that everyone can use for testing
• The cloud environment (to setup a cloud instance of the ETF validator) is available

• JRC to agree with the Contractors on how to setup an instance in the cloud environment
  

• Visual improvement of test reports #1https://github.com/inspire-eu-validation/community/issues/1:
  • considered of high priority/nice to have by subgroup members
  • related to the possible future use of the validator as a Monitoring & Reporting tool to assess metadata conformity

• Show conformance class dependencies to users #6 https://github.com/inspire-eu-validation/community/issues/6:
  
  • the first proposal (automatic display of dependencies of conformance classes in the user interface) is considered of high priority/nice to have
  • agreement to move forward this first proposal, and keep the second proposal (dependencies also displayed as a tree in the "Configure Test Run" window) parked for the moment

• Improving the way test reports are searched and found #7 https://github.com/inspire-eu-validation/community/issues/7:
  • considered as high priority/nice to have, will be moved forward
    
    
• Support pdf printable version of test reports #8 https://github.com/inspire-eu-validation/community/issues/8:
  • considered of high priority/nice to have
  • agreement to provide the possibility to download the test report in all possible levels of detail
  • the default will be a summary document, but the user will be able to ask for higher levels of detail
    
    
• Simplified user interface for starting tests #10 https://github.com/inspire-eu-validation/community/issues/10:
  • agreement that this is a low priority improvement, because usually also people who are not used to work with the Validator get used to it
  • in terms of how to simplify the interface, most members prefer to have a list of known resource types, but there is not a full agreement on this and we may even think to offer both options
    • further discussion needed
• Improving the user dialogue for the selection of the tests to execute #9 https://github.com/inspire-eu-validation/community/issues/9:
  • confirmed to be low priority

• ETF Status page #4 https://github.com/inspire-eu-validation/community/issues/4
  • agreement that the Status page is not very used and not suitable for users

• JRC to decide what to do with this page
  
  
• JRC to prepare and submit improvement proposals for the ETF, based on the feedback from the subgroup
  

• https://github.com/inspire-eu-validation/community/issues/2

• https://github.com/inspire-eu-validation/ets-repository/issues/182

• https://github.com/inspire-eu-validation/ets-repository/issues/180

  • a bug fix for these 3 issues has been submitted
• https://github.com/inspire-eu-validation/ets-repository/issues/177
  
  • this can lead to an improvement proposal (keep out the manual checks, and show them as a checklist at the bottom of the report)

• JRC to create an improvement proposal
  

• https://github.com/inspire-eu-validation/view-service/issues/145

• Contractors to create a PR to fix the issue

• https://github.com/inspire-eu-validation/ets-repository/issues/146
  • longstanding issue
  • the problem is that there is no such requirement in the DS, so there is no test planned for it; thus, in order to introduce a test we need a change in the SD

• JRC to check with the issue proposer on which problem this generates
  

• Background: we received a number of change proposals for the Validator, which are mostly related to the UI and not to the underlying validation system. Therefore, we would like to understand what is the best way to get ideas on future developments and we wondered to organize a workshop with the everyday users of the Validator (similarly to what we did in September 2018 for the Registry).
• Since we received few comments on this idea, we are not sure whether it makes sense to have it.
• Alternatively, another idea is to have a survey (as also used for the Registry) to get input by people that are actually using the Validator.

• JRC to prepare a draft survey (as a Github issue) for the next subgroup meeting, that everyone can comment
  

AOB

• Creation of the Changelog page on the community space, in order to:
  
  • notify about the current status of the ATS/ETS, the changes made and issues addressed
  • notify about planned future changes of the ATS/ETS

• JRC to place a link to the changelog (instead of the roadmap) in the README
  

• On January 23-24 JRC will host a workshop on the INSPIRE Geoportal with MS admins of national catalogues to increase the availability of datasets.

• JRC to report about relevant outcomes from the Geoportal Workshop (especially the ongoing work on data-service linking)
  

• The date of next meeting will be communicated by the JRC.