Feature #2464
Updated by Alexander Watzinger 3 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
* See below for UI improvments
h2. Update
Work has started in the *feature/new_classes* branch but will take some time. Status per OpenAtlas class:
*To do*
* Administrative unit
* Artifact
* Feature
* File
* Human remains
* Object location
* Place
* Reference system
* Stratigraphic unit
* Type
* Type tools
*Done*
* Activity
* Acquisition
* Appellation
* Bibliography
* Creation
* Edition
* Event
* External reference
* Group
* Modification
* Move
* Person
* Production
* Source
* Source translation
*Removed*
* Actor function
* Actor relation
* Involvement
h2. New features
* *Human remains* can now also be used with *Modification* and *Move*
h2. UI improvements
* Actor
** The map is shown at an actor detail view if e.g. residence is available
* Source
** The source index now also shows source translations
** The source of a source translation can be changed when updating a translation
** Source translations annotations can be linked to entities of the source at insert too (before it was only possible at update)
* Type
** Types are linked in table views
** Sub types can also be added at the type detail view
** The type of entities can also be removed in the entities tab of a type detail view (if not required)
h2. Minor fixes
* Removed *insert and continue* buttons when inserting and linking with additional fields (which weren't working anyway)