Feature #2464
Updated by Alexander Watzinger 5 months ago
Currently we have a mixed bag of used classes at entity level, forms and displays that are not directly connected. After some talks with colleagues and very helpful input from @Katharina, Lukas and Birger just to name a few I found a new approach: Using model config files which contain all the information to build views, forms and similar in a generic way. Advantages would be: * Easier model adaptions at one place * Possibility to test for "allowed" relations * More consistent layout, e.g. table headers, form fields order, ... * Less error prone and fewer tests are needed *Update* Work has started in the *feature/new_classes* branch but will take some time. Status per OpenAtlas class: *To do* * Actor function * Actor relation * Administrative unit * Appellation * Artifact * Bibliography * Edition * Event * External reference * Feature * File * Group * Human remains * Involvement * Modification * Move * Object location * Person * Place * Production * Reference system * Stratigraphic unit * Type * Type tools *Done* * Activity * Acquisition * Creation * Event * Source * Source translation