I have just exchanged some data with a partner organisation which also has a copy of Recorder using the NBN Acces database (zipped) format and we have noticed that the table Measurement_Unit_Value was not included in the export.

The purpose of the export on this occasion was to provide the partner with a copy of some additional measurement categories which we have added, which allow a restricted range of values (an example is that we have added a DAFOR scale to the abundance qualifiers in addition to the supplied count and range measurement units).

It would appear therefore that although the partner now has the relevant details in their term list, they can enter data without the restrictions which apply to ours. This might lead to data incompatibility in the future.

I know how to fix this on this occasion (I will send them the contents of our measurement unit values table), but it would be good if the exporter (and importer?) was updated to prevent this happening again.

In order to maintain proper control of this table it should also include a CUSTODIAN column, with the corresponding controls to prevent one partner from editing another's allowed values.