search

teksi / wastewater

[DEV] Future TEKSI wastewater module, adapted data model to fit VSA-DSS 2020 new standard
https://teksi.github.io/wastewater
GNU General Public License v3.0
1 stars 5 forks source link

ws_type in vw_tww_wastewater_structure and types in database #60

Open urskaufmann opened 8 months ago

urskaufmann commented 8 months ago

I understood a few days ago, that this type-fields (e.g.maintenance_event_type) work with the types in the database. And I ask, why we do not use also types for the ws_type field in vw_tww_wastewater_structure (the list there is just configured in the project file)? BUT: is it possible to translate this type-lists? If not: why do we not use normal vl_lists as type-lists (with value_en, value_de etc)? If it's not possible to translate and a vl_list instead is not a good idea: can we use multilingual-expressions (manhole/Normschacht/Chambre standard)? Instead of values "unknown" or "damage" or "overflow" (values that are shown with a new record): "Select a subclass ..."

3nids commented 8 months ago

This type is created by pirogue. I think we can translate these in the project using a value-map field widget.

sjib commented 7 months ago

@urskaufmann Is this still an issue?

urskaufmann commented 3 months ago

the question of the translation is not answered. I wish lists with the first element "Select a subclass..." and then the other elements for the subclasses (manhole, special_structure,...) This list should be with code and language-fields (value_en, value_de, ...). Like this we can configure the qgs-file with no problems in the case a tab is just shown for a specific subtype. Till now, there is the english name of the type in the formula for the tab-visibility, and you have to manually change the formula if the type-values are translated.