1 / 19

Response Rate: 91% - 10 of 11 partners send questionnaire back 11 questionnaires were evaluated (2x METLA) 37 data sets

Explore the confusion and challenges surrounding data rights in the NEFIS project. Discuss public access, user IDs, data storage preferences, and obstacles to providing additional data. Collaboration demands for further improvements and efficiency.

chantrea
Download Presentation

Response Rate: 91% - 10 of 11 partners send questionnaire back 11 questionnaires were evaluated (2x METLA) 37 data sets

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Response Rate: 91% - 10 of 11 partners send questionnaire back 11 questionnaires were evaluated (2x METLA) 37 data sets (Question 1-8) The response rate per question varies between 89-100% Varity of data types: Aljoscha Requardt, University of Hamburg

  2. Why to talk about Data Rights? • some partners seem to be confused about data rights within NEFIS • “Data Rights”, does it concern the actual data? Should not all data presented in NEFIS be “public”? • some partners seem to be confused about the data rights management within their own institution • NEFIS tables are available for free. On the other hand, same information is part of the on-line system XXX, to which you have a restricted access (restricted-need to purchase). How should we handle this? Confusion... • Clarify Data Rights • within the NEFIS project • beyond the time of NEFIS project Aljoscha Requardt, University of Hamburg

  3. Do you provide public access to your data set? Of 37 data sets: 33 = public ; 4 = restricted Aljoscha Requardt, University of Hamburg

  4. For which type of user do you require a user ID and a password registration? Aljoscha Requardt, University of Hamburg

  5. If the data set is available for public…? If the data set is available to a restricted group of users…? Aljoscha Requardt, University of Hamburg

  6. Which of the "drop down" options (if any) are relevant to your data set? Are these “drop down“ options appropriate for your data set? Yes : 95% No : 5% Aljoscha Requardt, University of Hamburg

  7. Who is responsible for data access management? 37% "another„ = one partner (13 of 14 datasets) Aljoscha Requardt, University of Hamburg

  8. Which form of data storage do you prefer for your data set? Aljoscha Requardt, University of Hamburg

  9. To get further relevant data or raw data… • data which are published for public any how are available for free, any other statistics or • raw data would be provided at a cost • if the request for additional data is excessive and requires a lot of extra work data would • be provided at a cost • cost is for the work to select the data • further or raw data have to be requested to the main provider Aljoscha Requardt, University of Hamburg

  10. Would you like to provide more data within the NEFIS project? Aljoscha Requardt, University of Hamburg

  11. Are there any obstacles to provide additional data? Aljoscha Requardt, University of Hamburg

  12. Obstacles to provide additional data are: • staff resources available for NEFIS • permission of the government (main provider) will be needed • the format accepted in the visual tool kit is a limitation(providing data in Excel format requires a lot of time as data have to be extracted from a relational database) Aljoscha Requardt, University of Hamburg

  13. Demands for further cooperation: • the cooperation and further data provision are important for us in the future. The cooperation is appropriate in the current way • a definition of interface between NEFIS server and our “decentralized” data centre is needed. The question is: how shall we (technically) link our data-bank via internet to the visualisation toolkit? • data should reside on data providers server; data provider should be able to do own updates of both metadata and actual data at any point in time; data provider should be able to block access to data at any time; the overall system should be maintained by a designated unit who guarantee that the system is running continuously and properly… • more efficient links - provide a direct access to providers relational database; more user-friendly tools for metadata entry - please standardise the lists (like entry forms) • stable specification of input - i.e. not to many changes in the guidelines; easy update of information - either by submission of some files or online • increase the compatibility of the systems with existing data format; increase the standardisation requirements between national dataset • the data sets should be same as in national or international (for example FAO) reporting Aljoscha Requardt, University of Hamburg

  14. Demands for further cooperation: • production costs and available staff resources may be limiting factors. …there should be an agreement which kind of forest statistical data would be useful to be made available • …sometimes it could be difficult to have time and personnel to prepare data. It needs some extra money... • we need resources for this work (of course!) • we are more interested in the description of the data than the provision of them, because of some obstacles (need permission from the government) Aljoscha Requardt, University of Hamburg

  15. If data a stored on a central server (e.g. NEFIS Server), who is the custodian of … • the original data provider is the best option, as this organisation knows the datasets best. • …the authorised body who maintenance the server – like for moving, freshening of the provided data set, but without modifying of the data itself. Aljoscha Requardt, University of Hamburg

  16. If data are hosted on a centralised database, do you forsee problems with: Aljoscha Requardt, University of Hamburg

  17. Discussion Aljoscha Requardt, University of Hamburg

  18. I foresee problems with “stale” data and/or data redundancies, because… • …if data are stored on a central server, then the ‘responsibility’ is in some way distanced from the data provider… therefore data providers should be encouraged to host the data for exactly this reason. • …data updating may be regarded only through direct access to providers database, yet to be implemented. • …at the moment no standards are developed, e.g.: administrative boundaries. Stale and redundancies problems are not relevant at the moment within the NEFIS project but could became relevant in an operational systems. • …it's additional work for the data provider and if they already are making data available on national homepage, this will be extra work. • …some data have more than one source, and most of them have their own system of dissemination and the present actualisation process does not include the actualisation in the central “NEFIS” database. Aljoscha Requardt, University of Hamburg

  19. I do not foresee problems with stale data and/or data redundancies, because… • …with a right regulation and cooperation the problems could be avoided. • In principle, there needs to be a central institution with the responsibility for connecting the decentralized data. This central body can easily check and avoid redundancies between the central and decentralized servers. The main “problem” will be the technical know-how at the decentralized centres. I do foresee problems to some extent • The idea of an European Forest Information System is based on the principle of distributed databases. That allows the data provider to be in control of both metadata and data….by this way problems like “stale” data and/or data redundancies will not occur and if they do it is in the responsibility of the data provider. Aljoscha Requardt, University of Hamburg

More Related