Finishing data entry wizard

[lislis]

This is the main interface for entering cases to the database. It is a wizard style form that allows jumping through different layers at any point. All changes are recorded locally until the first save. Main missing points are generating form fields from the new settings endpoint and saving to the server using the new internal API

[lena-nahrwold]

missing routes GET /cases, POST /cases

[lislis]

Hey! Most of what's in the frontend code of the wizard (or rather all of cases...) needs updating as the concept of cases does not exist anymore. Cases are now records and pull together information from their entities and their respective fields or attributes.

So I think what needs to happen is this:

• make a fresh route for /wizard or /records/new or something similar
• make a wizard view that pulls the settings_schema key from settings in the localstorage (should be loaded on pageload) (what can be edited under /admin/schema)
• parse the settings_schema into a nice object
• build the wizard subnavigation from that object:
  • the object should be an array that contains expected entities (eg victim, perpetrator etc)
  • create a link list that points to /wizard/entity/:entityname
• create a route /wizard/entity/:entityname that is a child route and renders a subview
• the subview renders / iterates over the entity's attributes key (that should also be an array)

Assuming we configured the schema to have an entity called 'Opfer' that has 'Bildungsgrad' and 'Familienstand' and another entity called 'Täter' that has 'Familienstand' and 'Vorstrafen', then going to /wizard we see a sidebar navigation that says:

• Opfer
• Täter and when we click on Opfer we go to /wizard/entity/opfer and see both the sidebar navigation and the points 'Bildungsgrad' and 'Familienstand'.

I hope that makes sense!

That would be a good place to build the rest from! Then the Wizard builds itself from the configured schema! Magic :sparkles:

[lislis]

I'll merge the bugfix to create categories and category_items, too. so you can play with creating data schemas (which is kind of a prerequisite for this :grimacing: )