https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19889
--- Comment #26 from Tomás Cohen Arazi <[email protected]> --- (In reply to Tomás Cohen Arazi from comment #25) > (In reply to Christopher Brannon from comment #22) > > (In reply to Tomás Cohen Arazi from comment #21) > > > > > So the result is similar, but ugly-ish. And involves an error prone > > > free-text field with pipe-separated values. So I don't see any advantage > > > on > > > it. If we were to expose this condition on the API also, we would need to > > > add methods to extract the boolean with this kind of comparison, instead > > > of > > > just reading what's on the category table. > > > > What if it wasn't a free-text field? What if we did something similar to > > what is being done in > > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22844? Select the > > categories from a list rather than free typing? > > I wasn't aware of that dev. Nice! After reviewing the implementation I can say that we would still need a separate dev so we can make it handle data from the DB (the defined categories) as it is only using a hardcoded list of attributes... -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] 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/
