This update the way Member is added and editing so that import and Edition
could be best automatized
GetMember evolves and allow ppl to serach on a hash of data
Adding SQLHelper A new package to deal with INSERT UPDATE and SELECT
Adding some new options to bulkmarcimport :
-k idtagsubfield in order to store the id of the file record into another field
-match tagsubfield,index
-a to import authorities
-l logfilename to store logs
Bug Fixing : C4/Charset.pm
Charset was incorrect for UNIMARC Authorities
Adding finedays and reservesallowed and renewalsallowed management in smart rules
Adding Clone Rules
Adding CanBookBeReserved and CanItemBeReserved in C4::Reserves
Manage Reservesallowed in opac and staff interface
Manage renewalsallowed in C4/Circulation.pm
Update Database follow
Jane Wagner [Thu, 24 Sep 2009 14:57:40 +0000 (10:57 -0400)]
Bug 3661 XSLT fixes
The XSLT results list (MARC21slim2OPACResults.xsl) did not have any separators between multiple 246 fields, so additional titles all ran together. I added the standard semicolon or period as in other repeating fields.
The display for personal and corporate authors was also confusing. The period after the last personal author (100/700) is very hard to see, so the display looked like the first corporate author only belonged to/was associated with the last personal author, rather than being a separate author entry. I've added a dash at the beginning of any 110/710 entries to set off the corporate authors a bit in the display.
I added the same code to insert a dash before any 111/711 (Meeting author) as well.
This patch also adds missing text labels for text_list_bullets.png
(bibliography) and remote.png (available online).
Owen Leonard [Fri, 25 Sep 2009 18:54:11 +0000 (13:54 -0500)]
Corrections to ensure message list appears in the proper box (Bug 3668).
The patch sets a "flagged" variable for displaying the messages correctly, bringing it in line with the way other messages are displayed. The patch also includes some markup tweaks and a change to make display of the "add message" link javascript-dependent.
Jane Wagner [Wed, 16 Sep 2009 15:15:55 +0000 (11:15 -0400)]
Bug-3098-Bug-3108-Bug-3545 revision to XSLT syspref patch
The patch I sent earlier repeated a line having to do with the count of items, which mean the count was now doubling (2 items instead of 1, 4 instead of 2, etc.). This patch removes the first, now superflous line of $xmlrecord =~ s/\<\/record\>/$itemsxml\<\/record\>/;
Adds a new system preference, ShowPatronImageInWebBasedSelfCheck;
if this preference is ON, a patron's image is displayed
if available when using web-based self-check.
Note: a patch for updatedatabase.pl will be made when this
change is ready to push.
This change is sponsored by the Plano Independent School
District.
Ability in system administration to define additional fee and fine options that appear in dropdown box
on the create manual invoice tab in patron fines.
To use create authorised values with the category MANUAL_INV,
Authorized Value is the description, and Description is the default fee, if any.
This work sponsered by East Brunswick Public Library, East Brunswick, NJ, USA
Signed-off-by: Colin Campbell <colin.campbell@ptfs-europe.com>
Colin Campbell [Sat, 25 Jul 2009 09:03:09 +0000 (10:03 +0100)]
New Messaging System.
This system is indended to replace the old opacnotes
and borrowernotes fields in the borrowers table.
This system allows an unlimited number of Libraran and OPAC notes to be
attached to a borrower. Each note has a message, a message type,
the data it was created, and which library created it.
Each message can only be deleted by the library that created it unless the syspref
AllowAllMessageDeletion has been set.
This system may be used simultaneously with the old notes system and does not affect it in any way.
A new database table (messages) was added for this feature.
The System also allows for pre-defined notes for Borrower records
To use these, just create authorised values with the category BOR_NOTES
where the Authorized Value is the short description shown in the pulldown,
and the description is the text that should be in the note.
Original Author: PTFS Contractor <dbavousett@ptfs.com>
This work co-sponsered by Middletown Township Public Library, Middletown, NJ, USA
and East Brunswick Public Library, East Brunswick, NJ, USA
Signed-off-by: Colin Campbell <colin.campbell@ptfs-europe.com>
Bug 2500 Correcting incorrect splitting of cutter numbers
This patch does two things to improve the call number splitting algorithms:
1. It makes changes to ensure that cutter numbers are split correctly in ddcns
2. It moves custom/fiction/biography call number splitting to a separate algorithm.
Before they were incorrectly placed in ddcns.
This patch also modifies the call number splitting tests to accept call numbers from the
command line to allow quick testing of any give call number against a particular algorithm.
Now requiring at least 0.80, the oldest version available
from CPAN, because use_ok tests were not being properly
accounted for in the test plan before 0.73. This led
to a situation where a test script containing a use_ok test
that passes running under an earlier version of Test::More
would fail under a more recent one.
Michael Hafen [Wed, 2 Sep 2009 20:14:59 +0000 (14:14 -0600)]
include grace period when calculating overdue fine
Before the grace period was not included in the number of days overdue when
calculating the fine. My librarians seem to think the number of days overdue
should include the grace period.
Fine is not assessed before the grace period is up though.
Bug 3606: fixes 'last 50 items only' link in members/readingrec.tmpl.
If a staff member clicked on 'Show all items' in a patron's reading record, and
then clicked on 'show last 50 items only,' all of the records would still be
shown. The link for the 'last 50' items contains a switch for 'limit=full'
instead of 'limit=50'.
Michael Hafen [Mon, 14 Sep 2009 15:07:57 +0000 (09:07 -0600)]
Avoid potentially unnecessary database call in Auth
Auth, after verifying the session/logging in the user, calls to the database
to get the users borrowernumber. This call is probably unnecessary because
borrowernumber is part of userenv. Check userenv before going to the database.