- Koha-bugs - lists.koha-community.org

[Bug 1000] installer: drop/suppress entries in mysql if re-launching installer script
by bugzilla-daemon＠wilbur.katipo.co.nz 05 Jul '05

05 Jul '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1000 mjr(a)ttllp.co.uk changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From mjr(a)ttllp.co.uk 2005-07-05 20:57 ------- The installer is cautious about deleting data. If you already have koha installed, why not use the upgrader? ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1000] New: installer: drop/suppress entries in mysql if re-launching installer script
by bugzilla-daemon＠wilbur.katipo.co.nz 05 Jul '05

05 Jul '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1000 Summary: installer: drop/suppress entries in mysql if re- launching installer script Product: Koha Version: 2.2.0 Platform: Sun OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: Installation AssignedTo: mjr(a)ttllp.co.uk ReportedBy: henry(a)cmi.univ-mrs.fr QAContact: koha-bugs(a)lists.sourceforge.net the script don't verify if user or database already exists when you re-launch the script.I think it is better if script begin to delete all previous entries? ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 999] Can't add TAG to MARC Structure...
by bugzilla-daemon＠wilbur.katipo.co.nz 30 Jun '05

30 Jun '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=999 henridamien(a)koha-fr.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED OS/Version| |All Resolution| |FIXED ------- Additional Comments From henridamien(a)koha-fr.org 2005-06-30 21:00 ------- Adding input tagfield ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 999] New: Can't add TAG to MARC Structure...
by bugzilla-daemon＠wilbur.katipo.co.nz 30 Jun '05

30 Jun '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=999 Summary: Can't add TAG to MARC Structure... Product: Koha Version: 2.2.0 Platform: PC URL: /cgi-bin/koha/admin/marctagstructure.pl Status: NEW Severity: normal Priority: P2 Component: Parameters AssignedTo: paul.poulain(a)free.fr ReportedBy: henridamien(a)koha-fr.org QAContact: koha-bugs(a)lists.sourceforge.net No Input text for MARC TAG... So It is impossible to input a new tag. ... Will Fix IT ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 998] MARC import fails when no ISBN present in 2.2.2b and 2.2.3
by bugzilla-daemon＠wilbur.katipo.co.nz 30 Jun '05

30 Jun '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=998 koha(a)alinto.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|paul.poulain(a)free.fr |chris(a)katipo.co.nz Component|MARC |Catalogue ------- Additional Comments From koha(a)alinto.com 2005-06-30 18:21 ------- A similar issue with the same ultimate effect had previously appeared as bug #27 from 2002. "Marcimport.pl had a bug that caused it to always use ISBN as the searchfield even if it was not set to anything. Now it fails back on ISSN, LCCN, or marc record control number." ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 998] New: MARC import fails when no ISBN present in 2.2.2b and 2.2.3
by bugzilla-daemon＠wilbur.katipo.co.nz 30 Jun '05

30 Jun '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=998 Summary: MARC import fails when no ISBN present in 2.2.2b and 2.2.3 Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: critical Priority: P2 Component: MARC AssignedTo: paul.poulain(a)free.fr ReportedBy: koha(a)alinto.com QAContact: koha-bugs(a)lists.sourceforge.net MARC import fails when records have no ISBN in Koha 2.2.2b and both an upgraded and fresh install of 2.2.3. The titles for which import failed cannot be found in the breeding farm after the failed import. I do not observe the problem in the LibLime 2.2.1 demo. I have been guessing that no ISBN is the distinguishing factor for import failures that I have had. I do not know certainly that is the problem the failed records have, although, it would be consistent with my results for what fails and what works. ERROR MESSAGE No relevant error messages appear in the log. The only other useful information I have for the problem is this message after import. "MARC acquisition system Import into the reservoir Import results : * 0 imported records * 1 not imported because already in catalog * 0 not imported because already in the reservoir * 0 not imported because they seem not to be in MARC format (or ISBN/ISSN missing) ! * 1 records parsed" This identical message appears whether or not overwrite duplicates is selected in the import form. PREVALENCE Presuming that no ISBN is the source of the problem the following would be entailed. Libraries adopting Koha with collections containing records for books published before 1968 and some years later, as well as other records for material that continues to be published without any ISBN will be unable to import those records into a current version of Koha. Most of the books that ever existed have no ISBNs and never will. Although, libraries adopting Koha should be careful to preserve all their old records with or without ISBNs, especially while bug #997 is still open. TEST FILES My tests for this problem have included records for the following titles downloaded from catalog.loc.gov . I can supply the copies of MARC communications format records if you have difficulty obtaining suitable records for reproducing the problem. Bunge, Mario Augusto. The myth of simplicity; problems of scientific philosophy. Englewood Cliffs, N.J., Prentice-Hall, 1963. Thompson, James Westfall, 1869-1941. Ancient libraries. Berkeley, Calif., University of California press, 1940. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 997] No MARC subfield sequence specification or subfield repeatability
by bugzilla-daemon＠wilbur.katipo.co.nz 30 Jun '05

30 Jun '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=997 koha(a)alinto.com changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|No MARC subfield sequence |No MARC subfield sequence |specification or subfield |specification or subfield |repeatablity |repeatability ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 997] New: No MARC subfield sequence specification or subfield repeatablity
by bugzilla-daemon＠wilbur.katipo.co.nz 27 Jun '05

27 Jun '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=997 Summary: No MARC subfield sequence specification or subfield repeatablity Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: critical Priority: P2 Component: MARC AssignedTo: paul.poulain(a)free.fr ReportedBy: koha(a)alinto.com QAContact: koha-bugs(a)lists.sourceforge.net GENERAL PROBLEM The Koha MARC data model has a design mistake that is more than a mere implementation bug and results in data loss for affected records. The cataloguing forms have no means for subfield sequence to be specified correctly by the cataloguer when the sequence requried by the item to be catalogued differs from the Koha default subfield order. Even when the correct subfield order is imported from an external record, the Koha MARC framework has no means to preserve the order of subfields in data storage when the order differs from the Koha default order. Furthermore, while the cataloguing forms have a means to enter repeated fields, they have no means to enter repeated subfields within the same field when required by the item to be catalogued. This problem would never be seen in very many common and simple cases but it this problem exists in Koha for many fields when the item requires a different data model than Koha uses. This is a terrible problem for intent of MARC records to be shared between systems, where the already corrupt data pool would become corrupted by these records. The problem may be most acute for subject fields where the complete form of the subject field with subdivisions should match the form found on other remote systems to properly locate other items with the same complete subject. Even where externally created records are imported into Koha, such as the former records of an institution prior to adopting Koha, the data will be corrupted and information will be lost. The information conveyed by the subfield sequence is lost for the problematic records. No automated process could recover the lost sequence information for most cases without referencing the original uncorrupted records; or some nonexistent intelligent system actually understanding the meaning of the subfield content and reordering the subfields according to real world knowledge of how they should properly be ordered. PROBLEMATIC EXAMPLES Some examples of the most problematic effects this problem has on the creation and interpretation of records follow. Many other examples may be taken from the same and other fields but these seem especially problematic. 260 ##$aParis :$bGauthier-Villars ;$aChicago :$bUniversity of Chicago Press,$c1955. Multiple publishers cannot be entered using the cataloguing forms. An externally catalogued record imported into Koha would be transformed as 260 ##$aChicago :$aParis :$bGauthier-Villars ;$bUniversity of Chicago Press,$c1955. Note that the place of publication and publisher are not only not adjacent but the correct place of publication would no longer match the correct publisher if reordered from this point. 490 1#$aDepartment of State publication ;$v10846.$aDepartment and Foreign Service series ;$v12128 . Multiple series titles cannot be entered using the cataloging forms. An externally catalogued record imported into Koha would be transformed as 490 1#$aDepartment and Foreign Service series ;$aDepartment of State publication ;$v10846.$v12128 . Note that the series title and volume number are not only not adjacent but the correct series title would no longer match the correct volume if reordered from this point. 505 00$tQuark models /$rJ. Rosner --$tIntroduction to gauge theories of the strong, weak, and electromagnetic interactions /$rC. Quigg --$tDeep inelastic leptognnucleon scattering /$rD.H. Perkins --$tJet phenomena /$rM. Jacob --$tAn accelerator design study /$rR.R. Wilson --$tLectures in accelerator theory /$rM. Month. Formatted contents notes cannot be entered using the cataloguing forms. .An externally catalogued record imported into Koha would be transformed as 505 00$rC. Quigg --$rD.H. Perkins --$rJ. Rosner --$rM. Jacob --$rM. Month.$rR.R. Wilson --$tAn accelerator design study /$tDeep inelastic leptognnucleon scattering /$tIntroduction to gauge theories of the strong, weak, and electromagnetic interactions /$tJet phenomena /$tLectures in accelerator theory /$tQuark models / . Note that the title and statement of responsibility are not only not adjacent but the correct title would no longer match the correct statement of responsibility if reordered from this point. 650 #0$aArchitecture$zIllinois$zChicago$xHistory$vPictorial works. Repeated subject subdivisions cannot be entered using the cataloguing forms. An externally catalogued record imported into Koha would be transformed as 650 #0$aArchitecture$vPictorial works.$xHistory$zChicago$zIllinois . Note that if reordered from this point, an automated system would need to know the subsidiary relationship of Chicago to Illinois for correctly reordering the subfields. SOLUTION APPROACHES It should be obvious why many many cataloguing systems have one free entry text field for all subfields. I the guided data entry approach that Koha uses for cataloguing preferable for its self validating effects. A means to include repeated subfields should be incorporated into the cataloguing forms similar to the means for repeated fields. The subfield to be entered at a particular point in the subfield list should be alterable from a drop down selection list for those fields that may have a variant subfield sequence and those records that may not have a varient subfield. The actual coded values for the subfield should have the position of that subfield in the sequence of subfields for that selection list for maintaining the subfield sequence in the Koha database. No implementation should prevent the use of a recommended or required value list or thesaurus for the subfield contents. If the page needs to be rewritten when the cataloguer alters the default subfield se sequence of subfields to accomidate a value list or thesaurus in the cataloguing form corresponding to the altered subfield sequence, then the page needs to be rewritten. The default cataloguing subfield sequence should provide for the most usually correct subfield order as a default that corresponds to the different usage of different fields. A parallel data structure to the existing data structure can be introduced to preserve the subfield sequence if there is no easy means to augment the existing data structure with subfield sequence information. At least newly catalogued and newly imported or reimported records from an uncorrupted source should have their subfield sequence preserved in the data structure after a suitable implementation is developed to correct this problem. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 996] Can't delete a biblio - javascript error
by bugzilla-daemon＠wilbur.katipo.co.nz 27 Jun '05

27 Jun '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=996 ------- Additional Comments From rachel(a)katipo.co.nz 2005-06-27 13:18 ------- Ah no it doesn't OK It doesn't work unless you're in MARC View - if you're in normal view then it doesn't work ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 996] Can't delete a biblio - javascript error
by bugzilla-daemon＠wilbur.katipo.co.nz 27 Jun '05

27 Jun '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=996 ------- Additional Comments From rachel(a)katipo.co.nz 2005-06-27 13:06 ------- hmm and now it does work ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0