# Require unique value

**URL:** <https://speciforum.org/t/require-unique-value/303>\
**Category:** New Feature Requests\
**Created:** [March 25, 2022, 4:10pm UTC](https://speciforum.org/t/require-unique-value/303 "2022-03-25T16:10:10Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![fedoras](https://yyz1.discourse-cdn.com/flex029/user_avatar/speciforum.org/fedoras/32/455_2.png) [@fedoras](https://speciforum.org/u/fedoras)\
**Post date:** [March 30, 2022, 1:55pm UTC](https://speciforum.org/t/require-unique-value/303/7 "2022-03-30T13:55:02Z")

</div>

OK 🙂

In that respect, it may be useful to consider a smarter auto-numbering system as I’m suggesting her:

#326

> [@Smarter Catalog Numbering](https://speciforum.org/t/smarter-catalog-numbering/326):
>
> Specify needs a smarter numbering system capable of: Reservation of (blocks of) catalog numbers Checking on already existing numbers upon data entry Skip already existing numbers upon data import Check for unused catalog numbers and start using those (preferably in backwards direction down to a baseline number e.g. 999) The current method is quite crude and is basically just starting from the highest number for a given collection, which is a problem, since we’re using the same numbering syste…

---

_[View the full topic](https://speciforum.org/t/require-unique-value/303)._
