|
From: |
Unknown |
regards
Serge
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
From Stephen >>>>
Paul, you are correct, most of these problems (I now get 88) are duplicate
barcodes from the old system. (A few are new staff errors that have resulted
in duplicate barcodes.)
These all seem to have two entries in the marc_subfield_table, with two
separate bibid numbers, and only one entry in the items table.
My first thought is to delete all of these from the catalog and start over.
(We'll still need to delete from the MARC tables manually in mysql, but in this
case that would be a good idea.)
Here's the question -- will that fix the problem? Remember that we first
noticed this when trying to edit new items, and our edits were attached to
records in the items table that had completely different barcode numbers.
(Most of these duplicate barcodes are only off by a digit or two.) And the
barcodes we had the problem with are not in the list of duplicates. So are we
looking at two separate problems? How would these duplicate barcodes affect
editing a newly entered barcode that is not a duplicate? Can you come up with
a logical explanation? (Good luck!)
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
From Stephen again >>>
Owen and I did some testing of the item editing problem I reported (bug 599)
using the default templates, with inconsistent results. We were able to
reproduce the error sometimes, but not every time. So now, I think it would be
valuable to take a closer look at what actually happened when we first noticed
the error to see if this is a database problem or a code problem.
First, remember that the problem started when staff had added an item to an
existing biblio record without a barcode, and then edited that item to add the
barcode. The barcode was 31000000109284. After the edit, this barcode
appeared correctly when searching the MARC database (bibid 130229), but was
attached to the wrong biblio (number 37717) in the old Koha DB. (At this point
in the database, the bibid and the biblionumber are the same.)
So here's the bibid/biblionumber 37717 from the MARC database:
mysql> select * from marc_subfield_table where bibid=37717;
29 rows in set (0.02 sec)
And here's bibid/biblionumber 37717 from the items table:
mysql> select * from items where biblionumber=37717;
3 rows in set (0.00 sec)
Notice that it look like the edited barcode (31000000109284) replaced barcode
37000000025523 that appears in the MARC record. But also notice that the MARC
record has an accession date (tag 952v) attached to barcode 37000000025523 that
is actually the date when the edit to barcode 31000000109284 was done! It
should actually have no accession date, because no date was in the imported
MARC record loaded on September 1.
So what happened to barcode 37000000025523 in the old Koha DB?:
mysql> select * from items where barcode='37000000025523';
Empty set (0.00 sec)
It's gone, been replaced by the edited barcode number.
Here's the edited barcode number in the MARC table:
mysql> select * from marc_subfield_table where subfieldvalue='31000000109284';
1 row in set (0.02 sec)
mysql> select * from marc_subfield_table where bibid=130229;
31 rows in set (0.03 sec)
So what happened here? It looks like the editing process saved the barcode to
the correct item ('A') in the MARC table, but also saved the accession date to
an item ('B') attached to a completely different bibid in the MARC table. And
it also looks like the barcode and date for item A overwrote the information
for item B stored in the old Koha DB. So if that is what happened, why did it
happen? (Does the tag and subfield order in bibid 130229 look odd to you?)
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
From Roger Horne by email:
I suggest a very simple change to the installer: put the MySQL
Password into a loop. Does anyone remember all their passwords? Entering the
wrong one in this field and finding the installer dies is a bit annoying
(since many files will have been installed, which tends to cause
difficulties with the next attempt). Adding "Wrong, try again" would make
things much easier.
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
From an email to koha-devel by Chris Michalak:
the bug is in OLDnewbiblio in Biblio.pm at line 1459 (version 2.0.0pre5)
To fix, replace :
$sth->execute($bibnum,$biblio->{'title'},$biblio->{'author'},$biblio->{'copyright'},$series,$biblio->{'seriestitle'},$biblio->{'notes'},$biblio->{'abstract'});
with :
$sth->execute($bibnum,$biblio->{'title'},$biblio->{'author'},$biblio->{'copyrightdate'},$series,$biblio->{'seriestitle'},$biblio->{'notes'},$biblio->{'abstract'});
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
From koha-devel on 12 Dec:
> Have I set something up wrong, or does the breeding farm only match on
> the first given ISBN? Is that fixable?
yes, you're right.
Should be fixable by duplicating an entry when we have more than 1 ISBN.
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
From Ph. Revault:
2- I confirm that all datas from the biblio and bibliotitem tables are not
exported (in test with my personal datas at least) . As i said in my previous
message, datas like additional authors, subject, subtitle, date, etc. are not.
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
From the add biblio link in the middle of the homepage.
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
| [Prev in Thread] |
Current Thread |
[Next in Thread] |