The main purpose of this is to exclude not broadly used cancel reasons from user drop down lists. Many of the stock cancel reasons are reserved for EDI cancelations and cannot be deleted even if they've never been used. So the list is quite long to scroll through when really maybe only 2-4 cancel reasons are ever selected by users. EDI should still be able to use a cancel reason even if it's marked as inactive, because the ID is still there.
My question is: I used "active", but is "visible" better wording? "Staff visible?"
I have a branch to add an active column to cancel reasons:
https:/ /git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ tlittle/ LP1924758_ acqcr_activefla g
The main purpose of this is to exclude not broadly used cancel reasons from user drop down lists. Many of the stock cancel reasons are reserved for EDI cancelations and cannot be deleted even if they've never been used. So the list is quite long to scroll through when really maybe only 2-4 cancel reasons are ever selected by users. EDI should still be able to use a cancel reason even if it's marked as inactive, because the ID is still there.
My question is: I used "active", but is "visible" better wording? "Staff visible?"