Presentation on theme: "Intro The Evaluation of the NEFIS Project focused on: Metadata"— Presentation transcript:
1 IntroThe Evaluation of the NEFIS Project focused on:MetadataData Rights and Data Rights ManagementUser Needs and User Expectations - VTK
2 Evaluation based on two approaches: IntroEvaluation based on two approaches:Standardised questionnairesmetadata and metadata guidelinesdata rights and data rights managementuser needs and user expectations - VTKExpert Statementsmetadata and metadata guidelinesProf. Dr. Keith Rennolls (Greenwich), Dr. Jarmo Saarikko (Metla)keyword list and thesaurusRenate Prüller (IUFRO), Gillian Petrokofsky (CAB International)data rights and data rights managementAndreas Schuck (EFI), Tim Green (EFI)EFIS – an electronic system for periodic reportingProf. Dr. Michael Köhl (UHH), Aljoscha Requardt (UHH)
3 Metadata Evaluation Metadata 1. Elaboration of metadata records a step-wise iterative process- preliminary records according previous schema- metadata schema developed further to its final version (D3, D5)- revise preliminary records make adjustments according new schema2. Questionnaire “Metadata and Metadata Guidelines”- evaluate experienced applicability and usability3. Questionnaire results represented and discussed at the Hamburg MeetingExpert Statements- metadata and metadata guidelines- keyword list and thesaurusEvaluation Metadata
4 Metadata Questionnaire “Metadata and Metadata Guidelines” Knowledge and experiences of the respondentWorkloadMetadata GuidelinesNEFIS Metadata SchemaSpecific Metadata Elements and RefinementsMetadata Functionality and StructureFuture Perspectives
5 MetadataGeneralAre the NEFIS metadata the first contact you have had with metadata?79% YesPartners knowledge and experience of elaborating metadataPartners knowledge and experience using metadata for data source retrieval
6 Time Investment - most partners between 5-10 hours in total MetadataWorkloadDo you consider the workload to enter metadata records as:Level of complexity to prepare and enter metadata:71% = acceptable29% = complexTime Investment - most partners between 5-10 hours in total
7 Metadata Guidelines Are the guidelines easy to understand? Would a metadata tutorial or training course be helpful and appropriate?71% Yes
12 Metadata Specific Issues Type Format Coverage Quality Report Subject DatasetGeoreferencedFormatReference System - encoding scheme for georeferenced dataCoveragePoint / Box encoding schemeQuality ReportSubjectAudience
13 Metadata Quality Report "Quality" addressed within DCMI elements, refinements and encoding schemes?Named elements which address “Quality” within the DCMI schema:Creator, Description, Publisher, Coverage, Source, Date, Audience
14 Metadata Quality Report Relative value of a “Quality Report“ “Quality Report“ under the element “Descriptions“?
15 Metadata Quality Report Value of listed options to describe and structure “Quality Report"
16 Metadata Quality Report Value of quantitative measures of quality (standard error, sample size, sampling unit, resampling for measurement control)Which of these quantitative measures are relevant and appropriate for which type of data?it could become very complicated and time consuming to collect such information in a standardised way.
17 MetadataSubjectCan the dataset be appropriately described by using the NEFIS terms?sometimes difficult to group the term under a themevery time consuming to go through the lists … more structure/ hierarchy would be helpful.
18 Metadata Subject How important is the option to add "Nominated Terms" it is the way to improve the term listsvery important during the development phase…it allows the provider to demonstrate which additional terms are seen necessary to describe the particular resource more accurately
20 MetadataConclusionObstacles within the challenging tasks as the development of keyword lists as well as the quality report could have been clearly reflected by the results of the metadata evaluationSubject, Description and Format caused problems for most partnerslow experience by some partnerscomplicated structure and defined proceduresNEFIS metadata schema is applicable in its current formfrom the perspective as a data provider – dataset documentationfrom the perspective as a data user – data resource retrieval
21 Data RightsData provider has to state what data are accessible and for whom, and which type of data rights and which levels of access should be assigned to which kind of data.Data provider should have options to assign different levels of access to individual datasets in order to protect sensitive data by restricting access to them.Prerequisite to guarantee that legal restrictions to data access will be satisfied
22 Data Rights Why to talk about Data Rights? Data rights provoked several discussions“Data Rights”, does it concern the actual data? Should not all data presented in NEFIS be “public”?NEFIS tables are available for free. On the other hand, same information is part of an on-line system to which you have a restricted access. How should we handle this?Clarify Data Rightswithin the NEFIS projectbeyond the time of NEFIS project
23 Data RightsWhich of the "drop down" options (if any) are relevant to your data set?Are these “drop down“ options appropriate for your data set?95% YesBut option “Public” needs further refinements
24 Data Rights Who is responsible for data access management? Which form of data storage do you prefer for your data set?
25 Data Rights Would you like to provide more data? Are there any obstacles to provide additional data?cost for the provider !cost for the usertechnical limitationsunclear data rights management
26 Data RightsPartners demands for further cooperation and data provisionTechnical demands and demands on data managementlink data easily to the system without complicating and restricting data management and maintenanceclear definitions and standards for data format and data contentFinancial demandscapacities for time and personnel investments
27 User Needs and User Expectations - VTK 1. VTK Workshop2. anonymous comments by partners regarding VTK display and analysis options3. Test CD4. Questionnaire “User Needs and User Expectations”5. Expert Statement (UHH) “EFIS - an electronic system for periodic reporting”Evaluation „VTK & Information needs“
28 User Needs and User Expectations - VTK Questionnaire “User Needs and User Expectations”The respondetUsabilityPerformancesVTK featuresTutorial and Help FunctionsImprovementsFuture Potential
29 User Needs and User Expectations - VTK The respondetA - familiar with the NEFIS project and the provided datasetB - only familiar with the provided dataset itselfC - someone who is not familiar with the NEFIS project and the provided dataset,but has some broad knowledge in using GIS applications and statistical programsQuestionnaire evaluated according:TotalGIS KnowledgeStatistical knowledge19 answered questionnairesExpirences of useing the VTK = average / less than averageRespondent spent 7 hours using the VTK (5 hours for one explicit dataset)
30 User Needs and User Expectations - VTK How easy is it to find applicable and reasonable functions to analyse and visualise data which are of explicit interest?functions are atractive but it is not easy to find out how to use them and select the one that is neededVTK examples are an important addition to get a more transparant view which of the features are useful for which kind of analysis
31 User Needs and User Expectations - VTK Respondent meaning about the VTK menuthe menu should be developed more simple and informativesome better “getting started directions” would be very helpful (essential even).
32 User Needs and User Expectations - VTK The VTK incorporates automated map designthe produced maps are interactive, including traditional GIS interactivity and visual manipulationsoutputs are available as data tables and thematic maps with different techniques for selected geographical areait allows production of statistical graphics (box plots, dot plots, scatter plots, etc.) that are dynamically linked to mapsThis could imply that expert knowledge on cartography or GIS is not requirednot necessariliy knowledge in GIS but some knowledge in cartography and data presentationthe user should be familiar with the data itself
33 User Needs and User Expectations - VTK Consideration of options to analyse available datasetsConsideration of options to visualise available datasets
34 User Needs and User Expectations - VTK Ability to recall explicit information from displayed formatsMapped dataData plotsTabular datahighFiguressatisfactoryUnitsunsatisfactoryLack in the actual dataset itself !!!
35 User Needs and User Expectations - VTK VTK offers many features, tools and options to analyse and to visualise datathe feature should be applicable to the datasetthe user should understand meaning and relevance of the featurethe user should be able to recall relevant information after using a suitable featurethe appearance of the outputs should be satisfactory for the userno essential functionality in that feature should be missing
37 User Needs and User Expectations - VTK Most respondents considered all listed applications as important or as interestingbut the respondent was not always able to test some explicit applications, mainly due to the lack of help functions and tutorial documentsfurther tutorial documents and help functions can be seen as a useful and important asset !
38 User Needs and User Expectations - VTK Time investment to understand and use VTK featureshighComplexitiy to understand available VTK featureshighSuggestion:Develop a set of tutorial tailored at different user groups and level of expertise
39 User Needs and User Expectations - VTK Reduce the set of VTK features or Add new features ???Suggestion:Develop a VTK for two different groups of usersBasic Version – new usersAdvanced Version – experienced usersKey: User Friendliness- improved interfaces- improved maneuvering through features- improved guidance for getting startedIncorporating too many purposes into one system component will logically lead to the consequence of not being able to meet all these demands. Therefore it is reasonable to differentiate the use but also the applications of the system.Reportingreporting schemesreporting query options
40 User Needs and User Expectations - VTK VTK functional and applicable for your purposes as a data provider?
41 User Needs and User Expectations - VTK User Backgrounds and Expectations are differentSimplified self explanatory output featuresClearly structured user guidelinesEasy to follow help functionsDefine the purposes of the system – Who are the potential users?Differentiate the use and applicationsReporting most important purpose- guarantee that VTK outputs not ambiguous in their statement- contact data user – data providerAlthough some applications could be developed further or improved, the VTK and its features provide a solid basis to meet various tasks of a full working EFIS.
Your consent to our cookies if you continue to use this website.