Hi Demian,
I didn't try your upgrade in the 1.3 trunk but used the solrmarc 2.4 vufind binary directly from http://code.google.com/p/solrmarc/downloads/list
After indexing I seems like the case sensitivity while reading the subfield-tags was lost.
MarcEdit Marc21:
=689 01$Af$2gnd$aKongress
1. Vufind FullRecord (v2.3.1):
689 01 |A f |2 gnd |a Kongress
2. Vufind FullRecord (v2.4):
689 01 |a f |2 gnd |a Kongress
marc.properties properties parses this Field using "topic_facet = 689a"
The result is, that in the second case I get the $A subfield with the value "f" als topic_facet.
Can anybody confirm this for his/her index? I suppose uppercase subfields like $A or $D is used mainly in germany.
Best wishes
Stefan
--
Stefan Winkler
Bibliotheksservice-Zentrum Baden-Württemberg (BSZ)
78457 Konstanz / Germany
Phone: +49 7531 88 2364
E-Mail: stefan....@bsz-bw.de
Von: Demian Katz [mailto:demia...@villanova.edu]
Gesendet: Mittwoch, 26. September 2012 19:11
An: vufin...@lists.sourceforge.net
Betreff: [VuFind-Tech] SolrMarc 2.4 upgrade
I have just upgraded both the VuFind 1.x trunk and the VuFind 2.x master branch to use SolrMarc 2.4, the latest release. (VuFind 1.x was previously on 2.3.1,
while 2.x was previously using a custom-built version very close to 2.4). Hopefully this will make Monday's 2.0beta release just a little bit easier to manage thanks to the inclusion of a known SolrMarc version. It also allows me to close a couple of JIRA
tickets related to fixes/improvements in 2.4.
I don't anticipate any problems related to this upgrade, but please let me know if you run into any indexing troubles using the latest-and-greatest code.
thanks,
Demian
Hm, strange. In the first case he swallowed the 'A' totally.
Could be that the solrmarc version of the first case was even older than 2.3.1 ? I think it was vufind 1.2 when I got this correct interpretation of upper cases:
http://solrtest.bsz-bw.de/vufind/Record/DE-208000000132/Details#tabnav
Yes, please pass it to solrmarc-tech.
Stefan
--
Stefan Winkler
Bibliotheksservice-Zentrum Baden-Württemberg (BSZ)
78457 Konstanz / Germany
Phone: +49 7531 88 2364
E-Mail: stefan....@bsz-bw.de
Von: Demian Katz [mailto:demia...@villanova.edu]
Gesendet: Freitag, 28. September 2012 13:36
An: Winkler, Stefan
Betreff: RE: SolrMarc 2.4 - subfield-tag case insensitivity change?
I am definitely seeing differences between 2.3.1 and 2.4, but I don't think they're the same differences you are seeing:
2.3.1:
|
689 |
0 |
0 |
|d s |0 (DE-588)4056637-7 |0 (DE-576)209118407 |2 gnd |a Staatsbankrott |
|
689 |
0 |
1 |
|
|f |2 gnd |a Kongress |
|
689 |
0 |
2 |
|g |2 gnd |a Wien <2010> |
2.4:
|
689 |
0 |
0 |
|d s |0 (DE-588)4056637-7 |0 (DE-576)209118407 |2 gnd |a Staatsbankrott |
|
689 |
0 |
1 |
|
|a f |2 gnd |a Kongress |
|
689 |
0 |
2 |
|a g |2 gnd |a Wien <2010> |
I'm not seeing uppercase subfields in either case... but the older code seems to be consuming the uppercase subfield marker and treating the value of the field as the subfield marker... while the newer code is just lowercasing it. So in my environment, 2.4
seems slightly more accurate than 2.3.1 even though not completely correct.
Would you like me to pass along your test record to solrmarc-tech?
- Demian
From: Winkler, Stefan [stefan....@bsz-bw.de]
Sent: Friday, September 28, 2012 7:16 AM
To: Demian Katz
Subject: AW: SolrMarc 2.4 - subfield-tag case insensitivity change?
Hi Demian,
thanks for forwarding the mail.
Here is the testrecord