[NEEDS REVIEW] Editing information and card views

This page offers a description on how the cards (blocks with data) should look in different views, and how editing of these cards should work.

Needs review from dev

Standard view

This is an example of a detail page with a card containing information.

• Any field/label that is left empty should not be visible in the card.

• There is only one edit button (Bewerk) at the top of the page, which allows the user to edit all the cards simultaneously in a new page (see further down).

Missing information view

For information on what to do if there is missing information [empty fields], please go to Conditional viewing of data.

This is not part of the current implementation.

Editing/Adding information

Once a user clicks on the edit button (Bewerk) on any page allowing to edit/add information, they will be taken to a new page, where they can edit all the cards.

Editing information in tabels, not cards, happens separately. (see below)

Editing data tables

Editing existing information in a detail page

To edit a cell in a table detail page, the user needs to click on the edit ("Bewerk") button of the corresponding row in the table.

Clicking on that button will open up a new page, where the data of that row is shown in a card, and where the user can make the necessary adjustments.

There have been concerns on having multiple Edit buttons on the page and the impact in usability, however this is the easiest way to implement the editing of tables at the moment.

We could test whether editing tables could happen in two steps, where the first Edit button (shown in the screen above) would not be visible on the first screen, but rather on the editing screen where the user edits cards. The table would then be replicated and the user would choose what row to edit on there. This would add a step to the journey and there are also implications concerning the behaviour when a user edits a card and then decides to edit a table row before saving, which would need looking into.

An alternative solution would be to change "Bewerk" in the table in the current solution, to "Bewerk voorwaarde" to specify what the user will be editing.

Editing rows in overview pages

To edit a full row in a table in an overview page [e.g. editing information about a Voorzitter in the current Bestuursorgaan ] the user will be taken to the editing screen for that position.

Adding a row to a table

To add a row in a table on an overview page, the user can simply click on the button "Nieuw".

If the user is adding new information [creating a new position, adding a person not yet in the database,..] please follow the page on Creating new entities.

If the user is adding existing information [e.g. adding a new mandate to the list of mandates], the user will be asked to search through the database to find existing data.

In this example, the user wants to add an existing person to the list of mandates.

They have to then select a person from the generated list:

And continue by filling in the information for that mandate - this, however is new information, and follows the rules on Adding information:

Deleting data

To delete a row in the table, the user needs to edit the end date of that position/clause [if there is a more general term for all of these, please feel free to amend this] . Adding an end date to the position will make it disappear from the table as it will no longer have all the criteria [being active] to be visible in a table.

We do not allow deleting data. The user can add an end date, which will archive that entry. If the user wants to delete information, they will need to request this via email to an administrator.

Outstanding questions

• How do we deal with editing information also available in Loket?

  • E.g.: information for mandates of a local authority?

SM 8/7: We need to talk to Katrien and Pieter. The local authorities are responsible for their own information. Emails are send to remind them to update.