As an Open Data Hu Data Browser user I want to group more records i a column, to reduce the number of the colums in my table

[sseppi]

This issue will focus on the possibility to group more information in one column.

For example:

• GPS Coordinates that could show fopr example
  • latitude
  • longitude
  • altitude
  • etc.
• push information that shows in one column:
  • push ID
  • push type
  • push timestamp
  • etc.

To implement this feature we should consider:

• the available components we have
• if we should start from the component or the field choiche

[gappc]

@sseppi if I remember correctly, we decided with Patrick that we don't add more than one information per column. By "information" I mean one component, is that the same what you mean by "information"?

Having one component per cell simplifies the design and probably the user experience (think of filter, sorting, ...).

Note, that any component may depend on several mapped field values. Maybe that's what you had in mind with "information"?

[sseppi]

@gappc In general I agree that we should have only one value per column, to simplify the understanding, the sorting and filtering of data.

What I wanted to discuss here was for example the case of the GPS coordinates where the user could add to the column a Map component to see the point on a map. In this case in the configuration of the component we should consider that the structure of the GpsInfo in the JSON is the following.

"GpsInfo": 
[
{
"Gpstype": "position",
"Altitude": 1108,
"Latitude": 46.477851,
"Longitude": 11.369939,
"AltitudeUnitofMeasure": "m"
}
],

This means that the user probably has to map at least two attributes (Latitude, Longitude) to render the data on the map.

For this reason, I mentioned that, we should understand which component we will provide to the user, to render data on the Table View.

Did I clarify better?

[gappc]

@sseppi we already map several properties per column to the rendering component, e.g. for GPS points, just like you mentioned, see https://github.com/noi-techpark/opendatahub-databrowser/blob/main/databrowser/src/config/builder/tourism/gpsData.ts#L57

So, if I understand you right, the task of this issue is to identify a good strategy on how to allow a user to provide the mapping, is that correct?

[sseppi]

@gappc Yes, we need to identify a good solution to provide the mapping for all the components that needs more then one attribute to be rendered.