http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9223
Olli-Antti Kivilahti <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #37 from Olli-Antti Kivilahti <[email protected]> --- AFAIK: The suggestions.itemtype-column is not used anywhere other than displayed as-is in the suggestions.pl-view. I tried setting the itemtype-column to "ITYPE - CCODE - LOCATION" and it seems to work quite well. I don't know why anybody would want to expose their patrons to ILS-configuration technical parameters like that, but using this simple trick it should be possible to collect and store all three values. On a followup those three parameters can be separated to their distinctive columns. Also using only one ITEMTYPE or COLLECTIONCODE should be more than enough for a borrower to categorize his suggestion. I think the suggestions-mechanism is meant for ordinary library users and if further "resource" description accurancy is needed, then an acquisitions integration would be more suitable for the task using EDI or similar. I feel sadness when a new system preference is added. In this case "SupportsAuthorizedValues"||"SuggestionsUseValues". A better solution would be to use the first value in "AdvancedSearchTypes", eg "ccode|itemtypes|loc" would translate to using "ccode" as the selection displayed for the user, or simply displaying all those options and concatenating them to the suggestions.itemtype-column. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
