You can set rules in the registry that ensure uniqueness between different entities of the same schema. The options include:
Sequence: for DNA or AA sequence schemas, you can set this constraint to ensure that no two entities have the same sequence.
Field or combination of fields: you can set a constraint on a certain field or combination of fields to ensure that no two entities have the same combination of links, values, etc. A common example is a constraint on Heavy and Light chains on an Antibody (i.e. no two antibodies can have both the same Heavy and Light chain)
Constraints give you peace of mind that you are registering a unique entity. When a constraint is set, if you attempt to create an entity that violates the constraint you will be prompted to merge with an existing entity.
How do I know when a merge will happen?
Benchling will let you know when you are trying to register a duplicate entity.
Note: If your incoming entity’s name or alias is already used as a name, alias, or registry ID of any entity already in the registry, this is treated differently and Benchling will not allow you to merge it or complete the registration.