I tried to create two entities that have the same name. This is a fairly common situation in an archive of moderate size. (e.g. consider how many John Smiths exist and write books). Instead, i get the following message:
There are errors preventing information in specific fields from being saved as noted below.
Value John///Smith/// is already used and duplicates are not allowed
Disable duplicate checking in app.conf - eg. set allow_duplicate_labels_for_ca_entities to 1
FYI - it is often custom to distinguish authors with identical names in some fashion, often with a parenthetical in the surname or display name. Having multiple "John Smiths" in an archive without any way to disambiguate is a problem. This is why entities are configured to require unique labels by default.
Thanks for the pointer, that's useful. FWIW, i tried setting the display name to be different between the two of them (thinking along the same lines as you describe), and i still got the error message and refusal to create.
Should this be the case?
The current implementation does not consider entity displayname when comparing labels. This was done specifically to meet requirements of users who rely upon (and requested) this option. Arguably we should provide an additional entity-specific option to enable/disable displayname inclusion in the comparison.