Make delete table button visible and update the MetaBuilder user interface to improve metadata editing experience.

[Darynarli]

Tasks

• [x] make tble delete button visible
• [ ] Improve MetaBuilder interface

Question:

1. What columns should be in the table?
2. Who can delete a table? (admin, table author or anyone)
3. Who can change the table data? (admin, table author or anyone)
4. I don’t see on the Mockups what changes when switching to the table in the date? Shouldn't there be a change?
5. What information should be stored in the subject? (How is it different from the General item?)
6. What is the difference between Temporal and Spatial?

Actions

1. button ‘delete table’
2. function ‘edit Meta information’: you can edit name, title, description, language, keywords, subject, context, spatial, temporal, sources, resources, review
3. division by individual items into:

• General: name, title, id, description, language, publication date, subject
• Spatial & Temporal: location, extent, resolution, reference date, timeseries (start, end, resolution, alignment, aggregation type)
• Sources
• Licenses
• Provenience

[bmlancien]

I don’t see on the Mockups what changes when switching to the table in the date? Shouldn't there be a change?

Can you explain what you mean with "in the date"? Or do you mean the Data section on the right?

[Darynarli]

Hi. Yes, the Data section on the right

[jh-RLI]

this? :

[Darynarli]

Yes

[jh-RLI]

Just to clarify the naming as I think this is confusing :) : The table page is the table-detail-view: it contains the data view and the metadata widget. The MetaBuilder is the tool that becomes visible once you click on the Edit button (meta Information). And there is a standalone version that can be accessed by clicking the button "OEMetaBuilder" on the table list view page.

Regarding your questions:

1. you don't need to create a new table. Generally the user will create the table and we allow any table structure.
2. I think that the person who created the table should be able to delete it. That would be the table owner or table author.
3. The data can be edited by all users who have access to the table. There is a permission button that is visible on the detailview. The table author can create a group there or add specific users. This will allow them to upload data.
4. You can view the oep diretly, as this part of the mockup is already implemented and released. If I understood you correctly: the data part shows the currently stored data and more.
5. the subject is a new field in the metadata that is used to provide information about the subject that the data is about. You can try it yourself in the standalone metaBuilder:https://openenergy-platform.org/dataedit/oemetabuilder/. For example, if the data contains data about energy demand, you can enter energy demand and get a suggestion for a term that is included in the Open Energy Ontology. This different from the name of the dataset and desciption of the dataset. This field also helps make the data Linked-Open-Data compliant because the data is linked to other data. This is a bit more complex, we can talk about it in a personal conversation.
6. the temporal part describes the temporal resolution of the data. Imagine a time series that contains a data entry every 5 minutes for a period of one year, for example. The spatial part refers to the geographic extent of the data, e.g. that the data was collected in Germany or similar. Sometimes coordinates are also included in the data.

[Darynarli]

Hi. What branch I have to use?

[jh-RLI]

This is a combination of the delete button and the metadata speration to make the tabs in the metaBuilder possible?

i suggest to name the branch: feature/update-metaBuilder-ui-and-make-table-delete-button-visible-1192