[Koha-cvs] CVS: koha/C4 Biblio.pm,1.124,1.125

[Paul POULAIN]

Update of /cvsroot/koha/koha/C4
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv7753/C4

Modified Files:
        Biblio.pm 
Log Message:
Ok guys, this time, it seems that item add and modif begin working as 
expected...
Still a lot of bugs to fix, of course

Index: Biblio.pm
===================================================================
RCS file: /cvsroot/koha/koha/C4/Biblio.pm,v
retrieving revision 1.124
retrieving revision 1.125
diff -C2 -r1.124 -r1.125
*** Biblio.pm   10 Aug 2005 10:21:15 -0000      1.124
--- Biblio.pm   11 Aug 2005 09:00:07 -0000      1.125
***************
*** 56,59 ****
--- 56,60 ----
    &MARCfindsubfield
    &MARCfind_frameworkcode
+   &find_biblioitemnumber
    &MARCgettagslib
  
***************
*** 490,553 ****
  sub MARCgetitem {
  
[...1019 lines suppressed...]
! # WHAT DOES IT ??? ==> END of Hitchcock suspens
! #
! # 1st, it does... nothing...
! # Every old API should be there. So if MARC-stuff is not done, the behaviour 
is EXACTLY the same (if there is no added bug, of course). So, if you use 
normal acquisition, you won't find anything new neither on screen or old-DB 
tables ...
! #
! # All old-API functions have been cloned. for example, the "newbiblio" sub, 
now has become :
! # * a "newbiblio" sub, with the same parameters. It just call a sub named 
OLDnewbiblio
! # * a "OLDnewbiblio" sub, which is a copy/paste of the previous newbiblio 
sub. Then, when you want to add the MARC-DB stuff, you can modify the newbiblio 
sub without modifying the OLDnewbiblio one. If we correct a bug in 1.2 in 
newbiblio, we can do the same in main branch by correcting OLDnewbiblio.
! # * The MARC stuff is usually done through a sub named MARCxxx where xxx is 
the same as OLDxxx. For example, newbiblio calls MARCnewbiblio. the MARCxxx 
subs use a MARC::Record as parameter.
! # The last thing to solve was to manage biblios through real MARC import : 
they must populate the old-db, but must populate the MARC-DB too, without 
loosing information (if we go from MARC::Record to old-data then back to 
MARC::Record, we loose A LOT OF ROWS). To do this, there are subs beginning by 
"NEWxxx" : they manage datas with MARC::Record datas. they call OLDxxx sub too 
(to populate old-DB), but MARCxxx subs too, with a complete MARC::Record ;-)
! #
! # In Biblio.pm, there are some subs that permits to build a old-style record 
from a MARC::Record, and the opposite. There is also a sub finding a MARC-bibid 
from a old-biblionumber and the opposite too.
! # Note we have decided with steve that a old-biblio <=> a MARC-Biblio.
! #
--- 2655,2658 ----
  # IMPORTANT NOTE : you need MARC::XML package 
(http://search.cpan.org/~esummers/MARC-XML-0.7/lib/MARC/File/XML.pm), that 
requires a recent version of MARC::Record
  # Updatedatabase stores the iso2709 data in biblioitems.marc field & an xml 
version in biblioitems.marcxml Not sure we will keep it when releasing the 
stable version, but I think it's a good idea to have something readable in sql, 
at least for development stage.
! 
! # tipaul cutted previous commit notes
\ No newline at end of file