Auth.pm now caches form submissions and resubmits them if a user logs back in
after being logged out for inactivity. Also switched from crypt passwords to
md5 passwords stored in borrowers table. Used Digest::MD5 module. I ain't
gonna reinvent _that_ wheel. :)
Auth.pm now checks the password againts a new field in the borrowers table
(password). There is also a new "userid" field in the borrowers table. When
a user logs in, the userid will be checked against the userid first and the
cardnumber second, so either method will work.
Checks for a basic authentication userid. If found, it skips the cookie stuff.
Also now supports scripts that do not _require_ authentication, but might
display differently if they get an authenticated userid (might be useful for
opac pages, where pages could be tailored to meet a patron's preferences).
Not related to MARC :
* removed HLT- empty link when no basket for a supplier (should be useful to copy this into rel-1-2 i think)
* fixed some "use of uninitialized value"
related to MARC
* changed use Acquisition to use Catalogue, new package for MARC management
For instance, nothing is done to MARC DB, but structure is modified (see Biblio.pm for details), and everything seems to work : it's still possible to use acqui, and it fills old-DB pretty good.
WARNING : if you work on main trunk, please note Acquisition.pm is NO MORE USED in /acqui/ system. Every sub in Acquisition.pm has been moved to Biblio.pm or Catalogue.pm.
tipaul [Thu, 20 Jun 2002 21:07:30 +0000 (21:07 +0000)]
* Acquisition synchronised with rel-1-2
* Update of biblio.pm and catalogue.pm that continuates MARC stuff. Lot of explanations at the beginning of Biblio.pm
tonnesen [Thu, 20 Jun 2002 17:33:07 +0000 (17:33 +0000)]
More merges in from rel-1-2
All of the changes so far have been minor. I did uncomment delbiblio($biblio)
in delbiblio.pl in the main branch to match delbiblio.pl in rel-1-2
rangi [Wed, 19 Jun 2002 01:04:47 +0000 (01:04 +0000)]
Fixing issues which i broke just before ... perhaps one more commit today.
Issues used to pop up a payment window when a borrower had finished issuing
and had money to pay.
We seem to have lost that, ill try and get it back
tipaul [Fri, 14 Jun 2002 16:47:33 +0000 (16:47 +0000)]
Going to MARC 1.4...
0- Requires MARC::Record from cpan to work
1- divided Catalogue.pm in 2 parts :
Biblio.pm ,that contains biblio management
Catalogue.pm, that contains acquisition management.
When ended, they will replace the Acquisition.pm package
2- Created MARCxxx functions :
* MARCgetbiblio : retrieves a MARC::Record from the bibid passed in parameter (working, see test.pl script)
* MARCaddbiblio : creates a MARC-DB entry, for a MARC::Record given as parameter. (working)
* MARCmodsubfield : modifies a subfield for a given subfieldid
* MARCfingsubfield : retrieves a subfieldvalue from a bibid/tag/subfield
* MARCaddsubfield : adds a subfield to biblio into the DB
* MARCkoha2marc : builds a MARC::Record, given a biblionumber, a biblioitemnumber and/or an itemnumber. (working).
TODO :
A lot ;-))))
For instance, you can create only a MARC-DB entry from a old-DB entry. Note some questions are still to solve around bibid (old-DB/MARC-DB)...
finlayt [Thu, 6 Jun 2002 04:15:18 +0000 (04:15 +0000)]
fixed bug http://bugzilla.katipo.co.nz/show_bug.cgi?id=1284
If an item doesnt have a holdingbranch it just shows blank instead of not appearing at all.
tipaul [Tue, 4 Jun 2002 16:08:47 +0000 (16:08 +0000)]
test.pl, contains a script to test the Catalogue.pm stuff.
Catalogue.pm : marc stuff :
* the 3 xxxSubfield functions works
* the addMarcBiblio function has been added : if you pass it a perlmarcstructure (sample in test.pl and explanation in marc/perlmarcstructure file), it adds a biblio to the marc_schema. The newbiblioitem (old koha-DB) still has to be updated to build the perlmarcstructure internally and call addMarcBiblio function.
tonnesen [Sat, 1 Jun 2002 05:46:08 +0000 (05:46 +0000)]
Added checking for option to run unsafe database tests. The idea is that tests
that attempt to modify the library database will _not_ be run unless the
environment variable DoUnsafeDBTests is set to 1. This allows people on
production systems to run the tests without any fear of data corruption, while
developers can run the full suite of tests on a standard sample database.