Allowing the client to update fields that are not meant to updateable
In 3d770816 and 465fd6e3 we have let the client change fields that, according to the Noark metadatacatalog, are not updateable. merknadsdato is an example of this.
Recent work on nikita and related import projects have shown that Noark is perhaps a bit too strict when it comes to import. Date fields are not settable by the client, Neither are createdBy etc fields. This leads to a discussion about how strict our interpretation of Noark API should be. The Noark API does not really say that much.
Definisjon: Dato og klokkeslett når merknaden ble registrert . Kilde: Registreres automatisk av systemet. Kommentarer: (ingen). M611
It does not say that the field is not updatable, but the M611 reference to the metadatacatlog is clear that the field is not updateable.
Going forward, we probably should be consistent. Either we ignore all "sensible" requirements when dealing with import or we keep to the "sensible" requirements. As it stands, we are starting to be inconsistent. The issue needs further discussion before we can land on an approach.
My fear with allowing a client to set dates and change things like "opprettet" is that it easier enables a situation where part of the archive can be deleted and recreated to change the story of the material. Without third part mechanisms to handle this, the authenticity of the archive can quickly be challenged. An easy counter argument is that with access to the database, it's relatively easy to rebuild parts of the archive anyway.
So perhaps the issue could be seen as boiling down to, if there are no third party mechanisms in place to detect such changes, should the API allow such changes to occur.