[Koha-bugs] [Bug 27512] Block creation of invalid authorised values for LOST, NOTFORLOAN, DAMAGED, RESTRICTED, and WITHDRAWN

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27512

--- Comment #5 from Marcel de Rooy <m.de.rooy at rijksmuseum.nl> ---
(In reply to Andrew Fuerste-Henry from comment #4)
> (In reply to Katrin Fischer from comment #3)
> > You can create the authorised values without issue, but you cannot use them
> > in items. items.damaged linked to DAMAGED only takes numerical AV codes.
> > (datatype)
> 
> Correct. I can create an authorized value in the DAMAGED category that has
> the value "TORN". Koha allows the creation of that authorized value, and
> then will show TORN as an option when editing items. However, it will never
> actually save TORN on an item and will never explain why it's failed to do
> so. The answer to that lies over in the schema, which tells us items.damaged
> only holds a bit.

Okay. How to proceed?
We could move damaged to varchar() as expected by Authorised Values?
Or we could intercept this in storing the item?
Or even before building the combo, but that could be quite generic code, so a
bit harder? Or when loading the form in javascript (hide options with a
non-numeric value)?
Another idea?

-- 
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.