http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10409
--- Comment #9 from Kyle M Hall <[email protected]> --- (In reply to Galen Charlton from comment #7) > (In reply to Owen Leonard from comment #0) > > The course reserves entry form shows an error message instead of a form > > field for the department if no departments are defined: "No DEPARTMENT > > authorised values found! Please create one or more authorised values with > > the category DEPARTMENT." > > A question about the premise of this patch, possibly for Kyle: is there a > functional reason why setting a department is absolutely required? If so, > why is courses.department a nullable column? There is no functional reason to require the setting of a department. It was merely a requirement of the specification I was following ( where the functionality was based on another implementation of course reserves which made Department a required field ). Making department an optional value would do no harm. Of course, the same could be said for the "Name" field, so it's more of a philosophical question than anything. I guess the question is "In practice, will anyone want to create courses *without* course departments?". So, we can either leave department as a required field, or make it optionally require via a system preference. What are your feelings on those options? -- 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/
