The image below summarises the needs of the frontend (and thus also the backend):
possibility to create an identification string, preferably consisting of surface name dash Django id (i.e 120-12-001) or something similar.
Tags: Type, Writing System (Latin, Arabic, Hebrew, Cyrillic), Language, Genre, and Descriptive tags (this one can simply be called tags though the other ones are also tags from a controlled list). Most of these would only require one tag, but descriptive, and possibly genre might need to accommodate for more than one tag.
Transcription. This has to be an agreed upon transcription done very careful by those involved. i.e I don't think we want to bother with having the possibility to have several different interpretations, but this might change. If so then we would also need to have alternatives and the possibility in the frontend (through a drop-down to pick between the various alternatives) but this would complicate things needlessly fort the translations that would then also have to change depending on transcription.
translations, and the possibility for the frontend to populate a dropdown with available translation options. For most there will only be Ukrainian and English.
Descriptions. This might be a commentary on the translations, but will in most cases be a description of the figures. Need also to have at least Ukrainian and English.
contributors, populated by a list of the names of those that have contributed (authors), so in the backend there needs to be a multioption-thing like we have in Etruscan.
Inscription position coordinates (to draw it in the right place). This should be a field high up for the django-object.
Ideally, all of these fields, with the exception of tags and authors, should be editable right in the inscription object.
The image below summarises the needs of the frontend (and thus also the backend):
Ideally, all of these fields, with the exception of tags and authors, should be editable right in the inscription object.