Add file and data_media classes to the datamodel, create vw_file

[ponceta]

General

• Fix a bug
• Add a feature
• Maintenance / sustainability
• Add Documentation

Describe your changes

Handle document management in TEKSI district heating

• Proposition is to add same classes as for TEKSI wastewater (file and data_media) (multi document management #51)
• Brings many aditionnal fixes on the application schema evolution (replicate this logic to TDH for consistency #56)
• QGIS project adaption - add new layer based on vw_file and create form for it. Discuss usability and needs of user. Check on tww how it is implemented and standardize
• Add documentation to Developers guide how to integrate these two classes in any module

Screenshots

Issue ticket number and link

Checklist before requesting a review

• I have performed a self-review of my code
• If it is a core feature, I have added thorough tests.
• CI Tests are green
• The documentation is up to date with the proposed change.
• My work is ready for review

Checklist before merge

• A review has been performed
• Comments are resolved
• Documentation is ready

[ponceta]

Requesting @sjib on the datamodel part (wise to base on such a part of a model / dangerous?)

[sjib]

Requesting @sjib on the datamodel part (wise to base on such a part of a model / dangerous?)

As these are two indepentand classes that are linke only to each other I think we can use them also in tdh. We could easily write an INTERLIS model file with just these two classes if we ever would need to transfer them. The matching logic and settings could be copied from VSA-KEK Import / Export in TWW.

What would be the other option?

• Create something new on our own? -> I don't think that would be better
• ...

[sjib]

@ponceta I listed the complete list of triggers and functions that should be added in this issue: #60

[sjib]

see comments above

[sjib]

Should solve #60 when finished

[sjib]

@ponceta I think meta_functions should also be added.
symbology_functions I think would also make sense - here we then would have to document the logic and name the symbology_triggers accordingly.

• meta_functions.sql
• modification_functions.sql
• oid_functions.sql
• organisation_functions.sql
• symbology_functions.sql

[sjib]

@ponceta First integrate #61 before pushing this

[ponceta]

Waiting for #61 then ;)