Skip to content

A series of recommendations will be formulated based on the experience gained in activities 1 through 3. The recommendations will be presented to and discussed with stakeholders and the broader open data community with the aim of presenting both the recommendations and feedback in a report.

Notifications You must be signed in to change notification settings

gopeg/issues-barriers

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

14 Commits
 
 

Repository files navigation

Issues and barriers of the GO-PEG use cases

This repository gathers issues faced and barriers encountered during the processes of data collection, data harmonisation and data publication of the GO-PEG data sets.

Collected information will be used to formulate a series of recommendations (based on the experience gained in project activities 1 through 3) that will be presented to and discussed with the stakeholders and the broader open data community.

Both the recommendations and feedback will be duly documented in a report.

Use the issue tracker to report problem faced with:

  • data harmonisation (e.g., data models development, vocabularies, source data content, data transformation tools)
  • service deployment (setup of web services / APIs for the data sharing)
  • data and/or metadata publication
  • license conditions
  • data usability (to what extent can the new data sets and services be used in mainstream tools / to what extent do they meet the user needs?)

How to report an issue

Use the labels from drop down menu to further categorise the issue and allow querying the repository content, and also indicate the affected use cases.

At least one issue category label must be provided!

Issue Category Labels

  • data harmonisation
  • service deployment
  • data publication
  • metadata publication
  • license conditions
  • data usability
  • data collection
  • stakeholder involvement

Optional Labels:

  • APIs
  • data model
  • vocabularies / semantics
  • license conditions

How to document solutions

Solutions tried shall be posted as comments to the issues. Once the issue is successfully solved, and the solution duly described, the issue shall be closed

About

A series of recommendations will be formulated based on the experience gained in activities 1 through 3. The recommendations will be presented to and discussed with stakeholders and the broader open data community with the aim of presenting both the recommendations and feedback in a report.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published