Closed niconoe closed 3 years ago
Sorry @peterdesmet, I implemented a first version of this since I didn't notice you were assigned. There's probably room for improvement, though.
The enum
constraint was already listed under the definition, so if that one was presented, it would be listed twice. Adding a column also pushes the table to the limits on smaller screens:
In cf35157 I updated this so that all constraints are listed under the definition: enum first (as a value list, see example: https://tdwg.github.io/camtrap-dp/data/#bait_use), then the other constraints (as a key: value list). This also frees up some horizontal space:
Make sure all important information from the table schema (JSON file), such as min/max values, type, format, ... clearly appear in a human-readable form on the website table.