Skip to content

Commit

Permalink
fix image path in oemetadata tutorial
Browse files Browse the repository at this point in the history
  • Loading branch information
@jh-RLI
jh-RLI committed Nov 18, 2024
1 parent a798d3e commit 9c8305e
Showing 1 changed file with 28 additions and 28 deletions.
56 changes: 28 additions & 28 deletions docs/tutorials/99_other/oemetadata.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -38,59 +38,59 @@ On the OEP there is a tool to create your OEMetadata directly on the platfrom. I
## How to use the OEMetaBuilder

You can find the [OEMetaBuilder](https://openenergyplatform.org/dataedit/oemetabuilder/) on the OEP under [Database](https://openenergyplatform.org/dataedit/schemas) by clicking on `OEMetaBuilder` in the upper right corner.
![Database](images/Screenshots_OEMetadata/0_Database.png)
![Database](images/oemetadata/0_Database.png)
Then the OEMetaBuilder opens and you can see all the fields. Right next to the headline `Create new Metadata` there are two buttons; With the first one (the pen with `JSON`) you can edit and/or copy the code on which this page is based on in a popup window. With the second (the menu with `properties`) you can choose which fields will be shown or hidden by clicking on them in the list in the popup window. Whenever there is a such a `menu` button next to a headline it enables you to choose which fields will be shown or hidden in the section the hedline belongs to. At the lower right corner three buttons appear to `Submit`, `Cancel` or `Download` your OEMetadata. You can submit your OEMetadata if there already exists a table for your dataset. You can always download the dataset as a JSON-file or cancel the process. Beneath all fields is a description of what values and information may be filled in the field above. For more detailed information please see the [key descriptions](https://github.com/OpenEnergyPlatform/OEMetadata/blob/develop/metadata/v160/metadata_key_description.md).
In order for the OEMetadata dataset to exist on the OEP the ID field must be filled out. You can also give a name, title and description to your OEMetadata. If you create OEMetadata to an already existing table some fields will be filled automatically once you filled in the ID of the table. This makes it easier for you and minimizes the possible errors.
![Anfang](images/Screenshots_OEMetadata/1_Anfang.png)
![Anfang](images/oemetadata/1_Anfang.png)
Under `Subject` you can provide subjects which describe your data. In the `Name`-field please provide the human readable name of the subject, e.g. energy. In the `Path`-field please provide the corresponding URL to the OEO, e.g. https://openenergy-platform.org/ontology/oeo/OEO_00000150. You can add subjects by clicking on the `+` right next to the headline `Subject`. Note: Subjects help other users to find your data and know what it is about.
![Subject](images/Screenshots_OEMetadata/2_Subject.png)
![Subject](images/oemetadata/2_Subject.png)
You can provide language tag(s) for all languages used in your data, inculding the table and the OEMetadata dataset. You can add multiple languages by clicking on the `+` right next to the headline `Language`. Note: Please use the required standard (IETF (BCP47)).
![Language](images/Screenshots_OEMetadata/3_Language.png)
![Language](images/oemetadata/3_Language.png)
Additionally to the Subjects you can also provide `Keywords`. These don't have to be defined in the OEO, but can help to describe the content of your data even more precisly. The Keywords make it also possible to filter the tables in the [OEO Database](https://openenergyplatform.org/dataedit/schemas).
![Language](images/Screenshots_OEMetadata/4_Keywords.png)
![Language](images/oemetadata/4_Keywords.png)
You can give context to your data, e.g. a research project. This makes your data more comprehendable and traceable for others.
![Context](images/Screenshots_OEMetadata/5_Context_1.png)
![Context](images/Screenshots_OEMetadata/6_Context_2.png)
![Context](/images/oemetadata/5_Context_1.png)
![Context](images/oemetadata/6_Context_2.png)
You can specify the spatial context of your data, e.g. the region in which a research was done.
![Spatial](images/Screenshots_OEMetadata/7_Spatial.png)
![Spatial](images/oemetadata/7_Spatial.png)
You can also define the time of your data. Either a reference date or a time span.
![Temporal](images/Screenshots_OEMetadata/8_Temporal.png)
![Temporal](images/oemetadata/8_Temporal.png)
You can add a `Timeseries` by clicking on the `+` next to the headline. There you can specify start, end and resolution of the series and information about how the data is implemented in the table. You can add multiple timeseries if neccessarry.
![Timeseries-1](images/Screenshots_OEMetadata/9_Timeseries-1.png)
![Timeseries-2](images/Screenshots_OEMetadata/10_Timeseries-2.png)
![Timeseries-1](images/oemetadata/9_Timeseries-1.png)
![Timeseries-2](images/oemetadata/10_Timeseries-2.png)
You can provide information on your `Sources`, `Licenses`, `Contributers` and `Recourses`. You can add each of them by clicking on the `+` next to the headline.
![Sources-1](images/Screenshots_OEMetadata/11_Sources-1.png)
![Sources-1](images/oemetadata/11_Sources-1.png)
You can list your sources by providing a human readable title, a description of the source and the path to the source as URL. You can add multiple sources.
![Sources-2](images/Screenshots_OEMetadata/12_Sources-2.png)
![Sources-2](images/oemetadata/12_Sources-2.png)
You can also provide the license of each source by providing the SPDX identifire, a human readable name as well as a path to the license and further information.
![License-1](images/Screenshots_OEMetadata/13_License-1.png)
![License-2](images/Screenshots_OEMetadata/14_License-2.png)
![License-1](images/oemetadata/13_License-1.png)
![License-2](images/oemetadata/14_License-2.png)
You may provide information about the contributors of your data. You can add multiple contributors and add details about their contribution.
![Contributors-1](images/Screenshots_OEMetadata/15_Contributors-1.png)
![Contributors-2](images/Screenshots_OEMetadata/16_Contributors-2.png)
![Contributors-1](images/oemetadata/15_Contributors-1.png)
![Contributors-2](images/oemetadata/16_Contributors-2.png)
You can also annotate the data in your table. This helps to make the data in your table comparable to others because it makes a connection between columns and/or fields to classes in the OEO. If you create OEMetadata for an already existing table, the names of the fields will be filled in autamatically and make the process of annotating more convinient. Note: If you want to annotate without an already on the OEO existing table you must have a basic understandning to datastructure and databases and their relations. In order to do so you must add resource(s) by clicking on the `+` next to the headline `Recourses`. For all resources you must add an unique name. Ich bin etwas verwirrt und weiß nicht, ob ich das folgende richtig beschreibe!
![Resources](images/Screenshots_OEMetadata/17_Resources.png)
![Resources](images/oemetadata/17_Resources.png)
You can specify the content of a field in your table by identifying the field, giving its description and data type.
![Field](images/Screenshots_OEMetadata/18_Field-1.png)
![Field](images/oemetadata/18_Field-1.png)
The important step of making the connection between the entries in your table and the classes of the ontology happens now by providing the human readable term and the path to the OEO.
![isabout](images/Screenshots_OEMetadata/19_isabout.png)
![isabout](images/oemetadata/19_isabout.png)
**Using the OEOextended**
If you want to use an unit which is not in the OEO yet, meaning you can't find it via the implemented search, you can click on the button `Open OEO-extended`. This will open a popup window.
![OEOex](images/Screenshots_OEMetadata/19-1_OEOex.png)
![OEOex](images/oemetadata/19-1_OEOex.png)
In the OEO-extended (OEOX) it is possible to create an additional unit using units already existing in the OEO. All created units will be reviewed and published on [GitHub](https://github.com/OpenEnergyPlatform/oeo-extended) and uploaded to the OEO. For further information on the OEOX please see [this paper](https://www.utwente.nl/en/eemcs/fois2024/resources/papers/kohler-et-al-oeox-a-post-coordination-extension-for-the-open-energy-ontology.pdf). To create the new unit you can choose your `Numerator(s)` and `Denominator(s)`. You can respectively choose the unit name from all units implemented in the OEO, e.g. hour, a `Unit Type` according to the power you want to have (linear, squared or cubic) and, if neccessarry, a `Unit Prefix` e.g. mega. Once you entered something in the `Unit Name`-field a fraction will appear showing you the unit you are about to create. It is possible to choose mulitple Numerator and Denominator, which will be each multiplied by each other. When you created the unit you want to use, click `Save`. Then the URI to the new unit in the OEOX will appear. You have to copy and paste it to your browser in order to entry the `Name` and `Path` in the `isAbout`-field. The OEOX is implemented on different fields in the OEMetaBuilder to make it easier to create new units.
![isabout](images/Screenshots_OEMetadata/19-2_Result.png)
![isabout](images/oemetadata/19-2_Result.png)
You can also provide a class of the OEO for entries of a whole column. By annotating the name of the column with the name and path of the OEO class. You only have to fill in the name fied and select one option from the drop down menu and the path will be filled in automatically. The result would be for example: The column name is 'sc' for 'scenario'. So the annotation name is 'scenario' and the path would be 'http://openenergy-platform.org/ontology/oeo/OEO_00000364'.
To annotate a single value from a cell as part of the current column, you can annotate the specific value, e.g. column 'Gas' has the value 'co2eq' and should be annotated with 'Carbon Dioxide Equivalent Quantity Value'. The annotation can therefore only be made if values are already known. This value must be entered in the value field. The `Name` & `Path` fields are filled in in the same way as in the is About section. This type of annotation can be very time consuming. If you have many unique values in your column, we recommend creating an additional table that assigns the values and annotations, as this seems to make more sense. Meaning in some specific cases it might be better to manually create your annotations in the OEMetadata and the OEMetaBuilder is not the best option.
![ValueReferences](images/Screenshots_OEMetadata/20_ValueReferences.png)
![EndeField](images/Screenshots_OEMetadata/21_EndeField.png)
![ValueReferences](images/oemetadata/20_ValueReferences.png)
![EndeField](images/oemetadata/21_EndeField.png)
You can also give a `Primary Key` which uniquely identifies each row of your table.
![PrimaryKey](images/Screenshots_OEMetadata/22_PrimaryKey.png)
![PrimaryKey](images/oemetadata/22_PrimaryKey.png)
You can also refer to an other table by giving a `Foreign Key`.
![ForeignKey](images/Screenshots_OEMetadata/23_ForeignKeys.png)
![ForeignKey](images/oemetadata/23_ForeignKeys.png)
If you want to reference another table you can provide the foreign table in the `Resource`-field and then specifying which column should be referencced in the `Field` below.
![References](images/Screenshots_OEMetadata/24_References.png)
![References](images/oemetadata/24_References.png)
At the end you can provide an explanation of your data in terms defined by the OEO and a URI via the DBpedia Databus.
![Ende](images/Screenshots_OEMetadata/25_Ende.png)
![Ende](images/oemetadata/25_Ende.png)



Expand Down

0 comments on commit 9c8305e

Please sign in to comment.