SIARDDK - include illlegal datatypes

[PhillipTommerholt]

During the pilot we experienced several times that a certain datatype made a SIARDDK export fatally crash.
This is because SIARDDK only allows for a small variety of datatypes, whereas SIARD2.0 is more open with even user defined datatypes.

According to SIARDDK all non-allowed datatypes should be forced into the nearest fitting (allowed) datatype.

However, I would like to know if it is possible to change the behaviour so everytime in an export when DPBTK meets an illegal datatype this datatype is kept as is and a warning appears after succesful export. The warning will let the user know that there are illegal datatypes in tableIndex.xml

[PhillipTommerholt]

Please note:
I am not suggesting that datatypes that are already transformed into "SIARDDK allowed datatypes" should be rolled back. I am only interested if it is possible that the tool will give a warning and export nonetheless if it meets new unknown and illegal datatypes.