• Initial proposals provided by the participants were gathered for later discussion in the 'Input/feedback session'

• Initial proposals provided by the participants were gathered for later discussion in the 'Input/feedback session'
• The feedback is summarised in the table below. Mainly bugs and new features have emerged

• JRC presented the Re3gistry improvement proposals submitted before the meeting. Similar or related proposals were grouped where applicable
• Every participant was asked to rank his/her 5 top proposals out of the overall possibilities
• The most voted proposals were:

  1. Provide support for linked data (16 votes)

  2. Improve filtering/search functionality in the user interface (13 votes)

  3. Improve the search engine to enable searching remote INSPIRE central registers from a “local” registry (9 votes)

  4. Enable a search history function to navigate across the item changes (9 votes)

  5. Provide support for additional formats to enhance interoperability, e.g. compliant SKOS/XML (8 votes)

  6. Provide a syndication service to notify changes in contents and/or functionalities (8 votes)

  7. Provide additional visualization modes, e.g. a hierarchical tree view (collapsible menus) for hierarchical registers, and an alphabetical index (glossary); suitable/suggested tools are WebVOWL and owlviz (8 votes)

  8. Provide a REST API for machine-readable access, filter & read actions (7 votes)

  9. Provide image field type support (7 votes)

  10. Store developed register types as templates in order to use them to create new registers (7 votes)

  11. Implement a web based import tool, allowing a preview of the content (for each new entry/change, create a dump of the current content) (7 votes)

• JRC to document the submitted improvement proposals on Github (using this template) and provide an estimation of the resources that those would imply

• Decision: The RoR application will not be published officially for the time being, since not many countries are sharing or planning to share their code lists in it yet. Testing and experiments will continue in the current sandbox at http://inspire-regadmin.jrc.ec.europa.eu/ror
• JRC should investigate how to integrate the RoR within the INSPIRE registry (e.g. showing in INSPIRE empty code lists types a link to the available values coming from other sources)

• JRC to double-check if SKOS/RDF format could act the federation format (instead of RoR specification)

• JRC to rediscuss with EEA how to align their vocabularies

• ELISE funding is available for the Re3gistry development for at least next year.
• Member States could contribute to the funding. AT, IT, FI might be interested.
• Decision: A steering group will not be set for the time being

• JRC to create a mailing list for stakeholders and general announcements
• JRC to set up the Github space (https://github.com/ec-jrc/re3gistry) for collecting requirements, feature proposal and sharing roadmaps for next releases

• Web-conferences will be set on request/on needs based
• Webinars should be organised to present the new versions, features, etc. These could be done also at physical events such as the INSPIRE Conference, FOSS4G, ISA2, etc.
• A 'Feedback button' should be included directly in the INSPIRE Registry website.

• Action JRC: To ask the IT services if the code can be shared although still in development

• SK suggests to investigate commonalities and possible synergies between the development of the validator, geoportal and the registry

• I want only changed field be highlighted (e.g. linked data are also highlighted)

• I want timestamp (visible information about time of action/decision)

• Possibilities to see a preview of changes (AT)

• Nice to have possibility to write some notes about reason for specific single action (e.g retired, invalid). But it is possible to put it in control body change log.

• I want to have for new added field  the mandatory icon * that currently is missing (required field)

• I want to have the date type content (date field with calendar instead of text field mask)

• Nice to have online help, examples, Guidance’s e.g. difference between definition and description (HR)

• I want to receive e-mail notifications when the CB approves/rejects a proposal

• Under the Structure tab, when adding a field, the 'Save' button should be placed under the bar, instead of being next to the bar and having the button 'Create new field' under the bar. By instinct, after creating a field we click the button 'Create a new field' instead of the button 'Save'.

• Check which fields are mandatory, sometimes it was noticed that the asterisk icon is not shown;

• Check which fields are mandatory, when leaving some mandatory fields blank (e.g. the Description), we can save the page as well (this should not happen).

I want to have a help button to provide explanations or hints on how to fill the different fields (sometimes this is difficult to understand) → same as 7

• I want to change the labels of the tabs 'Submitting Organizations', 'Control Body' and 'Registry Manager', which are currently not explaining what can be done under these tabs (they can be changes into something like 'Dashboard' or 'Actions').

• I want to see the breadcrumbs so that I see where I am in the workflow

• I want to have some indications on the order of the action to complete for the submission so that I can follow the workflow correctly

• I want to import the code-list information (e.g. CSV) so that I can have some kind of bulk import feature

• I want to have a popup as remainder/shortcut so that I can easily send/submit the changes

I want to receive an email notification/report so that I will know the current status and pending/awaiting proposals → same as 8

• I want the Back button so that I see the status/progress of the workflow

• I want to see the registry partial URL next to the input text field

• I want to see a Save button in the Structure tab so that I know how & when it saves

• I want to have a better tooltip/clue on how to order fields and visibility (instead of a simple four arrows cursor when hovering)

• I want to see the application fields/labels translated in the selected language (top-right)

• I want browsers compatibility & support (IE, Firefox, Chrome) so that I can use a modern browser without issues

• I want to see clearly under which role the user is logged in