Closed Ksepka closed 10 years ago
I think this is an unintended consequence of the new edit collections restrictions (meant as safeties to keep us editors from wrecking things).
Absolutely right, sorry about that. I did not properly distinguish when the user entered a new (vs. chose an existing) collection when validating this acronym. Fixed now and behaving as expected.
Looks good now, thanks.
I think this is an unintended consequence of the new edit collections restrictions (meant as safeties to keep us editors from wrecking things).
I tried to enter a new fossil from an existing collection (e.g., CM, Canterbury Museum 500). This error pops up: "There's already a collection with this acronym! Please modify it or choose the existing collection."
The database doesn't seem to recognize that I just want to add a new CM fossil, not add a new CM collection abbreviation. So I think the only way to enter a new fossil right now is generating a new collections, obviously bad because it locks out new fossils being entered for any collection already represented.