Re: silva metadata: changing properties

> Maybe we find a better procedure than just throwing an exception, but 
> at least the worst case of part of the documents having properties 
> which don't exist any more was inhibited.

it's exactly the opposite, isn't it? the problem IS that the documents 
HAVE a property which has been changed and is now incorrect and the 
error inhibits the user to correct it.

>> metadatasets can evolve and change with time...
> Of course. But this is not the case that you are describing above.

this is simply a hint that this might not only be a typo problem and 
one has to check into this a little bit deeper. e.g. what happens when 
the type of a metadata element is changed? we already know that the 
listfield element works different than the other elements in the 
metadata. maybe there are other problems? not everybody can develop 
some kind of migration script.

> No implicit automatic reset. I prefer definitely: "Explicit is better 
> than implicit".

i prefere the automatic one or at least let the user choose to let 
silva fix the problem. because when the person with access to the 
metadata system is unavailable how could the others resolve this issue? 
for small sites or companies there is often only one person available 
(although this is a mistake) which can fix this problem.

regards,
marc