{"action":"created","issue":{"url":"https://api.github.com/repos/eForms/eForms/issues/199","repository_url":"https://api.github.com/repos/eForms/eForms","labels_url":"https://api.github.com/repos/eForms/eForms/issues/199/labels{/name}","comments_url":"https://api.github.com/repos/eForms/eForms/issues/199/comments","events_url":"https://api.github.com/repos/eForms/eForms/issues/199/events","html_url":"https://github.com/eForms/eForms/issues/199","id":367187611,"node_id":"MDU6SXNzdWUzNjcxODc2MTE=","number":199,"title":"BT_All eforms / Simplification - Data collection","user":{"login":"GReaadhsy","id":43879085,"node_id":"MDQ6VXNlcjQzODc5MDg1","avatar_url":"https://avatars1.githubusercontent.com/u/43879085?v=4","gravatar_id":"","url":"https://api.github.com/users/GReaadhsy","html_url":"https://github.com/GReaadhsy","followers_url":"https://api.github.com/users/GReaadhsy/followers","following_url":"https://api.github.com/users/GReaadhsy/following{/other_user}","gists_url":"https://api.github.com/users/GReaadhsy/gists{/gist_id}","starred_url":"https://api.github.com/users/GReaadhsy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/GReaadhsy/subscriptions","organizations_url":"https://api.github.com/users/GReaadhsy/orgs","repos_url":"https://api.github.com/users/GReaadhsy/repos","events_url":"https://api.github.com/users/GReaadhsy/events{/privacy}","received_events_url":"https://api.github.com/users/GReaadhsy/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-10-05T12:22:52Z","updated_at":"2018-10-12T16:43:46Z","closed_at":null,"author_association":"NONE","body":"We would like to stress out that the purposes of data collection / simplification / ensuring data quality, as depicted in the explanatory note, are rather contradictory concepts. Especially as far as simplification concerns, we understand that such a concept should go into the direction of reducing the number of fields as well as minimizing the amount and complexity of the content for each eForm to the absolute minimum information required for eNotification. On the other hand, the need of (additional) data collection having in mind statistical evaluation or monitoring key/performance indicators is contradicting this purpose directly, since this requires new additional and/or more complex fields. In addition, judging from experience derived from our national eNotification system, which is being used in Greece for several different purposes, like  eNotification and special transparency policy and statistics on public procurement:\r\n• data and/or data quality for voluntary or non-mandatory fields, is non-existent or poor\r\n• data quality decreases rapidly with the increase of data fields and/or its complexity\r\n\r\nIf the purpose of SIMAP is to be shifted, besides eNotification, towards statistics or monitoring key/performance indicators on public procurement, and having in mind the member states’ obligation to provide statistical data/reports on public procurement, it might be worth to consider a “unification” of these processes in order to decrease administrative burden. \r\n\r\nFinally, we consider ESPD and eForms should definitely be linked, so that the same information are filled automatically from ESPD to eForms and vice versa, minimizing that way the administrative burden."},"comment":{"url":"https://api.github.com/repos/eForms/eForms/issues/comments/429388165","html_url":"https://github.com/eForms/eForms/issues/199#issuecomment-429388165","issue_url":"https://api.github.com/repos/eForms/eForms/issues/199","id":429388165,"node_id":"MDEyOklzc3VlQ29tbWVudDQyOTM4ODE2NQ==","user":{"login":"JachymHercher","id":22431403,"node_id":"MDQ6VXNlcjIyNDMxNDAz","avatar_url":"https://avatars0.githubusercontent.com/u/22431403?v=4","gravatar_id":"","url":"https://api.github.com/users/JachymHercher","html_url":"https://github.com/JachymHercher","followers_url":"https://api.github.com/users/JachymHercher/followers","following_url":"https://api.github.com/users/JachymHercher/following{/other_user}","gists_url":"https://api.github.com/users/JachymHercher/gists{/gist_id}","starred_url":"https://api.github.com/users/JachymHercher/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/JachymHercher/subscriptions","organizations_url":"https://api.github.com/users/JachymHercher/orgs","repos_url":"https://api.github.com/users/JachymHercher/repos","events_url":"https://api.github.com/users/JachymHercher/events{/privacy}","received_events_url":"https://api.github.com/users/JachymHercher/received_events","type":"User","site_admin":false},"created_at":"2018-10-12T16:43:46Z","updated_at":"2018-10-12T16:43:46Z","author_association":"NONE","body":"Thank you for the comments, we understand your point. Nevertheless, while we agree that sometimes the concepts may be contradictory, we would say that usually they are not. For example, looking at the improvements listed in the explanatory note, most seem to lead to better data quality as well as simplify the life of users (e.g. having clear definitions; harmonizing definitions and data structures; giving flexibility on labels;  harmonizing with the ESPD).  \r\n\r\nConcerning purely statistical and monitoring fields, where the trade-off indeed exists, we are not sure that there are too many. Essentially, these are only the BTs on GPA and the clean vehicles directive in BG-710 and BT-706 (Winner Parent Country). (Arguably, the fields on the number of bids and some information about the buyer and seller fall within this category as well, but those are prescribed by the directive anyway.) Do you consider more BTs as falling into this category? \r\n\r\nWe agree that optional compliance is low and that more data leads to less quality. To deal with the former, we propose a strict alignment between legally mandatory and technically mandatory fields and we recommend making optional fields mandatory at national level for those countries which consider the information relevant. To deal with the latter, we emphasize the need to prefill fields on behalf of users as much as possible in the e-tendering systems themselves (see e.g. #9, #163)). \r\n\r\nYes, this is the case, it will be possible to publish ESPD as part of the eForms, thus replacing the corresponding BTs (see #195). \r\n\r\n\r\n"}}
{"actor":{"display_login":"JachymHercher"}}