You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Mapping Component shows possible properties of interest of one or more sources where no appropriate field exists. At example it could contain the SkiresortId on Dolomitii Superski etc... Fields like CustomId, SmgId, OutdooractiveID, HgvId etc... will be marked as obsolete and added into the Mapping Property.
Since it is a Dictionary<string, Dictionary<string,string>> i think we have to create a component for managing this data?
I added into the openapi spec all possible values for the field Type
I think we have to create a component here.
GpsInfo
As described in the other issue we need a Component where we can set all GPSInfo. I added to the openapi spec the possible values for the field Gpstype
AdditionalPoiInfos
Language Based, for us for Interest is the field Novelty and the field Categories to check if the field Categories can be populated on save.
PoiProperty
Language Based Key/Value List to store all fields where there is no corresponding field in the Datamodel. Generic and useful for all Datasets. Maybe here we need also a Property where the Key/Value List is not language based.
"PoiProperty": {"de": [{"Name": "openingtimesgastronomie","Value": "März bis Dezember"},{"Name": "hasvisits","Value": "False"}]}
Gastronomy Infos
There are some fields which contains Infos about a Gastronomy which are not displayed. To check if we need to create a component here
As discussed before, I would suggest to wait till the next meeting with Delia and then plan what is feasible simply by optimizing the configuration of the single datasets and what should be implemented in a new component.
Quick draft to find out which components are needed for the ODHActivityPoi Endpoint
LicenseInfo
The Component to set the Licenseinfo is missing (seems we can configure this without a component)
Mapping
The Mapping Component shows possible properties of interest of one or more sources where no appropriate field exists. At example it could contain the SkiresortId on Dolomitii Superski etc... Fields like
CustomId
,SmgId
,OutdooractiveID
,HgvId
etc... will be marked as obsolete and added into the Mapping Property.Since it is a Dictionary<string, Dictionary<string,string>> i think we have to create a component for managing this data?
RelatedContent
The actual RelatedContent Webcomponent is not what we need
it simply populates a string field
"RelatedContent": "aaa"
which does not correspond to the datastructureThe datastructure of RelatedContent is:
I added into the openapi spec all possible values for the field
Type
I think we have to create a component here.
GpsInfo
As described in the other issue we need a Component where we can set all GPSInfo. I added to the openapi spec the possible values for the field
Gpstype
AdditionalPoiInfos
Language Based, for us for Interest is the field
Novelty
and the fieldCategories
to check if the field Categories can be populated on save.PoiProperty
Language Based Key/Value List to store all fields where there is no corresponding field in the Datamodel. Generic and useful for all Datasets. Maybe here we need also a Property where the Key/Value List is not language based.
Gastronomy Infos
There are some fields which contains Infos about a Gastronomy which are not displayed. To check if we need to create a component here
CapacityCeremony
CategoryCodes
DishRates
Facilities
MaxSeatingCapacity
ChildPoiIds, MasterPoiIds
To check where we have to show this assignments, to discuss if this assignment can be shifted to another already present generic field
VideoItems
Todo Component for adding Videos
DistanceInfo
Todo Config for adding the fields for DistanceInfo
GpsTrack
Current Datamodel is:
The text was updated successfully, but these errors were encountered: