[koha-Infos] question stratégique à propos des différentes branches (2.2 et 3.0)
Paul POULAIN
paul.poulain at free.fr
Ven 9 Sep 17:38:40 CEST 2005
Bonjour,
La version 2.2.4 est toujours prévue pour la fin du mois.
En regardant les notes de cette future version, je m'aperçois qu'il n'y
a presque plus de bug corrigé, mais qu'il y a pas mal de nouveautés.
Je me pose la question de la stratégie à suivre pour la suite : dois-je
continuer à diffuser des versions avec de nouvelles fonctionnalités ou pas.
Je détaille mon questionnement :
Sortir une version 2.2.X, signifie :
* du pt de vue développeur, faire un effort toujours plus important pour
synchroniser les branches 2 et 3 pour l'avenir long terme
* du pt de vue utilisateur, les nouvelles fonctionnalités sont décrites
dans les notes de version, mais je crains que certaines d'entre elles
soient manquées. De plus 4 versions à mettre à jour dans l'année, c'est
peut-être un peu trop pour les bibliothèques ?
Donc je commence à me dire qu'il faudrait peut être limiter à partir de
maintenant la branche 2.2 aux seules corrections de bugs, et réserver
toutes les nouveautés pour la version 3.0
L'arrivée de cette dernière va supposer pour les bibliothèques qui
voudront l'installer un effort de découverte vu toutes les nouveautés
annoncées.
J'espère avoir été clair, et j'aimerai votre sentiment d'utilisateur sur
cette question.
A titre d'information, voilà les notes de version de la 2.2.4 dans leur
état actuel (donc pas nécessairement complètes, à ne pas diffuser svp) :
BUGFIXES
=== CATALOGUING ===
* created a plugin & tools to manage the MARC leader.
* fixing a bug in subfield order when MARCgetbiblio
* adding some diacritic decoding (Ä, Ü...)
* removing -s parameter in z3950 client, as it does not work for FreeBSD
servers
* Managing multiple URLs in normal view : if you type more than 1 URL in
856$u (same field in both marc21 and unimarc!), the normal view will
show multiple URL, not a single one with all urls concatenated.
* Fixing a bug in MARC editor for fields >200 characters.
* fixing a bug in MARC editor when there are more than 1 list of the
same type (lang, branch...)
=== OPAC ===
* getting rid with "Internal Server Error" that happends when there is
no stopwords
* Removing a 'request' button in opac-detail, that was here even if
there was no items for loan
IMPROVEMENTS
=== ACQUISITION ===
* budget can now be branch dependant : when you define a bookfund, you
can choose a branch. If you don't, the bookfund can be used by any
librarian in acquisition. If you choose one, only a librarian from the
branch can use this bookfund. Note that librarians with superlibrarian
flag can always order from any bookfund.
* adding the number of orders & line count in acquisition history.
* if the library defines Asort1 or/and Asort2 (A for Acquisition)
authorized values category, the free fields sort1 and sort2 will be a
list containing what the authorized value category contains. If they are
not defined, the behaviour does not change : the value in sort1 and
sort2 is a standard input
=== CIRCULATION===
* added a ReturnBeforeExpiry systempreferences. If set to yes, then the
returndate will be limited to the expirydate of the borrower card. If
set to no, then the returndate can be after the expirydate of the
borrowercard. This was the previous behaviour, but some libraries have
expirydate that means "the student will leave the school at this date",
so the return limit must be properly set.
=== CATALOGUE ===
* when displaying ISBN, - are automatically added where needed.
(Internally, ISBN are sill without -)
* some graphic modifs in MARC view : colors & font weight + when a field
has only 1 subfield, the subfield name & code is not repeated, as it is
useless.
=== CATALOGUING ===
* getting rid with the limit "biblionumber & biblioitemnumber must be in
the same tag". So, we can put biblionumber in 001 (field that has no
subfields, so we can't also put biblioitemnumber in this field), and use
biblionumber as identifier in the MARC biblio too.
* adding a script misc/migration_tools/build_authorities.pl to rebuild
authorities after a bulkmarcimport. This script is highly faster &
better than build_6xx.pl that is still here, but just for historic purposes.
=== MEMBERS ===
* adding the number of member & line count in searching members screen
* if the library defines Bsort1 or/and Bsort2 (B for Borrower)
authorized values category, the free fields sort1 and sort2 will be a
list containing what the authorized value category contains. If they are
not defined, the behaviour does not change : the value in sort1 and
sort2 is a standard input.
=== OPAC ===
* Adding reading history button when the user is identified.
* Adding page to let patron change it's password.
=== SERIALS ===
* when recieving a serial, 2 options have been added (not issued &
delete. Options added to waited, arrived, missing & late). Not issued
means "book not issued, will never arrive at the library. "delete"
deletes the entry. It's useful when you are waiting for Issue #511 and
Issue #512 and recieve a Issue #511-512 : you change issue # for one of
them & set "recieved" and delete the other.
* a note field has been added for each serial. You can use it to store
some information on a given (waited/late) serial. For example, you can
note "bookseller called on 8/21/05, serial will be sent next month".
* detailled history view ported from OPAC to librarian interface as well.
* the history view is ordered by year, but also by subscription, to see
all issues of a given subscription at once.
* the feature to delete a subscription ONLY when no issues has been done
has been removed : you can delete a subscription at any time (it deletes
issues & history as well, be careful when deleting ;-) )
=== SYSTEM PREFERENCES ===
* adding tabs to systempreferences screen : displaying preferences
category by category (admin, acquisition, authorities, catalogue,
circulation, members, OPAC and others). That makes systempreferences
system easier to use
* Adding a "IndependantBranch" systempref. If you select it, then your
branches are considered as independant, and the librarians from a branch
can't change things from another branch :
- items owned by branch A can't be modified/deleted by a librarian from
branch B
- items, bookfunds and borrower created by a librarian can only be
attached to it's own branch
- borrowers from a branch A can't be modified/deleted by a librarian
from branch B
Note that issues are not concerned by this limit : a borrower from
branch A can issue/return book from anywhere and, of course, transferts
can always be done too.
Also remember that librarians with superlibrarian privilege can alway
work on every branch
=== ALL ==
* adding a small image with Koha egg to have the egg in window title bar
& get rid with those pesky "can't find favicon.gif" in apache logs.
--
Paul POULAIN
Consultant indépendant en logiciels libres
responsable francophone de koha (SIGB libre http://www.koha-fr.org)
Plus d'informations sur la liste de diffusion Infos