Bug 6796 adds the ability to define library opening hours for each branch. It does not, however, respect weekday closed days as defined in the Calendar page. We should expose that detail from the libraries interface, including in the summary table, details view and edit form. I believe this would be best achieved by migrating the weekly closed days from repeatable holidays into the new library_hours table and thus making it available via the existing library_hours embed in the API. This makes it trivial to display the open/closed state in the api driven datatable as well as on the view and edit pages. We should continue to support displaying and editing these weekly closed days from the calendar too, however.
Trying to think this through: 1) Is there a difference in purpose of the hours listed in Library info, versus what the calendar does? Are the hours in Library info intended to define the 'standard' hours, versus the calendar marking exceptions to these? ("Holidays repeating weekly" on the calendar can be used to close the same day of every week though, and if so, how to be reconcile the data in both places?) 2) Does it make sense to incorporate the weekly hours to the calendar? If we define the 'normal' hours for each day of the week for each location (or all locations) and then use the calendar to mark exceptions to that? 3) As it stands, the calendar is really just for marking closed days, not for making exceptions to hours like closing early or opening late. This could be very helpful for many libraries who change hours around holidays or seasonally. Integrating the daily hours settings into the calendar could allow for defined exceptions to hours via the calendar.