1. Action 1 Tomas Kliment 3:00 – 4:30pm
EnvEurope metadata management tool for dataset level metadata – introduction and initial hands-on exercise
Action 1
Tomas Kliment
3:00 – 4:30pm
ENVEurope coordination/QA/QC/ and technical meetings
Ramada majestic Bucharest hotel
15-18/ , Bucharest, Romania, EU

2. Outlines Short intro ~ 10min Let's get dirty with the stuff ~ 50min
where we were in March 2011?
where we’re now?
where we would like to go?
Let's get dirty with the stuff ~ 50min
hands on exercise
Summary & discussions ~ 30min
Proposals, recommendations, criticisms

3. Where we were in March 2011? Group 1 Group 2 we talked about metadata
we talked about EML specification
we tried to define the MD structure for data discovery, evaluation and use
Group 1
Group 2

4. Where we’re now?
EnvEurope (LTER-Europe) Metadata Specification for Dataset Level Draft v3.0
Specification contains introduction parts (Overview, Terms, Definitions, Symbols) the main part containing the MD specification, detail information about each metadata element defined to be included within the md spec. EnvEurope MD crosswalk to INSPIRE ISO metadata and examples of XML sample metadata records and XSLT transformation file.

5. Where we’re now?
XSLT Transformation of EML dataset module to ISO (INSPIRE)

6. Where we’re now? EnvEurope Geocatalogue development
adapted from First official release of the Drupal Metadata Editor® (US LTER)
The adaptation of existing MD tool phase has been started thanks to our US LTER colleagues, who have provided for us the instance of their First official release of the Drupal Metadata Editor - This instance contains the latest suite of tools to manage the information associated with a research site, including forms to capture metadata and export it as EML and BDP.

7. Where we’d like to go? 1 1a 1b 2 3

8. Let’s get started – hands on exercise
Create “n” groups (max 12 possible now)
Try to describe one dataset from your group using EnvEurope (LTER-Europe) metadata editor
Save you record and comment each MD element accordingly your findings, problems, criticisms, anything appeared during your work
Try to search for your record using discovery client

9. Feedback on the metadata editor General comments
“Great work!” 
“First common tool for the entire group of stakeholders” 
This tool would really be a step forward 
Continuous storage during the filling of the form is needed
Technical interoperability for Internet Explorer is needed
Option to create a template for particular dataset in order to get filled common fields (Creator, BBOX .. ) for more MD records would be helpful
Default appearance of text entry field type should appear only 1 field also for multiple fields
Add PDF Print out possibility
Add button to delete item by mistake – similar to existing add another item

10. Feedback for the metadata editor General comments
The error list should provide links to particular elements
Go back button within the web browser brought loss of data; data cache is needed
Ensure minimum level of multiple work within the metadata collection (Dataset, Site level and even monitoring data)
Keyword part – to be unified – EnvThes desperately needed
Still too much freedom for filling (i.e. Code)
Autocomplete function for responsible party information – refers also to template creation function
Separate button for validation and save

11. Feedback for the metadata editor comments for individual elements
Group2-campale
3. Dataset creator – organization name acronym to be used as an acronym or full name
9. DS keyword set - EnvThes
13. DS BBOX – field for manual insertion of coordinates is required
Group4-carrpao
2. Dataset identifier – missing site code of filling AB site;
12. Dataset online distribution – DS isn’t online accessible, what to fill then?
18. Dataset methods – not possible to delete value selected by mistake from the list
19. Dataset instrumentation – to detailed request

12. Feedback for the metadata editor comments for individual elements
Group6-diazric
2. DS identifier – site code has to be an unique code; What codeSpace mean?
9. DS KeywordSet – what level is saved within the tree, fill automately root terms;
10. DS access and use constraints – who are other?
11. DS Intellectual rights – text to write other IPR
13. BBOX – functionality to delete feature
18. DS Methods – list to be excluded
Group7-mattgio
2. DS Identifier – Site code unification
7. DS language – here should be clarified within the field description that this refers to natural language used in column heading and values (parameter names)
9. DS Keyword set – it’s a mess needs desperately common vocabulary EnvThes

13. Feedback for the metadata editor comments for individual elements
Group8 – bascmar
1. Dataset title: be more precise about what we are supposed to write (include any keywords like "terrestrial" or others) in order for the dataset to be found easily
9. Dataset keyword set: It should be stated that one can stop everywhere down the tree
14. Dataset geographic bounding altitudes or depths: unit of measurement should be stated
Group10 – petejoh
2. Dataset identifier – setting identifier (code) automatically.
9. Dataset keyword set – might be shortened
14. Dataset geographic bounding altitudes or depths – depth should be excluded due it’s possible appearance in methods
18. Dataset method description – description is the most valuable part and should be written as scientific paper and minimum length of text fields should be set.
19&20 should be merged within 18 DS Methods description as its part

14. Feedback for the metadata editor comments for individual elements
Group11 – frenmar
1. Dataset identifier – use name of the site instead of code, for code define a rules how to create it; codeSpace is not clear what does it mean
3. Dataset creator – show only one field; add another item to be changed to add another item
4. Metadata provider – often the same as 3 therefore should be filled automatically if so
9. Keyword set – it is quite mass currently
13. BBOX – explanation how to draw rectangle and where coordinates are appeared
20. Sampling description - sampling frequency – should be established a list within EnvThes

15. Feedback for the metadata editor comments for individual elements
Group12 – mirtmic
2. Dataset identifier – LTER code list has to be provided name of the site; Add option to add another site, Reference to infobase; CodeSpace isn’t understandable
3. DS contact – it’s strangely organized
10. DS Access rules - very strange and complicated wording; much simpler: “Potential user groups and their access options”
11. DS Intellectual rights - complicated list, ev. too many entries; Can they be grouped;Did not work when storing: whatever was clicked gave a “illegal value”
13. DS BBOX – does not work in IE, Coordinates are not visible
20. Sampling description – units should be included, sampling frequency should not be select list; Allow for 1) minutes and the 2) number of minutes (applicable to hours, days, years....)

16. Thank you very much for your effort! tomas.kliment@gmail.com