https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36594
CJ Lynce <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Patch complexity|--- |Small patch CC| |[email protected] | |g Assignee|[email protected] |[email protected] |ity.org |g Status|NEW |In Discussion --- Comment #8 from CJ Lynce <[email protected]> --- Please take a look at a first try at addressing the issues here. The following assumptions/decisions apply: A) Days with both open and close times undefined are considered 'CLOSED'. B) It might be possible to have a library open one day and close the next? This would mean that an opening time is defined, but a closing time is not for one day, and a closing time defined for the next day, but no opening time. Regarding B) The more I think about this, I don't think this is going to work well. If a library opened on a Monday, and remained opened straight through to Wednesday, Tuesday would shows as closed since both times are undefined. I also don't have a great understanding yet of all the places these times are used (e.g. calculating due dates/times, or displaying in the OPAC?), but I would imagine allowing and opening time, and no closing time for a day would cause problems? I think a better way would be to require BOTH open and close times for a day for it to be considered valid. If a library is opening spanning days, do it 'close' at 23:59, and open at 0:00 the next day? I welcome any comments on these thoughts. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug. _______________________________________________ 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/
