Comparative summary of feedback interaction processes across five European open data portals
| Step no. | Step description | Estonia | Luxembourg | Poland | Sweden | Spain |
|---|---|---|---|---|---|---|
| 1 | Define the Feedback Message | Specific questions or dataset concerns | Case-by-case; format, access, updates | Dataset comments, new data requests | Data requests, API issues | Dataset comments, new initiatives |
| 2 | Sending the Message | Email, forum, rating | Email, forums, favourite/reuse marking | Surveys, feedback forms, email | Interactive dashboard, comment threads | Feedback/request forms |
| 3 | Broadcast to other users | Not applicable | Forum only | Not applicable | Public community forum | Public comments, social media |
| 4 | Read the Message | Admins assess issues | Technical team collaborates with data producers | Team and officers assess feedback | Team and community members read and engage | Admins and responsible bodies review |
| 5 | Publish the Message | Not usually published | Managed internally, not published | Not public | Immediately published in threads | Visible on dataset pages |
| 6 | Classify the Message | By theme (e.g. errors) | Not formally classified | No specific methods | Eleven predefined topics | Categorized (e.g. incidents, data requests, use cases) |
| 7 | Action on the Portal | Focus on portal usability | Mostly accessibility, scalability improvements | Steps to improve data quality | Some feedback leads to portal improvements | Incident handling, platform improvements |
| 8 | Statistics Count | User star ratings updated | Favourite/reuse counts updated | Not applicable | Tracks posts and participants by topic | Likes updated and shown |
| 9 | Publish Use Case | Sometimes use cases are generated | Not indicated | Benchmarking with other portals | Not explicitly published | Successful use cases shown publicly |
| 10 | Action on the Dataset | Dataset corrections based on feedback | Mostly format and update issues | Data quality improvements | Dataset actions arise from discussion | Dataset requests relayed to providers |
| 11 | Report to the User | Private reports, ratings are public | Not systematically reported | No mention of response | Transparent, real-time discussions | Public responses or private follow-ups depending on type |
| Step no. | Step description | Estonia | Luxembourg | Poland | Sweden | Spain |
|---|---|---|---|---|---|---|
| 1 | Define the Feedback Message | Specific questions or dataset concerns | Case-by-case; format, access, updates | Dataset comments, new data requests | Data requests, API issues | Dataset comments, new initiatives |
| 2 | Sending the Message | Email, forum, rating | Email, forums, favourite/reuse marking | Surveys, feedback forms, email | Interactive dashboard, comment threads | Feedback/request forms |
| 3 | Broadcast to other users | Not applicable | Forum only | Not applicable | Public community forum | Public comments, social media |
| 4 | Read the Message | Admins assess issues | Technical team collaborates with data producers | Team and officers assess feedback | Team and community members read and engage | Admins and responsible bodies review |
| 5 | Publish the Message | Not usually published | Managed internally, not published | Not public | Immediately published in threads | Visible on dataset pages |
| 6 | Classify the Message | By theme (e.g. errors) | Not formally classified | No specific methods | Eleven predefined topics | Categorized (e.g. incidents, data requests, use cases) |
| 7 | Action on the Portal | Focus on portal usability | Mostly accessibility, scalability improvements | Steps to improve data quality | Some feedback leads to portal improvements | Incident handling, platform improvements |
| 8 | Statistics Count | User star ratings updated | Favourite/reuse counts updated | Not applicable | Tracks posts and participants by topic | Likes updated and shown |
| 9 | Publish Use Case | Sometimes use cases are generated | Not indicated | Benchmarking with other portals | Not explicitly published | Successful use cases shown publicly |
| 10 | Action on the Dataset | Dataset corrections based on feedback | Mostly format and update issues | Data quality improvements | Dataset actions arise from discussion | Dataset requests relayed to providers |
| 11 | Report to the User | Private reports, ratings are public | Not systematically reported | No mention of response | Transparent, real-time discussions | Public responses or private follow-ups depending on type |