A number of things need to be in specific places for the system to be happy. Some of them make some kind of sense to someone looking quickly. Others don't.
For example, the default "Stacks" location doesn't make sense to everyone (at least not in libraries) and the fact that it has to exist causes confusion at times.
Things like the "-1" bib and call number at least are outside of the normal numbering range of 1+ and thus are obviously special, but many of the others aren't as obvious, especially when people are encouraged and/or expected to be adding and removing entries.
Also, if we are going to add special constraints for some of these I think we may need to add them for others. Like "You can't delete or change the id/owner of the stacks location", preventing deletion of the core statuses, etc.
A number of things need to be in specific places for the system to be happy. Some of them make some kind of sense to someone looking quickly. Others don't.
For example, the default "Stacks" location doesn't make sense to everyone (at least not in libraries) and the fact that it has to exist causes confusion at times.
Things like the "-1" bib and call number at least are outside of the normal numbering range of 1+ and thus are obviously special, but many of the others aren't as obvious, especially when people are encouraged and/or expected to be adding and removing entries.
Also, if we are going to add special constraints for some of these I think we may need to add them for others. Like "You can't delete or change the id/owner of the stacks location", preventing deletion of the core statuses, etc.