Metadata entries lost

[Samuel Schluep]

Metadata entries are lost, if required metadata entries are missing. If required
metadata are missing, pressing "save metadata" will show the metadata tab with
an error message at the top. The fields where metadata is missing are
highlighted red. Unfortunately newly entered data in other fields, is not
transfered to the new metadata view. This means, the users hard work of entering
metadata is lost! (BTW these fields are not highlighted red.)

[Jan-Wijbrand Kolman (jw-infrae)]

This *is* irritating indeed. I'll look into it!

[Martijn Faassen (faassen)]

This is related to the transactional abort issue elsewhere,
right? The easy way would be to translate these errors into
warnings.

Perhaps we can reserve the 'error' message for any event
where things are so wrong they shouldn't be happening, I
don't know..

[Jan-Wijbrand Kolman (jw-infrae)]

Oh wait, maybe that's it! I sure hope (testing right away) since I thought it
was due to the metadata system not using Formulator properly....

[Jan-Wijbrand Kolman (jw-infrae)]

Unfortunatly no, this is not due to the transaction abort by setting the
feedback message type to 'error'. The metadata system first validates the input
and does not set anything when this validation fails.

The *actual* problem is that the metadata system does not use Formulator to its
full extent - which could have solved this and other metadata related issues
(like with checkboxes etc.).

I do have an quite concrete idea how to overcome this. However, I'm not sure if
the changes needed (for the bigger part changes in the silva views I think) are
allowed to be in scope for the 1.0 releaase (we *are* in RC phase now after all).

I can of course do the work on a branch anyway, so that it can be merged
whenever appropiate.

[Martijn Faassen (faassen)]

They're not allowed in the 1.0 process, as too big a change is required. I'll
move this to Silva-future.

[Samuel Schluep (schluep)]

Unfortunately this issue has still not been resolved yet (Silva 1.3 is now out)!
Maybe it should be classified as bug together with a specific Silva version.