[Koha-bugs] [Bug 2076] Resolve differences in DB schema for a new vs. upgraded database

[bugzilla-daemon at pippin.metavore.com]

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2076





------- Comment #12 from drdrulm at yahoo.com  2008-08-21 09:26 -------
This works fairly well for Dev week except for some reason the biblio mapping
has errors. I repaired some easy ones in the 600's but the item ones are
strange and there is no 952 that can be either found, or added. Most of the
remaining data upgraded worked, although the data output was strange during the
scripts running. Output follows:

NOTE : if you change the link between a MARC subfield and a non-MARC field, ask
your administrator to run misc/rebuildnonmarc.pl script.
Tag     Lib     Repeatable      Mandatory       Auth value      Subfields      
Edit    Delete
951     EQUIVALENCE OR CROSS-REFERENCE--GEOGRAPHIC NAME/AREA NAME [OBSOLETE]
[CAN/MARC only]    Yes     No              Subfields       Edit    Delete
[.................952 should be here..............]
955     COPY-LEVEL INFORMATION (RLIN)   Yes     No              Subfields      
Edit    Delete

___________________________________________________________________________

MARC Bibliographic Framework Test
Test    Result
OK      itemnum : the field itemnumber is mapped to a field in tab -1
OK      All item fields are in the same tag and in item tab
Item tag        There is more than 1 MARC tag related to items tab (10) :
952,959,
OK      biblioitems.itemtype defined
OK      homebranch defined
OK      holdingbranch defined
OK      at least 1 item type defined
OK      at least 1 branch defined
OK      biblionumber and biblioitemnumber mapped correctly
OK      no NULL value in frameworkcode
OK      all subfields for each tag are in the same tab (or ignored)
OK      all authority types used in the frameworks are defined
TOTAL   You have 1 error(s) in your MARC configuration. Please fix them before
using Koha




------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.