A quick look at some possible changes in 3.2

There is a growing collection of “RFC”s for 3.2 features on the koha wiki. These are potential features that may be added in 3.2 or later. They’re put there to try to elicit community discussion to help steer them to make the best possible product. The 3.2 release manager, Galen, has indicated an interest in having these RFCs looked over by the end of next week, so I thought I’d take you on a quick tour of some of the more interesting ones. Here’s a quick look at some of the types of things being considered:

Administration improvements: The system of maintaining and using system preferences may get expanded by using roles and making the permissions collection more granular. On a somewhat related topic, there may be some work put into making independent branches work a little bit better.

Improvements to the user interface: In order to make Koha look and feel better to users, it’s possible we’ll extend the amount of AJAX elements that we use.

There are a handful of potential improvements for circulation. Among these is adding the concept of hourly circulation policies for some items. There are also a few that touch on holds, recalls, and fines.

Another interesting one would introduce summary holdings for grouping related items.

These are just a few of the RFCs that will get considered for features for 3.2 and beyond. You can help make Koha better by weighing in on how these may work together best.

4 Responses to “A quick look at some possible changes in 3.2”

  1. MJ Ray Says:

    You post on a Friday that the RFCs need looking over by the end of the week? I didn’t even see the post until Monday morning! We’re still busy upgrading our Koha libraries to 3.0 - way to exclude them from 3.2 direction. :-(

  2. Galen Charlton Says:

    The date of 10 October was proposed without disagreement during the community meeting on 12 September, mentioned again in the summary I sent to the mailing lists the same day, and noted in the post about the community meeting that Josh made on 16 September. Nearly a month’s notice is more than sufficient to at least glance at the RFCs.

  3. MJ Ray Says:

    I thought it was 10 October! That’s why I was surprised that the above article seemed to say it was 3 October.

    Even so, less than a month is a pretty short time to upgrade enough of our largest libraries to 3.0 and gather their input to 3.2.

  4. Joe Atzberger Says:

    > the above article seemed to say it was 3 October.

    It refers to “the end of next week” having been “posted on Friday, October 3rd, 2008 at 3:25 pm”. It should be pretty clear that doesn’t mean “today”.

    > less than a month is a pretty short time to upgrade enough of our
    > largest libraries to 3.0 and gather their input to 3.2.

    Then gather their input for next version or refer them to the RFCs directly.

Leave a Reply