EERAdata Wiki - User contributions [en]

Main Page

2024-07-04T11:46:13Z

Manfred: /* Join and collaborate interactively! */

Welcome to the EERAdata MediaWiki!

== The project EERAdata ==

'''Towards a FAIR and open data ecosystem in the low carbon energy research community.''' Transparent, re-usable, and integrated energy data enable society to choose, monitor, and implement sustainable transition pathways. It is not only a prerequisite for people to have ownership over the changes, but it is also offering huge potential for industrial and social innovation. The majority of energy databases are not fit for this purpose, which the project aims to change. The consortium develops, tests, and implements a [[FAIR_guiding_principles|FAIR]] and open data ecosystem in the energy field. FAIR stands for F-findable, A-accessible, I-interoperable, and R-re-usable. The EU-funded EERAdata project builds a pool of data stewards to guide the community towards fit-for-purpose data practices.

'''EERAdata logo and key visual'''. The elements of the logo include ''data points'' - symbolizing databases or data platforms - and a ''data folder'' which are connected through the ''feed symbol''. All stand for the idea of EERAdata to support FAIR and open data. The folder furthermore is a nostalgic reminder of the grand library catalogs to search for books, all of them are masterpieces on their own. [[File:EERAdata_key_visual.png|thumb|Key visual of EERAdata]]

The project is funded by [https://cordis.europa.eu/project/id/883823 Europa's Horizon 2020 Research Program].
[[File:Co-funded.png|thumb|The project is funded by the European Union, Horizon 2020 Programme]]

=== Website ===
The website is here: https://www.eeradata.eu/

=== Timeline ===
Here we report when we did what to implement EERAdata. Workshops, meetings to build a FAIR/O community for energy data, etc. [[Timeline|Timeline]]

=== EERAdata & Arts ===
The artist Barbara Bellier from Clairmont-Ferrand in France joined our workshops to illustrate the discussions. With her beautiful art, she lifted our spirit when discussions became tough and problems seemed too huge for our small project. Many thanks for your manifold inspirations!

[[File:Business card Barbara.jpg|thumb|The artist's footprint: barbara.bllr@gmail.com.]]

See the [[WS1#WS1_through_the_lense_of_an_artist|gallery from workshop 1]].

See the [[WS2_through_the_lense_of_an_artist|gallery from workshop 2]].

== Join and collaborate interactively! ==
The workshop is a hackathon! EERAdata is evolving jointly only! Join the discussions and work together online:
* [[Main_Page#Getting_started_with_EERAdata_wiki|EERAdata WIKI]]
* [[WS1#EERAdata_story_board|EERAdata storyboard]]
* [https://github.com/valeria6856/EERAdata EERAdata@github]
* [https://www.researchgate.net/project/Towards-a-FAIR-and-open-data-ecosystem-in-the-low-carbon-energy-research-community EERAdata@ResearchGate]

=== EERAdata story board ===
'''Objective:''' collect views from participants regarding energy data, energy metadata, FAIR/O problems etc. to support discussions, identification of gaps & needs (WP2) and elements to design the platform (WP3).

'''Questions:'''
* Q#1: What is your user story regarding FAIR/O energy data?
* Q#2: What is your user story regarding metadata?

Template to answer: As a <stakeholder>, I want <goal> so that <reason>.

'''How to post a story?'''
# Click on the link: https://padlet.com/janaschwanitz/aciywzt9fs1h70m2
# Click on plus at the right bottom to add a story.
# Choose a title depending on the question you want to answer. Choose for Q#1: FAIR/O data, or for Q#2: metadata. In the example above, the title “metadata” was chosen.
# Type your sentence to let us know where the gaps and hopes are: The template is: As a <stakeholder>, I want <goal> so that <reason>.

'''Example:''' As a data-driven energy researcher, I want utopia - i.e. one-stop access to all relevant metadata -, so that I can browse available data, check where they are from and whether I can trust them when reusing.

'''How to comment a story?'''
* One can rate stories by clicking on a number of stars.
* One can comment stories as well as comments with words.
* It is anonymous commenting and adding of stories, as long as one does not login into one's personal profile at padlet.com.

=== EERAdata wiki - How to? ===

The easiest way is you simply start writing and editing. You can install an easy editor by doing what is described on the picture to the right.
[[File:Install easy editor.png|thumb|How to install an easy editor]]

Temporarily login for guests:
* user name: guest, pwd: guest2020
Login for EERAdata consortium members:
* user name: <your_first_name+firstletter_of_your_last_name>, e.g., ''valerias''
* pwd: sent seperately to each of you individually

Here is also additional (advanced) documentation on DOKUWIKI which you might want to consult:
Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]

=== EERAdata on github ===
Link here and share your thoughts and issues! Note, work in progress.
* [https://github.com/valeria6856/EERAdata EERAdata@github]

=== Just have fun! ===
==== Metadata memory game ====
This is a little memory game where players need to identify triples. They will learn about metadata. A triple describes an example of metadata used in low carbon energy. Different formats, file types, and descriptions are introduced.
[https://eeradata-platform.eu/memory/memory_3plus.html '''Link''']

== List of project partners ==
#[https://www.hvl.no/en/ HVL - Western Norway University of Applied Sciences]
#[https://www.ieu.edu.tr/en IUE - Izmir University of Economics]
#[https://www.ait.ac.at/ AIT - Austrian Institute of Technology]
#[https://www.gig.eu/en GIG - Central Mining Institute]
#[https://www.eera-set.eu/ EERA - European Energy Research Alliance]
#[https://www.enea.it/ ENEA - Italian National Agency for New Technologies, Energy and Sustainable Economic Development]

== Use cases in EERAdata ==
'''Definition:''' Use cases are an exercise for testing and refining the general approach towards FAIRification and opening of databases as well as to testing and refining the community platform. Use cases constitute practical commitments for implementation (PCI), i.e. the FAIRification and opening of data. Through exercises, the status quo of FAIR/O data principles in each use case is advanced by:

*Identifying taxonometric elements and metadata common among different domains of the energy system. Proper metadata will enable separating expert knowledge (and expert interest) from general knowledge and general interest, allowing coarse-grained and fine-grained navigation.
*Linking these metadata standards to existing metadata standards in other domains. Example: Weather-related data are integral to the efficient operation of PV, wind technology, or district heating. The assignment of geo-tagged information to low carbon energy technology data is thus the way forward. EERAdata will link energy domain metadata with metadata defined by ISO 19115 Geographic Metadata Information.
*Exploring a variety of challenges towards FAIRification and Opening of data. Use cases provide a means to test the EERAdata concept towards FAIRification and the opening of data. Therefore, use cases are chosen to cover, on the one hand, low hanging fruits to demonstrate do-ability, promote the FAIR/O data principle implementation and showing associated benefits for the low carbon energy research community. On the other hand, EERAdata also includes use cases where the concept is challenged, because FAIRification and opening activities are still in their infancy.
*Broad testing and application to enable trans-disciplinary research combining data from different domains and at different scales. Use cases are at the same time selected to cover wider aspects of the low carbon energy transformation, exploring different sub-domains. This ensures a broad testing and application of the FAIR/O ecosystem as well as the community platform.
*Gender as a cross-cutting issue, see [[Gender]] for more details.

'''Selection''': Altogether 4 use cases were selected:
{| class="wikitable"
|-
! Use case 1 !! Use case 2 !! Use case 3 !! Use case 4 !! Machine-actionable DMP
|-
| [[UC1|Buildings efficiency]] || [[UC2|Power transmission & distribution networks]] || [[UC3|Material solutions for low carbon energy]] || [[UC4|Low carbon energy and energy efficiency policies]] || [[DMP|Data Management Plan]]
|-
|
[[File:UC1 logo.jpg|thumb]]
||
[[File:UC 2 logo.jpg|thumb]]
||
[[File:UC 3 logo.jpg|thumb]]
||
[[File:UC 4 logo.jpg|thumb]]
||
[[File:UC 5 logo.jpg|thumb]]
|}

=== Inspiration from other use cases ===
* https://eudat.eu/use-cases

==== Metadata standards in the energy domain that allow machine-actionability ====
'''General'''
* RDF - @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
* Fundamental data types - @prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
* Media resources ontology - @prefix ma: <http://www.w3.org/ns/ma-ont#> .
* Doublin Core - @prefix dc: <http://purl.org/dc/elements/1.1/> .
* Schema.org - @prefix schema: <http://schema.org/> .
* DBpedia - defining concepts @prefix dbo: <http://dbpedia.org/ontology/> .
* DBpedia - defining resources @prefix dbr: <http://dbpedia.org/resource/> .
* Geographic information - @prefix geo: <http://www.w3.org/2003/01/geo/wgs84_pos#> .
* WIKIDATA - @prefix wikidata: <https://www.wikidata.org/wiki/> .
* Microsoft standard for data cleaning/governance concepts - @prefix grel: <http://users.ugent.be/~bjdmeest/function/grel.ttl#> .
* Countries names - @prefix country: <http://dd.eionet.europa.eu/vocabulary/common/countries/> .
* Physical units - @prefix qudt-unit-1-1: <http://qudt.org/1.1/vocab/unit#> .
* Geopolitical terms - @prefix geop: <http://aims.fao.org/aos/geopolitical.owl#> .

'''Researchers and institutions'''
* ORICID - @prefix orcid: <http://www.orcid.org/> .
* Registered organisations ontology - @prefix rov: <http://www.w3.org/ns/regorg#> .
* GLEIF for legal forms ontology - @prefix gleif: <https://www.gleif.org/ontology/Base/> .
* GLEIF for legal forms ontology@prefix gleif-elf: <https://www.gleif.org/ontology/EntityLegalForm-v1.0/EntityLegalForm/> .
* GLEIF for legal forms ontology@prefix gleif-L1: <https://www.gleif.org/ontology/L1/> .
* @prefix qudt-1-1: <http://qudt.org/1.1/schema/qudt#> .

'''Economic sectors'''
* Economic Sectors - @prefix nace: <https://dd.eionet.europa.eu/vocabulary/eurostat/nace_r2/> .
* Extensible Business Report Language - @prefix xbrll: <https://w3id.org/vocab/xbrll#> .

'''Energy domain terminology'''
* SIEC - International Energy Product Classification Standard - @prefix siec: <http://dd.eionet.europa.eu/vocabulary/eurostat/siec/> .
* Open Energy Ontology - @prefix oeo: <http://openenergy-platform.org/ontology/oeo/> .

==== Other, ontologies, thesauri etc. in energy ====
# '''Energy Management Applications (OEMA).''' Creating ontologies can be a very tedious task if done by hand. Therefore, it is crucial to automatize this procedure. Details can be found in the Wikipedia article on [https://en.wikipedia.org/wiki/Ontology_learning Ontology learning]. Examples for the energy sector are: Javier Cuenca et al. [http://ceur-ws.org/Vol-1936/paper-08.pdf A Unified Semantic Ontology for Energy Management Applications].
[[File:OEMA-Ontology-for-Energy-Management-Applications-ontology-network-structure-Cuenca-et.png|thumb|Fig. 1 from Cuenca et al.: OEMA energy management ontology. See: http://ceur-ws.org/Vol-1936/paper-08.pdf.]]

== Gap analysis ==

'''[[Gap analysis| Gap analysis]]'''. Identification and clustering of energy research data sources (data collection or identification from existing repositories and former national and EU projects prioritizing databases relevant for the use cases, conceptual grouping/clustering of data-related use cases, building on workshop discussions). The goal is to elicit metadata and FAIR/O bottlenecks relevant across energy use cases and their positioning in the energy system. EERAdata uses Wilkinson et al. 2016 as well as the FAIR self-assessment tools (e.g., nectar and RDS) to develop criteria for assessing appliance with FAIR/O principles in the energy domain. The consortium will also discuss the possibility of developing a badge, able to display results of assessments on the community platform. Related deliverables and output: D2.2 Gap analysis report, D3.1 Platform specifications, and D2.3. Report on Research Recommendations (see [[Project_management|Project Management]]).

== Workshop concept of EERAdata ==

The workshop concept of EERAdata is developed along with the ''Index to FAIR Action Plan'' as recommended by [https://ec.europa.eu/info/sites/info/files/turning_fair_into_reality_1.pdf EC Expert Group on FAIR data, 2018] More specifically, the testing and discussion of the FAIR/O ecosystem (incl. the community platform) are organized through a series of workshops that take place twice a year with sequential annual foci. Each workshop takes three days. The first day is dedicated to state of the art for each workshop topic. Experts from the energy and other research communities are invited to present best practices (ensuring the participation from institutions providing research infrastructure, academia, and industry and private sector persons). Mutual learning and exchange of knowledge are facilitated in moderated discussions following presentations. The first day advances the understanding of cutting-edge concepts and approaches towards FAIR/O data (e.g., the role of metadata, data management plans, metrics, incentive mechanisms, etc.). The second day uses the knowledge and understanding obtained during the first day to translate the concepts and approaches to the domain of low carbon energy research data at the level of selected use cases. The goal is to understand the ways of data discovery and to synthesize metadata from mental models of domain experts (otherwise proposed metadata will remain artificial and, thus, not used in the community). Hence, the work done during the second day takes place in parallel groups structured around use cases (see details below). The key participants of workshops are consortium members for each use case and the groups of stewards of FAIR/O data principles recruited from invited experts. The third day synthesizes, integrates, and concludes the results achieved during the first two days (e.g., unifying and linking metadata across use cases). First, discussed concepts and approaches for the FAIR/O ecosystem, as well as the community platform, are refined. This continuously shapes the main deliverables of the workshops. Second, the agenda of the next workshop is agreed upon and specified with respect to experts to be invited and topics to be addressed. It should be noted that the first and the second day are open to participants from outside of the consortium to allow community-wide participation in EERAdata.

*'''1st Year:''' Define. Concept for FAIR implementation. Skills for FAIR.
*'''2nd Year:''' Implement. FAIR culture. FAIR Ecosystem. Skills for FAIR.
*'''3rd Year:''' Embed & sustain. Incentives, metrics, and investments for FAIR data and services.

[[File:WS concept.jpg|800px|Workshop concept of EERAdata]]

== List of workshops ==

=== Workshop 1 ===
# [[WS1| Workshop 1 - link to workshop page]] on "'''FAIR principles and METADATA for low carbon energy'''"
=== Workshop 2 ===
# [[WS2| Workshop 2 - link to workshop page]] on "'''FAIR and open energy metadata'''"
=== Workshop 3 ===
# [[WS3| Workshop 3 - link to workshop page]] on "'''FAIRification put into practice'''"

=== Workshop 4 ===
# [[WS4| Workshop 4 - link to workshop page]] on "'''Supporting technologies for FAIRification'''"

=== Workshop 5 ===
# [[WS5| Workshop 5 - link to workshop page]] on "'''Sustainable models for FAIR and open low carbon energy research data'''"

=== Workshop 6 ===
# Workshop on "'''New trends in open science & steps beyond EERAdata'''"

== Community Platform ==

In its Work Package 3, EERAdata develops a web-based platform for the low carbon energy research community to access relevant databases in a uniform and seamless way. This Wiki section supports the development of the platform and formulates its [[functional specifications|'''Functional Specifications''']]. We conceive it as a '''living document''' collecting inputs from a variety of user perspectives, especially from the EERAdata use cases ([[UC1|Buildings efficiency]], [[UC2|Power transmission & distribution networks]], [[UC3|Material solutions for low carbon energy]] and [[UC4|Low carbon energy and energy efficiency policies]]). This living document forms the basis of Deliverable 3.1 that will guide the design and implementation of the platform. It´s main elements are:
# A [[community forum|'''Community forum''']] to support EERAdata and the wider community to develop and discuss the ecosystem for FAIR/O energy data (e.g., joint ontologies, metadata standards, assessment criteria, etc.). Along with the EERAdata Workshops, this forum is a possibility for discussing the '''users´ needs and expectations towards the platform''' online and also to support the metadata harmonization procedures (e.g., joint ontologies, metadata standards, assessment criteria, etc.).
# A [[community platform|'''Web-based dashboard''']] providing systematic access to external energy research databases in distributed open repositories. In a searchable database of metadata, the user will be able to start queries and will be linked – through an internal processing and storage device – to information on the queried databases. As such, the platform will not duplicate resources but work as a federated database and offer basic analytic features.

'''Figure:''' Web-based Platform elements (from Project proposal)

[[file:Platform_.jpg|800px]]

[https://eeradata-platform.eu/ Access the EERAdata Community Platform]

== Project management ==

Link to a page with [https://eeradata-platform.eu/mediawiki-1.30.0/index.php?title=Project_management#Deliverables|page with deliverables] etc.

File:Cat99.jpg

2024-01-29T12:18:55Z

Manfred: Besnik Upload

Besnik Upload

References on metadata

2022-12-01T08:29:50Z

Manfred: /* Articles in scientific journals */

== Articles in scientific journals ==
* [https://riojournal.com/article/38698/ A literature review of scholarly communications metadata]
* [https://link.springer.com/article/10.1007/s13740-018-0091-5 Harnessing the Power of Unified Metadata in an Ontology Repository: The Case of AgroPortal]
* [https://doi.org/10.3233/ISU-140746 Metadata for Big Data: A preliminary investigation of metadata quality issues in research data repositories]
* [https://www.tandfonline.com/doi/abs/10.1080/07317131.2020.1810443 Rethinking Metadata’s Value and How It Is Evaluated]
* [https://dl.acm.org/doi/10.1145/2964909 Automated Quality Assessment of Metadata across Open Data Portals]
* [https://www.semanticscholar.org/paper/Scenario-based-Metadata-Design-for-Open-Data-User-Liang/fa355d6bba404dd6fed699e7f7f90e6d3fa15cd5 Scenario-based Metadata Design for Open Data User Interaction]
* [https://www.sciencedirect.com/science/article/abs/pii/S0306457313000526 Dealing with metadata quality: The legacy of digital library efforts]
* [https://link.springer.com/article/10.1007/s00799-020-00279-3 An analysis and comparison of keyword recommendation methods for scientific data]
* [https://dl.acm.org/doi/10.1145/2993422.2993577 Brick: Towards a Unified Metadata Schema For Buildings]
* [https://www.springer.com/gp/book/9783319408910 Ontology-based multi-domain metadata for research data management using triple stores]
* [https://riojournal.com/article/53916/ Methods & proposal for metadata guiding principles for scholarly communications]
* [https://doi.org/10.1080/0361526X.2018.1428483 Can Richer Metadata Rescue Research?]
* [https://link.springer.com/chapter/10.1007/978-3-030-14401-2_12 The Genesis of EngMeta - A Metadata Model for Research Data in Computational Engineering]
* [http://www.hedden-information.com/wp-content/uploads/2019/07/Creating-Indexes-and-Thesauri.pdf Creating indexes and thesauri: similarities and differences]
* [https://www.tandfonline.com/doi/full/10.1080/07317131.2020.1810443 Rethinking Metadata’s Value and How It Is Evaluated]
* [https://www.nature.com/articles/sdata20192 Qresp, a tool for curating, discovering and exploring reproducible scientific papers]
* [https://www.escienceediting.org/journal/view.php?doi=10.6087/kcse.185 An analysis of data paper templates and guidelines: types of contextual information described by data journals]
* [https://arxiv.org/pdf/1910.09313.pdf Using Supervised Learning to Classify Metadata of Research Data by Discipline of Research]

== Reports and grey literature ==
* [https://dcpapers.dublincore.org/pubs/article/view/3714 Metadata for Research Data: Current Practices and Trends]
* [https://zenodo.org/record/1199489/files/Taxonomy%20and%20meta%20data%20for%20wind%20energy%20Sector.pdf Taxonomy and meta data for wind energy R&D Work Package 2 - Deliverable D2.3]
*[https://www.researchgate.net/publication/324833153_Metadaten_fur_Forschungsdaten_in_der_Praxis/fulltext/5ae668ebaca272ba5081e24c/Metadaten-fuer-Forschungsdaten-in-der-Praxis.pdf Metadata for research data in practise]
* [https://support.sas.com/resources/papers/proceedings/proceedings/sugi31/104-31.pdf THE DESIGN AND USE OF METADATA: PART FINE ART, PART BLACK ART]

== Opinion pieces ==
* [https://blog.scholasticahq.com/post/metadata-2020-improve-quality-of-metadata/ Interview - Metadata 2020 working to improve the quality of metadata for research]
* [https://www.cmswire.com/digital-asset-management/what-makes-a-good-metadata-schema/ Opinion piece - What Makes a Good Metadata Schema?]
* [https://www.rd-alliance.org/metadata-principles RDA metadata principles]
* [https://www.semanticscholar.org/paper/Big-Metadata%2C-Smart-Metadata%2C-and-Metadata-Capital%3A-Greenberg/021865bb9fcc59814d2ce84d086554e5e0259779 Jane Greenburg - Big Metadata, Smart Metadata, and Metadata Capital: Toward Greater Synergy Between Data Science and Metadata]
*

== Books ==
* [https://www.cambridge.org/core/books/metadata-for-information-management-and-retrieval/FBDE16B5739A32A6C8D9E56A38AE8223 D. Haynes, Metadata for Information Management and Retrieval, facet Publishing, 2018]
* [https://www.sciencedirect.com/book/9780240808697/developing-quality-metadata Cliff Wootton, Developing Quality Metadata, Focal Press, 2007]
* [https://mitpress.mit.edu/books/metadata Jeffrey Pomerantz, Metadata, MIT Press, 2015]
* [https://www.getty.edu/publications/virtuallibrary/0892368969.html Murtha Baca, Introduction to metadata, Getty Publications, 2008]
* [https://www.worldscientific.com/worldscibooks/10.1142/7077 Miguel-Angel Sicilia, Handbook of Metadata, Semantics and Ontologies, World Scientific, 2014]
* [https://www.springer.com/gp/book/9783319408910 Richard Gartner, Metadata - Shaping Knowledge from Antiquity to the Semantic Web, Springer, 2016]

== Websites ==
* [http://www.metadata2020.org/ Metadata 2020]
* [https://earthdata.nasa.gov/eosdis/science-system-description/eosdis-components/cmr/umm NASA’s Common Metadata Repository]
* [https://c2metadata.org/ c2metadata - Continuous capture of metadata]

== Webinars ==
* [https://www.sspnet.org/?library=building-a-common-infrastructure-the-challenges-of-modern-metadata SSP Webinar - Building a Common Infrastructure: The Challenges of Modern Metadata]
* [http://aims.fao.org/activity/blog/recorded-webinar-metadata-standard-improving-interoperability-through-research-data AIMS Webinar : Metadata as Standard: improving Interoperability through the Research Data Alliance]

Main Page

2022-11-07T11:33:01Z

Manfred: /* Community Platform */

Welcome to the EERAdata MediaWiki!

== The project EERAdata ==

'''Towards a FAIR and open data ecosystem in the low carbon energy research community.''' Transparent, re-usable, and integrated energy data enable society to choose, monitor, and implement sustainable transition pathways. It is not only a prerequisite for people to have ownership over the changes, but it is also offering huge potential for industrial and social innovation. The majority of energy databases are not fit for this purpose, which the project aims to change. The consortium develops, tests, and implements a [[FAIR_guiding_principles|FAIR]] and open data ecosystem in the energy field. FAIR stands for F-findable, A-accessible, I-interoperable, and R-re-usable. The EU-funded EERAdata project builds a pool of data stewards to guide the community towards fit-for-purpose data practices.

'''EERAdata logo and key visual'''. The elements of the logo include ''data points'' - symbolizing databases or data platforms - and a ''data folder'' which are connected through the ''feed symbol''. All stand for the idea of EERAdata to support FAIR and open data. The folder furthermore is a nostalgic reminder of the grand library catalogs to search for books, all of them are masterpieces on their own. [[File:EERAdata_key_visual.png|thumb|Key visual of EERAdata]]

The project is funded by [https://cordis.europa.eu/project/id/883823 Europa's Horizon 2020 Research Program].
[[File:Co-funded.png|thumb|The project is funded by the European Union, Horizon 2020 Programme]]

=== Website ===
The website is here: https://www.eeradata.eu/

=== Timeline ===
Here we report when we did what to implement EERAdata. Workshops, meetings to build a FAIR/O community for energy data, etc. [[Timeline|Timeline]]

=== EERAdata & Arts ===
The artist Barbara Bellier from Clairmont-Ferrand in France joined our workshops to illustrate the discussions. With her beautiful art, she lifted our spirit when discussions became tough and problems seemed too huge for our small project. Many thanks for your manifold inspirations!

[[File:Business card Barbara.jpg|thumb|The artist's footprint: barbara.bllr@gmail.com.]]

See the [[WS1#WS1_through_the_lense_of_an_artist|gallery from workshop 1]].

See the [[WS2_through_the_lense_of_an_artist|gallery from workshop 2]].

== Join and collaborate interactively! ==
The workshop is a hackathon! EERAdata is evolving jointly only! Join the discussions and work together online:
* [[Main_Page#Getting_started_with_EERAdata_wiki|EERAdata WIKI]]
* [[WS1#EERAdata_story_board|EERAdata storyboard]]
* [https://github.com/valeria6856/EERAdata EERAdata@github]
* [https://www.researchgate.net/project/Towards-a-FAIR-and-open-data-ecosystem-in-the-low-carbon-energy-research-community EERAdata@ResearchGate]

=== EERAdata story board ===
'''Objective:''' collect views from participants regarding energy data, energy metadata, FAIR/O problems etc. to support discussions, identification of gaps & needs (WP2) and elements to design the platform (WP3).

'''Questions:'''
* Q#1: What is your user story regarding FAIR/O energy data?
* Q#2: What is your user story regarding metadata?

Template to answer: As a <stakeholder>, I want <goal> so that <reason>.

'''How to post a story?'''
# Click on the link: https://padlet.com/janaschwanitz/aciywzt9fs1h70m2
# Click on plus at the right bottom to add a story.
# Choose a title depending on the question you want to answer. Choose for Q#1: FAIR/O data, or for Q#2: metadata. In the example above, the title “metadata” was chosen.
# Type your sentence to let us know where the gaps and hopes are: The template is: As a <stakeholder>, I want <goal> so that <reason>.

'''Example:''' As a data-driven energy researcher, I want utopia - i.e. one-stop access to all relevant metadata -, so that I can browse available data, check where they are from and whether I can trust them when reusing.

'''How to comment a story?'''
* One can rate stories by clicking on a number of stars.
* One can comment stories as well as comments with words.
* It is anonymous commenting and adding of stories, as long as one does not login into one's personal profile at padlet.com.

=== EERAdata wiki - How to? ===

The easiest way is you simply start writing and editing. You can install an easy editor by doing what is described on the picture to the right.
[[File:Install easy editor.png|thumb|How to install an easy editor]]

Temporarily login for guests:
* user name: guest, pwd: guest2020
Login for EERAdata consortium members:
* user name: <your_first_name+firstletter_of_your_last_name>, e.g., ''valerias''
* pwd: sent seperately to each of you individually

Here is also additional (advanced) documentation on DOKUWIKI which you might want to consult:
Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]

=== EERAdata on github ===
Link here and share your thoughts and issues! Note, work in progress.
* [https://github.com/valeria6856/EERAdata EERAdata@github]

=== EERAdata @ Research Gate ===
Link here and share your thoughts and issues! Note, work in progress.
* [https://www.researchgate.net/project/Towards-a-FAIR-and-open-data-ecosystem-in-the-low-carbon-energy-research-community EERAdata@ResearchGate]

=== Just have fun! ===
==== Metadata memory game ====
This is a little memory game where players need to identify triples. They will learn about metadata. A triple describes an example of metadata used in low carbon energy. Different formats, file types, and descriptions are introduced.
[https://eeradata-platform.eu/memory/memory_3plus.html '''Link''']

== List of project partners ==
#[https://www.hvl.no/en/ HVL - Western Norway University of Applied Sciences]
#[https://www.ieu.edu.tr/en IUE - Izmir University of Economics]
#[https://www.ait.ac.at/ AIT - Austrian Institute of Technology]
#[https://www.gig.eu/en GIG - Central Mining Institute]
#[https://www.eera-set.eu/ EERA - European Energy Research Alliance]
#[https://www.enea.it/ ENEA - Italian National Agency for New Technologies, Energy and Sustainable Economic Development]

== Use cases in EERAdata ==
'''Definition:''' Use cases are an exercise for testing and refining the general approach towards FAIRification and opening of databases as well as to testing and refining the community platform. Use cases constitute practical commitments for implementation (PCI), i.e. the FAIRification and opening of data. Through exercises, the status quo of FAIR/O data principles in each use case is advanced by:

*Identifying taxonometric elements and metadata common among different domains of the energy system. Proper metadata will enable separating expert knowledge (and expert interest) from general knowledge and general interest, allowing coarse-grained and fine-grained navigation.
*Linking these metadata standards to existing metadata standards in other domains. Example: Weather-related data are integral to the efficient operation of PV, wind technology, or district heating. The assignment of geo-tagged information to low carbon energy technology data is thus the way forward. EERAdata will link energy domain metadata with metadata defined by ISO 19115 Geographic Metadata Information.
*Exploring a variety of challenges towards FAIRification and Opening of data. Use cases provide a means to test the EERAdata concept towards FAIRification and the opening of data. Therefore, use cases are chosen to cover, on the one hand, low hanging fruits to demonstrate do-ability, promote the FAIR/O data principle implementation and showing associated benefits for the low carbon energy research community. On the other hand, EERAdata also includes use cases where the concept is challenged, because FAIRification and opening activities are still in their infancy.
*Broad testing and application to enable trans-disciplinary research combining data from different domains and at different scales. Use cases are at the same time selected to cover wider aspects of the low carbon energy transformation, exploring different sub-domains. This ensures a broad testing and application of the FAIR/O ecosystem as well as the community platform.
*Gender as a cross-cutting issue, see [[Gender]] for more details.

'''Selection''': Altogether 4 use cases were selected:
{| class="wikitable"
|-
! Use case 1 !! Use case 2 !! Use case 3 !! Use case 4 !! Machine-actionable DMP
|-
| [[UC1|Buildings efficiency]] || [[UC2|Power transmission & distribution networks]] || [[UC3|Material solutions for low carbon energy]] || [[UC4|Low carbon energy and energy efficiency policies]] || [[DMP|Data Management Plan]]
|-
|
[[File:UC1 logo.jpg|thumb]]
||
[[File:UC 2 logo.jpg|thumb]]
||
[[File:UC 3 logo.jpg|thumb]]
||
[[File:UC 4 logo.jpg|thumb]]
||
[[File:UC 5 logo.jpg|thumb]]
|}

=== Inspiration from other use cases ===
* https://eudat.eu/use-cases

==== Metadata standards in the energy domain that allow machine-actionability ====
'''General'''
* RDF - @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
* Fundamental data types - @prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
* Media resources ontology - @prefix ma: <http://www.w3.org/ns/ma-ont#> .
* Doublin Core - @prefix dc: <http://purl.org/dc/elements/1.1/> .
* Schema.org - @prefix schema: <http://schema.org/> .
* DBpedia - defining concepts @prefix dbo: <http://dbpedia.org/ontology/> .
* DBpedia - defining resources @prefix dbr: <http://dbpedia.org/resource/> .
* Geographic information - @prefix geo: <http://www.w3.org/2003/01/geo/wgs84_pos#> .
* WIKIDATA - @prefix wikidata: <https://www.wikidata.org/wiki/> .
* Microsoft standard for data cleaning/governance concepts - @prefix grel: <http://users.ugent.be/~bjdmeest/function/grel.ttl#> .
* Countries names - @prefix country: <http://dd.eionet.europa.eu/vocabulary/common/countries/> .
* Physical units - @prefix qudt-unit-1-1: <http://qudt.org/1.1/vocab/unit#> .
* Geopolitical terms - @prefix geop: <http://aims.fao.org/aos/geopolitical.owl#> .

'''Researchers and institutions'''
* ORICID - @prefix orcid: <http://www.orcid.org/> .
* Registered organisations ontology - @prefix rov: <http://www.w3.org/ns/regorg#> .
* GLEIF for legal forms ontology - @prefix gleif: <https://www.gleif.org/ontology/Base/> .
* GLEIF for legal forms ontology@prefix gleif-elf: <https://www.gleif.org/ontology/EntityLegalForm-v1.0/EntityLegalForm/> .
* GLEIF for legal forms ontology@prefix gleif-L1: <https://www.gleif.org/ontology/L1/> .
* @prefix qudt-1-1: <http://qudt.org/1.1/schema/qudt#> .

'''Economic sectors'''
* Economic Sectors - @prefix nace: <https://dd.eionet.europa.eu/vocabulary/eurostat/nace_r2/> .
* Extensible Business Report Language - @prefix xbrll: <https://w3id.org/vocab/xbrll#> .

'''Energy domain terminology'''
* SIEC - International Energy Product Classification Standard - @prefix siec: <http://dd.eionet.europa.eu/vocabulary/eurostat/siec/> .
* Open Energy Ontology - @prefix oeo: <http://openenergy-platform.org/ontology/oeo/> .

==== Other, ontologies, thesauri etc. in energy ====
# '''Energy Management Applications (OEMA).''' Creating ontologies can be a very tedious task if done by hand. Therefore, it is crucial to automatize this procedure. Details can be found in the Wikipedia article on [https://en.wikipedia.org/wiki/Ontology_learning Ontology learning]. Examples for the energy sector are: Javier Cuenca et al. [http://ceur-ws.org/Vol-1936/paper-08.pdf A Unified Semantic Ontology for Energy Management Applications].
[[File:OEMA-Ontology-for-Energy-Management-Applications-ontology-network-structure-Cuenca-et.png|thumb|Fig. 1 from Cuenca et al.: OEMA energy management ontology. See: http://ceur-ws.org/Vol-1936/paper-08.pdf.]]

== Gap analysis ==

'''[[Gap analysis| Gap analysis]]'''. Identification and clustering of energy research data sources (data collection or identification from existing repositories and former national and EU projects prioritizing databases relevant for the use cases, conceptual grouping/clustering of data-related use cases, building on workshop discussions). The goal is to elicit metadata and FAIR/O bottlenecks relevant across energy use cases and their positioning in the energy system. EERAdata uses Wilkinson et al. 2016 as well as the FAIR self-assessment tools (e.g., nectar and RDS) to develop criteria for assessing appliance with FAIR/O principles in the energy domain. The consortium will also discuss the possibility of developing a badge, able to display results of assessments on the community platform. Related deliverables and output: D2.2 Gap analysis report, D3.1 Platform specifications, and D2.3. Report on Research Recommendations (see [[Project_management|Project Management]]).

== Workshop concept of EERAdata ==

The workshop concept of EERAdata is developed along with the ''Index to FAIR Action Plan'' as recommended by [https://ec.europa.eu/info/sites/info/files/turning_fair_into_reality_1.pdf EC Expert Group on FAIR data, 2018] More specifically, the testing and discussion of the FAIR/O ecosystem (incl. the community platform) are organized through a series of workshops that take place twice a year with sequential annual foci. Each workshop takes three days. The first day is dedicated to state of the art for each workshop topic. Experts from the energy and other research communities are invited to present best practices (ensuring the participation from institutions providing research infrastructure, academia, and industry and private sector persons). Mutual learning and exchange of knowledge are facilitated in moderated discussions following presentations. The first day advances the understanding of cutting-edge concepts and approaches towards FAIR/O data (e.g., the role of metadata, data management plans, metrics, incentive mechanisms, etc.). The second day uses the knowledge and understanding obtained during the first day to translate the concepts and approaches to the domain of low carbon energy research data at the level of selected use cases. The goal is to understand the ways of data discovery and to synthesize metadata from mental models of domain experts (otherwise proposed metadata will remain artificial and, thus, not used in the community). Hence, the work done during the second day takes place in parallel groups structured around use cases (see details below). The key participants of workshops are consortium members for each use case and the groups of stewards of FAIR/O data principles recruited from invited experts. The third day synthesizes, integrates, and concludes the results achieved during the first two days (e.g., unifying and linking metadata across use cases). First, discussed concepts and approaches for the FAIR/O ecosystem, as well as the community platform, are refined. This continuously shapes the main deliverables of the workshops. Second, the agenda of the next workshop is agreed upon and specified with respect to experts to be invited and topics to be addressed. It should be noted that the first and the second day are open to participants from outside of the consortium to allow community-wide participation in EERAdata.

*'''1st Year:''' Define. Concept for FAIR implementation. Skills for FAIR.
*'''2nd Year:''' Implement. FAIR culture. FAIR Ecosystem. Skills for FAIR.
*'''3rd Year:''' Embed & sustain. Incentives, metrics, and investments for FAIR data and services.

[[File:WS concept.jpg|800px|Workshop concept of EERAdata]]

== List of workshops ==

=== Workshop 1 ===
# [[WS1| Workshop 1 - link to workshop page]] on "'''FAIR principles and METADATA for low carbon energy'''"
=== Workshop 2 ===
# [[WS2| Workshop 2 - link to workshop page]] on "'''FAIR and open energy metadata'''"
=== Workshop 3 ===
# [[WS3| Workshop 3 - link to workshop page]] on "'''FAIRification put into practice'''"

=== Workshop 4 ===
# [[WS4| Workshop 4 - link to workshop page]] on "'''Supporting technologies for FAIRification'''"

=== Workshop 5 ===
# [[WS5| Workshop 5 - link to workshop page]] on "'''Sustainable models for FAIR and open low carbon energy research data'''"

=== Workshop 6 ===
# Workshop on "'''New trends in open science & steps beyond EERAdata'''"

== Community Platform ==

In its Work Package 3, EERAdata develops a web-based platform for the low carbon energy research community to access relevant databases in a uniform and seamless way. This Wiki section supports the development of the platform and formulates its [[functional specifications|'''Functional Specifications''']]. We conceive it as a '''living document''' collecting inputs from a variety of user perspectives, especially from the EERAdata use cases ([[UC1|Buildings efficiency]], [[UC2|Power transmission & distribution networks]], [[UC3|Material solutions for low carbon energy]] and [[UC4|Low carbon energy and energy efficiency policies]]). This living document forms the basis of Deliverable 3.1 that will guide the design and implementation of the platform. It´s main elements are:
# A [[community forum|'''Community forum''']] to support EERAdata and the wider community to develop and discuss the ecosystem for FAIR/O energy data (e.g., joint ontologies, metadata standards, assessment criteria, etc.). Along with the EERAdata Workshops, this forum is a possibility for discussing the '''users´ needs and expectations towards the platform''' online and also to support the metadata harmonization procedures (e.g., joint ontologies, metadata standards, assessment criteria, etc.).
# A [[community platform|'''Web-based dashboard''']] providing systematic access to external energy research databases in distributed open repositories. In a searchable database of metadata, the user will be able to start queries and will be linked – through an internal processing and storage device – to information on the queried databases. As such, the platform will not duplicate resources but work as a federated database and offer basic analytic features.

'''Figure:''' Web-based Platform elements (from Project proposal)

[[file:Platform_.jpg|800px]]

[https://eeradata-platform.eu/ Access the EERAdata Community Platform]

== Project management ==

Link to a page with [https://eeradata-platform.eu/mediawiki-1.30.0/index.php?title=Project_management#Deliverables|page with deliverables] etc.

Community platform

2022-11-07T11:31:44Z

Manfred:

[https://eeradata-platform.eu/ Access the EERAdata Community Platform]

Main Page

2022-11-07T11:31:07Z

Manfred: /* Community Platform */

Welcome to the EERAdata MediaWiki!

== The project EERAdata ==

'''Towards a FAIR and open data ecosystem in the low carbon energy research community.''' Transparent, re-usable, and integrated energy data enable society to choose, monitor, and implement sustainable transition pathways. It is not only a prerequisite for people to have ownership over the changes, but it is also offering huge potential for industrial and social innovation. The majority of energy databases are not fit for this purpose, which the project aims to change. The consortium develops, tests, and implements a [[FAIR_guiding_principles|FAIR]] and open data ecosystem in the energy field. FAIR stands for F-findable, A-accessible, I-interoperable, and R-re-usable. The EU-funded EERAdata project builds a pool of data stewards to guide the community towards fit-for-purpose data practices.

'''EERAdata logo and key visual'''. The elements of the logo include ''data points'' - symbolizing databases or data platforms - and a ''data folder'' which are connected through the ''feed symbol''. All stand for the idea of EERAdata to support FAIR and open data. The folder furthermore is a nostalgic reminder of the grand library catalogs to search for books, all of them are masterpieces on their own. [[File:EERAdata_key_visual.png|thumb|Key visual of EERAdata]]

The project is funded by [https://cordis.europa.eu/project/id/883823 Europa's Horizon 2020 Research Program].
[[File:Co-funded.png|thumb|The project is funded by the European Union, Horizon 2020 Programme]]

=== Website ===
The website is here: https://www.eeradata.eu/

=== Timeline ===
Here we report when we did what to implement EERAdata. Workshops, meetings to build a FAIR/O community for energy data, etc. [[Timeline|Timeline]]

=== EERAdata & Arts ===
The artist Barbara Bellier from Clairmont-Ferrand in France joined our workshops to illustrate the discussions. With her beautiful art, she lifted our spirit when discussions became tough and problems seemed too huge for our small project. Many thanks for your manifold inspirations!

[[File:Business card Barbara.jpg|thumb|The artist's footprint: barbara.bllr@gmail.com.]]

See the [[WS1#WS1_through_the_lense_of_an_artist|gallery from workshop 1]].

See the [[WS2_through_the_lense_of_an_artist|gallery from workshop 2]].

== Join and collaborate interactively! ==
The workshop is a hackathon! EERAdata is evolving jointly only! Join the discussions and work together online:
* [[Main_Page#Getting_started_with_EERAdata_wiki|EERAdata WIKI]]
* [[WS1#EERAdata_story_board|EERAdata storyboard]]
* [https://github.com/valeria6856/EERAdata EERAdata@github]
* [https://www.researchgate.net/project/Towards-a-FAIR-and-open-data-ecosystem-in-the-low-carbon-energy-research-community EERAdata@ResearchGate]

=== EERAdata story board ===
'''Objective:''' collect views from participants regarding energy data, energy metadata, FAIR/O problems etc. to support discussions, identification of gaps & needs (WP2) and elements to design the platform (WP3).

'''Questions:'''
* Q#1: What is your user story regarding FAIR/O energy data?
* Q#2: What is your user story regarding metadata?

Template to answer: As a <stakeholder>, I want <goal> so that <reason>.

'''How to post a story?'''
# Click on the link: https://padlet.com/janaschwanitz/aciywzt9fs1h70m2
# Click on plus at the right bottom to add a story.
# Choose a title depending on the question you want to answer. Choose for Q#1: FAIR/O data, or for Q#2: metadata. In the example above, the title “metadata” was chosen.
# Type your sentence to let us know where the gaps and hopes are: The template is: As a <stakeholder>, I want <goal> so that <reason>.

'''Example:''' As a data-driven energy researcher, I want utopia - i.e. one-stop access to all relevant metadata -, so that I can browse available data, check where they are from and whether I can trust them when reusing.

'''How to comment a story?'''
* One can rate stories by clicking on a number of stars.
* One can comment stories as well as comments with words.
* It is anonymous commenting and adding of stories, as long as one does not login into one's personal profile at padlet.com.

=== EERAdata wiki - How to? ===

The easiest way is you simply start writing and editing. You can install an easy editor by doing what is described on the picture to the right.
[[File:Install easy editor.png|thumb|How to install an easy editor]]

Temporarily login for guests:
* user name: guest, pwd: guest2020
Login for EERAdata consortium members:
* user name: <your_first_name+firstletter_of_your_last_name>, e.g., ''valerias''
* pwd: sent seperately to each of you individually

Here is also additional (advanced) documentation on DOKUWIKI which you might want to consult:
Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]

=== EERAdata on github ===
Link here and share your thoughts and issues! Note, work in progress.
* [https://github.com/valeria6856/EERAdata EERAdata@github]

=== EERAdata @ Research Gate ===
Link here and share your thoughts and issues! Note, work in progress.
* [https://www.researchgate.net/project/Towards-a-FAIR-and-open-data-ecosystem-in-the-low-carbon-energy-research-community EERAdata@ResearchGate]

=== Just have fun! ===
==== Metadata memory game ====
This is a little memory game where players need to identify triples. They will learn about metadata. A triple describes an example of metadata used in low carbon energy. Different formats, file types, and descriptions are introduced.
[https://eeradata-platform.eu/memory/memory_3plus.html '''Link''']

== List of project partners ==
#[https://www.hvl.no/en/ HVL - Western Norway University of Applied Sciences]
#[https://www.ieu.edu.tr/en IUE - Izmir University of Economics]
#[https://www.ait.ac.at/ AIT - Austrian Institute of Technology]
#[https://www.gig.eu/en GIG - Central Mining Institute]
#[https://www.eera-set.eu/ EERA - European Energy Research Alliance]
#[https://www.enea.it/ ENEA - Italian National Agency for New Technologies, Energy and Sustainable Economic Development]

== Use cases in EERAdata ==
'''Definition:''' Use cases are an exercise for testing and refining the general approach towards FAIRification and opening of databases as well as to testing and refining the community platform. Use cases constitute practical commitments for implementation (PCI), i.e. the FAIRification and opening of data. Through exercises, the status quo of FAIR/O data principles in each use case is advanced by:

*Identifying taxonometric elements and metadata common among different domains of the energy system. Proper metadata will enable separating expert knowledge (and expert interest) from general knowledge and general interest, allowing coarse-grained and fine-grained navigation.
*Linking these metadata standards to existing metadata standards in other domains. Example: Weather-related data are integral to the efficient operation of PV, wind technology, or district heating. The assignment of geo-tagged information to low carbon energy technology data is thus the way forward. EERAdata will link energy domain metadata with metadata defined by ISO 19115 Geographic Metadata Information.
*Exploring a variety of challenges towards FAIRification and Opening of data. Use cases provide a means to test the EERAdata concept towards FAIRification and the opening of data. Therefore, use cases are chosen to cover, on the one hand, low hanging fruits to demonstrate do-ability, promote the FAIR/O data principle implementation and showing associated benefits for the low carbon energy research community. On the other hand, EERAdata also includes use cases where the concept is challenged, because FAIRification and opening activities are still in their infancy.
*Broad testing and application to enable trans-disciplinary research combining data from different domains and at different scales. Use cases are at the same time selected to cover wider aspects of the low carbon energy transformation, exploring different sub-domains. This ensures a broad testing and application of the FAIR/O ecosystem as well as the community platform.
*Gender as a cross-cutting issue, see [[Gender]] for more details.

'''Selection''': Altogether 4 use cases were selected:
{| class="wikitable"
|-
! Use case 1 !! Use case 2 !! Use case 3 !! Use case 4 !! Machine-actionable DMP
|-
| [[UC1|Buildings efficiency]] || [[UC2|Power transmission & distribution networks]] || [[UC3|Material solutions for low carbon energy]] || [[UC4|Low carbon energy and energy efficiency policies]] || [[DMP|Data Management Plan]]
|-
|
[[File:UC1 logo.jpg|thumb]]
||
[[File:UC 2 logo.jpg|thumb]]
||
[[File:UC 3 logo.jpg|thumb]]
||
[[File:UC 4 logo.jpg|thumb]]
||
[[File:UC 5 logo.jpg|thumb]]
|}

=== Inspiration from other use cases ===
* https://eudat.eu/use-cases

==== Metadata standards in the energy domain that allow machine-actionability ====
'''General'''
* RDF - @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
* Fundamental data types - @prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
* Media resources ontology - @prefix ma: <http://www.w3.org/ns/ma-ont#> .
* Doublin Core - @prefix dc: <http://purl.org/dc/elements/1.1/> .
* Schema.org - @prefix schema: <http://schema.org/> .
* DBpedia - defining concepts @prefix dbo: <http://dbpedia.org/ontology/> .
* DBpedia - defining resources @prefix dbr: <http://dbpedia.org/resource/> .
* Geographic information - @prefix geo: <http://www.w3.org/2003/01/geo/wgs84_pos#> .
* WIKIDATA - @prefix wikidata: <https://www.wikidata.org/wiki/> .
* Microsoft standard for data cleaning/governance concepts - @prefix grel: <http://users.ugent.be/~bjdmeest/function/grel.ttl#> .
* Countries names - @prefix country: <http://dd.eionet.europa.eu/vocabulary/common/countries/> .
* Physical units - @prefix qudt-unit-1-1: <http://qudt.org/1.1/vocab/unit#> .
* Geopolitical terms - @prefix geop: <http://aims.fao.org/aos/geopolitical.owl#> .

'''Researchers and institutions'''
* ORICID - @prefix orcid: <http://www.orcid.org/> .
* Registered organisations ontology - @prefix rov: <http://www.w3.org/ns/regorg#> .
* GLEIF for legal forms ontology - @prefix gleif: <https://www.gleif.org/ontology/Base/> .
* GLEIF for legal forms ontology@prefix gleif-elf: <https://www.gleif.org/ontology/EntityLegalForm-v1.0/EntityLegalForm/> .
* GLEIF for legal forms ontology@prefix gleif-L1: <https://www.gleif.org/ontology/L1/> .
* @prefix qudt-1-1: <http://qudt.org/1.1/schema/qudt#> .

'''Economic sectors'''
* Economic Sectors - @prefix nace: <https://dd.eionet.europa.eu/vocabulary/eurostat/nace_r2/> .
* Extensible Business Report Language - @prefix xbrll: <https://w3id.org/vocab/xbrll#> .

'''Energy domain terminology'''
* SIEC - International Energy Product Classification Standard - @prefix siec: <http://dd.eionet.europa.eu/vocabulary/eurostat/siec/> .
* Open Energy Ontology - @prefix oeo: <http://openenergy-platform.org/ontology/oeo/> .

==== Other, ontologies, thesauri etc. in energy ====
# '''Energy Management Applications (OEMA).''' Creating ontologies can be a very tedious task if done by hand. Therefore, it is crucial to automatize this procedure. Details can be found in the Wikipedia article on [https://en.wikipedia.org/wiki/Ontology_learning Ontology learning]. Examples for the energy sector are: Javier Cuenca et al. [http://ceur-ws.org/Vol-1936/paper-08.pdf A Unified Semantic Ontology for Energy Management Applications].
[[File:OEMA-Ontology-for-Energy-Management-Applications-ontology-network-structure-Cuenca-et.png|thumb|Fig. 1 from Cuenca et al.: OEMA energy management ontology. See: http://ceur-ws.org/Vol-1936/paper-08.pdf.]]

== Gap analysis ==

'''[[Gap analysis| Gap analysis]]'''. Identification and clustering of energy research data sources (data collection or identification from existing repositories and former national and EU projects prioritizing databases relevant for the use cases, conceptual grouping/clustering of data-related use cases, building on workshop discussions). The goal is to elicit metadata and FAIR/O bottlenecks relevant across energy use cases and their positioning in the energy system. EERAdata uses Wilkinson et al. 2016 as well as the FAIR self-assessment tools (e.g., nectar and RDS) to develop criteria for assessing appliance with FAIR/O principles in the energy domain. The consortium will also discuss the possibility of developing a badge, able to display results of assessments on the community platform. Related deliverables and output: D2.2 Gap analysis report, D3.1 Platform specifications, and D2.3. Report on Research Recommendations (see [[Project_management|Project Management]]).

== Workshop concept of EERAdata ==

The workshop concept of EERAdata is developed along with the ''Index to FAIR Action Plan'' as recommended by [https://ec.europa.eu/info/sites/info/files/turning_fair_into_reality_1.pdf EC Expert Group on FAIR data, 2018] More specifically, the testing and discussion of the FAIR/O ecosystem (incl. the community platform) are organized through a series of workshops that take place twice a year with sequential annual foci. Each workshop takes three days. The first day is dedicated to state of the art for each workshop topic. Experts from the energy and other research communities are invited to present best practices (ensuring the participation from institutions providing research infrastructure, academia, and industry and private sector persons). Mutual learning and exchange of knowledge are facilitated in moderated discussions following presentations. The first day advances the understanding of cutting-edge concepts and approaches towards FAIR/O data (e.g., the role of metadata, data management plans, metrics, incentive mechanisms, etc.). The second day uses the knowledge and understanding obtained during the first day to translate the concepts and approaches to the domain of low carbon energy research data at the level of selected use cases. The goal is to understand the ways of data discovery and to synthesize metadata from mental models of domain experts (otherwise proposed metadata will remain artificial and, thus, not used in the community). Hence, the work done during the second day takes place in parallel groups structured around use cases (see details below). The key participants of workshops are consortium members for each use case and the groups of stewards of FAIR/O data principles recruited from invited experts. The third day synthesizes, integrates, and concludes the results achieved during the first two days (e.g., unifying and linking metadata across use cases). First, discussed concepts and approaches for the FAIR/O ecosystem, as well as the community platform, are refined. This continuously shapes the main deliverables of the workshops. Second, the agenda of the next workshop is agreed upon and specified with respect to experts to be invited and topics to be addressed. It should be noted that the first and the second day are open to participants from outside of the consortium to allow community-wide participation in EERAdata.

*'''1st Year:''' Define. Concept for FAIR implementation. Skills for FAIR.
*'''2nd Year:''' Implement. FAIR culture. FAIR Ecosystem. Skills for FAIR.
*'''3rd Year:''' Embed & sustain. Incentives, metrics, and investments for FAIR data and services.

[[File:WS concept.jpg|800px|Workshop concept of EERAdata]]

== List of workshops ==

=== Workshop 1 ===
# [[WS1| Workshop 1 - link to workshop page]] on "'''FAIR principles and METADATA for low carbon energy'''"
=== Workshop 2 ===
# [[WS2| Workshop 2 - link to workshop page]] on "'''FAIR and open energy metadata'''"
=== Workshop 3 ===
# [[WS3| Workshop 3 - link to workshop page]] on "'''FAIRification put into practice'''"

=== Workshop 4 ===
# [[WS4| Workshop 4 - link to workshop page]] on "'''Supporting technologies for FAIRification'''"

=== Workshop 5 ===
# [[WS5| Workshop 5 - link to workshop page]] on "'''Sustainable models for FAIR and open low carbon energy research data'''"

=== Workshop 6 ===
# Workshop on "'''New trends in open science & steps beyond EERAdata'''"

== Community Platform ==

In its Work Package 3, EERAdata develops a web-based platform for the low carbon energy research community to access relevant databases in a uniform and seamless way. This Wiki section supports the development of the platform and formulates its [[functional specifications|'''Functional Specifications''']]. We conceive it as a '''living document''' collecting inputs from a variety of user perspectives, especially from the EERAdata use cases ([[UC1|Buildings efficiency]], [[UC2|Power transmission & distribution networks]], [[UC3|Material solutions for low carbon energy]] and [[UC4|Low carbon energy and energy efficiency policies]]). This living document forms the basis of Deliverable 3.1 that will guide the design and implementation of the platform. It´s main elements are:
# A [[community forum|'''Community forum''']] to support EERAdata and the wider community to develop and discuss the ecosystem for FAIR/O energy data (e.g., joint ontologies, metadata standards, assessment criteria, etc.). Along with the EERAdata Workshops, this forum is a possibility for discussing the '''users´ needs and expectations towards the platform''' online and also to support the metadata harmonization procedures (e.g., joint ontologies, metadata standards, assessment criteria, etc.).
# A [[community platform|'''Web-based dashboard''']] providing systematic access to external energy research databases in distributed open repositories. In a searchable database of metadata, the user will be able to start queries and will be linked – through an internal processing and storage device – to information on the queried databases. As such, the platform will not duplicate resources but work as a federated database and offer basic analytic features.

'''Figure:''' Web-based Platform elements (from Project proposal)

[[file:Platform_.jpg|800px]]

[https://eeradata-platform.eu/ Access the EERAdata Community Platform]

== Project management ==

Link to a page with [https://eeradata-platform.eu/mediawiki-1.30.0/index.php?title=Project_management#Deliverables|page with deliverables] etc.

WS4

2022-04-07T14:05:56Z

Manfred: /* Programme - 17 March 2022 */

'''Workshop No.4: Supporting technologies for FAIRification'''

The fourth EERAdata Workshop is a 3-day event taking place from '''Tue 15 - Thu 17 March, 2022'''. It is conceived as a hands-on workshop and discussion event complemented with external inputs given by invited contributors. Organized as a hybrid meeting, the workshop will be hosted by the AIT Austrian Institute of Technology (physical meeting in Vienna) and by the EERA Secretariat (online meeting). Given the expected pandemic-related restrictions and safety regulations, only a core group of the EERAdata project team will gather in person at the AIT. All other participants will be able to participate online upon registration.

== Objectives ==
* Explore and discuss tools that support a FAIR and open database infrastructure
* Agree on supporting technologies to be implemented, work on the community platform concept

== Read & watch aheads ==

In preperation of WS4, four Mini-Workshops where held from the 6th December 2021 to the 17th December 2021.

The content of these workshops can be found here:
[[Mini-Workshops]]

== Programme - 15 March 2022 ==
We adopt the perspective of database holders, focusing on those who are willing to create a FAIR database from scratch, following the FAIR criteria as far as possible.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 10:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Manfred Paier, AIT
|-
| 10:05 - 10:15 || Introduction to EERAdata || Valeria Jana Schwanitz (EERAdata PI), HVL
|-
| 10:15 - 11:00 || [https://eeradata-platform.eu/wiki/images/d/dc/EERAdata_BarberUnger_Presentation1.pdf A view on the EERAdata platform: supporting the FAIRification of energy research databases] || Astrid Unger, Michael Barber, AIT
|-
| 11:00 - 12:00 || FAIRifying a database: Experience with the COMETS FAIR database (Use Case 2) || August Hubert Wierling (EERAdata Co-PI), HVL
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 14:30 || EnergieAtlas: Scenario development with geo-referenced data for (electrical) energy applications || Stefan Übermasser, Fabian Leimgruber, AIT
|-
| 14.30 - 14:45 || Break
|-
| 14:45 - 16:00 || A focus on FAIR data needs: design of a survey questionnaire || Aleksandra Zgórska, GIG
|-
|}

== Programme - 16 March 2022 ==

We adopt the perspective of database users who encounter a non-FAIR database and intend to improve on the FAIR status of the database to increase visibility and reuse potential.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 09:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Demet Suna, AIT
|-
| 09:00 - 10:00 || Managing multi-model scenario ensembles for climate change & energy systems transition:
Lessons and insights from the IPCC process and Horizon 2020 projects https://doi.org/10.5281/zenodo.6361259
|| Daniel Huppmann, IIASA
|-
| 10.00 - 10:15 || Break
|-
| 10:15 - 11:00 || [[Media:220316-Costanzo-Demir-EERAData-ENEA-IUE.pdf|FAIR Platforms? Experience with the European Building Stock Observatory]] / [[Media:220316-Filippi-Slides-on-metadata.pdf|BuiltHub analysis of BSO metadata]] || Ezilda Costanzo, ENEA; Muhittin Demir, IUE / Ulrich Filippi Oberegger, EURAC
|-
| 11:00 - 12:00 || [https://eeradata-platform.eu/wiki/images/1/1a/EERAdata_UC1_Working_Session.pdf Use Case Working Session: Workflows and tools for buildings efficiency data] || Moderation: Astrid Unger, AIT
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 14:00 || Use Case Working Session: Workflows and tools for energy materials data || Moderation: Astrid Unger, AIT
|-
| 14.00 - 14:15 || Break
|-
| 14:15 - 15:15 || Use Case Working Session: Workflows and tools for energy efficiency policies || Moderation: Astrid Unger, AIT
|-
| 15:15 - 16:00 || [https://eeradata-platform.eu/wiki/images/c/c6/MURAL_Results_.pdf Plenary Discussion: Use Case-specific needs and cross-Use-Case learning potentials] || Moderation: Michael Barber, AIT
|-
|}

== Programme - 17 March 2022 ==
We focus on machine actionability of databases, comprising a short crash course in APIs, what they are, why machines need them, and how to use them as an energy data scientist.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 09:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Manfred Paier, AIT
|-
| 09:00 - 10:00 || Building an infrastructure integrating data and service for the humanities: Experience from the RISIS Core Facility https://doi.org/10.5281/zenodo.6364974 || Philippe Breucker, Univ. Gustave Eiffel
|-
| 10:00 - 10:45 || [https://eeradata-platform.eu/wiki/images/f/f8/EERAdata_BarberUnger_Presentation2.pdf What does machine-actionability mean? An API perspective on the EERAdata platform] || Michael Barber, Astrid Unger, AIT
|-
| 10.45 - 11:00 || Break
|-
| 11:00 - 12:00 || How FAIR and open data support a human-centered digitization || Valeria Jana Schwanitz, HVL
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 13:45 || 4 Breakout Sessions: [https://eeradata-platform.eu/wiki/images/7/72/EERAdata_Presentation3.pdf Use Case-specific needs for platform services] || Moderators: Use Case Leaders
|-
| 13.45 - 15:30 || Plenary Session
* Reports from Breakout Sessions (5 mins each) and discussion (10 mins), Moderator: Manfred Paier, AIT
* Break
* Discussion about EOSC - [https://eeradata-platform.eu/wiki/images/c/c1/EERAdata_EOSC_wierling.pdf How EERAdata can collaborate with and contribute to EOSC], Moderator: August Hubert Wierling, HVL
|-
| 15:30 - 16:00 || [https://eeradata-platform.eu/wiki/images/5/56/Paier_220317_Roundup_PlatformOutlook.pdf Round-up of the Workshop; Next steps of platform implementation & closing of the workshop] || Manfred Paier, AIT
|}

WS4

2022-03-25T09:35:31Z

Manfred: /* Programme - 17 March 2022 */

'''Workshop No.4: Supporting technologies for FAIRification'''

The fourth EERAdata Workshop is a 3-day event taking place from '''Tue 15 - Thu 17 March, 2022'''. It is conceived as a hands-on workshop and discussion event complemented with external inputs given by invited contributors. Organized as a hybrid meeting, the workshop will be hosted by the AIT Austrian Institute of Technology (physical meeting in Vienna) and by the EERA Secretariat (online meeting). Given the expected pandemic-related restrictions and safety regulations, only a core group of the EERAdata project team will gather in person at the AIT. All other participants will be able to participate online upon registration.

== Objectives ==
* Explore and discuss tools that support a FAIR and open database infrastructure
* Agree on supporting technologies to be implemented, work on the community platform concept

== Read & watch aheads ==

In preperation of WS4, four Mini-Workshops where held from the 6th December 2021 to the 17th December 2021.

The content of these workshops can be found here:
[[Mini-Workshops]]

== Programme - 15 March 2022 ==
We adopt the perspective of database holders, focusing on those who are willing to create a FAIR database from scratch, following the FAIR criteria as far as possible.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 10:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Manfred Paier, AIT
|-
| 10:05 - 10:15 || Introduction to EERAdata || Valeria Jana Schwanitz (EERAdata PI), HVL
|-
| 10:15 - 11:00 || [https://eeradata-platform.eu/wiki/images/d/dc/EERAdata_BarberUnger_Presentation1.pdf A view on the EERAdata platform: supporting the FAIRification of energy research databases] || Astrid Unger, Michael Barber, AIT
|-
| 11:00 - 12:00 || FAIRifying a database: Experience with the COMETS FAIR database (Use Case 2) || August Hubert Wierling (EERAdata Co-PI), HVL
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 14:30 || EnergieAtlas: Scenario development with geo-referenced data for (electrical) energy applications || Stefan Übermasser, Fabian Leimgruber, AIT
|-
| 14.30 - 14:45 || Break
|-
| 14:45 - 16:00 || A focus on FAIR data needs: design of a survey questionnaire || Aleksandra Zgórska, GIG
|-
|}

== Programme - 16 March 2022 ==

We adopt the perspective of database users who encounter a non-FAIR database and intend to improve on the FAIR status of the database to increase visibility and reuse potential.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 09:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Demet Suna, AIT
|-
| 09:00 - 10:00 || Managing multi-model scenario ensembles for climate change & energy systems transition:
Lessons and insights from the IPCC process and Horizon 2020 projects https://doi.org/10.5281/zenodo.6361259
|| Daniel Huppmann, IIASA
|-
| 10.00 - 10:15 || Break
|-
| 10:15 - 11:00 || [[Media:220316-Costanzo-Demir-EERAData-ENEA-IUE.pdf|FAIR Platforms? Experience with the European Building Stock Observatory]] / [[Media:220316-Filippi-Slides-on-metadata.pdf|BuiltHub analysis of BSO metadata]] || Ezilda Costanzo, ENEA; Muhittin Demir, IUE / Ulrich Filippi Oberegger, EURAC
|-
| 11:00 - 12:00 || [https://eeradata-platform.eu/wiki/images/1/1a/EERAdata_UC1_Working_Session.pdf Use Case Working Session: Workflows and tools for buildings efficiency data] || Moderation: Astrid Unger, AIT
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 14:00 || Use Case Working Session: Workflows and tools for energy materials data || Moderation: Astrid Unger, AIT
|-
| 14.00 - 14:15 || Break
|-
| 14:15 - 15:15 || Use Case Working Session: Workflows and tools for energy efficiency policies || Moderation: Astrid Unger, AIT
|-
| 15:15 - 16:00 || [https://eeradata-platform.eu/wiki/images/c/c6/MURAL_Results_.pdf Plenary Discussion: Use Case-specific needs and cross-Use-Case learning potentials] || Moderation: Michael Barber, AIT
|-
|}

== Programme - 17 March 2022 ==
We focus on machine actionability of databases, comprising a short crash course in APIs, what they are, why machines need them, and how to use them as an energy data scientist.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 09:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Manfred Paier, AIT
|-
| 09:00 - 10:00 || Building an infrastructure integrating data and service for the humanities: Experience from the RISIS Core Facility || Philippe Breucker, Univ. Gustave Eiffel
|-
| 10:00 - 10:45 || [https://eeradata-platform.eu/wiki/images/f/f8/EERAdata_BarberUnger_Presentation2.pdf What does machine-actionability mean? An API perspective on the EERAdata platform] || Michael Barber, Astrid Unger, AIT
|-
| 10.45 - 11:00 || Break
|-
| 11:00 - 12:00 || How FAIR and open data support a human-centered digitization || Valeria Jana Schwanitz, HVL
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 13:45 || 4 Breakout Sessions: [https://eeradata-platform.eu/wiki/images/7/72/EERAdata_Presentation3.pdf Use Case-specific needs for platform services] || Moderators: Use Case Leaders
|-
| 13.45 - 15:30 || Plenary Session
* Reports from Breakout Sessions (5 mins each) and discussion (10 mins), Moderator: Manfred Paier, AIT
* Break
* Discussion about EOSC - [https://eeradata-platform.eu/wiki/images/c/c1/EERAdata_EOSC_wierling.pdf How EERAdata can collaborate with and contribute to EOSC], Moderator: August Hubert Wierling, HVL
|-
| 15:30 - 16:00 || [https://eeradata-platform.eu/wiki/images/5/56/Paier_220317_Roundup_PlatformOutlook.pdf Round-up of the Workshop; Next steps of platform implementation & closing of the workshop] || Manfred Paier, AIT
|}

WS4

2022-03-24T20:54:57Z

Manfred: /* Programme - 17 March 2022 */

'''Workshop No.4: Supporting technologies for FAIRification'''

The fourth EERAdata Workshop is a 3-day event taking place from '''Tue 15 - Thu 17 March, 2022'''. It is conceived as a hands-on workshop and discussion event complemented with external inputs given by invited contributors. Organized as a hybrid meeting, the workshop will be hosted by the AIT Austrian Institute of Technology (physical meeting in Vienna) and by the EERA Secretariat (online meeting). Given the expected pandemic-related restrictions and safety regulations, only a core group of the EERAdata project team will gather in person at the AIT. All other participants will be able to participate online upon registration.

== Objectives ==
* Explore and discuss tools that support a FAIR and open database infrastructure
* Agree on supporting technologies to be implemented, work on the community platform concept

== Read & watch aheads ==

In preperation of WS4, four Mini-Workshops where held from the 6th December 2021 to the 17th December 2021.

The content of these workshops can be found here:
[[Mini-Workshops]]

== Programme - 15 March 2022 ==
We adopt the perspective of database holders, focusing on those who are willing to create a FAIR database from scratch, following the FAIR criteria as far as possible.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 10:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Manfred Paier, AIT
|-
| 10:05 - 10:15 || Introduction to EERAdata || Valeria Jana Schwanitz (EERAdata PI), HVL
|-
| 10:15 - 11:00 || [https://eeradata-platform.eu/wiki/images/d/dc/EERAdata_BarberUnger_Presentation1.pdf A view on the EERAdata platform: supporting the FAIRification of energy research databases] || Astrid Unger, Michael Barber, AIT
|-
| 11:00 - 12:00 || FAIRifying a database: Experience with the COMETS FAIR database (Use Case 2) || August Hubert Wierling (EERAdata Co-PI), HVL
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 14:30 || EnergieAtlas: Scenario development with geo-referenced data for (electrical) energy applications || Stefan Übermasser, Fabian Leimgruber, AIT
|-
| 14.30 - 14:45 || Break
|-
| 14:45 - 16:00 || A focus on FAIR data needs: design of a survey questionnaire || Aleksandra Zgórska, GIG
|-
|}

== Programme - 16 March 2022 ==

We adopt the perspective of database users who encounter a non-FAIR database and intend to improve on the FAIR status of the database to increase visibility and reuse potential.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 09:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Demet Suna, AIT
|-
| 09:00 - 10:00 || Managing multi-model scenario ensembles for climate change & energy systems transition:
Lessons and insights from the IPCC process and Horizon 2020 projects https://doi.org/10.5281/zenodo.6361259
|| Daniel Huppmann, IIASA
|-
| 10.00 - 10:15 || Break
|-
| 10:15 - 11:00 || [[Media:220316-Costanzo-Demir-EERAData-ENEA-IUE.pdf|FAIR Platforms? Experience with the European Building Stock Observatory]] / [[Media:220316-Filippi-Slides-on-metadata.pdf|BuiltHub analysis of BSO metadata]] || Ezilda Costanzo, ENEA; Muhittin Demir, IUE / Ulrich Filippi Oberegger, EURAC
|-
| 11:00 - 12:00 || [https://eeradata-platform.eu/wiki/images/1/1a/EERAdata_UC1_Working_Session.pdf Use Case Working Session: Workflows and tools for buildings efficiency data] || Moderation: Astrid Unger, AIT
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 14:00 || Use Case Working Session: Workflows and tools for energy materials data || Moderation: Astrid Unger, AIT
|-
| 14.00 - 14:15 || Break
|-
| 14:15 - 15:15 || Use Case Working Session: Workflows and tools for energy efficiency policies || Moderation: Astrid Unger, AIT
|-
| 15:15 - 16:00 || [https://eeradata-platform.eu/wiki/images/c/c6/MURAL_Results_.pdf Plenary Discussion: Use Case-specific needs and cross-Use-Case learning potentials] || Moderation: Michael Barber, AIT
|-
|}

== Programme - 17 March 2022 ==
We focus on machine actionability of databases, comprising a short crash course in APIs, what they are, why machines need them, and how to use them as an energy data scientist.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 09:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Manfred Paier, AIT
|-
| 09:00 - 10:00 || Building an infrastructure integrating data and service for the humanities: Experience from the RISIS Core Facility || Philippe Breucker, Univ. Gustave Eiffel
|-
| 10:00 - 10:45 || [https://eeradata-platform.eu/wiki/images/f/f8/EERAdata_BarberUnger_Presentation2.pdf What does machine-actionability mean? An API perspective on the EERAdata platform] || Michael Barber, Astrid Unger, AIT
|-
| 10.45 - 11:00 || Break
|-
| 11:00 - 12:00 || How FAIR and open data support a human-centered digitization || Valeria Jana Schwanitz, HVL
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 13:45 || 4 Breakout Sessions: [https://eeradata-platform.eu/wiki/images/7/72/EERAdata_Presentation3.pdf Use Case-specific needs for platform services] || Moderators: Use Case Leaders (tbc.)
|-
| 13.45 - 15:30 || Plenary Session
* Reports from Breakout Sessions (5 mins each) and discussion (10 mins), Moderator: Manfred Paier, AIT
* Break
* Discussion about EOSC - [https://eeradata-platform.eu/wiki/images/c/c1/EERAdata_EOSC_wierling.pdf How EERAdata can collaborate with and contribute to EOSC], Moderator: August Hubert Wierling, HVL
|-
| 15:30 - 16:00 || [https://eeradata-platform.eu/wiki/images/5/56/Paier_220317_Roundup_PlatformOutlook.pdf Round-up of the Workshop; Next steps of platform implementation & closing of the workshop] || Manfred Paier, AIT
|}

File:EERAdata BarberUnger Presentation2.pdf

2022-03-24T20:53:44Z

Manfred:

WS4

2022-03-24T20:52:36Z

Manfred: /* Programme - 15 March 2022 */

'''Workshop No.4: Supporting technologies for FAIRification'''

The fourth EERAdata Workshop is a 3-day event taking place from '''Tue 15 - Thu 17 March, 2022'''. It is conceived as a hands-on workshop and discussion event complemented with external inputs given by invited contributors. Organized as a hybrid meeting, the workshop will be hosted by the AIT Austrian Institute of Technology (physical meeting in Vienna) and by the EERA Secretariat (online meeting). Given the expected pandemic-related restrictions and safety regulations, only a core group of the EERAdata project team will gather in person at the AIT. All other participants will be able to participate online upon registration.

== Objectives ==
* Explore and discuss tools that support a FAIR and open database infrastructure
* Agree on supporting technologies to be implemented, work on the community platform concept

== Read & watch aheads ==

In preperation of WS4, four Mini-Workshops where held from the 6th December 2021 to the 17th December 2021.

The content of these workshops can be found here:
[[Mini-Workshops]]

== Programme - 15 March 2022 ==
We adopt the perspective of database holders, focusing on those who are willing to create a FAIR database from scratch, following the FAIR criteria as far as possible.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 10:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Manfred Paier, AIT
|-
| 10:05 - 10:15 || Introduction to EERAdata || Valeria Jana Schwanitz (EERAdata PI), HVL
|-
| 10:15 - 11:00 || [https://eeradata-platform.eu/wiki/images/d/dc/EERAdata_BarberUnger_Presentation1.pdf A view on the EERAdata platform: supporting the FAIRification of energy research databases] || Astrid Unger, Michael Barber, AIT
|-
| 11:00 - 12:00 || FAIRifying a database: Experience with the COMETS FAIR database (Use Case 2) || August Hubert Wierling (EERAdata Co-PI), HVL
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 14:30 || EnergieAtlas: Scenario development with geo-referenced data for (electrical) energy applications || Stefan Übermasser, Fabian Leimgruber, AIT
|-
| 14.30 - 14:45 || Break
|-
| 14:45 - 16:00 || A focus on FAIR data needs: design of a survey questionnaire || Aleksandra Zgórska, GIG
|-
|}

== Programme - 16 March 2022 ==

We adopt the perspective of database users who encounter a non-FAIR database and intend to improve on the FAIR status of the database to increase visibility and reuse potential.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 09:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Demet Suna, AIT
|-
| 09:00 - 10:00 || Managing multi-model scenario ensembles for climate change & energy systems transition:
Lessons and insights from the IPCC process and Horizon 2020 projects https://doi.org/10.5281/zenodo.6361259
|| Daniel Huppmann, IIASA
|-
| 10.00 - 10:15 || Break
|-
| 10:15 - 11:00 || [[Media:220316-Costanzo-Demir-EERAData-ENEA-IUE.pdf|FAIR Platforms? Experience with the European Building Stock Observatory]] / [[Media:220316-Filippi-Slides-on-metadata.pdf|BuiltHub analysis of BSO metadata]] || Ezilda Costanzo, ENEA; Muhittin Demir, IUE / Ulrich Filippi Oberegger, EURAC
|-
| 11:00 - 12:00 || [https://eeradata-platform.eu/wiki/images/1/1a/EERAdata_UC1_Working_Session.pdf Use Case Working Session: Workflows and tools for buildings efficiency data] || Moderation: Astrid Unger, AIT
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 14:00 || Use Case Working Session: Workflows and tools for energy materials data || Moderation: Astrid Unger, AIT
|-
| 14.00 - 14:15 || Break
|-
| 14:15 - 15:15 || Use Case Working Session: Workflows and tools for energy efficiency policies || Moderation: Astrid Unger, AIT
|-
| 15:15 - 16:00 || [https://eeradata-platform.eu/wiki/images/c/c6/MURAL_Results_.pdf Plenary Discussion: Use Case-specific needs and cross-Use-Case learning potentials] || Moderation: Michael Barber, AIT
|-
|}

== Programme - 17 March 2022 ==
We focus on machine actionability of databases, comprising a short crash course in APIs, what they are, why machines need them, and how to use them as an energy data scientist.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 09:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Manfred Paier, AIT
|-
| 09:00 - 10:00 || Building an infrastructure integrating data and service for the humanities: Experience from the RISIS Core Facility || Philippe Breucker, Univ. Gustave Eiffel
|-
| 10:00 - 10:45 || What does machine-actionability mean? An API perspective on the EERAdata platform || Michael Barber, Astrid Unger, AIT
|-
| 10.45 - 11:00 || Break
|-
| 11:00 - 12:00 || How FAIR and open data support a human-centered digitization || Valeria Jana Schwanitz, HVL
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 13:45 || 4 Breakout Sessions: [https://eeradata-platform.eu/wiki/images/7/72/EERAdata_Presentation3.pdf Use Case-specific needs for platform services] || Moderators: Use Case Leaders (tbc.)
|-
| 13.45 - 15:30 || Plenary Session
* Reports from Breakout Sessions (5 mins each) and discussion (10 mins), Moderator: Manfred Paier, AIT
* Break
* Discussion about EOSC - [https://eeradata-platform.eu/wiki/images/c/c1/EERAdata_EOSC_wierling.pdf How EERAdata can collaborate with and contribute to EOSC], Moderator: August Hubert Wierling, HVL
|-
| 15:30 - 16:00 || [https://eeradata-platform.eu/wiki/images/5/56/Paier_220317_Roundup_PlatformOutlook.pdf Round-up of the Workshop; Next steps of platform implementation & closing of the workshop] || Manfred Paier, AIT
|}

File:EERAdata BarberUnger Presentation1.pdf

2022-03-24T20:51:10Z

Manfred:

WS4

2022-03-18T18:28:22Z

Manfred: /* Programme - 17 March 2022 */

'''Workshop No.4: Supporting technologies for FAIRification'''

The fourth EERAdata Workshop is a 3-day event taking place from '''Tue 15 - Thu 17 March, 2022'''. It is conceived as a hands-on workshop and discussion event complemented with external inputs given by invited contributors. Organized as a hybrid meeting, the workshop will be hosted by the AIT Austrian Institute of Technology (physical meeting in Vienna) and by the EERA Secretariat (online meeting). Given the expected pandemic-related restrictions and safety regulations, only a core group of the EERAdata project team will gather in person at the AIT. All other participants will be able to participate online upon registration.

== Objectives ==
* Explore and discuss tools that support a FAIR and open database infrastructure
* Agree on supporting technologies to be implemented, work on the community platform concept

== Read & watch aheads ==

In preperation of WS4, four Mini-Workshops where held from the 6th December 2021 to the 17th December 2021.

The content of these workshops can be found here:
[[Mini-Workshops]]

== Programme - 15 March 2022 ==
We adopt the perspective of database holders, focusing on those who are willing to create a FAIR database from scratch, following the FAIR criteria as far as possible.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 10:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Manfred Paier, AIT
|-
| 10:05 - 10:15 || Introduction to EERAdata || Valeria Jana Schwanitz (EERAdata PI), HVL
|-
| 10:15 - 11:00 || A view on the EERAdata platform: supporting the FAIRification of energy research databases || Astrid Unger, Michael Barber, AIT
|-
| 11:00 - 12:00 || FAIRifying a database: Experience with the COMETS FAIR database (Use Case 2) || August Hubert Wierling (EERAdata Co-PI), HVL
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 14:30 || EnergieAtlas: Scenario development with geo-referenced data for (electrical) energy applications || Stefan Übermasser, Fabian Leimgruber, AIT
|-
| 14.30 - 14:45 || Break
|-
| 14:45 - 16:00 || A focus on FAIR data needs: design of a survey questionnaire || Aleksandra Zgórska, GIG
|-
|}

== Programme - 16 March 2022 ==

We adopt the perspective of database users who encounter a non-FAIR database and intend to improve on the FAIR status of the database to increase visibility and reuse potential.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 09:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Demet Suna, AIT
|-
| 09:00 - 10:00 || Managing multi-model scenario ensembles for climate change & energy systems transition:
Lessons and insights from the IPCC process and Horizon 2020 projects https://doi.org/10.5281/zenodo.6361259
|| Daniel Huppmann, IIASA
|-
| 10.00 - 10:15 || Break
|-
| 10:15 - 11:00 || [[Media:220316-Costanzo-Demir-EERAData-ENEA-IUE.pdf|FAIR Platforms? Experience with the European Building Stock Observatory]] / [[Media:220316-Filippi-Slides-on-metadata.pdf|BuiltHub analysis of BSO metadata]] || Ezilda Costanzo, ENEA; Muhittin Demir, IUE / Ulrich Filippi Oberegger, EURAC
|-
| 11:00 - 12:00 || [https://eeradata-platform.eu/wiki/images/1/1a/EERAdata_UC1_Working_Session.pdf Use Case Working Session: Workflows and tools for buildings efficiency data] || Moderation: Astrid Unger, AIT
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 14:00 || Use Case Working Session: Workflows and tools for energy materials data || Moderation: Astrid Unger, AIT
|-
| 14.00 - 14:15 || Break
|-
| 14:15 - 15:15 || Use Case Working Session: Workflows and tools for energy efficiency policies || Moderation: Astrid Unger, AIT
|-
| 15:15 - 16:00 || [https://eeradata-platform.eu/wiki/images/c/c6/MURAL_Results_.pdf Plenary Discussion: Use Case-specific needs and cross-Use-Case learning potentials] || Moderation: Michael Barber, AIT
|-
|}

== Programme - 17 March 2022 ==
We focus on machine actionability of databases, comprising a short crash course in APIs, what they are, why machines need them, and how to use them as an energy data scientist.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 09:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Manfred Paier, AIT
|-
| 09:00 - 10:00 || Building an infrastructure integrating data and service for the humanities: Experience from the RISIS Core Facility || Philippe Breucker, Univ. Gustave Eiffel
|-
| 10:00 - 10:45 || What does machine-actionability mean? An API perspective on the EERAdata platform || Michael Barber, Astrid Unger, AIT
|-
| 10.45 - 11:00 || Break
|-
| 11:00 - 12:00 || How FAIR and open data support a human-centered digitization || Valeria Jana Schwanitz, HVL
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 13:45 || 4 Breakout Sessions: [https://eeradata-platform.eu/wiki/images/7/72/EERAdata_Presentation3.pdf Use Case-specific needs for platform services] || Moderators: Use Case Leaders (tbc.)
|-
| 13.45 - 15:30 || Plenary Session
* Reports from Breakout Sessions (5 mins each) and discussion (10 mins), Moderator: Manfred Paier, AIT
* Break
* Discussion about EOSC - [https://eeradata-platform.eu/wiki/images/c/c1/EERAdata_EOSC_wierling.pdf How EERAdata can collaborate with and contribute to EOSC], Moderator: August Hubert Wierling, HVL
|-
| 15:30 - 16:00 || [https://eeradata-platform.eu/wiki/images/5/56/Paier_220317_Roundup_PlatformOutlook.pdf Round-up of the Workshop; Next steps of platform implementation & closing of the workshop] || Manfred Paier, AIT
|}

File:Paier 220317 Roundup PlatformOutlook.pdf

2022-03-18T18:27:02Z

Manfred: Manfred uploaded a new version of File:Paier 220317 Roundup PlatformOutlook.pdf

WS4

2022-03-18T18:21:16Z

Manfred: /* Programme - 17 March 2022 */

'''Workshop No.4: Supporting technologies for FAIRification'''

The fourth EERAdata Workshop is a 3-day event taking place from '''Tue 15 - Thu 17 March, 2022'''. It is conceived as a hands-on workshop and discussion event complemented with external inputs given by invited contributors. Organized as a hybrid meeting, the workshop will be hosted by the AIT Austrian Institute of Technology (physical meeting in Vienna) and by the EERA Secretariat (online meeting). Given the expected pandemic-related restrictions and safety regulations, only a core group of the EERAdata project team will gather in person at the AIT. All other participants will be able to participate online upon registration.

== Objectives ==
* Explore and discuss tools that support a FAIR and open database infrastructure
* Agree on supporting technologies to be implemented, work on the community platform concept

== Read & watch aheads ==

In preperation of WS4, four Mini-Workshops where held from the 6th December 2021 to the 17th December 2021.

The content of these workshops can be found here:
[[Mini-Workshops]]

== Programme - 15 March 2022 ==
We adopt the perspective of database holders, focusing on those who are willing to create a FAIR database from scratch, following the FAIR criteria as far as possible.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 10:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Manfred Paier, AIT
|-
| 10:05 - 10:15 || Introduction to EERAdata || Valeria Jana Schwanitz (EERAdata PI), HVL
|-
| 10:15 - 11:00 || A view on the EERAdata platform: supporting the FAIRification of energy research databases || Astrid Unger, Michael Barber, AIT
|-
| 11:00 - 12:00 || FAIRifying a database: Experience with the COMETS FAIR database (Use Case 2) || August Hubert Wierling (EERAdata Co-PI), HVL
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 14:30 || EnergieAtlas: Scenario development with geo-referenced data for (electrical) energy applications || Stefan Übermasser, Fabian Leimgruber, AIT
|-
| 14.30 - 14:45 || Break
|-
| 14:45 - 16:00 || A focus on FAIR data needs: design of a survey questionnaire || Aleksandra Zgórska, GIG
|-
|}

== Programme - 16 March 2022 ==

We adopt the perspective of database users who encounter a non-FAIR database and intend to improve on the FAIR status of the database to increase visibility and reuse potential.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 09:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Demet Suna, AIT
|-
| 09:00 - 10:00 || Managing multi-model scenario ensembles for climate change & energy systems transition:
Lessons and insights from the IPCC process and Horizon 2020 projects https://doi.org/10.5281/zenodo.6361259
|| Daniel Huppmann, IIASA
|-
| 10.00 - 10:15 || Break
|-
| 10:15 - 11:00 || [[Media:220316-Costanzo-Demir-EERAData-ENEA-IUE.pdf|FAIR Platforms? Experience with the European Building Stock Observatory]] / [[Media:220316-Filippi-Slides-on-metadata.pdf|BuiltHub analysis of BSO metadata]] || Ezilda Costanzo, ENEA; Muhittin Demir, IUE / Ulrich Filippi Oberegger, EURAC
|-
| 11:00 - 12:00 || [https://eeradata-platform.eu/wiki/images/1/1a/EERAdata_UC1_Working_Session.pdf Use Case Working Session: Workflows and tools for buildings efficiency data] || Moderation: Astrid Unger, AIT
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 14:00 || Use Case Working Session: Workflows and tools for energy materials data || Moderation: Astrid Unger, AIT
|-
| 14.00 - 14:15 || Break
|-
| 14:15 - 15:15 || Use Case Working Session: Workflows and tools for energy efficiency policies || Moderation: Astrid Unger, AIT
|-
| 15:15 - 16:00 || [https://eeradata-platform.eu/wiki/images/c/c6/MURAL_Results_.pdf Plenary Discussion: Use Case-specific needs and cross-Use-Case learning potentials] || Moderation: Michael Barber, AIT
|-
|}

== Programme - 17 March 2022 ==
We focus on machine actionability of databases, comprising a short crash course in APIs, what they are, why machines need them, and how to use them as an energy data scientist.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 09:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Manfred Paier, AIT
|-
| 09:00 - 10:00 || Building an infrastructure integrating data and service for the humanities: Experience from the RISIS Core Facility || Philippe Breucker, Univ. Gustave Eiffel
|-
| 10:00 - 10:45 || What does machine-actionability mean? An API perspective on the EERAdata platform || Michael Barber, Astrid Unger, AIT
|-
| 10.45 - 11:00 || Break
|-
| 11:00 - 12:00 || How FAIR and open data support a human-centered digitization || Valeria Jana Schwanitz, HVL
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 13:45 || 4 Breakout Sessions: [https://eeradata-platform.eu/wiki/images/7/72/EERAdata_Presentation3.pdf Use Case-specific needs for platform services] || Moderators: Use Case Leaders (tbc.)
|-
| 13.45 - 15:30 || Plenary Session
* Reports from Breakout Sessions (5 mins each) and discussion (10 mins), Moderator: Manfred Paier, AIT
* Break
* Discussion about EOSC - [https://eeradata-platform.eu/wiki/images/c/c1/EERAdata_EOSC_wierling.pdf How EERAdata can collaborate with and contribute to EOSC], Moderator: August Hubert Wierling, HVL
|-
| 15:30 - 16:00 || [[Media:Paier_220317_Roundup_PlatformOutlook.pdf | Round-up of the Workshop; Next steps of platform implementation & closing of the workshop]] || Manfred Paier, AIT
|}

File:EERAdata Presentation3.pdf

2022-03-18T18:17:54Z

Manfred:

WS4

2022-03-18T18:14:47Z

Manfred: /* Programme - 16 March 2022 */

'''Workshop No.4: Supporting technologies for FAIRification'''

The fourth EERAdata Workshop is a 3-day event taking place from '''Tue 15 - Thu 17 March, 2022'''. It is conceived as a hands-on workshop and discussion event complemented with external inputs given by invited contributors. Organized as a hybrid meeting, the workshop will be hosted by the AIT Austrian Institute of Technology (physical meeting in Vienna) and by the EERA Secretariat (online meeting). Given the expected pandemic-related restrictions and safety regulations, only a core group of the EERAdata project team will gather in person at the AIT. All other participants will be able to participate online upon registration.

== Objectives ==
* Explore and discuss tools that support a FAIR and open database infrastructure
* Agree on supporting technologies to be implemented, work on the community platform concept

== Read & watch aheads ==

In preperation of WS4, four Mini-Workshops where held from the 6th December 2021 to the 17th December 2021.

The content of these workshops can be found here:
[[Mini-Workshops]]

== Programme - 15 March 2022 ==
We adopt the perspective of database holders, focusing on those who are willing to create a FAIR database from scratch, following the FAIR criteria as far as possible.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 10:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Manfred Paier, AIT
|-
| 10:05 - 10:15 || Introduction to EERAdata || Valeria Jana Schwanitz (EERAdata PI), HVL
|-
| 10:15 - 11:00 || A view on the EERAdata platform: supporting the FAIRification of energy research databases || Astrid Unger, Michael Barber, AIT
|-
| 11:00 - 12:00 || FAIRifying a database: Experience with the COMETS FAIR database (Use Case 2) || August Hubert Wierling (EERAdata Co-PI), HVL
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 14:30 || EnergieAtlas: Scenario development with geo-referenced data for (electrical) energy applications || Stefan Übermasser, Fabian Leimgruber, AIT
|-
| 14.30 - 14:45 || Break
|-
| 14:45 - 16:00 || A focus on FAIR data needs: design of a survey questionnaire || Aleksandra Zgórska, GIG
|-
|}

== Programme - 16 March 2022 ==

We adopt the perspective of database users who encounter a non-FAIR database and intend to improve on the FAIR status of the database to increase visibility and reuse potential.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 09:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Demet Suna, AIT
|-
| 09:00 - 10:00 || Managing multi-model scenario ensembles for climate change & energy systems transition:
Lessons and insights from the IPCC process and Horizon 2020 projects https://doi.org/10.5281/zenodo.6361259
|| Daniel Huppmann, IIASA
|-
| 10.00 - 10:15 || Break
|-
| 10:15 - 11:00 || [[Media:220316-Costanzo-Demir-EERAData-ENEA-IUE.pdf|FAIR Platforms? Experience with the European Building Stock Observatory]] / [[Media:220316-Filippi-Slides-on-metadata.pdf|BuiltHub analysis of BSO metadata]] || Ezilda Costanzo, ENEA; Muhittin Demir, IUE / Ulrich Filippi Oberegger, EURAC
|-
| 11:00 - 12:00 || [https://eeradata-platform.eu/wiki/images/1/1a/EERAdata_UC1_Working_Session.pdf Use Case Working Session: Workflows and tools for buildings efficiency data] || Moderation: Astrid Unger, AIT
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 14:00 || Use Case Working Session: Workflows and tools for energy materials data || Moderation: Astrid Unger, AIT
|-
| 14.00 - 14:15 || Break
|-
| 14:15 - 15:15 || Use Case Working Session: Workflows and tools for energy efficiency policies || Moderation: Astrid Unger, AIT
|-
| 15:15 - 16:00 || [https://eeradata-platform.eu/wiki/images/c/c6/MURAL_Results_.pdf Plenary Discussion: Use Case-specific needs and cross-Use-Case learning potentials] || Moderation: Michael Barber, AIT
|-
|}

== Programme - 17 March 2022 ==
We focus on machine actionability of databases, comprising a short crash course in APIs, what they are, why machines need them, and how to use them as an energy data scientist.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 09:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Manfred Paier, AIT
|-
| 09:00 - 10:00 || Building an infrastructure integrating data and service for the humanities: Experience from the RISIS Core Facility || Philippe Breucker, Univ. Gustave Eiffel
|-
| 10:00 - 10:45 || What does machine-actionability mean? An API perspective on the EERAdata platform || Michael Barber, Astrid Unger, AIT
|-
| 10.45 - 11:00 || Break
|-
| 11:00 - 12:00 || How FAIR and open data support a human-centered digitization || Valeria Jana Schwanitz, HVL
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 13:45 || 4 Breakout Sessions: Use Case-specific needs for platform services || Moderators: Use Case Leaders (tbc.)
|-
| 13.45 - 15:30 || Plenary (incl. break)
* Reports from Breakout Sessions (5 mins each) and discussion (10 mins), Moderator: Manfred Paier, AIT
* Discussion about EOSC - [https://eeradata-platform.eu/wiki/images/c/c1/EERAdata_EOSC_wierling.pdf How EERAdata can collaborate with and contribute to EOSC], Moderator: August Hubert Wierling, HVL
|-
| 15:30 - 16:00 || [[Media:Paier_220317_Roundup_PlatformOutlook.pdf | Round-up of the Workshop; Next steps of platform implementation & closing of the workshop]] || Manfred Paier, AIT
|}

File:MURAL Results .pdf

2022-03-18T18:14:02Z

Manfred:

WS4

2022-03-18T18:13:13Z

Manfred: /* Programme - 16 March 2022 */

'''Workshop No.4: Supporting technologies for FAIRification'''

The fourth EERAdata Workshop is a 3-day event taking place from '''Tue 15 - Thu 17 March, 2022'''. It is conceived as a hands-on workshop and discussion event complemented with external inputs given by invited contributors. Organized as a hybrid meeting, the workshop will be hosted by the AIT Austrian Institute of Technology (physical meeting in Vienna) and by the EERA Secretariat (online meeting). Given the expected pandemic-related restrictions and safety regulations, only a core group of the EERAdata project team will gather in person at the AIT. All other participants will be able to participate online upon registration.

== Objectives ==
* Explore and discuss tools that support a FAIR and open database infrastructure
* Agree on supporting technologies to be implemented, work on the community platform concept

== Read & watch aheads ==

In preperation of WS4, four Mini-Workshops where held from the 6th December 2021 to the 17th December 2021.

The content of these workshops can be found here:
[[Mini-Workshops]]

== Programme - 15 March 2022 ==
We adopt the perspective of database holders, focusing on those who are willing to create a FAIR database from scratch, following the FAIR criteria as far as possible.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 10:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Manfred Paier, AIT
|-
| 10:05 - 10:15 || Introduction to EERAdata || Valeria Jana Schwanitz (EERAdata PI), HVL
|-
| 10:15 - 11:00 || A view on the EERAdata platform: supporting the FAIRification of energy research databases || Astrid Unger, Michael Barber, AIT
|-
| 11:00 - 12:00 || FAIRifying a database: Experience with the COMETS FAIR database (Use Case 2) || August Hubert Wierling (EERAdata Co-PI), HVL
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 14:30 || EnergieAtlas: Scenario development with geo-referenced data for (electrical) energy applications || Stefan Übermasser, Fabian Leimgruber, AIT
|-
| 14.30 - 14:45 || Break
|-
| 14:45 - 16:00 || A focus on FAIR data needs: design of a survey questionnaire || Aleksandra Zgórska, GIG
|-
|}

== Programme - 16 March 2022 ==

We adopt the perspective of database users who encounter a non-FAIR database and intend to improve on the FAIR status of the database to increase visibility and reuse potential.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 09:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Demet Suna, AIT
|-
| 09:00 - 10:00 || Managing multi-model scenario ensembles for climate change & energy systems transition:
Lessons and insights from the IPCC process and Horizon 2020 projects https://doi.org/10.5281/zenodo.6361259
|| Daniel Huppmann, IIASA
|-
| 10.00 - 10:15 || Break
|-
| 10:15 - 11:00 || [[Media:220316-Costanzo-Demir-EERAData-ENEA-IUE.pdf|FAIR Platforms? Experience with the European Building Stock Observatory]] / [[Media:220316-Filippi-Slides-on-metadata.pdf|BuiltHub analysis of BSO metadata]] || Ezilda Costanzo, ENEA; Muhittin Demir, IUE / Ulrich Filippi Oberegger, EURAC
|-
| 11:00 - 12:00 || [https://eeradata-platform.eu/wiki/images/1/1a/EERAdata_UC1_Working_Session.pdf Use Case Working Session: Workflows and tools for buildings efficiency data] || Moderation: Astrid Unger, AIT
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 14:00 || Use Case Working Session: Workflows and tools for energy materials data || Moderation: Astrid Unger, AIT
|-
| 14.00 - 14:15 || Break
|-
| 14:15 - 15:15 || Use Case Working Session: Workflows and tools for energy efficiency policies || Moderation: Astrid Unger, AIT
|-
| 15:15 - 16:00 || Plenary Discussion: Use Case-specific needs and cross-Use-Case learning potentials || Moderation: Michael Barber, AIT
|-
|}

== Programme - 17 March 2022 ==
We focus on machine actionability of databases, comprising a short crash course in APIs, what they are, why machines need them, and how to use them as an energy data scientist.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 09:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Manfred Paier, AIT
|-
| 09:00 - 10:00 || Building an infrastructure integrating data and service for the humanities: Experience from the RISIS Core Facility || Philippe Breucker, Univ. Gustave Eiffel
|-
| 10:00 - 10:45 || What does machine-actionability mean? An API perspective on the EERAdata platform || Michael Barber, Astrid Unger, AIT
|-
| 10.45 - 11:00 || Break
|-
| 11:00 - 12:00 || How FAIR and open data support a human-centered digitization || Valeria Jana Schwanitz, HVL
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 13:45 || 4 Breakout Sessions: Use Case-specific needs for platform services || Moderators: Use Case Leaders (tbc.)
|-
| 13.45 - 15:30 || Plenary (incl. break)
* Reports from Breakout Sessions (5 mins each) and discussion (10 mins), Moderator: Manfred Paier, AIT
* Discussion about EOSC - [https://eeradata-platform.eu/wiki/images/c/c1/EERAdata_EOSC_wierling.pdf How EERAdata can collaborate with and contribute to EOSC], Moderator: August Hubert Wierling, HVL
|-
| 15:30 - 16:00 || [[Media:Paier_220317_Roundup_PlatformOutlook.pdf | Round-up of the Workshop; Next steps of platform implementation & closing of the workshop]] || Manfred Paier, AIT
|}

File:EERAdata UC1 Working Session.pdf

2022-03-18T18:10:53Z

Manfred:

WS4

2022-03-18T18:10:36Z

Manfred: /* Programme - 16 March 2022 */

'''Workshop No.4: Supporting technologies for FAIRification'''

The fourth EERAdata Workshop is a 3-day event taking place from '''Tue 15 - Thu 17 March, 2022'''. It is conceived as a hands-on workshop and discussion event complemented with external inputs given by invited contributors. Organized as a hybrid meeting, the workshop will be hosted by the AIT Austrian Institute of Technology (physical meeting in Vienna) and by the EERA Secretariat (online meeting). Given the expected pandemic-related restrictions and safety regulations, only a core group of the EERAdata project team will gather in person at the AIT. All other participants will be able to participate online upon registration.

== Objectives ==
* Explore and discuss tools that support a FAIR and open database infrastructure
* Agree on supporting technologies to be implemented, work on the community platform concept

== Read & watch aheads ==

In preperation of WS4, four Mini-Workshops where held from the 6th December 2021 to the 17th December 2021.

The content of these workshops can be found here:
[[Mini-Workshops]]

== Programme - 15 March 2022 ==
We adopt the perspective of database holders, focusing on those who are willing to create a FAIR database from scratch, following the FAIR criteria as far as possible.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 10:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Manfred Paier, AIT
|-
| 10:05 - 10:15 || Introduction to EERAdata || Valeria Jana Schwanitz (EERAdata PI), HVL
|-
| 10:15 - 11:00 || A view on the EERAdata platform: supporting the FAIRification of energy research databases || Astrid Unger, Michael Barber, AIT
|-
| 11:00 - 12:00 || FAIRifying a database: Experience with the COMETS FAIR database (Use Case 2) || August Hubert Wierling (EERAdata Co-PI), HVL
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 14:30 || EnergieAtlas: Scenario development with geo-referenced data for (electrical) energy applications || Stefan Übermasser, Fabian Leimgruber, AIT
|-
| 14.30 - 14:45 || Break
|-
| 14:45 - 16:00 || A focus on FAIR data needs: design of a survey questionnaire || Aleksandra Zgórska, GIG
|-
|}

== Programme - 16 March 2022 ==

We adopt the perspective of database users who encounter a non-FAIR database and intend to improve on the FAIR status of the database to increase visibility and reuse potential.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 09:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Demet Suna, AIT
|-
| 09:00 - 10:00 || Managing multi-model scenario ensembles for climate change & energy systems transition:
Lessons and insights from the IPCC process and Horizon 2020 projects https://doi.org/10.5281/zenodo.6361259
|| Daniel Huppmann, IIASA
|-
| 10.00 - 10:15 || Break
|-
| 10:15 - 11:00 || [[Media:220316-Costanzo-Demir-EERAData-ENEA-IUE.pdf|FAIR Platforms? Experience with the European Building Stock Observatory]] / [[Media:220316-Filippi-Slides-on-metadata.pdf|BuiltHub analysis of BSO metadata]] || Ezilda Costanzo, ENEA; Muhittin Demir, IUE / Ulrich Filippi Oberegger, EURAC
|-
| 11:00 - 12:00 || Use Case Working Session: Workflows and tools for buildings efficiency data || Moderation: Astrid Unger, AIT
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 14:00 || Use Case Working Session: Workflows and tools for energy materials data || Moderation: Astrid Unger, AIT
|-
| 14.00 - 14:15 || Break
|-
| 14:15 - 15:15 || Use Case Working Session: Workflows and tools for energy efficiency policies || Moderation: Astrid Unger, AIT
|-
| 15:15 - 16:00 || Plenary Discussion: Use Case-specific needs and cross-Use-Case learning potentials || Moderation: Michael Barber, AIT
|-
|}

== Programme - 17 March 2022 ==
We focus on machine actionability of databases, comprising a short crash course in APIs, what they are, why machines need them, and how to use them as an energy data scientist.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 09:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Manfred Paier, AIT
|-
| 09:00 - 10:00 || Building an infrastructure integrating data and service for the humanities: Experience from the RISIS Core Facility || Philippe Breucker, Univ. Gustave Eiffel
|-
| 10:00 - 10:45 || What does machine-actionability mean? An API perspective on the EERAdata platform || Michael Barber, Astrid Unger, AIT
|-
| 10.45 - 11:00 || Break
|-
| 11:00 - 12:00 || How FAIR and open data support a human-centered digitization || Valeria Jana Schwanitz, HVL
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 13:45 || 4 Breakout Sessions: Use Case-specific needs for platform services || Moderators: Use Case Leaders (tbc.)
|-
| 13.45 - 15:30 || Plenary (incl. break)
* Reports from Breakout Sessions (5 mins each) and discussion (10 mins), Moderator: Manfred Paier, AIT
* Discussion about EOSC - [https://eeradata-platform.eu/wiki/images/c/c1/EERAdata_EOSC_wierling.pdf How EERAdata can collaborate with and contribute to EOSC], Moderator: August Hubert Wierling, HVL
|-
| 15:30 - 16:00 || [[Media:Paier_220317_Roundup_PlatformOutlook.pdf | Round-up of the Workshop; Next steps of platform implementation & closing of the workshop]] || Manfred Paier, AIT
|}

WS4

2022-03-18T17:43:45Z

Manfred: /* Programme - 17 March 2022 */

'''Workshop No.4: Supporting technologies for FAIRification'''

The fourth EERAdata Workshop is a 3-day event taking place from '''Tue 15 - Thu 17 March, 2022'''. It is conceived as a hands-on workshop and discussion event complemented with external inputs given by invited contributors. Organized as a hybrid meeting, the workshop will be hosted by the AIT Austrian Institute of Technology (physical meeting in Vienna) and by the EERA Secretariat (online meeting). Given the expected pandemic-related restrictions and safety regulations, only a core group of the EERAdata project team will gather in person at the AIT. All other participants will be able to participate online upon registration.

== Objectives ==
* Explore and discuss tools that support a FAIR and open database infrastructure
* Agree on supporting technologies to be implemented, work on the community platform concept

== Read & watch aheads ==

In preperation of WS4, four Mini-Workshops where held from the 6th December 2021 to the 17th December 2021.

The content of these workshops can be found here:
[[Mini-Workshops]]

== Programme - 15 March 2022 ==
We adopt the perspective of database holders, focusing on those who are willing to create a FAIR database from scratch, following the FAIR criteria as far as possible.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 10:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Manfred Paier, AIT
|-
| 10:05 - 10:15 || Introduction to EERAdata || Valeria Jana Schwanitz (EERAdata PI), HVL
|-
| 10:15 - 11:00 || A view on the EERAdata platform: supporting the FAIRification of energy research databases || Astrid Unger, Michael Barber, AIT
|-
| 11:00 - 12:00 || FAIRifying a database: Experience with the COMETS FAIR database (Use Case 2) || August Hubert Wierling (EERAdata Co-PI), HVL
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 14:30 || EnergieAtlas: Scenario development with geo-referenced data for (electrical) energy applications || Stefan Übermasser, Fabian Leimgruber, AIT
|-
| 14.30 - 14:45 || Break
|-
| 14:45 - 16:00 || A focus on FAIR data needs: design of a survey questionnaire || Aleksandra Zgórska, GIG
|-
|}

== Programme - 16 March 2022 ==

We adopt the perspective of database users who encounter a non-FAIR database and intend to improve on the FAIR status of the database to increase visibility and reuse potential.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 09:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Demet Suna, AIT
|-
| 09:00 - 10:00 || Managing multi-model scenario ensembles for climate change & energy systems transition:
Lessons and insights from the IPCC process and Horizon 2020 projects https://doi.org/10.5281/zenodo.6361259
|| Daniel Huppmann, IIASA
|-
| 10.00 - 10:15 || Break
|-
| 10:15 - 11:00 || [[Media:220316-Costanzo-Demir-EERAData-ENEA-IUE.pdf|FAIR Platforms? Experience with the European Building Stock Observatory]] / [[Media:220316-Filippi-Slides-on-metadata.pdf|BuiltHub analysis of BSO metadata]] || Ezilda Costanzo, ENEA; Muhittin Demir, IUE / Ulrich Filippi Oberegger, EURAC
|-
| 11:00 - 12:00 || Use Case 1 Working Session: Workflows and tools for buildings efficiency data || Moderation: Astrid Unger, AIT
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 14:00 || Use Case 3 Working Session: Workflows and tools for energy materials data || Moderation: Astrid Unger, AIT
|-
| 14.00 - 14:15 || Break
|-
| 14:15 - 15:15 || Use Case 4 Working Session: Workflows and tools for energy efficiency policies || Moderation: Astrid Unger, AIT
|-
| 15:15 - 16:00 || Plenary Discussion: Use Case-specific needs and cross-Use-Case learning potentials || Moderation: Michael Barber, AIT
|-
|}

== Programme - 17 March 2022 ==
We focus on machine actionability of databases, comprising a short crash course in APIs, what they are, why machines need them, and how to use them as an energy data scientist.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 09:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Manfred Paier, AIT
|-
| 09:00 - 10:00 || Building an infrastructure integrating data and service for the humanities: Experience from the RISIS Core Facility || Philippe Breucker, Univ. Gustave Eiffel
|-
| 10:00 - 10:45 || What does machine-actionability mean? An API perspective on the EERAdata platform || Michael Barber, Astrid Unger, AIT
|-
| 10.45 - 11:00 || Break
|-
| 11:00 - 12:00 || How FAIR and open data support a human-centered digitization || Valeria Jana Schwanitz, HVL
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 13:45 || 4 Breakout Sessions: Use Case-specific needs for platform services || Moderators: Use Case Leaders (tbc.)
|-
| 13.45 - 15:30 || Plenary (incl. break)
* Reports from Breakout Sessions (5 mins each) and discussion (10 mins), Moderator: Manfred Paier, AIT
* Discussion about EOSC - [https://eeradata-platform.eu/wiki/images/c/c1/EERAdata_EOSC_wierling.pdf How EERAdata can collaborate with and contribute to EOSC], Moderator: August Hubert Wierling, HVL
|-
| 15:30 - 16:00 || [[Media:Paier_220317_Roundup_PlatformOutlook.pdf | Round-up of the Workshop; Next steps of platform implementation & closing of the workshop]] || Manfred Paier, AIT
|}

File:Paier 220317 Roundup PlatformOutlook.pdf

2022-03-18T17:39:30Z

Manfred:

WS4

2022-03-18T17:13:18Z

Manfred: /* Programme - 16 March 2022 */

'''Workshop No.4: Supporting technologies for FAIRification'''

The fourth EERAdata Workshop is a 3-day event taking place from '''Tue 15 - Thu 17 March, 2022'''. It is conceived as a hands-on workshop and discussion event complemented with external inputs given by invited contributors. Organized as a hybrid meeting, the workshop will be hosted by the AIT Austrian Institute of Technology (physical meeting in Vienna) and by the EERA Secretariat (online meeting). Given the expected pandemic-related restrictions and safety regulations, only a core group of the EERAdata project team will gather in person at the AIT. All other participants will be able to participate online upon registration.

== Objectives ==
* Explore and discuss tools that support a FAIR and open database infrastructure
* Agree on supporting technologies to be implemented, work on the community platform concept

== Read & watch aheads ==

In preperation of WS4, four Mini-Workshops where held from the 6th December 2021 to the 17th December 2021.

The content of these workshops can be found here:
[[Mini-Workshops]]

== Programme - 15 March 2022 ==
We adopt the perspective of database holders, focusing on those who are willing to create a FAIR database from scratch, following the FAIR criteria as far as possible.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 10:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Manfred Paier, AIT
|-
| 10:05 - 10:15 || Introduction to EERAdata || Valeria Jana Schwanitz (EERAdata PI), HVL
|-
| 10:15 - 11:00 || A view on the EERAdata platform: supporting the FAIRification of energy research databases || Astrid Unger, Michael Barber, AIT
|-
| 11:00 - 12:00 || FAIRifying a database: Experience with the COMETS FAIR database (Use Case 2) || August Hubert Wierling (EERAdata Co-PI), HVL
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 14:30 || EnergieAtlas: Scenario development with geo-referenced data for (electrical) energy applications || Stefan Übermasser, Fabian Leimgruber, AIT
|-
| 14.30 - 14:45 || Break
|-
| 14:45 - 16:00 || A focus on FAIR data needs: design of a survey questionnaire || Aleksandra Zgórska, GIG
|-
|}

== Programme - 16 March 2022 ==

We adopt the perspective of database users who encounter a non-FAIR database and intend to improve on the FAIR status of the database to increase visibility and reuse potential.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 09:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Demet Suna, AIT
|-
| 09:00 - 10:00 || Managing multi-model scenario ensembles for climate change & energy systems transition:
Lessons and insights from the IPCC process and Horizon 2020 projects https://doi.org/10.5281/zenodo.6361259
|| Daniel Huppmann, IIASA
|-
| 10.00 - 10:15 || Break
|-
| 10:15 - 11:00 || [[Media:220316-Costanzo-Demir-EERAData-ENEA-IUE.pdf|FAIR Platforms? Experience with the European Building Stock Observatory]] / [[Media:220316-Filippi-Slides-on-metadata.pdf|BuiltHub analysis of BSO metadata]] || Ezilda Costanzo, ENEA; Muhittin Demir, IUE / Ulrich Filippi Oberegger, EURAC
|-
| 11:00 - 12:00 || Use Case 1 Working Session: Workflows and tools for buildings efficiency data || Moderation: Astrid Unger, AIT
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 14:00 || Use Case 3 Working Session: Workflows and tools for energy materials data || Moderation: Astrid Unger, AIT
|-
| 14.00 - 14:15 || Break
|-
| 14:15 - 15:15 || Use Case 4 Working Session: Workflows and tools for energy efficiency policies || Moderation: Astrid Unger, AIT
|-
| 15:15 - 16:00 || Plenary Discussion: Use Case-specific needs and cross-Use-Case learning potentials || Moderation: Michael Barber, AIT
|-
|}

== Programme - 17 March 2022 ==
We focus on machine actionability of databases, comprising a short crash course in APIs, what they are, why machines need them, and how to use them as an energy data scientist.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 09:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Manfred Paier, AIT
|-
| 09:00 - 10:00 || Building an infrastructure integrating data and service for the humanities: Experience from the RISIS Core Facility || Philippe Breucker, Univ. Gustave Eiffel
|-
| 10:00 - 10:45 || What does machine-actionability mean? An API perspective on the EERAdata platform || Michael Barber, Astrid Unger, AIT
|-
| 10.45 - 11:00 || Break
|-
| 11:00 - 12:00 || How FAIR and open data support a human-centered digitization || Valeria Jana Schwanitz, HVL
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 13:45 || 4 Breakout Sessions: Use Case-specific needs for platform services || Moderators: Use Case Leaders (tbc.)
|-
| 13.45 - 15:30 || Plenary (incl. break)
* Reports from Breakout Sessions (5 mins each) and discussion (10 mins), Moderator: Manfred Paier, AIT
* Discussion about EOSC - [https://eeradata-platform.eu/wiki/images/c/c1/EERAdata_EOSC_wierling.pdf How EERAdata can collaborate with and contribute to EOSC], Moderator: August Hubert Wierling, HVL
|-
| 15:30 - 16:00 || Round-up of the Workshop; Next steps of platform implementation & closing of the workshop || Manfred Paier, AIT
|}

WS4

2022-03-18T17:01:07Z

Manfred: /* Programme - 16 March 2022 */

'''Workshop No.4: Supporting technologies for FAIRification'''

The fourth EERAdata Workshop is a 3-day event taking place from '''Tue 15 - Thu 17 March, 2022'''. It is conceived as a hands-on workshop and discussion event complemented with external inputs given by invited contributors. Organized as a hybrid meeting, the workshop will be hosted by the AIT Austrian Institute of Technology (physical meeting in Vienna) and by the EERA Secretariat (online meeting). Given the expected pandemic-related restrictions and safety regulations, only a core group of the EERAdata project team will gather in person at the AIT. All other participants will be able to participate online upon registration.

== Objectives ==
* Explore and discuss tools that support a FAIR and open database infrastructure
* Agree on supporting technologies to be implemented, work on the community platform concept

== Read & watch aheads ==

In preperation of WS4, four Mini-Workshops where held from the 6th December 2021 to the 17th December 2021.

The content of these workshops can be found here:
[[Mini-Workshops]]

== Programme - 15 March 2022 ==
We adopt the perspective of database holders, focusing on those who are willing to create a FAIR database from scratch, following the FAIR criteria as far as possible.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 10:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Manfred Paier, AIT
|-
| 10:05 - 10:15 || Introduction to EERAdata || Valeria Jana Schwanitz (EERAdata PI), HVL
|-
| 10:15 - 11:00 || A view on the EERAdata platform: supporting the FAIRification of energy research databases || Astrid Unger, Michael Barber, AIT
|-
| 11:00 - 12:00 || FAIRifying a database: Experience with the COMETS FAIR database (Use Case 2) || August Hubert Wierling (EERAdata Co-PI), HVL
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 14:30 || EnergieAtlas: Scenario development with geo-referenced data for (electrical) energy applications || Stefan Übermasser, Fabian Leimgruber, AIT
|-
| 14.30 - 14:45 || Break
|-
| 14:45 - 16:00 || A focus on FAIR data needs: design of a survey questionnaire || Aleksandra Zgórska, GIG
|-
|}

== Programme - 16 March 2022 ==

We adopt the perspective of database users who encounter a non-FAIR database and intend to improve on the FAIR status of the database to increase visibility and reuse potential.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 09:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Demet Suna, AIT
|-
| 09:00 - 10:00 || Managing multi-model scenario ensembles for climate change & energy systems transition:
Lessons and insights from the IPCC process and Horizon 2020 projects
|| Daniel Huppmann, IIASA
|-
| 10.00 - 10:15 || Break
|-
| 10:15 - 11:00 || [[Media:220316-Costanzo-Demir-EERAData-ENEA-IUE.pdf|FAIR Platforms? Experience with the European Building Stock Observatory]] / [[Media:220316-Filippi-Slides-on-metadata.pdf|BuiltHub analysis of BSO metadata]] || Ezilda Costanzo, ENEA; Muhittin Demir, IUE / Ulrich Filippi Oberegger, EURAC
|-
| 11:00 - 12:00 || Use Case 1 Working Session: Workflows and tools for buildings efficiency data || Moderation: Astrid Unger, AIT
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 14:00 || Use Case 3 Working Session: Workflows and tools for energy materials data || Moderation: Astrid Unger, AIT
|-
| 14.00 - 14:15 || Break
|-
| 14:15 - 15:15 || Use Case 4 Working Session: Workflows and tools for energy efficiency policies || Moderation: Astrid Unger, AIT
|-
| 15:15 - 16:00 || Plenary Discussion: Use Case-specific needs and cross-Use-Case learning potentials || Moderation: Michael Barber, AIT
|-
|}

== Programme - 17 March 2022 ==
We focus on machine actionability of databases, comprising a short crash course in APIs, what they are, why machines need them, and how to use them as an energy data scientist.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 09:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Manfred Paier, AIT
|-
| 09:00 - 10:00 || Building an infrastructure integrating data and service for the humanities: Experience from the RISIS Core Facility || Philippe Breucker, Univ. Gustave Eiffel
|-
| 10:00 - 10:45 || What does machine-actionability mean? An API perspective on the EERAdata platform || Michael Barber, Astrid Unger, AIT
|-
| 10.45 - 11:00 || Break
|-
| 11:00 - 12:00 || How FAIR and open data support a human-centered digitization || Valeria Jana Schwanitz, HVL
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 13:45 || 4 Breakout Sessions: Use Case-specific needs for platform services || Moderators: Use Case Leaders (tbc.)
|-
| 13.45 - 15:30 || Plenary (incl. break)
* Reports from Breakout Sessions (5 mins each) and discussion (10 mins), Moderator: Manfred Paier, AIT
* Discussion about EOSC - [https://eeradata-platform.eu/wiki/images/c/c1/EERAdata_EOSC_wierling.pdf How EERAdata can collaborate with and contribute to EOSC], Moderator: August Hubert Wierling, HVL
|-
| 15:30 - 16:00 || Round-up of the Workshop; Next steps of platform implementation & closing of the workshop || Manfred Paier, AIT
|}

File:220316-Filippi-Slides-on-metadata.pdf

2022-03-18T17:00:06Z

Manfred:

WS4

2022-03-18T16:58:28Z

Manfred: /* Programme - 16 March 2022 */

'''Workshop No.4: Supporting technologies for FAIRification'''

The fourth EERAdata Workshop is a 3-day event taking place from '''Tue 15 - Thu 17 March, 2022'''. It is conceived as a hands-on workshop and discussion event complemented with external inputs given by invited contributors. Organized as a hybrid meeting, the workshop will be hosted by the AIT Austrian Institute of Technology (physical meeting in Vienna) and by the EERA Secretariat (online meeting). Given the expected pandemic-related restrictions and safety regulations, only a core group of the EERAdata project team will gather in person at the AIT. All other participants will be able to participate online upon registration.

== Objectives ==
* Explore and discuss tools that support a FAIR and open database infrastructure
* Agree on supporting technologies to be implemented, work on the community platform concept

== Read & watch aheads ==

In preperation of WS4, four Mini-Workshops where held from the 6th December 2021 to the 17th December 2021.

The content of these workshops can be found here:
[[Mini-Workshops]]

== Programme - 15 March 2022 ==
We adopt the perspective of database holders, focusing on those who are willing to create a FAIR database from scratch, following the FAIR criteria as far as possible.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 10:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Manfred Paier, AIT
|-
| 10:05 - 10:15 || Introduction to EERAdata || Valeria Jana Schwanitz (EERAdata PI), HVL
|-
| 10:15 - 11:00 || A view on the EERAdata platform: supporting the FAIRification of energy research databases || Astrid Unger, Michael Barber, AIT
|-
| 11:00 - 12:00 || FAIRifying a database: Experience with the COMETS FAIR database (Use Case 2) || August Hubert Wierling (EERAdata Co-PI), HVL
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 14:30 || EnergieAtlas: Scenario development with geo-referenced data for (electrical) energy applications || Stefan Übermasser, Fabian Leimgruber, AIT
|-
| 14.30 - 14:45 || Break
|-
| 14:45 - 16:00 || A focus on FAIR data needs: design of a survey questionnaire || Aleksandra Zgórska, GIG
|-
|}

== Programme - 16 March 2022 ==

We adopt the perspective of database users who encounter a non-FAIR database and intend to improve on the FAIR status of the database to increase visibility and reuse potential.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 09:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Demet Suna, AIT
|-
| 09:00 - 10:00 || Managing multi-model scenario ensembles for climate change & energy systems transition:
Lessons and insights from the IPCC process and Horizon 2020 projects
|| Daniel Huppmann, IIASA
|-
| 10.00 - 10:15 || Break
|-
| 10:15 - 11:00 || [[Media:220316-Costanzo-Demir-EERAData-ENEA-IUE.pdf|FAIR Platforms? Experience with the European Building Stock Observatory]] / BuiltHub analysis of BSO metadata || Ezilda Costanzo, ENEA; Muhittin Demir, IUE / Ulrich Filippi Oberegger, EURAC
|-
| 11:00 - 12:00 || Use Case 1 Working Session: Workflows and tools for buildings efficiency data || Moderation: Astrid Unger, AIT
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 14:00 || Use Case 3 Working Session: Workflows and tools for energy materials data || Moderation: Astrid Unger, AIT
|-
| 14.00 - 14:15 || Break
|-
| 14:15 - 15:15 || Use Case 4 Working Session: Workflows and tools for energy efficiency policies || Moderation: Astrid Unger, AIT
|-
| 15:15 - 16:00 || Plenary Discussion: Use Case-specific needs and cross-Use-Case learning potentials || Moderation: Michael Barber, AIT
|-
|}

== Programme - 17 March 2022 ==
We focus on machine actionability of databases, comprising a short crash course in APIs, what they are, why machines need them, and how to use them as an energy data scientist.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 09:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Manfred Paier, AIT
|-
| 09:00 - 10:00 || Building an infrastructure integrating data and service for the humanities: Experience from the RISIS Core Facility || Philippe Breucker, Univ. Gustave Eiffel
|-
| 10:00 - 10:45 || What does machine-actionability mean? An API perspective on the EERAdata platform || Michael Barber, Astrid Unger, AIT
|-
| 10.45 - 11:00 || Break
|-
| 11:00 - 12:00 || How FAIR and open data support a human-centered digitization || Valeria Jana Schwanitz, HVL
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 13:45 || 4 Breakout Sessions: Use Case-specific needs for platform services || Moderators: Use Case Leaders (tbc.)
|-
| 13.45 - 15:30 || Plenary (incl. break)
* Reports from Breakout Sessions (5 mins each) and discussion (10 mins), Moderator: Manfred Paier, AIT
* Discussion about EOSC - [https://eeradata-platform.eu/wiki/images/c/c1/EERAdata_EOSC_wierling.pdf How EERAdata can collaborate with and contribute to EOSC], Moderator: August Hubert Wierling, HVL
|-
| 15:30 - 16:00 || Round-up of the Workshop; Next steps of platform implementation & closing of the workshop || Manfred Paier, AIT
|}

WS4

2022-03-18T16:57:14Z

Manfred: /* Programme - 16 March 2022 */

'''Workshop No.4: Supporting technologies for FAIRification'''

The fourth EERAdata Workshop is a 3-day event taking place from '''Tue 15 - Thu 17 March, 2022'''. It is conceived as a hands-on workshop and discussion event complemented with external inputs given by invited contributors. Organized as a hybrid meeting, the workshop will be hosted by the AIT Austrian Institute of Technology (physical meeting in Vienna) and by the EERA Secretariat (online meeting). Given the expected pandemic-related restrictions and safety regulations, only a core group of the EERAdata project team will gather in person at the AIT. All other participants will be able to participate online upon registration.

== Objectives ==
* Explore and discuss tools that support a FAIR and open database infrastructure
* Agree on supporting technologies to be implemented, work on the community platform concept

== Read & watch aheads ==

In preperation of WS4, four Mini-Workshops where held from the 6th December 2021 to the 17th December 2021.

The content of these workshops can be found here:
[[Mini-Workshops]]

== Programme - 15 March 2022 ==
We adopt the perspective of database holders, focusing on those who are willing to create a FAIR database from scratch, following the FAIR criteria as far as possible.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 10:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Manfred Paier, AIT
|-
| 10:05 - 10:15 || Introduction to EERAdata || Valeria Jana Schwanitz (EERAdata PI), HVL
|-
| 10:15 - 11:00 || A view on the EERAdata platform: supporting the FAIRification of energy research databases || Astrid Unger, Michael Barber, AIT
|-
| 11:00 - 12:00 || FAIRifying a database: Experience with the COMETS FAIR database (Use Case 2) || August Hubert Wierling (EERAdata Co-PI), HVL
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 14:30 || EnergieAtlas: Scenario development with geo-referenced data for (electrical) energy applications || Stefan Übermasser, Fabian Leimgruber, AIT
|-
| 14.30 - 14:45 || Break
|-
| 14:45 - 16:00 || A focus on FAIR data needs: design of a survey questionnaire || Aleksandra Zgórska, GIG
|-
|}

== Programme - 16 March 2022 ==

We adopt the perspective of database users who encounter a non-FAIR database and intend to improve on the FAIR status of the database to increase visibility and reuse potential.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 09:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Demet Suna, AIT
|-
| 09:00 - 10:00 || Managing multi-model scenario ensembles for climate change & energy systems transition:
Lessons and insights from the IPCC process and Horizon 2020 projects
|| Daniel Huppmann, IIASA
|-
| 10.00 - 10:15 || Break
|-
| 10:15 - 11:00 || [[:File:220316-Costanzo-Demir-EERAData-ENEA-IUE.pdf|FAIR Platforms? Experience with the European Building Stock Observatory]] / BuiltHub analysis of BSO metadata || Ezilda Costanzo, ENEA; Muhittin Demir, IUE / Ulrich Filippi Oberegger, EURAC
|-
| 11:00 - 12:00 || Use Case 1 Working Session: Workflows and tools for buildings efficiency data || Moderation: Astrid Unger, AIT
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 14:00 || Use Case 3 Working Session: Workflows and tools for energy materials data || Moderation: Astrid Unger, AIT
|-
| 14.00 - 14:15 || Break
|-
| 14:15 - 15:15 || Use Case 4 Working Session: Workflows and tools for energy efficiency policies || Moderation: Astrid Unger, AIT
|-
| 15:15 - 16:00 || Plenary Discussion: Use Case-specific needs and cross-Use-Case learning potentials || Moderation: Michael Barber, AIT
|-
|}

== Programme - 17 March 2022 ==
We focus on machine actionability of databases, comprising a short crash course in APIs, what they are, why machines need them, and how to use them as an energy data scientist.

{| class="wikitable"
|-
!colspan="6"| <big>Morning Session 09:00 - 12:00 (CET)</big>
|-
!colspan="6"| Session Chair: Manfred Paier, AIT
|-
| 09:00 - 10:00 || Building an infrastructure integrating data and service for the humanities: Experience from the RISIS Core Facility || Philippe Breucker, Univ. Gustave Eiffel
|-
| 10:00 - 10:45 || What does machine-actionability mean? An API perspective on the EERAdata platform || Michael Barber, Astrid Unger, AIT
|-
| 10.45 - 11:00 || Break
|-
| 11:00 - 12:00 || How FAIR and open data support a human-centered digitization || Valeria Jana Schwanitz, HVL
|-
|}

'''12:00 - 13:00 Lunch Break'''

{| class="wikitable"
!colspan="6"| <big>Afternoon Session 13:00 - 16:00 (CET)</big>
|-
!colspan="6"| Session Chair: Michael Barber, AIT
|-
| 13.00 - 13:45 || 4 Breakout Sessions: Use Case-specific needs for platform services || Moderators: Use Case Leaders (tbc.)
|-
| 13.45 - 15:30 || Plenary (incl. break)
* Reports from Breakout Sessions (5 mins each) and discussion (10 mins), Moderator: Manfred Paier, AIT
* Discussion about EOSC - [https://eeradata-platform.eu/wiki/images/c/c1/EERAdata_EOSC_wierling.pdf How EERAdata can collaborate with and contribute to EOSC], Moderator: August Hubert Wierling, HVL
|-
| 15:30 - 16:00 || Round-up of the Workshop; Next steps of platform implementation & closing of the workshop || Manfred Paier, AIT
|}

File:220316-Costanzo-Demir-EERAData-ENEA-IUE.pdf

2022-03-18T16:49:58Z

Manfred:

WS2

2020-11-18T11:58:12Z

Manfred: /* Agenda and notes */

The second workshop of EERAdata is organized as an online webinar and hackathon during November, 30, to December, 4th, 2020. It is dedicated to metadata.

== Objective ==
* Discuss and develop metadata standards for FAIR and open data in the low carbon energy research community. '''The focus is on the link between metadata and how humans explore data.'''
* Identify gaps and needs that hinder their standardized realization and implementation.
* Jointly work on a community paper and/or join the discussions in use cases. We start with a commented and revised draft. [https://docs.google.com/document/d/1oS_t7yb9_xDM-RYDPTd48B7O9Sq9dXiz3ibUO34G7oA/edit?usp=sharing Link to draft of the community paper]

[[File:EERAdata community paper.png|thumb|Workshop concept of EERAdata]]

== Read & watch aheads ==

To prepare for the paper writing hackathon, please participate in the preparatory 'Briefing Workshop' or watch the recorded videos. The workshop took place Thursday, 5th of November, 10-12 CET. The workshop introduced recent work on metadata and outlined the tasks and procedures on how to join the writing team for the community.

{| class="wikitable"
|-
! Agenda & Material of Briefing Workshop !! Full video recording: [https://kaltura.hvl.no/media/EERAdata+Workshop+to+prepare+for+the+hackathon/0_xxdhcjl7 link]
|-
|Slides: [[File:EERAdata_WS2_wierling.pdf|80px|thumb|none]] || Introduction & Talk ''Advancing metadata standards for low carbon energy research'', August Wierling, HVL.
|-
| Slides: [[File:EERAdata KIT Suess.pdf|80px|thumb|none]] || ''Overview of the Helmholtz Metadata Collaboration Platform'', Wolfgang Süß, KIT.
|-
| Slides: [[File:Talk_Celino_ENEA.pdf|80px|thumb|none]] || ''Metadata in materials: The new path forward'', Massimo Celino, ENEA.
|-
| Chat Notes: [[File:EERAdata chat notes.pdf|80px|thumb|none]] || ''Panel discussion with Q&A''
|-
| Slides[[File:WS2 prep schwanitz.pdf|80px|thumb|none]] || ''Briefing for EERAdata paper writing workshop (Who? How? When? What?)'', Valeria Jana Schwanitz, EERAdata PI.
|}

* Invitation to [https://docs.google.com/document/d/1oS_t7yb9_xDM-RYDPTd48B7O9Sq9dXiz3ibUO34G7oA/edit# comment the draft] before the writing workshop
* Suggested read on the history of metadata
Metadata - [https://www.springer.com/gp/book/9783319408910 Shaping Knowledge from Antiquity to the Semantic Web by Richard Gartner]

== Join us and collaborate interactively! ==
=== Becoming a co-author ===
Workshop participants are invited to become co-authors of the planned community paper.

'''How to join the team writing the community paper?'''
Briefing is provided during the preparatory workshop (also recorded). Includes recommendation for read and watch aheads.

The community paper addresses 3 key questions:
* Q1: How to align mental models of those searching for data with navigation along metadata? What is specific to the energy domain?
* Q2: What consequences for the construction of domain-specific metadata follow? and how can they be dynamically updated?
* Q3: What are the recommendations to the low carbon community?

The envisaged output of the paper is:
* A community-reviewed draft for a low carbon energy ontology in support of metadata,
* Metadata suggestion cards for low carbon energy researchers,
* Recommendations on how to proceed.

'''Invitation to [https://docs.google.com/document/d/1oS_t7yb9_xDM-RYDPTd48B7O9Sq9dXiz3ibUO34G7oA/edit# comment the draft] before the writing workshop''', e.g.:
* Review of key questions,
* Suggestions of literature, illustrative cases, metadata perspectives & issues,
* Suggestions to any section (e.g., Introduction, Method, Discussion of Results, Outlook)
* Adding snippets of texts,

'''Any other idea is welcome!'''

Using above prior comments & contributions provided by 23.11.2020, the EERAdata team will revise the draft before the workshop starts. During the workshop, the discussion & writing of the paper continues in small writing teams. A prior registration to teams is therefore recommended. However, teams can change anytime. The EERAdata team is strongly interested in inviting a large group of contributing authors. It is not only in the interest of the community project as such, but it increases the credibility of the main output - the draft (or road towards) a low carbon energy ontology in support of metadata”.

'''Co-authorship is granted to active participants of the EERAdata workshop as well as to other contributors to the community paper.'''

=== EERAdata wiki - How to? ===
The easiest way is you simply start writing and editing. You can '''install an easy editor''' by doing what is described in the picture to the right.
[[File:Install easy editor.png|thumb|How to install an easy editor]]

Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]

=== EERAdata on github ===
Link here and share your thoughts and issues! Note, work in progress.
* [https://github.com/valeria6856/EERAdata EERAdata@github]

=== EERAdata @ Research Gate ===
Link here and share your thoughts and issues! Note, work in progress.
* [https://www.researchgate.net/project/Towards-a-FAIR-and-open-data-ecosystem-in-the-low-carbon-energy-research-community EERAdata@ResearchGate]

=== Just have fun! ===
'''Read before playing:''' This is a little memory game where players need to '''identify triples''', that is three tiles that belong to one data set. All of them relate to low carbon energy. Some tiles have the form of a picture, others show metadata descriptions (in various formats) and some are even sound files. So, the game is to have fun, while learning about metadata. Try out if you can find all triples. Note if you have opened 3 tiles and they do not match, all will automatically close. Just as you know it from a real-life memory game.
[http://eeradata.webfactional.com/memory/memory.html '''Link''']

== Agenda and notes ==
Builds on read aheads. Online talks and discussions. Space for interaction with participants after each presentation. Moderated discussion of collected comments.

{| class="wikitable"
|-
! 30th November !! Framing workshop (Part 1): Online hackathon to write a community paper. '''Link to register:'''
|-
| 10.00-10.15 || Welcome and introduction to the first draft of the planned paper: “[https://docs.google.com/document/d/1oS_t7yb9_xDM-RYDPTd48B7O9Sq9dXiz3ibUO34G7oA/edit# Advancing metadata for low carbon energy research - current state and call for action]”, Valeria Jana Schwanitz & August Wierling, HVL.
|-
| 10.15-10.30 ||Discussion of the structure, collection of comments and notes
|-
| 10.30-10.45 || Creation of writing teams in break out groups. Preferences are collected beforehand if possible.
|-
| 10.45-15.00 || Work in '''writing teams''' (break out groups in zoom). The work-flow, coffee and lunch breaks etc. are organized by the groups themselves.
|-
| 15.00-16.00 || Wrap up day 1 of the framing workshop: Reports from the work done in break out groups, collection of feedback and comments from all. Suggestions of questions to be investigated in use case workshops.
|}

{| class="wikitable"
|-
! 1st December !! Use case “EU policy and energy research taxonomies” '''Link to register: coming soon'''
|-
| 10:00am - 2:00pm || The workshop focuses on metadata, exploring how to link ontologies used for policy-making and those used in research domains. Using the EU policy taxonomy, Art.2 EU Directive 944 (2019), and the inventory of collective action initiatives of the COMETS project as a starting point, common metadata elements and connections between them are identified. The workshop will use the software “GitMind” to design the ontology, incorporating suggestions from workshop participants. The participants will form one of the writing teams for the community paper. Link to zoom meeting: upcoming. [[WS2UC4|Link to workshop page with agenda, notes and results]]
|}

{| class="wikitable"
|-
! 2nd December !! Use case “Buildings efficiency” '''Link to register:'''
|-
| 10:00-12:00 (GMT+1) || The aim of this session is to build up on discussions that took place in 1st EERADATA workshop together with the participation of the invited experts, utilizing the experience related to the FAIR assessment in order to: a) Highlight main issues with FAIRness, b) Jointly come up with possible remedies and solutions, and c) Identify pointers to metadata standardization, if and how it can be achieved in Buildings Efficiency domain. [[WS2UC1|Link to workshop page with agenda, notes and results]]
|-
|10.00-10.10 || Introduction: What does the “Buildings Efficiency” use case of EERADATA aim? Mehmet Efe Biresselioğlu, IUE
|-
| 10.10-10.25 || Standardized Flexibility: FAIR data principles in H2020 projects - ECHOES and ENCHANT - databases, Jens Olgard Dalseth Røyrvik, NTNU Samfunnsforskning
|-
| 10.25-10.40 || Achieving Fair Principles: An Overview of the Hotmaps Project and Hotmaps Building Stock EU28 Dataset, Simon Pezzutto, EURAC
|-
| 10.40-10.55 || openENTRANCE CS1 residential energy demand response: The importance of nomenclature and data transparency for open source energy system model platform, Ryan O’Reilly, Energieinstitut an der JKU
|-
| 10.55-11.05 || Exceed database: Lessons learned and continuous improvement, Daniele Antonucci, EURAC
|-
| 11.05-11.15 || Energy related Building data: Opportunities from FAIRness, Ezilda Costanzo, ENEA
|-
| 11.15-11.20 ||Short Break
|-
| 11.20-12.00 ||Panel Discussion with Q&A
|}

{| class="wikitable"
|-
! 3rd December !! Use case “Metadata user stories” '''Link to register:'''
|-
| 10:00-12:00 (GMT+1) || The goal of this workshop is to understand how users find, request, use and also provide data. The workshop connects to functional specifications needed for developing the EERAdata platform and other infrastructure in support of data FAIRification work flows. Participants will have the possibility to comment on first mock-ups of the platform and try out some functionalities. For example, using the ontologies produced during UC “EU policy and energy research taxonomies” and participating in virtual discussions on the EERAdata Community Forum. [[WS2UC Metadata User Stories|Link to workshop page with agenda, notes and results]] Link to zoom meeting: upcoming.
|-
|10:00-10:15 || '''Welcome & Introduction'''
Aims and intended role of the platform in the community (Manfred Paier, AIT)
|-
| 10:15-10:30 || '''Platform elements'''
Status quo (initial mock-ups, Community Forum) (Astrid Unger, AIT)
|-
| 10:30-11:30 || '''User stories'''
Experiences from UC4, UC1, other Use Cases and Gap Analysis

1. Searching for data

2. Linking existing datasets

General discussion
|-
| 11:30-11:45 || '''Implications for the data model'''
Top-down metadata, bottom-up metadata (Michael Barber, AIT)
|-
| 11:45-12:00 || '''Way forward'''
for designing and implementing the platform (Manfred Paier, AIT)
|-
|}

{| class="wikitable"
|-
! 4th December !! Art workshop “Collaborative mosaic about FAIR data and Sustainable Development Goals” '''Link to register: coming soon'''
|-
| 9-15 || The aim is to create a mosaic which reflects the views of different researchers and data stakeholders on the relevance of FAIR data and the achieving of the Sustainable Development Goals. Participants are ask to contribute their retrospective from the year 2030. The artist Barbara Bellier will connect the individual pieces creating the collaborative mosaic.
|}

{| class="wikitable"
|-
! 4th December !! EERAdata participates in [https://conference.codata.org/FAIRconvergence2020/programme/ International FAIR Convergence 2020 Symposium] '''Link to register: https://conference.codata.org/FAIRconvergence2020/sessions/265/'''
|-
| 15-17 || '''M4M Workshops: Making domain-relevant machine-actionable metadata at scale'''. There is no FAIR data without machine-actionable metadata. Semantically-rich, domain-relevant, machine-actionable metadata is fundamental for FAIR interoperation of data, algorithms and compute resources. However, FAIR-enabling metadata schema often do not yet exist for many communities and need to be created de novo by the relevant domain experts. In other cases there may be already existing metadata schema but they are difficult to find, assess and reuse. In an effort to support convergence of metadata components, the GO FAIR initiative has launched a systematic and scalable approach to the creation, registration and reuse of machine-actionable metadata called Metadata for Machines (M4M) Workshops. M4M workshops bring together representatives from given scientific communities and FAIR metadata experts to jointly define standards for the metadata that they wish to use in practice. We have found scientists to be highly motivated to develop and use metadata standards through our M4M workshops, and tooling such as the CEDAR Workbench to be effective in the collaborative development of new metadata templates. Thirteen M4M Workshops that have been delivered and in this Session, the most recent workshops (for VODAN Africa, DeiC and ZonMW) will be reviewed. This will be followed by a focused discussion on a proposed M4M workshop for EERA Data Consortium to be run early in 2021.

The '''agenda''', roughly, is:
* to use the first hour to recap recent M4M accomplishments (VODAN Africa, DeiC, ZonMW COVID Program), and
* to use the second hour to scope plans for an M4M workshop with the EERA Data Consortium
|}

{| class="wikitable"
|-
! 7th December !! Framing workshop (Part 2): Online hackathon to write a community paper. '''Link to register:'''
|-
| 10.00-10.45 || Welcome and input from use case workshops presented by use case leaders (see above).
|-
| 10.45-11.00 || Guidance for writing teams
|-
| 11.00-11.15 || Creation of writing teams in break out groups (continuation of day 1).
|-
| 11.15-15.00 || Work in break out groups. The work-flow, coffee and lunch breaks etc. are organized by the groups themselves.
|-
| 15.00-16.00 ||Wrap up day 2 of the framing workshop: Reports from the work done in break out groups. Collection of feedback and comments from all. Guidance on how to finalize the paper collaboratively after the workshop.
|}

== Metadata knowledge base ==
[[Domain_specific_classification_schemes]]

WS2

2020-11-18T11:53:03Z

Manfred: /* Agenda and notes */

The second workshop of EERAdata is organized as an online webinar and hackathon during November, 30, to December, 4th, 2020. It is dedicated to metadata.

== Objective ==
* Discuss and develop metadata standards for FAIR and open data in the low carbon energy research community. '''The focus is on the link between metadata and how humans explore data.'''
* Identify gaps and needs that hinder their standardized realization and implementation.
* Jointly work on a community paper and/or join the discussions in use cases. We start with a commented and revised draft. [https://docs.google.com/document/d/1oS_t7yb9_xDM-RYDPTd48B7O9Sq9dXiz3ibUO34G7oA/edit?usp=sharing Link to draft of the community paper]

[[File:EERAdata community paper.png|thumb|Workshop concept of EERAdata]]

== Read & watch aheads ==

To prepare for the paper writing hackathon, please participate in the preparatory 'Briefing Workshop' or watch the recorded videos. The workshop took place Thursday, 5th of November, 10-12 CET. The workshop introduced recent work on metadata and outlined the tasks and procedures on how to join the writing team for the community.

{| class="wikitable"
|-
! Agenda & Material of Briefing Workshop !! Full video recording: [https://kaltura.hvl.no/media/EERAdata+Workshop+to+prepare+for+the+hackathon/0_xxdhcjl7 link]
|-
|Slides: [[File:EERAdata_WS2_wierling.pdf|80px|thumb|none]] || Introduction & Talk ''Advancing metadata standards for low carbon energy research'', August Wierling, HVL.
|-
| Slides: [[File:EERAdata KIT Suess.pdf|80px|thumb|none]] || ''Overview of the Helmholtz Metadata Collaboration Platform'', Wolfgang Süß, KIT.
|-
| Slides: [[File:Talk_Celino_ENEA.pdf|80px|thumb|none]] || ''Metadata in materials: The new path forward'', Massimo Celino, ENEA.
|-
| Chat Notes: [[File:EERAdata chat notes.pdf|80px|thumb|none]] || ''Panel discussion with Q&A''
|-
| Slides[[File:WS2 prep schwanitz.pdf|80px|thumb|none]] || ''Briefing for EERAdata paper writing workshop (Who? How? When? What?)'', Valeria Jana Schwanitz, EERAdata PI.
|}

* Invitation to [https://docs.google.com/document/d/1oS_t7yb9_xDM-RYDPTd48B7O9Sq9dXiz3ibUO34G7oA/edit# comment the draft] before the writing workshop
* Suggested read on the history of metadata
Metadata - [https://www.springer.com/gp/book/9783319408910 Shaping Knowledge from Antiquity to the Semantic Web by Richard Gartner]

== Join us and collaborate interactively! ==
=== Becoming a co-author ===
Workshop participants are invited to become co-authors of the planned community paper.

'''How to join the team writing the community paper?'''
Briefing is provided during the preparatory workshop (also recorded). Includes recommendation for read and watch aheads.

The community paper addresses 3 key questions:
* Q1: How to align mental models of those searching for data with navigation along metadata? What is specific to the energy domain?
* Q2: What consequences for the construction of domain-specific metadata follow? and how can they be dynamically updated?
* Q3: What are the recommendations to the low carbon community?

The envisaged output of the paper is:
* A community-reviewed draft for a low carbon energy ontology in support of metadata,
* Metadata suggestion cards for low carbon energy researchers,
* Recommendations on how to proceed.

'''Invitation to [https://docs.google.com/document/d/1oS_t7yb9_xDM-RYDPTd48B7O9Sq9dXiz3ibUO34G7oA/edit# comment the draft] before the writing workshop''', e.g.:
* Review of key questions,
* Suggestions of literature, illustrative cases, metadata perspectives & issues,
* Suggestions to any section (e.g., Introduction, Method, Discussion of Results, Outlook)
* Adding snippets of texts,

'''Any other idea is welcome!'''

Using above prior comments & contributions provided by 23.11.2020, the EERAdata team will revise the draft before the workshop starts. During the workshop, the discussion & writing of the paper continues in small writing teams. A prior registration to teams is therefore recommended. However, teams can change anytime. The EERAdata team is strongly interested in inviting a large group of contributing authors. It is not only in the interest of the community project as such, but it increases the credibility of the main output - the draft (or road towards) a low carbon energy ontology in support of metadata”.

'''Co-authorship is granted to active participants of the EERAdata workshop as well as to other contributors to the community paper.'''

=== EERAdata wiki - How to? ===
The easiest way is you simply start writing and editing. You can '''install an easy editor''' by doing what is described in the picture to the right.
[[File:Install easy editor.png|thumb|How to install an easy editor]]

Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]

=== EERAdata on github ===
Link here and share your thoughts and issues! Note, work in progress.
* [https://github.com/valeria6856/EERAdata EERAdata@github]

=== EERAdata @ Research Gate ===
Link here and share your thoughts and issues! Note, work in progress.
* [https://www.researchgate.net/project/Towards-a-FAIR-and-open-data-ecosystem-in-the-low-carbon-energy-research-community EERAdata@ResearchGate]

=== Just have fun! ===
'''Read before playing:''' This is a little memory game where players need to '''identify triples''', that is three tiles that belong to one data set. All of them relate to low carbon energy. Some tiles have the form of a picture, others show metadata descriptions (in various formats) and some are even sound files. So, the game is to have fun, while learning about metadata. Try out if you can find all triples. Note if you have opened 3 tiles and they do not match, all will automatically close. Just as you know it from a real-life memory game.
[http://eeradata.webfactional.com/memory/memory.html '''Link''']

== Agenda and notes ==
Builds on read aheads. Online talks and discussions. Space for interaction with participants after each presentation. Moderated discussion of collected comments.

{| class="wikitable"
|-
! 30th November !! Framing workshop (Part 1): Online hackathon to write a community paper. '''Link to register:'''
|-
| 10.00-10.15 || Welcome and introduction to the first draft of the planned paper: “[https://docs.google.com/document/d/1oS_t7yb9_xDM-RYDPTd48B7O9Sq9dXiz3ibUO34G7oA/edit# Advancing metadata for low carbon energy research - current state and call for action]”, Valeria Jana Schwanitz & August Wierling, HVL.
|-
| 10.15-10.30 ||Discussion of the structure, collection of comments and notes
|-
| 10.30-10.45 || Creation of writing teams in break out groups. Preferences are collected beforehand if possible.
|-
| 10.45-15.00 || Work in '''writing teams''' (break out groups in zoom). The work-flow, coffee and lunch breaks etc. are organized by the groups themselves.
|-
| 15.00-16.00 || Wrap up day 1 of the framing workshop: Reports from the work done in break out groups, collection of feedback and comments from all. Suggestions of questions to be investigated in use case workshops.
|}

{| class="wikitable"
|-
! 1st December !! Use case “EU policy and energy research taxonomies” '''Link to register: coming soon'''
|-
| 10:00am - 2:00pm || The workshop focuses on metadata, exploring how to link ontologies used for policy-making and those used in research domains. Using the EU policy taxonomy, Art.2 EU Directive 944 (2019), and the inventory of collective action initiatives of the COMETS project as a starting point, common metadata elements and connections between them are identified. The workshop will use the software “GitMind” to design the ontology, incorporating suggestions from workshop participants. The participants will form one of the writing teams for the community paper. Link to zoom meeting: upcoming. [[WS2UC4|Link to workshop page with agenda, notes and results]]
|}

{| class="wikitable"
|-
! 2nd December !! Use case “Buildings efficiency” '''Link to register:'''
|-
| 10:00-12:00 (GMT+1) || The aim of this session is to build up on discussions that took place in 1st EERADATA workshop together with the participation of the invited experts, utilizing the experience related to the FAIR assessment in order to: a) Highlight main issues with FAIRness, b) Jointly come up with possible remedies and solutions, and c) Identify pointers to metadata standardization, if and how it can be achieved in Buildings Efficiency domain. [[WS2UC1|Link to workshop page with agenda, notes and results]]
|-
|10.00-10.10 || Introduction: What does the “Buildings Efficiency” use case of EERADATA aim? Mehmet Efe Biresselioğlu, IUE
|-
| 10.10-10.25 || Standardized Flexibility: FAIR data principles in H2020 projects - ECHOES and ENCHANT - databases, Jens Olgard Dalseth Røyrvik, NTNU Samfunnsforskning
|-
| 10.25-10.40 || Achieving Fair Principles: An Overview of the Hotmaps Project and Hotmaps Building Stock EU28 Dataset, Simon Pezzutto, EURAC
|-
| 10.40-10.55 || openENTRANCE CS1 residential energy demand response: The importance of nomenclature and data transparency for open source energy system model platform, Ryan O’Reilly, Energieinstitut an der JKU
|-
| 10.55-11.05 || Exceed database: Lessons learned and continuous improvement, Daniele Antonucci, EURAC
|-
| 11.05-11.15 || Energy related Building data: Opportunities from FAIRness, Ezilda Costanzo, ENEA
|-
| 11.15-11.20 ||Short Break
|-
| 11.20-12.00 ||Panel Discussion with Q&A
|}

{| class="wikitable"
|-
! 3rd December !! Use case “Metadata user stories” '''Link to register:'''
|-
| 10:00-12:00 (GMT+1) || The goal of this workshop is to understand how users find, request, use and also provide data. The workshop connects to functional specifications needed for developing the EERAdata platform and other infrastructure in support of data FAIRification work flows. Participants will have the possibility to comment on first mock-ups of the platform and try out some functionalities. For example, using the ontologies produced during UC “EU policy and energy research taxonomies” and participating in virtual discussions on the EERAdata Community Forum. [[WS2UC Metadata User Stories|Link to workshop page with agenda, notes and results]] Link to zoom meeting: upcoming.
|}

{| class="wikitable"
|-
! 4th December !! Art workshop “Collaborative mosaic about FAIR data and Sustainable Development Goals” '''Link to register: coming soon'''
|-
| 9-15 || The aim is to create a mosaic which reflects the views of different researchers and data stakeholders on the relevance of FAIR data and the achieving of the Sustainable Development Goals. Participants are ask to contribute their retrospective from the year 2030. The artist Barbara Bellier will connect the individual pieces creating the collaborative mosaic.
|}

{| class="wikitable"
|-
! 4th December !! EERAdata participates in [https://conference.codata.org/FAIRconvergence2020/programme/ International FAIR Convergence 2020 Symposium] '''Link to register: https://conference.codata.org/FAIRconvergence2020/sessions/265/'''
|-
| 15-17 || '''M4M Workshops: Making domain-relevant machine-actionable metadata at scale'''. There is no FAIR data without machine-actionable metadata. Semantically-rich, domain-relevant, machine-actionable metadata is fundamental for FAIR interoperation of data, algorithms and compute resources. However, FAIR-enabling metadata schema often do not yet exist for many communities and need to be created de novo by the relevant domain experts. In other cases there may be already existing metadata schema but they are difficult to find, assess and reuse. In an effort to support convergence of metadata components, the GO FAIR initiative has launched a systematic and scalable approach to the creation, registration and reuse of machine-actionable metadata called Metadata for Machines (M4M) Workshops. M4M workshops bring together representatives from given scientific communities and FAIR metadata experts to jointly define standards for the metadata that they wish to use in practice. We have found scientists to be highly motivated to develop and use metadata standards through our M4M workshops, and tooling such as the CEDAR Workbench to be effective in the collaborative development of new metadata templates. Thirteen M4M Workshops that have been delivered and in this Session, the most recent workshops (for VODAN Africa, DeiC and ZonMW) will be reviewed. This will be followed by a focused discussion on a proposed M4M workshop for EERA Data Consortium to be run early in 2021.

The '''agenda''', roughly, is:
* to use the first hour to recap recent M4M accomplishments (VODAN Africa, DeiC, ZonMW COVID Program), and
* to use the second hour to scope plans for an M4M workshop with the EERA Data Consortium
|}

{| class="wikitable"
|-
! 7th December !! Framing workshop (Part 2): Online hackathon to write a community paper. '''Link to register:'''
|-
| 10.00-10.45 || Welcome and input from use case workshops presented by use case leaders (see above).
|-
| 10.45-11.00 || Guidance for writing teams
|-
| 11.00-11.15 || Creation of writing teams in break out groups (continuation of day 1).
|-
| 11.15-15.00 || Work in break out groups. The work-flow, coffee and lunch breaks etc. are organized by the groups themselves.
|-
| 15.00-16.00 ||Wrap up day 2 of the framing workshop: Reports from the work done in break out groups. Collection of feedback and comments from all. Guidance on how to finalize the paper collaboratively after the workshop.
|}

== Metadata knowledge base ==
[[Domain_specific_classification_schemes]]

WS2UC Metadata User Stories

2020-11-18T11:49:44Z

Manfred:

The goal of this workshop is to understand how users find, request, use and also provide data. The workshop connects to functional specifications needed for developing the EERAdata platform and other infrastructure in support of data FAIRification work flows. Participants will have the possibility to comment on first mock-ups the platform and try out some functionalities. For example, using the ontologies produced during UC “EU policy and energy research taxonomies” and participating in virtual discussions on the EERAdata Community Forum.

== Program ==
{| class="wikitable"
|-
|'''2020-12-03 10:00-12:00 GMT+1''' || '''Workshop UC 'Metadata User Stories' '''
|-
|10:00-10:15 || '''Welcome & Introduction'''
Aims and intended role of the platform in the community (Manfred Paier, AIT)
|-
| 10:15-10:30 || '''Platform elements'''
Status quo (initial mock-ups, Community Forum) (Astrid Unger, AIT)
|-
| 10:30-11:30 || '''User stories'''
Experiences from UC4, UC1, other Use Cases and Gap Analysis

1. Searching for data

2. Linking existing datasets

General discussion
|-
| 11:30-11:45 || '''Implications for the data model'''
Top-down metadata, bottom-up metadata (Michael Barber, AIT)
|-
| 11:45-12:00 || '''Way forward'''
for designing and implementing the platform (Manfred Paier, AIT)
|-
| 12:00 || '''End of the meeting'''
|-
|}

== Notes ==
text

== Workshop results ==
text

WS2UC Metadata User Stories

2020-11-18T11:19:43Z

Manfred: /* Detailed agenda */

Details for the use case workshop "Metadata User Stories".

The goal is to understand how users find, use, and request data. The workshop connects to functional specifications needed for the EERAdata platform and other infrastructure in support of work flows. Participants will have the possibility to comment mock-ups and try out some functionalities. For example, browsing the ontologies produced during UC “EU policy and energy research taxonomies” and the community forum.

== Detailed agenda ==
{| class="wikitable"
|-
! 2020-12-03 !! '''Metadata User Stories '''
|-
| || The aim of this session is to...
|-
|10:00-10:15 || '''Welcome & Introduction'''
Aims and role of the platform in the community, synopsis (Manfred Paier, AIT)
|-
| 10:15-10:30 || '''Platform elements'''
Status quo (initial mock-ups, community forum) (Astrid Unger, AIT)
|-
| 10:30-11:30 || '''User stories'''
Experiences from UC4, UC1, other Use Cases and Gap Analysis

1. Searching for data

2. Linking existing datasets

General discussion
|-
| 11:30-11:45 || '''Implications for the data model'''
Top-down metadata, bottom-up metadata (Michael Barber, AIT)
|-
| 11:45-12:00 || '''Way forward'''
for designing and implementing the platform (Manfred Paier, AIT)
|-
| 12:00 || End of the meeting
|-
|}

== Notes ==
text

== Workshop results ==
text

WS2

2020-11-18T07:42:05Z

Manfred: /* Agenda and notes */

The second workshop of EERAdata is organized as an online webinar and hackathon during November, 30, to December, 4th, 2020. It is dedicated to metadata.

== Objective ==
* Discuss and develop metadata standards for FAIR and open data in the low carbon energy research community. '''The focus is on the link between metadata and how humans explore data.'''
* Identify gaps and needs that hinder their standardized realization and implementation.
* Jointly work on a community paper and/or join the discussions in use cases. We start with a commented and revised draft. [https://docs.google.com/document/d/1oS_t7yb9_xDM-RYDPTd48B7O9Sq9dXiz3ibUO34G7oA/edit?usp=sharing Link to draft of the community paper]

[[File:EERAdata community paper.png|thumb|Workshop concept of EERAdata]]

== Read & watch aheads ==

To prepare for the paper writing hackathon, please participate in the preparatory 'Briefing Workshop' or watch the recorded videos. The workshop took place Thursday, 5th of November, 10-12 CET. The workshop introduced recent work on metadata and outlined the tasks and procedures on how to join the writing team for the community.

{| class="wikitable"
|-
! Agenda & Material of Briefing Workshop !! Full video recording: [https://kaltura.hvl.no/media/EERAdata+Workshop+to+prepare+for+the+hackathon/0_xxdhcjl7 link]
|-
|Slides: [[File:EERAdata_WS2_wierling.pdf|80px|thumb|none]] || Introduction & Talk ''Advancing metadata standards for low carbon energy research'', August Wierling, HVL.
|-
| Slides: [[File:EERAdata KIT Suess.pdf|80px|thumb|none]] || ''Overview of the Helmholtz Metadata Collaboration Platform'', Wolfgang Süß, KIT.
|-
| Slides: [[File:Talk_Celino_ENEA.pdf|80px|thumb|none]] || ''Metadata in materials: The new path forward'', Massimo Celino, ENEA.
|-
| Chat Notes: [[File:EERAdata chat notes.pdf|80px|thumb|none]] || ''Panel discussion with Q&A''
|-
| Slides[[File:WS2 prep schwanitz.pdf|80px|thumb|none]] || ''Briefing for EERAdata paper writing workshop (Who? How? When? What?)'', Valeria Jana Schwanitz, EERAdata PI.
|}

* Invitation to [https://docs.google.com/document/d/1oS_t7yb9_xDM-RYDPTd48B7O9Sq9dXiz3ibUO34G7oA/edit# comment the draft] before the writing workshop
* Suggested read on the history of metadata
Metadata - [https://www.springer.com/gp/book/9783319408910 Shaping Knowledge from Antiquity to the Semantic Web by Richard Gartner]

== Join us and collaborate interactively! ==
=== Becoming a co-author ===
Workshop participants are invited to become co-authors of the planned community paper.

'''How to join the team writing the community paper?'''
Briefing is provided during the preparatory workshop (also recorded). Includes recommendation for read and watch aheads.

The community paper addresses 3 key questions:
* Q1: How to align mental models of those searching for data with navigation along metadata? What is specific to the energy domain?
* Q2: What consequences for the construction of domain-specific metadata follow? and how can they be dynamically updated?
* Q3: What are the recommendations to the low carbon community?

The envisaged output of the paper is:
* A community-reviewed draft for a low carbon energy ontology in support of metadata,
* Metadata suggestion cards for low carbon energy researchers,
* Recommendations on how to proceed.

'''Invitation to [https://docs.google.com/document/d/1oS_t7yb9_xDM-RYDPTd48B7O9Sq9dXiz3ibUO34G7oA/edit# comment the draft] before the writing workshop''', e.g.:
* Review of key questions,
* Suggestions of literature, illustrative cases, metadata perspectives & issues,
* Suggestions to any section (e.g., Introduction, Method, Discussion of Results, Outlook)
* Adding snippets of texts,

'''Any other idea is welcome!'''

Using above prior comments & contributions provided by 23.11.2020, the EERAdata team will revise the draft before the workshop starts. During the workshop, the discussion & writing of the paper continues in small writing teams. A prior registration to teams is therefore recommended. However, teams can change anytime. The EERAdata team is strongly interested in inviting a large group of contributing authors. It is not only in the interest of the community project as such, but it increases the credibility of the main output - the draft (or road towards) a low carbon energy ontology in support of metadata”.

'''Co-authorship is granted to active participants of the EERAdata workshop as well as to other contributors to the community paper.'''

=== EERAdata wiki - How to? ===
The easiest way is you simply start writing and editing. You can '''install an easy editor''' by doing what is described in the picture to the right.
[[File:Install easy editor.png|thumb|How to install an easy editor]]

Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]

=== EERAdata on github ===
Link here and share your thoughts and issues! Note, work in progress.
* [https://github.com/valeria6856/EERAdata EERAdata@github]

=== EERAdata @ Research Gate ===
Link here and share your thoughts and issues! Note, work in progress.
* [https://www.researchgate.net/project/Towards-a-FAIR-and-open-data-ecosystem-in-the-low-carbon-energy-research-community EERAdata@ResearchGate]

=== Just have fun! ===
'''Read before playing:''' This is a little memory game where players need to '''identify triples''', that is three tiles that belong to one data set. All of them relate to low carbon energy. Some tiles have the form of a picture, others show metadata descriptions (in various formats) and some are even sound files. So, the game is to have fun, while learning about metadata. Try out if you can find all triples. Note if you have opened 3 tiles and they do not match, all will automatically close. Just as you know it from a real-life memory game.
[http://eeradata.webfactional.com/memory/memory.html '''Link''']

== Agenda and notes ==
Builds on read aheads. Online talks and discussions. Space for interaction with participants after each presentation. Moderated discussion of collected comments.

{| class="wikitable"
|-
! 30th November !! Framing workshop (Part 1): Online hackathon to write a community paper. '''Link to register:'''
|-
| 10.00-10.15 || Welcome and introduction to the first draft of the planned paper: “[https://docs.google.com/document/d/1oS_t7yb9_xDM-RYDPTd48B7O9Sq9dXiz3ibUO34G7oA/edit# Advancing metadata for low carbon energy research - current state and call for action]”, Valeria Jana Schwanitz & August Wierling, HVL.
|-
| 10.15-10.30 ||Discussion of the structure, collection of comments and notes
|-
| 10.30-10.45 || Creation of writing teams in break out groups. Preferences are collected beforehand if possible.
|-
| 10.45-15.00 || Work in '''writing teams''' (break out groups in zoom). The work-flow, coffee and lunch breaks etc. are organized by the groups themselves.
|-
| 15.00-16.00 || Wrap up day 1 of the framing workshop: Reports from the work done in break out groups, collection of feedback and comments from all. Suggestions of questions to be investigated in use case workshops.
|}

{| class="wikitable"
|-
! 1st December !! Use case “EU policy and energy research taxonomies” '''Link to register: coming soon'''
|-
| 10:00am - 2:00pm || The workshop focuses on metadata, exploring how to link ontologies used for policy-making and those used in research domains. Using the EU policy taxonomy, Art.2 EU Directive 944 (2019), and the inventory of collective action initiatives of the COMETS project as a starting point, common metadata elements and connections between them are identified. The workshop will use the software “GitMind” to design the ontology, incorporating suggestions from workshop participants. The participants will form one of the writing teams for the community paper. Link to zoom meeting: upcoming. [[WS2UC4|Link to workshop page with agenda, notes and results]]
|}

{| class="wikitable"
|-
! 2nd December !! Use case “Buildings efficiency” '''Link to register:'''
|-
| 10:00-12:00 (GMT+1) || The aim of this session is to build up on discussions that took place in 1st EERADATA workshop together with the participation of the invited experts, utilizing the experience related to the FAIR assessment in order to: a) Highlight main issues with FAIRness, b) Jointly come up with possible remedies and solutions, and c) Identify pointers to metadata standardization, if and how it can be achieved in Buildings Efficiency domain. [[WS2UC1|Link to workshop page with agenda, notes and results]]
|-
|10.00-10.10 || Introduction: What does the “Buildings Efficiency” use case of EERADATA aim? Mehmet Efe Biresselioğlu, IUE
|-
| 10.10-10.25 || Standardized Flexibility: FAIR data principles in H2020 projects - ECHOES and ENCHANT - databases, Jens Olgard Dalseth Røyrvik, NTNU Samfunnsforskning
|-
| 10.25-10.40 || Achieving Fair Principles: An Overview of the Hotmaps Project and Hotmaps Building Stock EU28 Dataset, Simon Pezzutto, EURAC
|-
| 10.40-10.55 || openENTRANCE CS1 residential energy demand response: The importance of nomenclature and data transparency for open source energy system model platform, Ryan O’Reilly, Energieinstitut an der JKU
|-
| 10.55-11.05 || Exceed database: Lessons learned and continuous improvement, Daniele Antonucci, EURAC
|-
| 11.05-11.15 || Energy related Building data: Opportunities from FAIRness, Ezilda Costanzo, ENEA
|-
| 11.15-11.20 ||Short Break
|-
| 11.20-12.00 ||Panel Discussion with Q&A
|}

{| class="wikitable"
|-
! 3rd December !! Use case “Metadata user stories” '''Link to register:'''
|-
| 10:00-12:00 (GMT+1) || The goal is to understand how users find, use, and request data. The workshop connects to functional specifications needed for the EERAdata platform and other infrastructure in support of work flows. Participants will have the possibility to comment mock-ups and try out some functionalities. For example, browsing the ontologies produced during UC “EU policy and energy research taxonomies” and the community forum. [[WS2UC Metadata User Stories|Link to workshop page with agenda, notes and results]] Link to zoom meeting: upcoming.
|}

{| class="wikitable"
|-
! 4th December !! Art workshop “Collaborative mosaic about FAIR data and Sustainable Development Goals” '''Link to register: coming soon'''
|-
| 9-15 || The aim is to create a mosaic which reflects the views of different researchers and data stakeholders on the relevance of FAIR data and the achieving of the Sustainable Development Goals. Participants are ask to contribute their retrospective from the year 2030. The artist Barbara Bellier will connect the individual pieces creating the collaborative mosaic.
|}

{| class="wikitable"
|-
! 4th December !! EERAdata participates in [https://conference.codata.org/FAIRconvergence2020/programme/ International FAIR Convergence 2020 Symposium] '''Link to register: https://conference.codata.org/FAIRconvergence2020/sessions/265/'''
|-
| 15-17 || '''M4M Workshops: Making domain-relevant machine-actionable metadata at scale'''. There is no FAIR data without machine-actionable metadata. Semantically-rich, domain-relevant, machine-actionable metadata is fundamental for FAIR interoperation of data, algorithms and compute resources. However, FAIR-enabling metadata schema often do not yet exist for many communities and need to be created de novo by the relevant domain experts. In other cases there may be already existing metadata schema but they are difficult to find, assess and reuse. In an effort to support convergence of metadata components, the GO FAIR initiative has launched a systematic and scalable approach to the creation, registration and reuse of machine-actionable metadata called Metadata for Machines (M4M) Workshops. M4M workshops bring together representatives from given scientific communities and FAIR metadata experts to jointly define standards for the metadata that they wish to use in practice. We have found scientists to be highly motivated to develop and use metadata standards through our M4M workshops, and tooling such as the CEDAR Workbench to be effective in the collaborative development of new metadata templates. Thirteen M4M Workshops that have been delivered and in this Session, the most recent workshops (for VODAN Africa, DeiC and ZonMW) will be reviewed. This will be followed by a focused discussion on a proposed M4M workshop for EERA Data Consortium to be run early in 2021.

The '''agenda''', roughly, is:
* to use the first hour to recap recent M4M accomplishments (VODAN Africa, DeiC, ZonMW COVID Program), and
* to use the second hour to scope plans for an M4M workshop with the EERA Data Consortium
|}

{| class="wikitable"
|-
! 7th December !! Framing workshop (Part 2): Online hackathon to write a community paper. '''Link to register:'''
|-
| 10.00-10.45 || Welcome and input from use case workshops presented by use case leaders (see above).
|-
| 10.45-11.00 || Guidance for writing teams
|-
| 11.00-11.15 || Creation of writing teams in break out groups (continuation of day 1).
|-
| 11.15-15.00 || Work in break out groups. The work-flow, coffee and lunch breaks etc. are organized by the groups themselves.
|-
| 15.00-16.00 ||Wrap up day 2 of the framing workshop: Reports from the work done in break out groups. Collection of feedback and comments from all. Guidance on how to finalize the paper collaboratively after the workshop.
|}

== Metadata knowledge base ==
[[Domain_specific_classification_schemes]]

WS2

2020-11-18T07:41:05Z

Manfred: /* Agenda and notes */

The second workshop of EERAdata is organized as an online webinar and hackathon during November, 30, to December, 4th, 2020. It is dedicated to metadata.

== Objective ==
* Discuss and develop metadata standards for FAIR and open data in the low carbon energy research community. '''The focus is on the link between metadata and how humans explore data.'''
* Identify gaps and needs that hinder their standardized realization and implementation.
* Jointly work on a community paper and/or join the discussions in use cases. We start with a commented and revised draft. [https://docs.google.com/document/d/1oS_t7yb9_xDM-RYDPTd48B7O9Sq9dXiz3ibUO34G7oA/edit?usp=sharing Link to draft of the community paper]

[[File:EERAdata community paper.png|thumb|Workshop concept of EERAdata]]

== Read & watch aheads ==

To prepare for the paper writing hackathon, please participate in the preparatory 'Briefing Workshop' or watch the recorded videos. The workshop took place Thursday, 5th of November, 10-12 CET. The workshop introduced recent work on metadata and outlined the tasks and procedures on how to join the writing team for the community.

{| class="wikitable"
|-
! Agenda & Material of Briefing Workshop !! Full video recording: [https://kaltura.hvl.no/media/EERAdata+Workshop+to+prepare+for+the+hackathon/0_xxdhcjl7 link]
|-
|Slides: [[File:EERAdata_WS2_wierling.pdf|80px|thumb|none]] || Introduction & Talk ''Advancing metadata standards for low carbon energy research'', August Wierling, HVL.
|-
| Slides: [[File:EERAdata KIT Suess.pdf|80px|thumb|none]] || ''Overview of the Helmholtz Metadata Collaboration Platform'', Wolfgang Süß, KIT.
|-
| Slides: [[File:Talk_Celino_ENEA.pdf|80px|thumb|none]] || ''Metadata in materials: The new path forward'', Massimo Celino, ENEA.
|-
| Chat Notes: [[File:EERAdata chat notes.pdf|80px|thumb|none]] || ''Panel discussion with Q&A''
|-
| Slides[[File:WS2 prep schwanitz.pdf|80px|thumb|none]] || ''Briefing for EERAdata paper writing workshop (Who? How? When? What?)'', Valeria Jana Schwanitz, EERAdata PI.
|}

* Invitation to [https://docs.google.com/document/d/1oS_t7yb9_xDM-RYDPTd48B7O9Sq9dXiz3ibUO34G7oA/edit# comment the draft] before the writing workshop
* Suggested read on the history of metadata
Metadata - [https://www.springer.com/gp/book/9783319408910 Shaping Knowledge from Antiquity to the Semantic Web by Richard Gartner]

== Join us and collaborate interactively! ==
=== Becoming a co-author ===
Workshop participants are invited to become co-authors of the planned community paper.

'''How to join the team writing the community paper?'''
Briefing is provided during the preparatory workshop (also recorded). Includes recommendation for read and watch aheads.

The community paper addresses 3 key questions:
* Q1: How to align mental models of those searching for data with navigation along metadata? What is specific to the energy domain?
* Q2: What consequences for the construction of domain-specific metadata follow? and how can they be dynamically updated?
* Q3: What are the recommendations to the low carbon community?

The envisaged output of the paper is:
* A community-reviewed draft for a low carbon energy ontology in support of metadata,
* Metadata suggestion cards for low carbon energy researchers,
* Recommendations on how to proceed.

'''Invitation to [https://docs.google.com/document/d/1oS_t7yb9_xDM-RYDPTd48B7O9Sq9dXiz3ibUO34G7oA/edit# comment the draft] before the writing workshop''', e.g.:
* Review of key questions,
* Suggestions of literature, illustrative cases, metadata perspectives & issues,
* Suggestions to any section (e.g., Introduction, Method, Discussion of Results, Outlook)
* Adding snippets of texts,

'''Any other idea is welcome!'''

Using above prior comments & contributions provided by 23.11.2020, the EERAdata team will revise the draft before the workshop starts. During the workshop, the discussion & writing of the paper continues in small writing teams. A prior registration to teams is therefore recommended. However, teams can change anytime. The EERAdata team is strongly interested in inviting a large group of contributing authors. It is not only in the interest of the community project as such, but it increases the credibility of the main output - the draft (or road towards) a low carbon energy ontology in support of metadata”.

'''Co-authorship is granted to active participants of the EERAdata workshop as well as to other contributors to the community paper.'''

=== EERAdata wiki - How to? ===
The easiest way is you simply start writing and editing. You can '''install an easy editor''' by doing what is described in the picture to the right.
[[File:Install easy editor.png|thumb|How to install an easy editor]]

Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]

=== EERAdata on github ===
Link here and share your thoughts and issues! Note, work in progress.
* [https://github.com/valeria6856/EERAdata EERAdata@github]

=== EERAdata @ Research Gate ===
Link here and share your thoughts and issues! Note, work in progress.
* [https://www.researchgate.net/project/Towards-a-FAIR-and-open-data-ecosystem-in-the-low-carbon-energy-research-community EERAdata@ResearchGate]

=== Just have fun! ===
'''Read before playing:''' This is a little memory game where players need to '''identify triples''', that is three tiles that belong to one data set. All of them relate to low carbon energy. Some tiles have the form of a picture, others show metadata descriptions (in various formats) and some are even sound files. So, the game is to have fun, while learning about metadata. Try out if you can find all triples. Note if you have opened 3 tiles and they do not match, all will automatically close. Just as you know it from a real-life memory game.
[http://eeradata.webfactional.com/memory/memory.html '''Link''']

== Agenda and notes ==
Builds on read aheads. Online talks and discussions. Space for interaction with participants after each presentation. Moderated discussion of collected comments.

{| class="wikitable"
|-
! 30th November !! Framing workshop (Part 1): Online hackathon to write a community paper. '''Link to register:'''
|-
| 10.00-10.15 || Welcome and introduction to the first draft of the planned paper: “[https://docs.google.com/document/d/1oS_t7yb9_xDM-RYDPTd48B7O9Sq9dXiz3ibUO34G7oA/edit# Advancing metadata for low carbon energy research - current state and call for action]”, Valeria Jana Schwanitz & August Wierling, HVL.
|-
| 10.15-10.30 ||Discussion of the structure, collection of comments and notes
|-
| 10.30-10.45 || Creation of writing teams in break out groups. Preferences are collected beforehand if possible.
|-
| 10.45-15.00 || Work in '''writing teams''' (break out groups in zoom). The work-flow, coffee and lunch breaks etc. are organized by the groups themselves.
|-
| 15.00-16.00 || Wrap up day 1 of the framing workshop: Reports from the work done in break out groups, collection of feedback and comments from all. Suggestions of questions to be investigated in use case workshops.
|}

{| class="wikitable"
|-
! 1st December !! Use case “EU policy and energy research taxonomies” '''Link to register: coming soon'''
|-
| 10:00am - 2:00pm || The workshop focuses on metadata, exploring how to link ontologies used for policy-making and those used in research domains. Using the EU policy taxonomy, Art.2 EU Directive 944 (2019), and the inventory of collective action initiatives of the COMETS project as a starting point, common metadata elements and connections between them are identified. The workshop will use the software “GitMind” to design the ontology, incorporating suggestions from workshop participants. The participants will form one of the writing teams for the community paper. Link to zoom meeting: upcoming. [[WS2UC4|Link to workshop page with agenda, notes and results]]
|}

{| class="wikitable"
|-
! 2nd December !! Use case “Buildings efficiency” '''Link to register:'''
|-
| 10:00-12:00(GMT+1) || The aim of this session is to build up on discussions that took place in 1st EERADATA workshop together with the participation of the invited experts, utilizing the experience related to the FAIR assessment in order to: a) Highlight main issues with FAIRness, b) Jointly come up with possible remedies and solutions, and c) Identify pointers to metadata standardization, if and how it can be achieved in Buildings Efficiency domain. [[WS2UC1|Link to workshop page with agenda, notes and results]]
|-
|10.00-10.10 || Introduction: What does the “Buildings Efficiency” use case of EERADATA aim? Mehmet Efe Biresselioğlu, IUE
|-
| 10.10-10.25 || Standardized Flexibility: FAIR data principles in H2020 projects - ECHOES and ENCHANT - databases, Jens Olgard Dalseth Røyrvik, NTNU Samfunnsforskning
|-
| 10.25-10.40 || Achieving Fair Principles: An Overview of the Hotmaps Project and Hotmaps Building Stock EU28 Dataset, Simon Pezzutto, EURAC
|-
| 10.40-10.55 || openENTRANCE CS1 residential energy demand response: The importance of nomenclature and data transparency for open source energy system model platform, Ryan O’Reilly, Energieinstitut an der JKU
|-
| 10.55-11.05 || Exceed database: Lessons learned and continuous improvement, Daniele Antonucci, EURAC
|-
| 11.05-11.15 || Energy related Building data: Opportunities from FAIRness, Ezilda Costanzo, ENEA
|-
| 11.15-11.20 ||Short Break
|-
| 11.20-12.00 ||Panel Discussion with Q&A
|}

{| class="wikitable"
|-
! 3rd December !! Use case “Metadata user stories” '''Link to register:'''
|-
| 10:00-12:00(GMT+1) || The goal is to understand how users find, use, and request data. The workshop connects to functional specifications needed for the EERAdata platform and other infrastructure in support of work flows. Participants will have the possibility to comment mock-ups and try out some functionalities. For example, browsing the ontologies produced during UC “EU policy and energy research taxonomies” and the community forum. [[WS2UC Metadata User Stories|Link to workshop page with agenda, notes and results]] Link to zoom meeting: upcoming.
|}

{| class="wikitable"
|-
! 4th December !! Art workshop “Collaborative mosaic about FAIR data and Sustainable Development Goals” '''Link to register: coming soon'''
|-
| 9-15 || The aim is to create a mosaic which reflects the views of different researchers and data stakeholders on the relevance of FAIR data and the achieving of the Sustainable Development Goals. Participants are ask to contribute their retrospective from the year 2030. The artist Barbara Bellier will connect the individual pieces creating the collaborative mosaic.
|}

{| class="wikitable"
|-
! 4th December !! EERAdata participates in [https://conference.codata.org/FAIRconvergence2020/programme/ International FAIR Convergence 2020 Symposium] '''Link to register: https://conference.codata.org/FAIRconvergence2020/sessions/265/'''
|-
| 15-17 || '''M4M Workshops: Making domain-relevant machine-actionable metadata at scale'''. There is no FAIR data without machine-actionable metadata. Semantically-rich, domain-relevant, machine-actionable metadata is fundamental for FAIR interoperation of data, algorithms and compute resources. However, FAIR-enabling metadata schema often do not yet exist for many communities and need to be created de novo by the relevant domain experts. In other cases there may be already existing metadata schema but they are difficult to find, assess and reuse. In an effort to support convergence of metadata components, the GO FAIR initiative has launched a systematic and scalable approach to the creation, registration and reuse of machine-actionable metadata called Metadata for Machines (M4M) Workshops. M4M workshops bring together representatives from given scientific communities and FAIR metadata experts to jointly define standards for the metadata that they wish to use in practice. We have found scientists to be highly motivated to develop and use metadata standards through our M4M workshops, and tooling such as the CEDAR Workbench to be effective in the collaborative development of new metadata templates. Thirteen M4M Workshops that have been delivered and in this Session, the most recent workshops (for VODAN Africa, DeiC and ZonMW) will be reviewed. This will be followed by a focused discussion on a proposed M4M workshop for EERA Data Consortium to be run early in 2021.

The '''agenda''', roughly, is:
* to use the first hour to recap recent M4M accomplishments (VODAN Africa, DeiC, ZonMW COVID Program), and
* to use the second hour to scope plans for an M4M workshop with the EERA Data Consortium
|}

{| class="wikitable"
|-
! 7th December !! Framing workshop (Part 2): Online hackathon to write a community paper. '''Link to register:'''
|-
| 10.00-10.45 || Welcome and input from use case workshops presented by use case leaders (see above).
|-
| 10.45-11.00 || Guidance for writing teams
|-
| 11.00-11.15 || Creation of writing teams in break out groups (continuation of day 1).
|-
| 11.15-15.00 || Work in break out groups. The work-flow, coffee and lunch breaks etc. are organized by the groups themselves.
|-
| 15.00-16.00 ||Wrap up day 2 of the framing workshop: Reports from the work done in break out groups. Collection of feedback and comments from all. Guidance on how to finalize the paper collaboratively after the workshop.
|}

== Metadata knowledge base ==
[[Domain_specific_classification_schemes]]

WS2UC Metadata User Stories

2020-11-12T13:09:34Z

Manfred: Created page with "Details for the use case workshop "Metadata User Stories". The goal is to understand how users find, use, and request data. The workshop connects to functional specifications..."

WS2

2020-11-12T13:05:08Z

Manfred: /* Agenda and notes */

The second workshop of EERAdata is organized as an online webinar and hackathon during November, 30, to December, 4th, 2020. It is dedicated to metadata.

== Objective ==
* Discuss and develop metadata standards for FAIR and open data in the low carbon energy research community.
* Identify gaps and needs that hinder their standardized realization and implementation.
* Jointly work on a community paper and/or join the discussions in use cases. We start with a commented and revised draft. [https://docs.google.com/document/d/1oS_t7yb9_xDM-RYDPTd48B7O9Sq9dXiz3ibUO34G7oA/edit?usp=sharing Link to draft of the community paper]

[[File:EERAdata community paper.png|thumb|Workshop concept of EERAdata]]

== Read & watch aheads ==

To prepare for the paper writing hackathon, please participate in the preparatory 'Briefing Workshop' or watch the recorded videos. The workshop took place Thursday, 5th of November, 10-12 CET. The workshop introduced recent work on metadata and outlined the tasks and procedures on how to join the writing team for the community.

{| class="wikitable"
|-
! Agenda & Material of Briefing Workshop !! Full video recording: [https://kaltura.hvl.no/media/EERAdata+Workshop+to+prepare+for+the+hackathon/0_xxdhcjl7 link]
|-
|Slides: [[File:EERAdata_WS2_wierling.pdf|80px|thumb|none]] || Introduction & Talk ''Advancing metadata standards for low carbon energy research'', August Wierling, HVL.
|-
| Slides: [[File:EERAdata KIT Suess.pdf|80px|thumb|none]] || ''Overview of the Helmholtz Metadata Collaboration Platform'', Wolfgang Süß, KIT.
|-
| Slides: [[File:Talk_Celino_ENEA.pdf|80px|thumb|none]] || ''Metadata in materials: The new path forward'', Massimo Celino, ENEA.
|-
| Chat Notes: [[File:EERAdata chat notes.pdf|80px|thumb|none]] || ''Panel discussion with Q&A''
|-
| Slides[[File:WS2 prep schwanitz.pdf|80px|thumb|none]] || ''Briefing for EERAdata paper writing workshop (Who? How? When? What?)'', Valeria Jana Schwanitz, EERAdata PI.
|}

* Invitation to [https://docs.google.com/document/d/1oS_t7yb9_xDM-RYDPTd48B7O9Sq9dXiz3ibUO34G7oA/edit# comment the draft] before the writing workshop
* Suggested read on the history of metadata
Metadata - [https://www.springer.com/gp/book/9783319408910 Shaping Knowledge from Antiquity to the Semantic Web by Richard Gartner]

== Join us and collaborate interactively! ==
=== Becoming a co-author ===
Workshop participants are invited to become co-authors of the planned community paper.

'''How to join the team writing the community paper?'''
Briefing is provided during the preparatory workshop (also recorded). Includes recommendation for read and watch aheads.

The community paper addresses 3 key questions:
* Q1: How to align mental models of those searching for data with navigation along metadata? What is specific to the energy domain?
* Q2: What consequences for the construction of domain-specific metadata follow? and how can they be dynamically updated?
* Q3: What are the recommendations to the low carbon community?

The envisaged output of the paper is:
* A community-reviewed draft for a low carbon energy ontology in support of metadata,
* Metadata suggestion cards for low carbon energy researchers,
* Recommendations on how to proceed.

'''Invitation to [https://docs.google.com/document/d/1oS_t7yb9_xDM-RYDPTd48B7O9Sq9dXiz3ibUO34G7oA/edit# comment the draft] before the writing workshop''', e.g.:
* Review of key questions,
* Suggestions of literature, illustrative cases, metadata perspectives & issues,
* Suggestions to any section (e.g., Introduction, Method, Discussion of Results, Outlook)
* Adding snippets of texts,

'''Any other idea is welcome!'''

Using above prior comments & contributions provided by 23.11.2020, the EERAdata team will revise the draft before the workshop starts. During the workshop, the discussion & writing of the paper continues in small writing teams. A prior registration to teams is therefore recommended. However, teams can change anytime. The EERAdata team is strongly interested in inviting a large group of contributing authors. It is not only in the interest of the community project as such, but it increases the credibility of the main output - the draft (or road towards) a low carbon energy ontology in support of metadata”.

'''Co-authorship is granted to active participants of the EERAdata workshop as well as to other contributors to the community paper.'''

=== EERAdata wiki - How to? ===
The easiest way is you simply start writing and editing. You can '''install an easy editor''' by doing what is described in the picture to the right.
[[File:Install easy editor.png|thumb|How to install an easy editor]]

Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]

=== EERAdata on github ===
Link here and share your thoughts and issues! Note, work in progress.
* [https://github.com/valeria6856/EERAdata EERAdata@github]

=== EERAdata @ Research Gate ===
Link here and share your thoughts and issues! Note, work in progress.
* [https://www.researchgate.net/project/Towards-a-FAIR-and-open-data-ecosystem-in-the-low-carbon-energy-research-community EERAdata@ResearchGate]

=== Just have fun! ===
'''Read before playing:''' This is a little memory game where players need to '''identify triples''', that is three tiles that belong to one data set. All of them relate to low carbon energy. Some tiles have the form of a picture, others show metadata descriptions (in various formats) and some are even sound files. So, the game is to have fun, while learning about metadata. Try out if you can find all triples. Note if you have opened 3 tiles and they do not match, all will automatically close. Just as you know it from a real-life memory game.
[http://eeradata.webfactional.com/memory/memory.html '''Link''']

== Agenda and notes ==
Builds on read aheads. Online talks and discussions. Space for interaction with participants after each presentation. Moderated discussion of collected comments.

{| class="wikitable"
|-
! 30th Nov. !! Framing workshop (Part 1): Online hackathon to write a community paper. '''Link to register:'''
|-
| 10.00-10.15 || Welcome and introduction to the first draft of the planned paper: “[https://docs.google.com/document/d/1oS_t7yb9_xDM-RYDPTd48B7O9Sq9dXiz3ibUO34G7oA/edit# Advancing metadata for low carbon energy research - current state and call for action]”, Valeria Jana Schwanitz & August Wierling, HVL.
|-
| 10.15-10.30 ||Discussion of the structure, collection of comments and notes
|-
| 10.30-10.45 || Creation of writing teams in break out groups. Preferences are collected beforehand if possible.
|-
| 10.45-15.00 || Work in '''writing teams''' (break out groups in zoom). The work-flow, coffee and lunch breaks etc. are organized by the groups themselves.
|-
| 15.00-16.00 || Wrap up day 1 of the framing workshop: Reports from the work done in break out groups, collection of feedback and comments from all. Suggestions of questions to be investigated in use case workshops.
|}

{| class="wikitable"
|-
! 1st Dec. !! Use case “EU policy and energy research taxonomies” '''Link to register:'''
|-
| 10am-2pm || The workshop focuses on metadata, exploring how to link ontologies used for policy-making and those used in research domains. Using the EU policy taxonomy, Art.2 EU Directive 944 (2019), and the inventory of collective action initiatives of the COMETS project as a starting point, common metadata elements and connections between them are identified. The workshop will use the software “upcoming” to design the ontology, incorporating suggestions from workshop participants. The participants will form one of the writing teams for the community paper. Link to zoom meeting: upcoming. [[WS2UC4|Link to workshop page with agenda, notes and results]]
|}

{| class="wikitable"
|-
! 2nd Dec. !! Use case “Buildings efficiency” '''Link to register:'''
|-
| 09:00-11:00 (GMT+1) || In this session, we will be building on discussions in 1st EERADATA workshop together with the participation of the invited experts, utilizing the experience related to the FAIR assessment in order to: a) Highlight main issues with FAIRness, b) Jointly come up with possible remedies and solutions, and d) Identify pointers to metadata standardization, if and how it can be achieved in Buildings Efficiency domain. Link to meeting: [https://global.gotomeeting.com/join/423955317 From your computer, tablet or smartphone]. New to GoToMeeting? [https://global.gotomeeting.com/install/423955317 Get the app now] and be ready when your first meeting starts. [[WS2UC1|Link to workshop page with agenda, notes and results]]
|}

{| class="wikitable"
|-
! 3rd Dec. !! Use case “Meta data user stories” '''Link to register:'''
|-
| to be confirmed || The goal is to understand how users find, use, and request data. The workshop connects to functional specifications needed for the EERAdata platform and other infrastructure in support of work flows. Participants will have the possibility to comment mock-ups and try out some functionalities. For example, browsing the ontologies produced during UC “EU policy and energy research taxonomies” and the community forum. [[WS2UC Metadata User Stories|Link to workshop page with agenda, notes and results]] Link to zoom meeting: upcoming.
|}

{| class="wikitable"
|-
! 4th Dec. !! Use case “Online art project” '''Link to register:'''
|-
| to be confirmed || The goal is to produce a piece of art where energy researchers and stakeholders communicate their perspectives on the need for high quality and FAIR data for Sustainable Development. Link to zoom meeting: upcoming.
|}

{| class="wikitable"
|-
! 7th Dec. !! Framing workshop (Part 2): Online hackathon to write a community paper. '''Link to register:'''
|-
| 10.00-10.45 || Welcome and input from use case workshops presented by use case leaders (see above).
|-
| 10.45-11.00 || Guidance for writing teams
|-
| 11.00-11.15 || Creation of writing teams in break out groups (continuation of day 1).
|-
| 11.15-15.00 || Work in break out groups. The work-flow, coffee and lunch breaks etc. are organized by the groups themselves.
|-
| 15.00-16.00 ||Wrap up day 2 of the framing workshop: Reports from the work done in break out groups. Collection of feedback and comments from all. Guidance on how to finalize the paper collaboratively after the workshop.
|}

== Metadata knowledge base ==
[[Domain_specific_classification_schemes]]

Functional specifications

2020-11-02T09:20:36Z

Manfred: /* Front end */

This '''living document''' forms the basis of Deliverable 3.1 that will guide the design and implementation of the platform.

==Introduction==
The intention of this living document is to reach a team consensus on what the EERAdata platform is to achieve. We expect that such consensus among the stakeholders is established step by step during the project implementation. Hereby, we draw on practices in professional software development with the purpose

* '''To specify the stakeholders´ needs.''' A Product Requirements Document (PRD) is a document containing all the requirements for a certain software product. It is written with direct user involvement to allow all stakeholders to understand what the product should do. A PRD, however, does not anticipate or define how the product will do it. In EERAdata we provide this by asking the project partners in their role as energy researchers for '''''user stories''''', comprising concrete support needs for FAIR data in their use cases.

* '''To link requirements and functionality.''' The Functional Specifications Document (FSD) specifies the functions that a software must perform. A functional specification is a more technical response to the PRD. It does not define the inner workings of the proposed system, nor does it include the specification of how the system function will be implemented. Instead, it focuses on what various outside agents (people using the program, computer peripherals, or other computers, for example) might observe when interacting with the system. In EERAdata we achieve this by providing mock-ups, descriptions of the front-end features on the EERAdata Wiki and allowing test users to access preliminary platform implementations during development. In this way feedback can be collected continually from the consortium and from a wider community through the EERAdata workshops.

* '''To specify technical implementation options.''' A Software Requirements Specification (SRS) is a description of a software system to be developed. Typically, it is written by a technical writer, a systems architect, or a software programmer. Software requirements specification is a rigorous assessment of requirements before the more specific system design stages, and its goal is to reduce later redesign. It should also provide a realistic basis for estimating risks, schedules, and, in our case, future maintenance issues. I

Thus, in the following, three perspectives are considered - user needs, software design- and software implementation issues - in the development of the platform elements and in the use of the methods and tools.

==Platform elements==

===Front end===
Methods: user stories, design thinking, mock-ups, Wiki (comments, feedback)
====Landing page====
user authentication; user guide
====Community forum====
feedback on platform; discussion of content

====Metadata selector====
*Dashboard structure
*linking to external databases
*identification of relevant databases using metadata

====Display, analysis & visualization====
*Dashboard structure
*direct access to selected databases
*display of tabular data from supported databases
*integrated applications for basic analytic features

====Session logging====
*utilizing cookies for collecting session history for later performance monitoring
*GDPR compliance (opt-in, request for stored data, request to delete PII)

===Processing and storage device===
====Metadata database model====

Methods: Design thinking, EERAdata Workshop 2, Wiki-Platform interface

In the following figure, we sketch how metadata describing the thematic character of external databases may be harmonized for use in the EERAdata platform. A similar strategy could also be used to harmonize the metadata for the specific records in the databases; this would be conceptually similar, but with a more complicated structure to the records.

[[file:DBstructure.png|800px]]

Three external databases are considered, and termed DB1, DB2, and DB3. They are each described in terms of a set of thematic classes following some standard classification, given in terms of persistent identifiers (pIDs) for the appropriate classes. DB1 and DB2 use the same standardization system, providing pIDs (Class-std1-ID) for the appropriate classes. DB3 uses a second standardization system, providing pIDs (Class-std2-ID) for its corresponding classes. We cannot assume the two systems to be commensurable.

Further, we cannot assume that either system is commensurable with the standardization system adopted for the EERAdata platform. Thus, instead of directly using the standards from the external databases, we harmonize the external standards to that used by the EERAdata platform. This is shown as the tables Std1-harmonization and Std2-harmonization, which constitute correspondence tables between the external pIDs and the pIDs used internally by EERAdata (EERAdata-std-ID). The correspondence tables must accurately relate standards that may be at different levels of precision and with different approaches to classification. It is thus essential that the tables are constructed with input from domain experts.

The correspondence tables allow us to describe the external databases in a consistent fashion using the internal standard for the platform. Needed detail is provided internally, e.g., giving a short class name and a description as shown in the figure. Beyond using the classes as a nomenclature for thematic content, ontological relations between the classes can be expressed, e.g., as a Class-hierarchy specifying which classes have others as subclasses, shown in the figure as pairings of pIDs for the classes along with their separation in the hierarachy. Crucially, it is not necessary to use the ontological structures of the external databases, although they must be accounted for in preparing the correspondence tables.

===='Data' database====
The EERAdata platform is intended to build on external resources as far as possible, minimizing internal storage (and computation requirements. The complexity will depend on the visualization requirements that emerge in the course of the project. At the current stage, it is not possible to be more specific without some external databases in mind.
====Database interface====
to support standardization and harmonization process
====Open core search====
functionality to support the establishment of ontologies?
====Evaluation of session logs====

===Back end===
*Interfaces to external resources (APIs, …); communication with platform owners, support by Use Case Leaders required
*Interfaces to import metadata from external sources (provided by the Use Cases)
*Data preparation for front end
*User account management
*User group management
*...
Methods: software development, establishment of communication channels with database holders

===Software system requirements===
*Usability
*Graphic design
*Reliability
*Availability
*Adherence to IPRs
*Data protection
*Security
*Migration and future maintenance
*…

==Methods and tools==
To collect expectations and needs, we must account for different perspectives:
# energy research expertise from use cases & gap analysis;
# data science expertise from FAIR/O community; and
# process expertise from standardisation community

===Design thinking===
Which tools will we use to create the mock-ups?
Design suggestions are posted on the Wiki for voting and feedback within the project community.

===User stories===

As a first step, the use case leaders and other use-case members are involved in formulating the needs and requirements. As an important tool, we plan to use '''user stories''' to be provided by them or other stakeholders from the energy research community. User stories put features in the context of what the user needs to accomplish. They describe the task or feature, but not how the developers should implement it. First step: invite Use Case leaders and members to collect user stories on the Wiki. Second step: approach external stakeholders for user stories (database holders, interoperability community…).

===EERAdata Workshops===

===Community forum===

===EERAdata Wiki===

Main Page

2020-10-12T15:06:26Z

Manfred: /* Community Platform */

Welcome to the EERAdata MediaWiki!

== The project EERAdata ==

'''Towards a FAIR and open data ecosystem in the low carbon energy research community.''' Transparent, re-usable, and integrated energy data enable society to choose, monitor, and implement sustainable transition pathways. It is not only a prerequisite for people to have ownership over the changes, but it is also offering huge potential for industrial and social innovation. The majority of energy databases are not fit for this purpose, which the project aims to change. The consortium develops, tests, and implements a [[FAIR_guiding_principles|FAIR]] and open data ecosystem in the energy field. FAIR stands for F-findable, A-accessible, I-interoperable, and R-re-usable. The EU-funded EERAdata project builds a pool of data stewards to guide the community towards fit-for-purpose data practices.

'''EERAdata logo and key visual'''. The elements of the logo include ''data points'' - symbolizing databases or data platforms - and a ''data folder'' which are connected through the ''feed symbol''. All stand for the idea of EERAdata to support FAIR and open data. The folder furthermore is a nostalgic reminder of the grand library catalogs to search for books, all of them are masterpieces on their own. [[File:EERAdata_key_visual.png|thumb|Key visual of EERAdata]]

The project is funded by [https://cordis.europa.eu/project/id/883823 Europa's Horizon 2020 Research Program].
[[File:Co-funded.png|thumb|The project is funded by the European Union, Horizon 2020 Programme]]

=== Website ===
The website is here: https://www.eeradata.eu/

=== Timeline ===
Here we report when we did what to implement EERAdata. Workshops, meetings to build a FAIR/O community for energy data, etc. [[Timeline|Timeline]]

=== EERAdata & Arts ===
The artist Barbara Bellier from Clairmont-Ferrand in France joined our workshops to illustrate the discussions. With her beautiful art, she lifted our spirit when discussions became tough and problems seemed too huge for our small project. Many thanks for your manifold inspirations!

[[File:Business card Barbara.jpg|thumb|The artist's footprint: barbara.bllr@gmail.com.]]

See the [[WS1#WS1_through_the_lense_of_an_artist|gallery from workshop 1]].

== Join and collaborate interactively! ==
The workshop is a hackathon! EERAdata is evolving jointly only! Join the discussions and work together online:
* [[Main_Page#Getting_started_with_EERAdata_wiki|EERAdata WIKI]]
* [[WS1#EERAdata_story_board|EERAdata storyboard]]
* [https://github.com/valeria6856/EERAdata EERAdata@github]
* [https://www.researchgate.net/project/Towards-a-FAIR-and-open-data-ecosystem-in-the-low-carbon-energy-research-community EERAdata@ResearchGate]

=== EERAdata story board ===
'''Objective:''' collect views from participants regarding energy data, energy metadata, FAIR/O problems etc. to support discussions, identification of gaps & needs (WP2) and elements to design the platform (WP3).

'''Questions:'''
* Q#1: What is your user story regarding FAIR/O energy data?
* Q#2: What is your user story regarding metadata?

Template to answer: As a <stakeholder>, I want <goal> so that <reason>.

'''How to post a story?'''
# Click on the link: https://padlet.com/janaschwanitz/aciywzt9fs1h70m2
# Click on plus at the right bottom to add a story.
# Choose a title depending on the question you want to answer. Choose for Q#1: FAIR/O data, or for Q#2: metadata. In the example above, the title “metadata” was chosen.
# Type your sentence to let us know where the gaps and hopes are: The template is: As a <stakeholder>, I want <goal> so that <reason>.

'''Example:''' As a data-driven energy researcher, I want utopia - i.e. one-stop access to all relevant metadata -, so that I can browse available data, check where they are from and whether I can trust them when reusing.

'''How to comment a story?'''
* One can rate stories by clicking on a number of stars.
* One can comment stories as well as comments with words.
* It is anonymous commenting and adding of stories, as long as one does not login into one's personal profile at padlet.com.

=== EERAdata wiki - How to? ===

The easiest way is you simply start writing and editing. You can install an easy editor by doing what is described on the picture to the right.
[[File:Install easy editor.png|thumb|How to install an easy editor]]

Temporarily login for guests:
* user name: guest, pwd: guest2020
Login for EERAdata consortium members:
* user name: <your_first_name+firstletter_of_your_last_name>, e.g., ''valerias''
* pwd: sent seperately to each of you individually

Here is also additional (advanced) documentation on DOKUWIKI which you might want to consult:
Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]

=== EERAdata on github ===
Link here and share your thoughts and issues! Note, work in progress.
* [https://github.com/valeria6856/EERAdata EERAdata@github]

=== EERAdata @ Research Gate ===
Link here and share your thoughts and issues! Note, work in progress.
* [https://www.researchgate.net/project/Towards-a-FAIR-and-open-data-ecosystem-in-the-low-carbon-energy-research-community EERAdata@ResearchGate]

=== Just have fun! ===
==== Metadata memory game ====
This is a little memory game where players need to identify triples. They will learn about metadata. A triple describes an example of metadata used in low carbon energy. Different formats, file types, and descriptions are introduced.
[http://eeradata.webfactional.com/memory/memory_3plus.html '''Link''']

== List of project partners ==
#[https://www.hvl.no/en/ HVL - Western Norway University of Applied Sciences]
#[https://www.ieu.edu.tr/en IUE - Izmir University of Economics]
#[https://www.ait.ac.at/ AIT - Austrian Institute of Technology]
#[https://www.gig.eu/en GIG - Central Mining Institute]
#[https://www.eera-set.eu/ EERA - European Energy Research Alliance]
#[https://www.enea.it/ ENEA - Italian National Agency for New Technologies, Energy and Sustainable Economic Development]

== Use cases in EERAdata ==
'''Definition:''' Use cases are an exercise for testing and refining the general approach towards FAIRification and opening of databases as well as to testing and refining the community platform. Use cases constitute practical commitments for implementation (PCI), i.e. the FAIRification and opening of data. Through exercises, the status quo of FAIR/O data principles in each use case is advanced by:

*Identifying taxonometric elements and metadata common among different domains of the energy system. Proper metadata will enable separating expert knowledge (and expert interest) from general knowledge and general interest, allowing coarse-grained and fine-grained navigation.
*Linking these metadata standards to existing metadata standards in other domains. Example: Weather-related data are integral to the efficient operation of PV, wind technology, or district heating. The assignment of geo-tagged information to low carbon energy technology data is thus the way forward. EERAdata will link energy domain metadata with metadata defined by ISO 19115 Geographic Metadata Information.
*Exploring a variety of challenges towards FAIRification and Opening of data. Use cases provide a means to test the EERAdata concept towards FAIRification and the opening of data. Therefore, use cases are chosen to cover, on the one hand, low hanging fruits to demonstrate do-ability, promote the FAIR/O data principle implementation and showing associated benefits for the low carbon energy research community. On the other hand, EERAdata also includes use cases where the concept is challenged, because FAIRification and opening activities are still in their infancy.
*Broad testing and application to enable trans-disciplinary research combining data from different domains and at different scales. Use cases are at the same time selected to cover wider aspects of the low carbon energy transformation, exploring different sub-domains. This ensures a broad testing and application of the FAIR/O ecosystem as well as the community platform.
*Gender as a cross-cutting issue, see [[Gender]] for more details.

'''Selection''': Altogether 4 use cases were selected:
{| class="wikitable"
|-
! Use case 1 !! Use case 2 !! Use case 3 !! Use case 4 !! Machine-actionable DMP
|-
| [[UC1|Buildings efficiency]] || [[UC2|Power transmission & distribution networks]] || [[UC3|Material solutions for low carbon energy]] || [[UC4|Low carbon energy and energy efficiency policies]] || [[DMP|Data Management Plan]]
|-
|
[[File:UC1 logo.jpg|thumb]]
||
[[File:UC 2 logo.jpg|thumb]]
||
[[File:UC 3 logo.jpg|thumb]]
||
[[File:UC 4 logo.jpg|thumb]]
||
[[File:UC 5 logo.jpg|thumb]]
|}

=== Inspiration from other use cases ===
* https://eudat.eu/use-cases

==== Metadata, ontologies, thesauri etc. in energy ====
# '''Energy Management Applications (OEMA).''' Creating ontologies can be a very tedious task if done by hand. Therefore, it is crucial to automatize this procedure. Details can be found in the Wikipedia article on [https://en.wikipedia.org/wiki/Ontology_learning Ontology learning]. Examples for the energy sector are: Javier Cuenca et al. [http://ceur-ws.org/Vol-1936/paper-08.pdf A Unified Semantic Ontology for Energy Management Applications].
[[File:OEMA-Ontology-for-Energy-Management-Applications-ontology-network-structure-Cuenca-et.png|thumb|Fig. 1 from Cuenca et al.: OEMA energy management ontology. See: http://ceur-ws.org/Vol-1936/paper-08.pdf.]]

== Gap analysis ==

'''[[Gap analysis| Gap analysis]]'''. Identification and clustering of energy research data sources (data collection or identification from existing repositories and former national and EU projects prioritizing databases relevant for the use cases, conceptual grouping/clustering of data-related use cases, building on workshop discussions). The goal is to elicit metadata and FAIR/O bottlenecks relevant across energy use cases and their positioning in the energy system. EERAdata uses Wilkinson et al. 2016 as well as the FAIR self-assessment tools (e.g., nectar and RDS) to develop criteria for assessing appliance with FAIR/O principles in the energy domain. The consortium will also discuss the possibility of developing a badge, able to display results of assessments on the community platform. Related deliverables and output: D2.2 Gap analysis report, D3.1 Platform specifications, and D2.3. Report on Research Recommendations (see [[Project_management|Project Management]]).

== Workshops in EERAdata ==

The workshop concept of EERAdata is developed along with the ''Index to FAIR Action Plan'' as recommended by [https://ec.europa.eu/info/sites/info/files/turning_fair_into_reality_1.pdf EC Expert Group on FAIR data, 2018] More specifically, the testing and discussion of the FAIR/O ecosystem (incl. the community platform) are organized through a series of workshops that take place twice a year with sequential annual foci. Each workshop takes three days. The first day is dedicated to state of the art for each workshop topic. Experts from the energy and other research communities are invited to present best practices (ensuring the participation from institutions providing research infrastructure, academia, and industry and private sector persons). Mutual learning and exchange of knowledge are facilitated in moderated discussions following presentations. The first day advances the understanding of cutting-edge concepts and approaches towards FAIR/O data (e.g., the role of metadata, data management plans, metrics, incentive mechanisms, etc.). The second day uses the knowledge and understanding obtained during the first day to translate the concepts and approaches to the domain of low carbon energy research data at the level of selected use cases. The goal is to understand the ways of data discovery and to synthesize metadata from mental models of domain experts (otherwise proposed metadata will remain artificial and, thus, not used in the community). Hence, the work done during the second day takes place in parallel groups structured around use cases (see details below). The key participants of workshops are consortium members for each use case and the groups of stewards of FAIR/O data principles recruited from invited experts. The third day synthesizes, integrates, and concludes the results achieved during the first two days (e.g., unifying and linking metadata across use cases). First, discussed concepts and approaches for the FAIR/O ecosystem, as well as the community platform, are refined. This continuously shapes the main deliverables of the workshops. Second, the agenda of the next workshop is agreed upon and specified with respect to experts to be invited and topics to be addressed. It should be noted that the first and the second day are open to participants from outside of the consortium to allow community-wide participation in EERAdata.

*'''1st Year:''' Define. Concept for FAIR implementation. Skills for FAIR.
*'''2nd Year:''' Implement. FAIR culture. FAIR Ecosystem. Skills for FAIR.
*'''3rd Year:''' Embed & sustain. Incentives, metrics, and investments for FAIR data and services.

[[File:WS concept.jpg|800px|Workshop concept of EERAdata]]

=== List of workshops ===

# [[WS1| Workshop 1]] on "FAIR principles and METADATA for low carbon energy"
# Workshop on "FAIR and open energy metadata"
# Workshop on "FAIRification put into practice"
# Workshop on "Supporting technologies for FAIRification"
# Workshop on "Sustainable models for FAIR and open low carbon energy research data"
# Workshop on "New trends in open science & steps beyond EERAdata"

== Community Platform ==

In its Work Package 3, EERAdata develops a web-based platform for the low carbon energy research community to access relevant databases in a uniform and seamless way. This Wiki section supports the development of the platform and formulates its [[functional specifications|'''Functional Specifications''']]. We conceive it as a '''living document''' collecting inputs from a variety of user perspectives, especially from the EERAdata use cases ([[UC1|Buildings efficiency]], [[UC2|Power transmission & distribution networks]], [[UC3|Material solutions for low carbon energy]] and [[UC4|Low carbon energy and energy efficiency policies]]). This living document forms the basis of Deliverable 3.1 that will guide the design and implementation of the platform. It´s main elements are:
# A [[community forum|'''Community forum''']] to support EERAdata and the wider community to develop and discuss the ecosystem for FAIR/O energy data (e.g., joint ontologies, metadata standards, assessment criteria, etc.). Along with the EERAdata Workshops, this forum is a possibility for discussing the '''users´ needs and expectations towards the platform''' online and also to support the metadata harmonization procedures (e.g., joint ontologies, metadata standards, assessment criteria, etc.).
# A [[community platform|'''Web-based dashboard''']] providing systematic access to external energy research databases in distributed open repositories. In a searchable database of metadata, the user will be able to start queries and will be linked – through an internal processing and storage device – to information on the queried databases. As such, the platform will not duplicate resources but work as a federated database and offer basic analytic features.

'''Figure:''' Web-based Platform elements (from Project proposal)

[[file:Platform_.jpg|800px]]

== Project management ==

Link to a page with [http://eeradata.webfactional.com/mediawiki-1.30.0/index.php?title=Project_management#Deliverables|page with deliverables] etc.

Functional specifications

2020-10-12T12:28:50Z

Manfred: /* Back end */

This '''living document''' forms the basis of Deliverable 3.1 that will guide the design and implementation of the platform.

==Introduction==
The intention of this living document is to reach a team consensus on what the EERAdata platform is to achieve. We expect that such consensus among the stakeholders is established step by step during the project implementation. Hereby, we draw on practices in professional software development with the purpose

* '''To specify the stakeholders´ needs.''' A Product Requirements Document (PRD) is a document containing all the requirements for a certain software product. It is written with direct user involvement to allow all stakeholders to understand what the product should do. A PRD, however, does not anticipate or define how the product will do it. In EERAdata we provide this by asking the project partners in their role as energy researchers for '''''user stories''''', comprising concrete support needs for FAIR data in their use cases.

* '''To link requirements and functionality.''' The Functional Specifications Document (FSD) specifies the functions that a software must perform. A functional specification is a more technical response to the PRD. It does not define the inner workings of the proposed system, nor does it include the specification of how the system function will be implemented. Instead, it focuses on what various outside agents (people using the program, computer peripherals, or other computers, for example) might observe when interacting with the system. In EERAdata we achieve this by providing mock-ups, descriptions of the front-end features on the EERAdata Wiki and allowing test users to access preliminary platform implementations during development. In this way feedback can be collected continually from the consortium and from a wider community through the EERAdata workshops.

* '''To specify technical implementation options.''' A Software Requirements Specification (SRS) is a description of a software system to be developed. Typically, it is written by a technical writer, a systems architect, or a software programmer. Software requirements specification is a rigorous assessment of requirements before the more specific system design stages, and its goal is to reduce later redesign. It should also provide a realistic basis for estimating risks, schedules, and, in our case, future maintenance issues. I

Thus, in the following, three perspectives are considered - user needs, software design- and software implementation issues - in the development of the platform elements and in the use of the methods and tools.

==Platform elements==

===Front end===
Methods: user stories, design thinking, mock-ups, Wiki (voting)
====Landing page====
user authentication; user guide
====Community forum====
feedback on platform; discussion of content

====Metadata selector====
*Dashboard structure
*linking to external databases
*identification of relevant databases using metadata

====Display, analysis & visualization====
*Dashboard structure
*direct access to selected databases
*display of tabular data from supported databases
*integrated applications for basic analytic features

====Session logging====
*utilizing cookies for collecting session history for later performance monitoring
*GDPR compliance (opt-in, request for stored data, request to delete PII)

===Processing and storage device===
====Metadata database model====

Methods: Design thinking, EERAdata Workshop 2, Wiki-Platform interface

In the following figure, we sketch how metadata describing the thematic character of external databases may be harmonized for use in the EERAdata platform. A similar strategy could also be used to harmonize the metadata for the specific records in the databases; this would be conceptually similar, but with a more complicated structure to the records.

[[file:DBstructure.png|800px]]

Three external databases are considered, and termed DB1, DB2, and DB3. They are each described in terms of a set of thematic classes following some standard classification, given in terms of persistent identifiers (pIDs) for the appropriate classes. DB1 and DB2 use the same standardization system, providing pIDs (Class-std1-ID) for the appropriate classes. DB3 uses a second standardization system, providing pIDs (Class-std2-ID) for its corresponding classes. We cannot assume the two systems to be commensurable.

Further, we cannot assume that either system is commensurable with the standardization system adopted for the EERAdata platform. Thus, instead of directly using the standards from the external databases, we harmonize the external standards to that used by the EERAdata platform. This is shown as the tables Std1-harmonization and Std2-harmonization, which constitute correspondence tables between the external pIDs and the pIDs used internally by EERAdata (EERAdata-std-ID). The correspondence tables must accurately relate standards that may be at different levels of precision and with different approaches to classification. It is thus essential that the tables are constructed with input from domain experts.

The correspondence tables allow us to describe the external databases in a consistent fashion using the internal standard for the platform. Needed detail is provided internally, e.g., giving a short class name and a description as shown in the figure. Beyond using the classes as a nomenclature for thematic content, ontological relations between the classes can be expressed, e.g., as a Class-hierarchy specifying which classes have others as subclasses, shown in the figure as pairings of pIDs for the classes along with their separation in the hierarachy. Crucially, it is not necessary to use the ontological structures of the external databases, although they must be accounted for in preparing the correspondence tables.

===='Data' database====
The EERAdata platform is intended to build on external resources as far as possible, minimizing internal storage (and computation requirements. The complexity will depend on the visualization requirements that emerge in the course of the project. At the current stage, it is not possible to be more specific without some external databases in mind.
====Database interface====
to support standardization and harmonization process
====Open core search====
functionality to support the establishment of ontologies?
====Evaluation of session logs====

===Back end===
*Interfaces to external resources (APIs, …); communication with platform owners, support by Use Case Leaders required
*Interfaces to import metadata from external sources (provided by the Use Cases)
*Data preparation for front end
*User account management
*User group management
*...
Methods: software development, establishment of communication channels with database holders

===Software system requirements===
*Usability
*Graphic design
*Reliability
*Availability
*Adherence to IPRs
*Data protection
*Security
*Migration and future maintenance
*…

==Methods and tools==
To collect expectations and needs, we must account for different perspectives:
# energy research expertise from use cases & gap analysis;
# data science expertise from FAIR/O community; and
# process expertise from standardisation community

===Design thinking===
Which tools will we use to create the mock-ups?
Design suggestions are posted on the Wiki for voting and feedback within the project community.

===User stories===

As a first step, the use case leaders and other use-case members are involved in formulating the needs and requirements. As an important tool, we plan to use '''user stories''' to be provided by them or other stakeholders from the energy research community. User stories put features in the context of what the user needs to accomplish. They describe the task or feature, but not how the developers should implement it. First step: invite Use Case leaders and members to collect user stories on the Wiki. Second step: approach external stakeholders for user stories (database holders, interoperability community…).

===EERAdata Workshops===

===Community forum===

===EERAdata Wiki===

Functional specifications

2020-10-12T12:25:22Z

Manfred: /* Platform elements */

This '''living document''' forms the basis of Deliverable 3.1 that will guide the design and implementation of the platform.

==Introduction==
The intention of this living document is to reach a team consensus on what the EERAdata platform is to achieve. We expect that such consensus among the stakeholders is established step by step during the project implementation. Hereby, we draw on practices in professional software development with the purpose

* '''To specify the stakeholders´ needs.''' A Product Requirements Document (PRD) is a document containing all the requirements for a certain software product. It is written with direct user involvement to allow all stakeholders to understand what the product should do. A PRD, however, does not anticipate or define how the product will do it. In EERAdata we provide this by asking the project partners in their role as energy researchers for '''''user stories''''', comprising concrete support needs for FAIR data in their use cases.

* '''To link requirements and functionality.''' The Functional Specifications Document (FSD) specifies the functions that a software must perform. A functional specification is a more technical response to the PRD. It does not define the inner workings of the proposed system, nor does it include the specification of how the system function will be implemented. Instead, it focuses on what various outside agents (people using the program, computer peripherals, or other computers, for example) might observe when interacting with the system. In EERAdata we achieve this by providing mock-ups, descriptions of the front-end features on the EERAdata Wiki and allowing test users to access preliminary platform implementations during development. In this way feedback can be collected continually from the consortium and from a wider community through the EERAdata workshops.

* '''To specify technical implementation options.''' A Software Requirements Specification (SRS) is a description of a software system to be developed. Typically, it is written by a technical writer, a systems architect, or a software programmer. Software requirements specification is a rigorous assessment of requirements before the more specific system design stages, and its goal is to reduce later redesign. It should also provide a realistic basis for estimating risks, schedules, and, in our case, future maintenance issues. I

Thus, in the following, three perspectives are considered - user needs, software design- and software implementation issues - in the development of the platform elements and in the use of the methods and tools.

==Platform elements==

===Front end===
Methods: user stories, design thinking, mock-ups, Wiki (voting)
====Landing page====
user authentication; user guide
====Community forum====
feedback on platform; discussion of content

====Metadata selector====
*Dashboard structure
*linking to external databases
*identification of relevant databases using metadata

====Display, analysis & visualization====
*Dashboard structure
*direct access to selected databases
*display of tabular data from supported databases
*integrated applications for basic analytic features

====Session logging====
*utilizing cookies for collecting session history for later performance monitoring
*GDPR compliance (opt-in, request for stored data, request to delete PII)

===Processing and storage device===
====Metadata database model====

Methods: Design thinking, EERAdata Workshop 2, Wiki-Platform interface

In the following figure, we sketch how metadata describing the thematic character of external databases may be harmonized for use in the EERAdata platform. A similar strategy could also be used to harmonize the metadata for the specific records in the databases; this would be conceptually similar, but with a more complicated structure to the records.

[[file:DBstructure.png|800px]]

Three external databases are considered, and termed DB1, DB2, and DB3. They are each described in terms of a set of thematic classes following some standard classification, given in terms of persistent identifiers (pIDs) for the appropriate classes. DB1 and DB2 use the same standardization system, providing pIDs (Class-std1-ID) for the appropriate classes. DB3 uses a second standardization system, providing pIDs (Class-std2-ID) for its corresponding classes. We cannot assume the two systems to be commensurable.

Further, we cannot assume that either system is commensurable with the standardization system adopted for the EERAdata platform. Thus, instead of directly using the standards from the external databases, we harmonize the external standards to that used by the EERAdata platform. This is shown as the tables Std1-harmonization and Std2-harmonization, which constitute correspondence tables between the external pIDs and the pIDs used internally by EERAdata (EERAdata-std-ID). The correspondence tables must accurately relate standards that may be at different levels of precision and with different approaches to classification. It is thus essential that the tables are constructed with input from domain experts.

The correspondence tables allow us to describe the external databases in a consistent fashion using the internal standard for the platform. Needed detail is provided internally, e.g., giving a short class name and a description as shown in the figure. Beyond using the classes as a nomenclature for thematic content, ontological relations between the classes can be expressed, e.g., as a Class-hierarchy specifying which classes have others as subclasses, shown in the figure as pairings of pIDs for the classes along with their separation in the hierarachy. Crucially, it is not necessary to use the ontological structures of the external databases, although they must be accounted for in preparing the correspondence tables.

===='Data' database====
The EERAdata platform is intended to build on external resources as far as possible, minimizing internal storage (and computation requirements. The complexity will depend on the visualization requirements that emerge in the course of the project. At the current stage, it is not possible to be more specific without some external databases in mind.
====Database interface====
to support standardization and harmonization process
====Open core search====
functionality to support the establishment of ontologies?
====Evaluation of session logs====

===Back end===
*Interfaces to external resources (APIs, …); communication with platform owners, support by Use Case Leaders required
*Interfaces to import metadata from external sources (provided by the Use Cases)
*Data preparation for front end
*User group management
*...
Methods: software development, establishment of communication channels with database holders

===Software system requirements===
*Usability
*Graphic design
*Reliability
*Availability
*Adherence to IPRs
*Data protection
*Security
*Migration and future maintenance
*…

==Methods and tools==
To collect expectations and needs, we must account for different perspectives:
# energy research expertise from use cases & gap analysis;
# data science expertise from FAIR/O community; and
# process expertise from standardisation community

===Design thinking===
Which tools will we use to create the mock-ups?
Design suggestions are posted on the Wiki for voting and feedback within the project community.

===User stories===

As a first step, the use case leaders and other use-case members are involved in formulating the needs and requirements. As an important tool, we plan to use '''user stories''' to be provided by them or other stakeholders from the energy research community. User stories put features in the context of what the user needs to accomplish. They describe the task or feature, but not how the developers should implement it. First step: invite Use Case leaders and members to collect user stories on the Wiki. Second step: approach external stakeholders for user stories (database holders, interoperability community…).

===EERAdata Workshops===

===Community forum===

===EERAdata Wiki===

Functional specifications

2020-10-12T12:06:06Z

Manfred: /* Dashboard */

This '''living document''' forms the basis of Deliverable 3.1 that will guide the design and implementation of the platform.

==Introduction==
The intention of this living document is to reach a team consensus on what the EERAdata platform is to achieve. We expect that such consensus among the stakeholders is established step by step during the project implementation. Hereby, we draw on practices in professional software development with the purpose

* '''To specify the stakeholders´ needs.''' A Product Requirements Document (PRD) is a document containing all the requirements for a certain software product. It is written with direct user involvement to allow all stakeholders to understand what the product should do. A PRD, however, does not anticipate or define how the product will do it. In EERAdata we provide this by asking the project partners in their role as energy researchers for '''''user stories''''', comprising concrete support needs for FAIR data in their use cases.

* '''To link requirements and functionality.''' The Functional Specifications Document (FSD) specifies the functions that a software must perform. A functional specification is a more technical response to the PRD. It does not define the inner workings of the proposed system, nor does it include the specification of how the system function will be implemented. Instead, it focuses on what various outside agents (people using the program, computer peripherals, or other computers, for example) might observe when interacting with the system. In EERAdata we achieve this by providing mock-ups, descriptions of the front-end features on the EERAdata Wiki and allowing test users to access preliminary platform implementations during development. In this way feedback can be collected continually from the consortium and from a wider community through the EERAdata workshops.

* '''To specify technical implementation options.''' A Software Requirements Specification (SRS) is a description of a software system to be developed. Typically, it is written by a technical writer, a systems architect, or a software programmer. Software requirements specification is a rigorous assessment of requirements before the more specific system design stages, and its goal is to reduce later redesign. It should also provide a realistic basis for estimating risks, schedules, and, in our case, future maintenance issues. I

Thus, in the following, three perspectives are considered - user needs, software design- and software implementation issues - in the development of the platform elements and in the use of the methods and tools.

==Platform elements==

===Front end===
Methods: user stories, design thinking, mock-ups, Wiki (voting)
====Landing page====
user authentication; user guide
====Community forum====
feedback on platform; discussion of content
====Dashboard====
*identification of relevant databases using metadata
*direct access to selected databases
*integrated applications for basic analytic features

====Display, analysis & visualization====
====Session logging====
for later performance monitoring

===Processing and storage device===
====Metadata database model====

Methods: Design thinking, EERAdata Workshop 2, Wiki-Platform interface

In the following figure, we sketch how metadata describing the thematic character of external databases may be harmonized for use in the EERAdata platform. A similar strategy could also be used to harmonize the metadata for the specific records in the databases; this would be conceptually similar, but with a more complicated structure to the records.

[[file:DBstructure.png|800px]]

Three external databases are considered, and termed DB1, DB2, and DB3. They are each described in terms of a set of thematic classes following some standard classification, given in terms of persistent identifiers (pIDs) for the appropriate classes. DB1 and DB2 use the same standardization system, providing pIDs (Class-std1-ID) for the appropriate classes. DB3 uses a second standardization system, providing pIDs (Class-std2-ID) for its corresponding classes. We cannot assume the two systems to be commensurable.

Further, we cannot assume that either system is commensurable with the standardization system adopted for the EERAdata platform. Thus, instead of directly using the standards from the external databases, we harmonize the external standards to that used by the EERAdata platform. This is shown as the tables Std1-harmonization and Std2-harmonization, which constitute correspondence tables between the external pIDs and the pIDs used internally by EERAdata (EERAdata-std-ID). The correspondence tables must accurately relate standards that may be at different levels of precision and with different approaches to classification. It is thus essential that the tables are constructed with input from domain experts.

The correspondence tables allow us to describe the external databases in a consistent fashion using the internal standard for the platform. Needed detail is provided internally, e.g., giving a short class name and a description as shown in the figure. Beyond using the classes as a nomenclature for thematic content, ontological relations between the classes can be expressed, e.g., as a Class-hierarchy specifying which classes have others as subclasses, shown in the figure as pairings of pIDs for the classes along with their separation in the hierarachy. Crucially, it is not necessary to use the ontological structures of the external databases, although they must be accounted for in preparing the correspondence tables.

===='Data' database====
The EERAdata platform is intended to build on external resources as far as possible, minimizing internal storage (and computation requirements. The complexity will depend on the visualization requirements that emerge in the course of the project. At the current stage, it is not possible to be more specific without some external databases in mind.
====Database interface====
to support standardization and harmonization process
====Open core search====
functionality to support the establishment of ontologies?
====Evaluation of session logs====

===Back end===
*Interfaces to external resources (APIs, …); communication with platform owners, support by Use Case Leaders required
*Interfaces to import metadata from external sources (provided by the Use Cases)
*Data preparation for front end
*User group management
*...
Methods: software development, establishment of communication channels with database holders

===Software system requirements===
*Usability
*Graphic design
*Reliability
*Availability
*Adherence to IPRs
*Data protection
*Security
*Migration and future maintenance
*…

==Methods and tools==
To collect expectations and needs, we must account for different perspectives:
# energy research expertise from use cases & gap analysis;
# data science expertise from FAIR/O community; and
# process expertise from standardisation community

===Design thinking===
Which tools will we use to create the mock-ups?
Design suggestions are posted on the Wiki for voting and feedback within the project community.

===User stories===

As a first step, the use case leaders and other use-case members are involved in formulating the needs and requirements. As an important tool, we plan to use '''user stories''' to be provided by them or other stakeholders from the energy research community. User stories put features in the context of what the user needs to accomplish. They describe the task or feature, but not how the developers should implement it. First step: invite Use Case leaders and members to collect user stories on the Wiki. Second step: approach external stakeholders for user stories (database holders, interoperability community…).

===EERAdata Workshops===

===Community forum===

===EERAdata Wiki===

Functional specifications

2020-10-12T12:01:57Z

Manfred: /* Back end */

This '''living document''' forms the basis of Deliverable 3.1 that will guide the design and implementation of the platform.

==Introduction==
The intention of this living document is to reach a team consensus on what the EERAdata platform is to achieve. We expect that such consensus among the stakeholders is established step by step during the project implementation. Hereby, we draw on practices in professional software development with the purpose

* '''To specify the stakeholders´ needs.''' A Product Requirements Document (PRD) is a document containing all the requirements for a certain software product. It is written with direct user involvement to allow all stakeholders to understand what the product should do. A PRD, however, does not anticipate or define how the product will do it. In EERAdata we provide this by asking the project partners in their role as energy researchers for '''''user stories''''', comprising concrete support needs for FAIR data in their use cases.

* '''To link requirements and functionality.''' The Functional Specifications Document (FSD) specifies the functions that a software must perform. A functional specification is a more technical response to the PRD. It does not define the inner workings of the proposed system, nor does it include the specification of how the system function will be implemented. Instead, it focuses on what various outside agents (people using the program, computer peripherals, or other computers, for example) might observe when interacting with the system. In EERAdata we achieve this by providing mock-ups, descriptions of the front-end features on the EERAdata Wiki and allowing test users to access preliminary platform implementations during development. In this way feedback can be collected continually from the consortium and from a wider community through the EERAdata workshops.

* '''To specify technical implementation options.''' A Software Requirements Specification (SRS) is a description of a software system to be developed. Typically, it is written by a technical writer, a systems architect, or a software programmer. Software requirements specification is a rigorous assessment of requirements before the more specific system design stages, and its goal is to reduce later redesign. It should also provide a realistic basis for estimating risks, schedules, and, in our case, future maintenance issues. I

Thus, in the following, three perspectives are considered - user needs, software design- and software implementation issues - in the development of the platform elements and in the use of the methods and tools.

==Platform elements==

===Front end===
Methods: user stories, design thinking, mock-ups, Wiki (voting)
====Landing page====
user authentication; user guide
====Community forum====
feedback on platform; discussion of content
====Dashboard====
queries
====Display, analysis & visualization====
====Session logging====
for later performance monitoring

===Processing and storage device===
====Metadata database model====

Methods: Design thinking, EERAdata Workshop 2, Wiki-Platform interface

In the following figure, we sketch how metadata describing the thematic character of external databases may be harmonized for use in the EERAdata platform. A similar strategy could also be used to harmonize the metadata for the specific records in the databases; this would be conceptually similar, but with a more complicated structure to the records.

[[file:DBstructure.png|800px]]

Three external databases are considered, and termed DB1, DB2, and DB3. They are each described in terms of a set of thematic classes following some standard classification, given in terms of persistent identifiers (pIDs) for the appropriate classes. DB1 and DB2 use the same standardization system, providing pIDs (Class-std1-ID) for the appropriate classes. DB3 uses a second standardization system, providing pIDs (Class-std2-ID) for its corresponding classes. We cannot assume the two systems to be commensurable.

Further, we cannot assume that either system is commensurable with the standardization system adopted for the EERAdata platform. Thus, instead of directly using the standards from the external databases, we harmonize the external standards to that used by the EERAdata platform. This is shown as the tables Std1-harmonization and Std2-harmonization, which constitute correspondence tables between the external pIDs and the pIDs used internally by EERAdata (EERAdata-std-ID). The correspondence tables must accurately relate standards that may be at different levels of precision and with different approaches to classification. It is thus essential that the tables are constructed with input from domain experts.

The correspondence tables allow us to describe the external databases in a consistent fashion using the internal standard for the platform. Needed detail is provided internally, e.g., giving a short class name and a description as shown in the figure. Beyond using the classes as a nomenclature for thematic content, ontological relations between the classes can be expressed, e.g., as a Class-hierarchy specifying which classes have others as subclasses, shown in the figure as pairings of pIDs for the classes along with their separation in the hierarachy. Crucially, it is not necessary to use the ontological structures of the external databases, although they must be accounted for in preparing the correspondence tables.

===='Data' database====
The EERAdata platform is intended to build on external resources as far as possible, minimizing internal storage (and computation requirements. The complexity will depend on the visualization requirements that emerge in the course of the project. At the current stage, it is not possible to be more specific without some external databases in mind.
====Database interface====
to support standardization and harmonization process
====Open core search====
functionality to support the establishment of ontologies?
====Evaluation of session logs====

===Back end===
*Interfaces to external resources (APIs, …); communication with platform owners, support by Use Case Leaders required
*Interfaces to import metadata from external sources (provided by the Use Cases)
*Data preparation for front end
*User group management
*...
Methods: software development, establishment of communication channels with database holders

===Software system requirements===
*Usability
*Graphic design
*Reliability
*Availability
*Adherence to IPRs
*Data protection
*Security
*Migration and future maintenance
*…

==Methods and tools==
To collect expectations and needs, we must account for different perspectives:
# energy research expertise from use cases & gap analysis;
# data science expertise from FAIR/O community; and
# process expertise from standardisation community

===Design thinking===
Which tools will we use to create the mock-ups?
Design suggestions are posted on the Wiki for voting and feedback within the project community.

===User stories===

As a first step, the use case leaders and other use-case members are involved in formulating the needs and requirements. As an important tool, we plan to use '''user stories''' to be provided by them or other stakeholders from the energy research community. User stories put features in the context of what the user needs to accomplish. They describe the task or feature, but not how the developers should implement it. First step: invite Use Case leaders and members to collect user stories on the Wiki. Second step: approach external stakeholders for user stories (database holders, interoperability community…).

===EERAdata Workshops===

===Community forum===

===EERAdata Wiki===

Main Page

2020-10-12T11:57:03Z

Manfred: /* Community Platform */

Welcome to the EERAdata MediaWiki!

== The project EERAdata ==

'''Towards a FAIR and open data ecosystem in the low carbon energy research community.''' Transparent, re-usable, and integrated energy data enable society to choose, monitor, and implement sustainable transition pathways. It is not only a prerequisite for people to have ownership over the changes, but it is also offering huge potential for industrial and social innovation. The majority of energy databases are not fit for this purpose, which the project aims to change. The consortium develops, tests, and implements a [[FAIR_guiding_principles|FAIR]] and open data ecosystem in the energy field. FAIR stands for F-findable, A-accessible, I-interoperable, and R-re-usable. The EU-funded EERAdata project builds a pool of data stewards to guide the community towards fit-for-purpose data practices.

'''EERAdata logo and key visual'''. The elements of the logo include ''data points'' - symbolizing databases or data platforms - and a ''data folder'' which are connected through the ''feed symbol''. All stand for the idea of EERAdata to support FAIR and open data. The folder furthermore is a nostalgic reminder of the grand library catalogs to search for books, all of them are masterpieces on their own. [[File:EERAdata_key_visual.png|thumb|Key visual of EERAdata]]

The project is funded by [https://cordis.europa.eu/project/id/883823 Europa's Horizon 2020 Research Program].
[[File:Co-funded.png|thumb|The project is funded by the European Union, Horizon 2020 Programme]]

=== Website ===
The website is here: https://www.eeradata.eu/

=== Timeline ===
Here we report when we did what to implement EERAdata. Workshops, meetings to build a FAIR/O community for energy data, etc. [[Timeline|Timeline]]

=== EERAdata & Arts ===
The artist Barbara Bellier from Clairmont-Ferrand in France joined our workshops to illustrate the discussions. With her beautiful art, she lifted our spirit when discussions became tough and problems seemed too huge for our small project. Many thanks for your manifold inspirations!

[[File:Business card Barbara.jpg|thumb|The artist's footprint: barbara.bllr@gmail.com.]]

See the [[WS1#WS1_through_the_lense_of_an_artist|gallery from workshop 1]].

== Join and collaborate interactively! ==
The workshop is a hackathon! EERAdata is evolving jointly only! Join the discussions and work together online:
* [[Main_Page#Getting_started_with_EERAdata_wiki|EERAdata WIKI]]
* [[WS1#EERAdata_story_board|EERAdata storyboard]]
* [https://github.com/valeria6856/EERAdata EERAdata@github]
* [https://www.researchgate.net/project/Towards-a-FAIR-and-open-data-ecosystem-in-the-low-carbon-energy-research-community EERAdata@ResearchGate]

=== EERAdata story board ===
'''Objective:''' collect views from participants regarding energy data, energy metadata, FAIR/O problems etc. to support discussions, identification of gaps & needs (WP2) and elements to design the platform (WP3).

'''Questions:'''
* Q#1: What is your user story regarding FAIR/O energy data?
* Q#2: What is your user story regarding metadata?

Template to answer: As a <stakeholder>, I want <goal> so that <reason>.

'''How to post a story?'''
# Click on the link: https://padlet.com/janaschwanitz/aciywzt9fs1h70m2
# Click on plus at the right bottom to add a story.
# Choose a title depending on the question you want to answer. Choose for Q#1: FAIR/O data, or for Q#2: metadata. In the example above, the title “metadata” was chosen.
# Type your sentence to let us know where the gaps and hopes are: The template is: As a <stakeholder>, I want <goal> so that <reason>.

'''Example:''' As a data-driven energy researcher, I want utopia - i.e. one-stop access to all relevant metadata -, so that I can browse available data, check where they are from and whether I can trust them when reusing.

'''How to comment a story?'''
* One can rate stories by clicking on a number of stars.
* One can comment stories as well as comments with words.
* It is anonymous commenting and adding of stories, as long as one does not login into one's personal profile at padlet.com.

=== EERAdata wiki - How to? ===

The easiest way is you simply start writing and editing. You can install an easy editor by doing what is described on the picture to the right.
[[File:Install easy editor.png|thumb|How to install an easy editor]]

Temporarily login for guests:
* user name: guest, pwd: guest2020
Login for EERAdata consortium members:
* user name: <your_first_name+firstletter_of_your_last_name>, e.g., ''valerias''
* pwd: sent seperately to each of you individually

Here is also additional (advanced) documentation on DOKUWIKI which you might want to consult:
Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]

=== EERAdata on github ===
Link here and share your thoughts and issues! Note, work in progress.
* [https://github.com/valeria6856/EERAdata EERAdata@github]

=== EERAdata @ Research Gate ===
Link here and share your thoughts and issues! Note, work in progress.
* [https://www.researchgate.net/project/Towards-a-FAIR-and-open-data-ecosystem-in-the-low-carbon-energy-research-community EERAdata@ResearchGate]

=== Just have fun! ===
==== Metadata memory game ====
This is a little memory game where players need to identify triples. They will learn about metadata. A triple describes an example of metadata used in low carbon energy. Different formats, file types, and descriptions are introduced.
[http://eeradata.webfactional.com/memory/memory_3plus.html '''Link''']

== List of project partners ==
#[https://www.hvl.no/en/ HVL - Western Norway University of Applied Sciences]
#[https://www.ieu.edu.tr/en IUE - Izmir University of Economics]
#[https://www.ait.ac.at/ AIT - Austrian Institute of Technology]
#[https://www.gig.eu/en GIG - Central Mining Institute]
#[https://www.eera-set.eu/ EERA - European Energy Research Alliance]
#[https://www.enea.it/ ENEA - Italian National Agency for New Technologies, Energy and Sustainable Economic Development]

== Use cases in EERAdata ==
'''Definition:''' Use cases are an exercise for testing and refining the general approach towards FAIRification and opening of databases as well as to testing and refining the community platform. Use cases constitute practical commitments for implementation (PCI), i.e. the FAIRification and opening of data. Through exercises, the status quo of FAIR/O data principles in each use case is advanced by:

*Identifying taxonometric elements and metadata common among different domains of the energy system. Proper metadata will enable separating expert knowledge (and expert interest) from general knowledge and general interest, allowing coarse-grained and fine-grained navigation.
*Linking these metadata standards to existing metadata standards in other domains. Example: Weather-related data are integral to the efficient operation of PV, wind technology, or district heating. The assignment of geo-tagged information to low carbon energy technology data is thus the way forward. EERAdata will link energy domain metadata with metadata defined by ISO 19115 Geographic Metadata Information.
*Exploring a variety of challenges towards FAIRification and Opening of data. Use cases provide a means to test the EERAdata concept towards FAIRification and the opening of data. Therefore, use cases are chosen to cover, on the one hand, low hanging fruits to demonstrate do-ability, promote the FAIR/O data principle implementation and showing associated benefits for the low carbon energy research community. On the other hand, EERAdata also includes use cases where the concept is challenged, because FAIRification and opening activities are still in their infancy.
*Broad testing and application to enable trans-disciplinary research combining data from different domains and at different scales. Use cases are at the same time selected to cover wider aspects of the low carbon energy transformation, exploring different sub-domains. This ensures a broad testing and application of the FAIR/O ecosystem as well as the community platform.
*Gender as a cross-cutting issue, see [[Gender]] for more details.

'''Selection''': Altogether 4 use cases were selected:
{| class="wikitable"
|-
! Use case 1 !! Use case 2 !! Use case 3 !! Use case 4 !! Machine-actionable DMP
|-
| [[UC1|Buildings efficiency]] || [[UC2|Power transmission & distribution networks]] || [[UC3|Material solutions for low carbon energy]] || [[UC4|Low carbon energy and energy efficiency policies]] || [[DMP|Data Management Plan]]
|-
|
[[File:UC1 logo.jpg|thumb]]
||
[[File:UC 2 logo.jpg|thumb]]
||
[[File:UC 3 logo.jpg|thumb]]
||
[[File:UC 4 logo.jpg|thumb]]
||
[[File:UC 5 logo.jpg|thumb]]
|}

=== Inspiration from other use cases ===
* https://eudat.eu/use-cases

==== Metadata, ontologies, thesauri etc. in energy ====
# '''Energy Management Applications (OEMA).''' Creating ontologies can be a very tedious task if done by hand. Therefore, it is crucial to automatize this procedure. Details can be found in the Wikipedia article on [https://en.wikipedia.org/wiki/Ontology_learning Ontology learning]. Examples for the energy sector are: Javier Cuenca et al. [http://ceur-ws.org/Vol-1936/paper-08.pdf A Unified Semantic Ontology for Energy Management Applications].
[[File:OEMA-Ontology-for-Energy-Management-Applications-ontology-network-structure-Cuenca-et.png|thumb|Fig. 1 from Cuenca et al.: OEMA energy management ontology. See: http://ceur-ws.org/Vol-1936/paper-08.pdf.]]

== Gap analysis ==

'''[[Gap analysis| Gap analysis]]'''. Identification and clustering of energy research data sources (data collection or identification from existing repositories and former national and EU projects prioritizing databases relevant for the use cases, conceptual grouping/clustering of data-related use cases, building on workshop discussions). The goal is to elicit metadata and FAIR/O bottlenecks relevant across energy use cases and their positioning in the energy system. EERAdata uses Wilkinson et al. 2016 as well as the FAIR self-assessment tools (e.g., nectar and RDS) to develop criteria for assessing appliance with FAIR/O principles in the energy domain. The consortium will also discuss the possibility of developing a badge, able to display results of assessments on the community platform. Related deliverables and output: D2.2 Gap analysis report, D3.1 Platform specifications, and D2.3. Report on Research Recommendations (see [[Project_management|Project Management]]).

== Workshops in EERAdata ==

The workshop concept of EERAdata is developed along with the ''Index to FAIR Action Plan'' as recommended by [https://ec.europa.eu/info/sites/info/files/turning_fair_into_reality_1.pdf EC Expert Group on FAIR data, 2018] More specifically, the testing and discussion of the FAIR/O ecosystem (incl. the community platform) are organized through a series of workshops that take place twice a year with sequential annual foci. Each workshop takes three days. The first day is dedicated to state of the art for each workshop topic. Experts from the energy and other research communities are invited to present best practices (ensuring the participation from institutions providing research infrastructure, academia, and industry and private sector persons). Mutual learning and exchange of knowledge are facilitated in moderated discussions following presentations. The first day advances the understanding of cutting-edge concepts and approaches towards FAIR/O data (e.g., the role of metadata, data management plans, metrics, incentive mechanisms, etc.). The second day uses the knowledge and understanding obtained during the first day to translate the concepts and approaches to the domain of low carbon energy research data at the level of selected use cases. The goal is to understand the ways of data discovery and to synthesize metadata from mental models of domain experts (otherwise proposed metadata will remain artificial and, thus, not used in the community). Hence, the work done during the second day takes place in parallel groups structured around use cases (see details below). The key participants of workshops are consortium members for each use case and the groups of stewards of FAIR/O data principles recruited from invited experts. The third day synthesizes, integrates, and concludes the results achieved during the first two days (e.g., unifying and linking metadata across use cases). First, discussed concepts and approaches for the FAIR/O ecosystem, as well as the community platform, are refined. This continuously shapes the main deliverables of the workshops. Second, the agenda of the next workshop is agreed upon and specified with respect to experts to be invited and topics to be addressed. It should be noted that the first and the second day are open to participants from outside of the consortium to allow community-wide participation in EERAdata.

*'''1st Year:''' Define. Concept for FAIR implementation. Skills for FAIR.
*'''2nd Year:''' Implement. FAIR culture. FAIR Ecosystem. Skills for FAIR.
*'''3rd Year:''' Embed & sustain. Incentives, metrics, and investments for FAIR data and services.

[[File:WS concept.jpg|800px|Workshop concept of EERAdata]]

=== List of workshops ===

# [[WS1| Workshop 1]] on "FAIR principles and METADATA for low carbon energy"
# Workshop on "FAIR and open energy metadata"
# Workshop on "FAIRification put into practice"
# Workshop on "Supporting technologies for FAIRification"
# Workshop on "Sustainable models for FAIR and open low carbon energy research data"
# Workshop on "New trends in open science & steps beyond EERAdata"

== Community Platform ==

In its Work Package 3, EERAdata develops a web-based platform for the low carbon energy research community to access relevant databases in a uniform and seamless way. This Wiki section supports the development of the platform and formulates its [[functional specifications|'''Functional Specifications''']]. We conceive it as a '''living document''' collecting inputs from a variety of user perspectives, especially from the EERAdata use cases ([[UC1|Buildings efficiency]], [[UC2|Power transmission & distribution networks]], [[UC3|Material solutions for low carbon energy]] and [[UC4|Low carbon energy and energy efficiency policies]]). This living document forms the basis of Deliverable 3.1 that will guide the design and implementation of the platform. It´s main elements are:
# A [[community forum|'''Community forum''']] to support EERAdata and the wider community to develop and discuss the ecosystem for FAIR/O energy data (e.g., joint ontologies, metadata standards, assessment criteria, etc.). Along with the EERAdata Workshops, this forum is a possibility for discussing the '''users´ needs and expectations towards the platform''' online and also to support the metadata harmonization procedures (e.g., joint ontologies, metadata standards, assessment criteria, etc.).
# A [[community platform|'''Web-based Dashboard''']] providing systematic access to external energy research databases in distributed open repositories. In a searchable database of metadata, the user will be able to start queries and will be linked – through an internal processing and storage device – to information on the queried databases. As such, the platform will not duplicate resources but work as a federated database and offer basic analytic features.

'''Figure:''' Web-based Platform elements (from Project proposal)

[[file:Platform_.jpg|800px]]

== Project management ==

Link to a page with [http://eeradata.webfactional.com/mediawiki-1.30.0/index.php?title=Project_management#Deliverables|page with deliverables] etc.

Functional specifications

2020-10-05T16:45:31Z

Manfred: /* Metadata database model */

This '''living document''' forms the basis of Deliverable 3.1 that will guide the design and implementation of the platform.

==Introduction==
The intention of this living document is to reach a team consensus on what the EERAdata platform is to achieve. We expect that such consensus among the stakeholders is established step by step during the project implementation. Hereby, we draw on practices in professional software development with the purpose

* '''To specify the stakeholders´ needs.''' A Product Requirements Document (PRD) is a document containing all the requirements for a certain software product. It is written with direct user involvement to allow all stakeholders to understand what the product should do. A PRD, however, does not anticipate or define how the product will do it. In EERAdata we provide this by asking the project partners in their role as energy researchers for '''''user stories''''', comprising concrete support needs for FAIR data in their use cases.

* '''To link requirements and functionality.''' The Functional Specifications Document (FSD) specifies the functions that a software must perform. A functional specification is a more technical response to the PRD. It does not define the inner workings of the proposed system, nor does it include the specification of how the system function will be implemented. Instead, it focuses on what various outside agents (people using the program, computer peripherals, or other computers, for example) might observe when interacting with the system. In EERAdata we achieve this by providing mock-ups, descriptions of the front-end features on the EERAdata Wiki and allowing test users to access preliminary platform implementations during development. In this way feedback can be collected continually from the consortium and from a wider community through the EERAdata workshops.

* '''To specify technical implementation options.''' A Software Requirements Specification (SRS) is a description of a software system to be developed. Typically, it is written by a technical writer, a systems architect, or a software programmer. Software requirements specification is a rigorous assessment of requirements before the more specific system design stages, and its goal is to reduce later redesign. It should also provide a realistic basis for estimating risks, schedules, and, in our case, future maintenance issues. I

Thus, in the following, three perspectives are considered - user needs, software design- and software implementation issues - in the development of the platform elements and in the use of the methods and tools.

==Platform elements==

===Front end===
Methods: user stories, design thinking, mock-ups, Wiki (voting)
====Landing page====
user authentication; user guide
====Community forum====
feedback on platform; discussion of content
====Dashboard====
queries
====Display, analysis & visualization====
====Session logging====
for later performance monitoring

===Processing and storage device===
====Metadata database model====

Methods: Design thinking, EERAdata Workshop 2, Wiki-Platform interface

In the following figure, we sketch how metadata describing the thematic character of external databases may be harmonized for use in the EERAdata platform. A similar strategy could also be used to harmonize the metadata for the specific records in the databases; this would be conceptually similar, but with a more complicated structure to the records.

[[file:DBstructure.png|800px]]

Three external databases are considered, and termed DB1, DB2, and DB3. They are each described in terms of a set of thematic classes following some standard classification, given in terms of persistent identifiers (pIDs) for the appropriate classes. DB1 and DB2 use the same standardization system, providing pIDs (Class-std1-ID) for the appropriate classes. DB3 uses a second standardization system, providing pIDs (Class-std2-ID) for its corresponding classes. We cannot assume the two systems to be commensurable.

Further, we cannot assume that either system is commensurable with the standardization system adopted for the EERAdata platform. Thus, instead of directly using the standards from the external databases, we harmonize the external standards to that used by the EERAdata platform. This is shown as the tables Std1-harmonization and Std2-harmonization, which constitute correspondence tables between the external pIDs and the pIDs used internally by EERAdata (EERAdata-std-ID). The correspondence tables must accurately relate standards that may be at different levels of precision and with different approaches to classification. It is thus essential that the tables are constructed with input from domain experts.

The correspondence tables allow us to describe the external databases in a consistent fashion using the internal standard for the platform. Needed detail is provided internally, e.g., giving a short class name and a description as shown in the figure. Beyond using the classes as a nomenclature for thematic content, ontological relations between the classes can be expressed, e.g., as a Class-hierarchy specifying which classes have others as subclasses, shown in the figure as pairings of pIDs for the classes along with their separation in the hierarachy. Crucially, it is not necessary to use the ontological structures of the external databases, although they must be accounted for in preparing the correspondence tables.

===='Data' database====
The EERAdata platform is intended to build on external resources as far as possible, minimizing internal storage (and computation requirements. The complexity will depend on the visualization requirements that emerge in the course of the project. At the current stage, it is not possible to be more specific without some external databases in mind.
====Database interface====
to support standardization and harmonization process
====Open core search====
functionality to support the establishment of ontologies?
====Evaluation of session logs====

===Back end===
*Interfaces to external resources (APIs, …); communication with platform owners, support by Use Case Leaders required
*Interfaces to import metadata from external sources (provided by the Use Cases)
*Data preparation for front end
*…
Methods: software development, establishment of communication channels with database holders

===Software system requirements===
*Usability
*Graphic design
*Reliability
*Availability
*Adherence to IPRs
*Data protection
*Security
*Migration and future maintenance
*…

==Methods and tools==
To collect expectations and needs, we must account for different perspectives:
# energy research expertise from use cases & gap analysis;
# data science expertise from FAIR/O community; and
# process expertise from standardisation community

===Design thinking===
Which tools will we use to create the mock-ups?
Design suggestions are posted on the Wiki for voting and feedback within the project community.

===User stories===

As a first step, the use case leaders and other use-case members are involved in formulating the needs and requirements. As an important tool, we plan to use '''user stories''' to be provided by them or other stakeholders from the energy research community. User stories put features in the context of what the user needs to accomplish. They describe the task or feature, but not how the developers should implement it. First step: invite Use Case leaders and members to collect user stories on the Wiki. Second step: approach external stakeholders for user stories (database holders, interoperability community…).

===EERAdata Workshops===

===Community forum===

===EERAdata Wiki===

File:DBstructure.png

2020-10-05T16:41:09Z

Manfred:

Functional specifications

2020-10-05T16:40:21Z

Manfred: /* Methods and tools */

This '''living document''' forms the basis of Deliverable 3.1 that will guide the design and implementation of the platform.

==Introduction==
The intention of this living document is to reach a team consensus on what the EERAdata platform is to achieve. We expect that such consensus among the stakeholders is established step by step during the project implementation. Hereby, we draw on practices in professional software development with the purpose

* '''To specify the stakeholders´ needs.''' A Product Requirements Document (PRD) is a document containing all the requirements for a certain software product. It is written with direct user involvement to allow all stakeholders to understand what the product should do. A PRD, however, does not anticipate or define how the product will do it. In EERAdata we provide this by asking the project partners in their role as energy researchers for '''''user stories''''', comprising concrete support needs for FAIR data in their use cases.

* '''To link requirements and functionality.''' The Functional Specifications Document (FSD) specifies the functions that a software must perform. A functional specification is a more technical response to the PRD. It does not define the inner workings of the proposed system, nor does it include the specification of how the system function will be implemented. Instead, it focuses on what various outside agents (people using the program, computer peripherals, or other computers, for example) might observe when interacting with the system. In EERAdata we achieve this by providing mock-ups, descriptions of the front-end features on the EERAdata Wiki and allowing test users to access preliminary platform implementations during development. In this way feedback can be collected continually from the consortium and from a wider community through the EERAdata workshops.

* '''To specify technical implementation options.''' A Software Requirements Specification (SRS) is a description of a software system to be developed. Typically, it is written by a technical writer, a systems architect, or a software programmer. Software requirements specification is a rigorous assessment of requirements before the more specific system design stages, and its goal is to reduce later redesign. It should also provide a realistic basis for estimating risks, schedules, and, in our case, future maintenance issues. I

Thus, in the following, three perspectives are considered - user needs, software design- and software implementation issues - in the development of the platform elements and in the use of the methods and tools.

==Platform elements==

===Front end===
Methods: user stories, design thinking, mock-ups, Wiki (voting)
====Landing page====
user authentication; user guide
====Community forum====
feedback on platform; discussion of content
====Dashboard====
queries
====Display, analysis & visualization====
====Session logging====
for later performance monitoring

===Processing and storage device===
====Metadata database model====

Methods: Design thinking, EERAdata Workshop 2, Wiki-Platform interface

In the following figure, we sketch how metadata describing the thematic character of external databases may be harmonized for use in the EERAdata platform. A similar strategy could also be used to harmonize the metadata for the specific records in the databases; this would be conceptually similar, but with a more complicated structure to the records.

''Insert figure here''

Three external databases are considered, and termed DB1, DB2, and DB3. They are each described in terms of a set of thematic classes following some standard classification, given in terms of persistent identifiers (pIDs) for the appropriate classes. DB1 and DB2 use the same standardization system, providing pIDs (Class-std1-ID) for the appropriate classes. DB3 uses a second standardization system, providing pIDs (Class-std2-ID) for its corresponding classes. We cannot assume the two systems to be commensurable.

Further, we cannot assume that either system is commensurable with the standardization system adopted for the EERAdata platform. Thus, instead of directly using the standards from the external databases, we harmonize the external standards to that used by the EERAdata platform. This is shown as the tables Std1-harmonization and Std2-harmonization, which constitute correspondence tables between the external pIDs and the pIDs used internally by EERAdata (EERAdata-std-ID). The correspondence tables must accurately relate standards that may be at different levels of precision and with different approaches to classification. It is thus essential that the tables are constructed with input from domain experts.

The correspondence tables allow us to describe the external databases in a consistent fashion using the internal standard for the platform. Needed detail is provided internally, e.g., giving a short class name and a description as shown in the figure. Beyond using the classes as a nomenclature for thematic content, ontological relations between the classes can be expressed, e.g., as a Class-hierarchy specifying which classes have others as subclasses, shown in the figure as pairings of pIDs for the classes along with their separation in the hierarachy. Crucially, it is not necessary to use the ontological structures of the external databases, although they must be accounted for in preparing the correspondence tables.

===='Data' database====
The EERAdata platform is intended to build on external resources as far as possible, minimizing internal storage (and computation requirements. The complexity will depend on the visualization requirements that emerge in the course of the project. At the current stage, it is not possible to be more specific without some external databases in mind.
====Database interface====
to support standardization and harmonization process
====Open core search====
functionality to support the establishment of ontologies?
====Evaluation of session logs====

===Back end===
*Interfaces to external resources (APIs, …); communication with platform owners, support by Use Case Leaders required
*Interfaces to import metadata from external sources (provided by the Use Cases)
*Data preparation for front end
*…
Methods: software development, establishment of communication channels with database holders

===Software system requirements===
*Usability
*Graphic design
*Reliability
*Availability
*Adherence to IPRs
*Data protection
*Security
*Migration and future maintenance
*…

==Methods and tools==
To collect expectations and needs, we must account for different perspectives:
# energy research expertise from use cases & gap analysis;
# data science expertise from FAIR/O community; and
# process expertise from standardisation community

===Design thinking===
Which tools will we use to create the mock-ups?
Design suggestions are posted on the Wiki for voting and feedback within the project community.

===User stories===

As a first step, the use case leaders and other use-case members are involved in formulating the needs and requirements. As an important tool, we plan to use '''user stories''' to be provided by them or other stakeholders from the energy research community. User stories put features in the context of what the user needs to accomplish. They describe the task or feature, but not how the developers should implement it. First step: invite Use Case leaders and members to collect user stories on the Wiki. Second step: approach external stakeholders for user stories (database holders, interoperability community…).

===EERAdata Workshops===

===Community forum===

===EERAdata Wiki===

Functional specifications

2020-10-05T16:38:56Z

Manfred: /* Processing and storage device */

This '''living document''' forms the basis of Deliverable 3.1 that will guide the design and implementation of the platform.

==Introduction==
The intention of this living document is to reach a team consensus on what the EERAdata platform is to achieve. We expect that such consensus among the stakeholders is established step by step during the project implementation. Hereby, we draw on practices in professional software development with the purpose

* '''To specify the stakeholders´ needs.''' A Product Requirements Document (PRD) is a document containing all the requirements for a certain software product. It is written with direct user involvement to allow all stakeholders to understand what the product should do. A PRD, however, does not anticipate or define how the product will do it. In EERAdata we provide this by asking the project partners in their role as energy researchers for '''''user stories''''', comprising concrete support needs for FAIR data in their use cases.

* '''To link requirements and functionality.''' The Functional Specifications Document (FSD) specifies the functions that a software must perform. A functional specification is a more technical response to the PRD. It does not define the inner workings of the proposed system, nor does it include the specification of how the system function will be implemented. Instead, it focuses on what various outside agents (people using the program, computer peripherals, or other computers, for example) might observe when interacting with the system. In EERAdata we achieve this by providing mock-ups, descriptions of the front-end features on the EERAdata Wiki and allowing test users to access preliminary platform implementations during development. In this way feedback can be collected continually from the consortium and from a wider community through the EERAdata workshops.

* '''To specify technical implementation options.''' A Software Requirements Specification (SRS) is a description of a software system to be developed. Typically, it is written by a technical writer, a systems architect, or a software programmer. Software requirements specification is a rigorous assessment of requirements before the more specific system design stages, and its goal is to reduce later redesign. It should also provide a realistic basis for estimating risks, schedules, and, in our case, future maintenance issues. I

Thus, in the following, three perspectives are considered - user needs, software design- and software implementation issues - in the development of the platform elements and in the use of the methods and tools.

==Platform elements==

===Front end===
Methods: user stories, design thinking, mock-ups, Wiki (voting)
====Landing page====
user authentication; user guide
====Community forum====
feedback on platform; discussion of content
====Dashboard====
queries
====Display, analysis & visualization====
====Session logging====
for later performance monitoring

===Processing and storage device===
====Metadata database model====

Methods: Design thinking, EERAdata Workshop 2, Wiki-Platform interface

In the following figure, we sketch how metadata describing the thematic character of external databases may be harmonized for use in the EERAdata platform. A similar strategy could also be used to harmonize the metadata for the specific records in the databases; this would be conceptually similar, but with a more complicated structure to the records.

''Insert figure here''

Three external databases are considered, and termed DB1, DB2, and DB3. They are each described in terms of a set of thematic classes following some standard classification, given in terms of persistent identifiers (pIDs) for the appropriate classes. DB1 and DB2 use the same standardization system, providing pIDs (Class-std1-ID) for the appropriate classes. DB3 uses a second standardization system, providing pIDs (Class-std2-ID) for its corresponding classes. We cannot assume the two systems to be commensurable.

Further, we cannot assume that either system is commensurable with the standardization system adopted for the EERAdata platform. Thus, instead of directly using the standards from the external databases, we harmonize the external standards to that used by the EERAdata platform. This is shown as the tables Std1-harmonization and Std2-harmonization, which constitute correspondence tables between the external pIDs and the pIDs used internally by EERAdata (EERAdata-std-ID). The correspondence tables must accurately relate standards that may be at different levels of precision and with different approaches to classification. It is thus essential that the tables are constructed with input from domain experts.

The correspondence tables allow us to describe the external databases in a consistent fashion using the internal standard for the platform. Needed detail is provided internally, e.g., giving a short class name and a description as shown in the figure. Beyond using the classes as a nomenclature for thematic content, ontological relations between the classes can be expressed, e.g., as a Class-hierarchy specifying which classes have others as subclasses, shown in the figure as pairings of pIDs for the classes along with their separation in the hierarachy. Crucially, it is not necessary to use the ontological structures of the external databases, although they must be accounted for in preparing the correspondence tables.

===='Data' database====
The EERAdata platform is intended to build on external resources as far as possible, minimizing internal storage (and computation requirements. The complexity will depend on the visualization requirements that emerge in the course of the project. At the current stage, it is not possible to be more specific without some external databases in mind.
====Database interface====
to support standardization and harmonization process
====Open core search====
functionality to support the establishment of ontologies?
====Evaluation of session logs====

===Back end===
*Interfaces to external resources (APIs, …); communication with platform owners, support by Use Case Leaders required
*Interfaces to import metadata from external sources (provided by the Use Cases)
*Data preparation for front end
*…
Methods: software development, establishment of communication channels with database holders

===Software system requirements===
*Usability
*Graphic design
*Reliability
*Availability
*Adherence to IPRs
*Data protection
*Security
*Migration and future maintenance
*…

==Methods and tools==
To collect expectations and needs, we must account for different perspectives:
# energy research expertise from use cases & gap analysis;
# data science expertise from FAIR/O community; and
# process expertise from standardisation community

===Design thinking===
Which tools will we use to create the mock-ups?
Design suggestions are posted on the Wiki for voting and feedback within the project community.

===Collection of user requirements===

As a first step, the use case leaders and other use-case members are involved in formulating the needs and requirements. As an important tool, we plan to use '''user stories''' to be provided by them or other stakeholders from the energy research community. User stories put features in the context of what the user needs to accomplish. They describe the task or feature, but not how the developers should implement it. First step: invite Use Case leaders and members to collect user stories on the Wiki. Second step: approach external stakeholders for user stories (database holders, interoperability community…).

===EERAdata Workshops===

===Community forum===

===EERAdata Wiki===

Functional specifications

2020-10-05T16:31:43Z

Manfred: /* Processing and storage device */

This '''living document''' forms the basis of Deliverable 3.1 that will guide the design and implementation of the platform.

==Introduction==
The intention of this living document is to reach a team consensus on what the EERAdata platform is to achieve. We expect that such consensus among the stakeholders is established step by step during the project implementation. Hereby, we draw on practices in professional software development with the purpose

* '''To specify the stakeholders´ needs.''' A Product Requirements Document (PRD) is a document containing all the requirements for a certain software product. It is written with direct user involvement to allow all stakeholders to understand what the product should do. A PRD, however, does not anticipate or define how the product will do it. In EERAdata we provide this by asking the project partners in their role as energy researchers for '''''user stories''''', comprising concrete support needs for FAIR data in their use cases.

* '''To link requirements and functionality.''' The Functional Specifications Document (FSD) specifies the functions that a software must perform. A functional specification is a more technical response to the PRD. It does not define the inner workings of the proposed system, nor does it include the specification of how the system function will be implemented. Instead, it focuses on what various outside agents (people using the program, computer peripherals, or other computers, for example) might observe when interacting with the system. In EERAdata we achieve this by providing mock-ups, descriptions of the front-end features on the EERAdata Wiki and allowing test users to access preliminary platform implementations during development. In this way feedback can be collected continually from the consortium and from a wider community through the EERAdata workshops.

* '''To specify technical implementation options.''' A Software Requirements Specification (SRS) is a description of a software system to be developed. Typically, it is written by a technical writer, a systems architect, or a software programmer. Software requirements specification is a rigorous assessment of requirements before the more specific system design stages, and its goal is to reduce later redesign. It should also provide a realistic basis for estimating risks, schedules, and, in our case, future maintenance issues. I

Thus, in the following, three perspectives are considered - user needs, software design- and software implementation issues - in the development of the platform elements and in the use of the methods and tools.

==Platform elements==

===Front end===
Methods: user stories, design thinking, mock-ups, Wiki (voting)
====Landing page====
user authentication; user guide
====Community forum====
feedback on platform; discussion of content
====Dashboard====
queries
====Display, analysis & visualization====
====Session logging====
for later performance monitoring

===Processing and storage device===
In the following figure, we sketch how metadata describing the thematic character of external databases may be harmonized for use in the EERAdata platform. A similar strategy could also be used to harmonize the metadata for the specific records in the databases; this would be conceptually similar, but with a more complicated structure to the records.

Three external databases are considered, and termed DB1, DB2, and DB3. They are each described in terms of a set of thematic classes following some standard classification, given in terms of persistent identifiers (pIDs) for the appropriate classes. DB1 and DB2 use the same standardization system, providing pIDs (Class-std1-ID) for the appropriate classes. DB3 uses a second standardization system, providing pIDs (Class-std2-ID) for its corresponding classes. We cannot assume the two systems to be commensurable.

Further, we cannot assume that either system is commensurable with the standardization system adopted for the EERAdata platform. Thus, instead of directly using the standards from the external databases, we harmonize the external standards to that used by the EERAdata platform. This is shown as the tables Std1-harmonization and Std2-harmonization, which constitute correspondence tables between the external pIDs and the pIDs used internally by EERAdata (EERAdata-std-ID). The correspondence tables must accurately relate standards that may be at different levels of precision and with different approaches to classification. It is thus essential that the tables are constructed with input from domain experts.

The correspondence tables allow us to describe the external databases in a consistent fashion using the internal standard for the platform. Needed detail is provided internally, e.g., giving a short class name and a description as shown in the figure. Beyond using the classes as a nomenclature for thematic content, ontological relations between the classes can be expressed, e.g., as a Class-hierarchy specifying which classes have others as subclasses, shown in the figure as pairings of pIDs for the classes along with their separation in the hierarachy. Crucially, it is not necessary to use the ontological structures of the external databases, although they must be accounted for in preparing the correspondence tables.

===Back end===
*Interfaces to external resources (APIs, …); communication with platform owners, support by Use Case Leaders required
*Interfaces to import metadata from external sources (provided by the Use Cases)
*Data preparation for front end
*…
Methods: software development, establishment of communication channels with database holders

===Software system requirements===
*Usability
*Graphic design
*Reliability
*Availability
*Adherence to IPRs
*Data protection
*Security
*Migration and future maintenance
*…

==Methods and tools==
To collect expectations and needs, we must account for different perspectives:
# energy research expertise from use cases & gap analysis;
# data science expertise from FAIR/O community; and
# process expertise from standardisation community

===Design thinking===
Which tools will we use to create the mock-ups?
Design suggestions are posted on the Wiki for voting and feedback within the project community.

===Collection of user requirements===

As a first step, the use case leaders and other use-case members are involved in formulating the needs and requirements. As an important tool, we plan to use '''user stories''' to be provided by them or other stakeholders from the energy research community. User stories put features in the context of what the user needs to accomplish. They describe the task or feature, but not how the developers should implement it. First step: invite Use Case leaders and members to collect user stories on the Wiki. Second step: approach external stakeholders for user stories (database holders, interoperability community…).

===EERAdata Workshops===

===Community forum===

===EERAdata Wiki===

Functional specifications

2020-10-05T16:29:47Z

Manfred: