At 08:09 PM 10/29/2012 +0100, you wrote:
Hi Paul,
the fields in biblio, biblioitems and items are connected to MARC fields
by the Koha-to-MARC-Mappings in the administration area. Have you checked
if someone changed the mapping for your author fields? Also the mappings
are 1:1, so say someone tried mapping 700, 100 would no longer be used.
Hi Katrin,
Thanks for the reply. "Author" is mapped to 100$a, no change from
previously. But, respectfully, the point of my email was a bit different:
it appears maybe that we have a "?corrupt?" MySQL db since 3.8.5 which
might explain all my woes with authorities, and I don't want to have to do
hundreds of INSERT ... INTO ... WHERE ... manually.
The SQL structure itself appears to have changed. Here's a well snipped
output of 'mysql> SELECT biblionumber, datecreated, biblio.author FROM
biblio ORDER BY datecreated ASC;' :
| 256 | 2011-03-10 | Arundel,
Louis |
512 | 2011-03-10 | Barris,
Ted |
768 | 2011-03-10 | Berton, Pierre
/ ... /
| 18030 | 2012-09-22 | Heyerdahl,
Thor | 18031
| 2012-09-23 | Cook,
Graeme |
18032 | 2012-09-23 | Lubbock, Alfred Basil
#
# 3.8.5 upgrade this date
#
| 18033 | 2012-09-24 |
NULL
| 18034 | 2012-09-24 |
NULL
| 18035 | 2012-09-24 | NULL
/ ... /
| 18363 | 2012-10-29 |
NULL
| 18364 | 2012-10-29 |
NULL
| 18365 | 2012-10-29 | NULL
So it's pretty clear that 100$a is NOT being "put into the right place" in
MySQL since the 3.8.5 upgrade. It's being stored somewhere, perhaps in an
XML format, because if I run a Koha /tools/export.pl (and I haven't looked
to see if this queries XML or not) for e.g. the last biblionumber above I
get a proper 100$a:
=LDR 01432nam a2200313 a 4500
=001 1906853
=003 DLC
=005 20121029154904.0
=008 850207s1984\\\\onca\\\\\b\\\\000\0\eng\\
=010 \\$a 84199029
=020 \\$a0660115530 :$c{dollar}5.25 ({dollar}6.30 other countries)
=040 \\$aDLC$cOPIACS$dDLC$beng
=041 1\$aengfre
=043 \\$an-cn-qu$an-cn-on
=050 00$aHE401.O88$bL3413 1984
=082 00$a386/.48/097138$219
=100 1\$aLafreniere, Normand.$93870
=240 10$aReseau de canalisation de la riviere des Outaouais.$lEnglish
=245 14$aThe Ottawa River canal system /$cNormand Lafreniere.
=260 \\$a[Ottawa] :$bNational Historic Parks and Sites Branch, Parks
Canada, Environment Canada ;$aHull, Quebec, Canada :$bCanadian Govt. Pub.
Centre, Supply and Services Canada [distributor],$c1984.
=300 \\$a95 p. :$bill. ;$c23 cm.$3pb
=440 \0$aStudies in archaeology, architecture, and history,$x0821-1027$917623
=500 \\$aTranslation of: Le reseau de canalisation de la riviere des
Outaouais.
=504 \\$aBibliography: p. 87-95.
=520 \\$aOttawa Valley, canal system
=650 \0$aCanals$zOttawa River (Quand Ont.)$xHistory.$917624
=942 \\$2z$cBK
=999 \\$c18365$d18365
=952
\\$w2012-10-29$p1GRLK12100005$r2012-10-29$4-2$ehhalliday$00$6GRLKLAFR2$918905$10$oGRLK-LAFR-2$d2012-10-16$zOttawa
Valley, canals$8great_lak$50$71$cgreat_lak $2z$g12.00$yBK$iOttawa Valley,
canals$xg pb
For your reports you always have the option to query the MARCXML data
directly, nothing should be lost.
I agree -- in fact for staff, I've already written a new report replacing
biblio.author with
ExtractValue(marcxml,'//datafield[@tag="100"]/subfield[@code>="a"]') and it
works perfectly.
But this doesn't "correct" the MySQL db. Where/why on earth has it gone
wrong, and how to correct it? Does this affact 'authorities'?
Thanks and regards -- Paul
Hope that helps,
Katrin
-----Ursprüngliche Nachricht-----
Von: koha-devel-boun...@lists.koha-community.org im Auftrag von Paul
Gesendet: Mo 29.10.2012 19:55
An: koha-devel@lists.koha-community.org
Betreff: [Koha-devel] Losing biblio.author in 3.8.5
We have a [rather important, it's for donors' tax receipts] report that
includes:
SELECT
items.barcode AS Barcode,items.dateaccessioned AS 'Acc Date',
biblio.title AS Title, biblio.author AS Author,biblioitems.publishercode AS
Publisher,biblioitems.publicationyear AS Year,
biblioitems.editionstatement AS Edition,
items.price as FMV, etc etc etc
It worked perfectly from 3.6.1 up to and including 3.8.4
Since we upgraded to 3.8.5 (24 Sep, to fix bug 8520), something has changed
-- biblio.author systematically comes up empty (all 245$a fields are
present) while *all* the other field are perfect. (added later: just
checked some other reports that use biblio.author -- same result, other
fields are good, author fails.)
I've looked around release notes and bugs without finding anything
relevant, and am now at a loss as to what I should look for.
Any suggestions warmly accepted.
Thanks and regards,
Paul
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
---
Maritime heritage and history, preservation and conservation,
research and education through the written word and the arts.
<http://NavalMarineArchive.com> and <http://UltraMarine.ca>
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
