https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33932
--- Comment #5 from Christopher Brannon <cbran...@cdalibrary.org> --- (In reply to Jonathan Druart from comment #4) > Look at cgi-bin/koha/admin/koha2marclinks.pl: 1 DB column is mapped to 1 > MARC subfield. > > Everything is always possible, but that would be really hard to change :) Everything is hard to change from my perspective, especially mechanisms that have been in place for years, but there is a community of programmers out there that put together a brilliant ILS from nothing. Complexity should not be the deciding factor. I'm sure that answer could be given to most of the things the community programmers have contributed to Koha over the last 23 years. The question is, does the current setup tie our hands, and is it something that libraries would benefit from if it were changed? That's really why this is a discussion at this point. I am curious why the statuses are compartmentalized the way they are, and does this layout limit setup or functionality? Could consolidation improve system administration or item workflow? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug. _______________________________________________ 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/