Dear friends, I sometimes use the SQL export to get a build statement for the database structure resulting from the survey definition (for example to create a database or to visualize it). In this export, however, the species list is missing. E.g. if you use DBschema (as free software to visualize it) and parse the CREATE TABLE statement with the SQL exported from collect, my species list is missing. For completeness it would be nice to include this in the export, if possible. Cheers, Lutz asked 28 Apr '23, 09:19 Fehrmann |
Dear Lutz, answered 05 May '23, 09:02 Stefano (OF) ♦♦ |
Using the SQL export in Collect already includes all code tables, they come out nicely with all relations. Adding the species list would complement this. Even the sampling point data could potentially be included, at least the level_1 to level_x code and label which might be related to the plot entity. It should be no problem to include all columns of the species list (if users have additional fields), but in fact the species code (which is the key field relating to other tables) and species name (Latin and common) would already be fine. There are people who like to bypass the complex Collect and Calc database and use other techniques, like dynamical data models to analyze data, for them such a simpler structure might be helpful as basis. Thank you! Lutz answered 05 May '23, 12:59 Fehrmann |