Allow users to define icode1 in Sierra
Our library uses the icode1 field as a statistical category code. We'd like to be able to define our icode1 values, with codes and labels stored in Sierra and visible to staff. Currently we keep a list of codes and their meanings stored in a shared drive and have to share it with our cataloguers. Staff can see the "stat category" field in item records, but there's no translation anywhere in Sierra and the userdefinedicode1_myuser SQL view is blank.
Jennifer Moakler
shared this idea
This idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Lloyd Chittenden
commented
Most of our libraries don't use ICODE1 at all because keeping track of what they mean is a pain. However, I would point out that this would require all the libraries in a consortium to agree on what the codes mean. As it is, each one can make them mean whatever they want. I suppose if you can't agree, then you could leave them blank, and those who can agree could label them.
-
Phil Shirley
commented
This would be helpful to us, too. It's standard for the documentation of what a code means to be right there in the software where you use the code.
-
Alison Pruntel
commented
It would be much easier to have this in Sierra vs. relying on it to be documented somewhere else. With having it in Sierra, we can make sure the system admin is able to maintain that information (won't get overwritten on a spreadsheet somewhere).
-
Andrew Hollingsworth
commented
It's been 8-9 years since Sierra, there is a view for it in the DB. We're not sure why it's never been implemented.