There is no reason for a record to have duplicate values for repeating fields. Currently, duplicate values can be made unintentionally (and unavoidably) in the import process.
See Accession 1900-31 where type is “purchase” in Africa data and “gift” in Europe data: http://amnhdev.whirl-i-gig.com:8084/index.php/editor/object_lots/ObjectLotEditor/Edit/lot_id/964.
Can be tested on AMNHDev on Mermaid.
Implemented this on amnhdev for evaluation. It's not committed yet
New "allowDuplicateValues" setting on most metadata element date types (Container, Media and File are notable exceptions) controls whether you can apply duplicate values to a record when the element is standalone (ie. not in a container). The default setting is to *NOT* allow duplicate values, which is of course a change from how it has worked to now. I can't think of any typical real-world situations where you'd actually want dupes, so it seems like a good default to enforce uniqueness within a record. If we do need to allow for dupes, it's easy enough to enable.
great, thanks. is this change in amnhdemo on mermaid?
I just pulled it over to amnhdemo. It was already on amnhdev. Both of these are on Mermaid.