https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13547
--- Comment #12 from Christopher Brannon <cbran...@cdalibrary.org> --- (In reply to Joy Nelson from comment #11) > Koha developments most often (if not always) keep one eye towards current > users as well as future users. At times it's hard to balance the needs of a > library (or libraries) and workflows that seem so important with the needs > and workflows of the many. The things that seem obvious to me are not > always obvious to others. I rely on the input of others in the community to > give perspective on how other libraries operate. I believe someone once > said "show me a library with a mad scheme and I'll show you another with a > madder one"! > > Speaking from someone with experience migrating thousands of libraries to > Koha, I can confidently say that libraries have indeed used this field with > the expectation that it was NOT visible in the OPAC. There is the distinct > possibility that patron information (or staff information/direction) is > available in this field. A number of libraries come to my mind who have > been using Koha for years in a way that is built upon the original design > (not visible in opac). > > If this is to be implemented and visible in the OPAC, it must be made so it > is optional/configurable. I guess then there should be a configuration. Anything to move this forward. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list Koha-bugs@lists.koha-community.org https://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/