http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9011
--- Comment #124 from Kyle M Hall <[email protected]> --- (In reply to Katrin Fischer from comment #123) > Basically a big pile of paperwork where I have to document every table that > has in any form a connection to patron data and the duplication of the > information. Also the possibility that this will leak out into the OPAC with > the other item data when someone maps it to a 952 field not thinking about > the consequences. Thanks! I'm not sure we've any way around that. The connection won't be made unless the feature is specifically enabled. Likewise, this data would never be revealed in the opac unless some specifically map the column to a field. To accidentally reveal the data would definitely require jumping through some hoops, but we have no way to absolutely prevent such an occurrence. On the other hand I don't feel that this should be a blocker considering we could do the exact same thing in other areas of Koha. Consider how trivial it would be to create a patrons report and then mark it public? Just because that's possible doesn't mean we stopped the public reports feature from making it into Koha. That being said, I'll defer to your judgement, but someone has to make a decision. Either we go with choice A or choice B. -- 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/
