You can subscribe to this list here.
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(44) |
Aug
(143) |
Sep
(50) |
Oct
(46) |
Nov
(94) |
Dec
(106) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2008 |
Jan
(118) |
Feb
(77) |
Mar
(163) |
Apr
(203) |
May
(74) |
Jun
(90) |
Jul
(111) |
Aug
(23) |
Sep
(99) |
Oct
(46) |
Nov
(42) |
Dec
(38) |
| 2009 |
Jan
(55) |
Feb
(36) |
Mar
(60) |
Apr
(20) |
May
(75) |
Jun
(102) |
Jul
(117) |
Aug
(104) |
Sep
(188) |
Oct
(105) |
Nov
(45) |
Dec
(59) |
| 2010 |
Jan
(88) |
Feb
(147) |
Mar
(53) |
Apr
(54) |
May
(74) |
Jun
(76) |
Jul
(78) |
Aug
(99) |
Sep
(87) |
Oct
(133) |
Nov
(56) |
Dec
(61) |
| 2011 |
Jan
(61) |
Feb
(22) |
Mar
(57) |
Apr
(79) |
May
(128) |
Jun
(143) |
Jul
(64) |
Aug
(90) |
Sep
(90) |
Oct
(202) |
Nov
(91) |
Dec
(127) |
| 2012 |
Jan
(92) |
Feb
(122) |
Mar
(221) |
Apr
(248) |
May
(244) |
Jun
(228) |
Jul
(213) |
Aug
(189) |
Sep
(125) |
Oct
(140) |
Nov
(137) |
Dec
(65) |
| 2013 |
Jan
(124) |
Feb
(160) |
Mar
(168) |
Apr
(276) |
May
(154) |
Jun
(106) |
Jul
(117) |
Aug
(124) |
Sep
(113) |
Oct
(95) |
Nov
(19) |
Dec
(43) |
| 2014 |
Jan
(93) |
Feb
(39) |
Mar
(103) |
Apr
(99) |
May
(66) |
Jun
(78) |
Jul
(98) |
Aug
(32) |
Sep
(69) |
Oct
(71) |
Nov
(60) |
Dec
(64) |
| 2015 |
Jan
(32) |
Feb
(24) |
Mar
(36) |
Apr
(47) |
May
(86) |
Jun
(53) |
Jul
(65) |
Aug
(95) |
Sep
(67) |
Oct
(87) |
Nov
(37) |
Dec
(59) |
| 2016 |
Jan
(86) |
Feb
(80) |
Mar
(47) |
Apr
(74) |
May
(47) |
Jun
(87) |
Jul
(84) |
Aug
(72) |
Sep
(49) |
Oct
(43) |
Nov
(65) |
Dec
(40) |
| 2017 |
Jan
(32) |
Feb
(31) |
Mar
(52) |
Apr
(51) |
May
(48) |
Jun
(35) |
Jul
(51) |
Aug
(28) |
Sep
(54) |
Oct
(44) |
Nov
(48) |
Dec
(19) |
| 2018 |
Jan
(41) |
Feb
(34) |
Mar
(30) |
Apr
(64) |
May
(53) |
Jun
(49) |
Jul
(49) |
Aug
(36) |
Sep
(44) |
Oct
(34) |
Nov
(50) |
Dec
(16) |
| 2019 |
Jan
(40) |
Feb
(21) |
Mar
(28) |
Apr
(19) |
May
(32) |
Jun
(26) |
Jul
(11) |
Aug
(39) |
Sep
(41) |
Oct
(79) |
Nov
(42) |
Dec
(31) |
| 2020 |
Jan
(19) |
Feb
(37) |
Mar
(17) |
Apr
(9) |
May
(10) |
Jun
(14) |
Jul
(52) |
Aug
(41) |
Sep
(38) |
Oct
(24) |
Nov
(9) |
Dec
(13) |
| 2021 |
Jan
(29) |
Feb
(12) |
Mar
(21) |
Apr
(19) |
May
(28) |
Jun
(21) |
Jul
(26) |
Aug
(31) |
Sep
(26) |
Oct
(84) |
Nov
(18) |
Dec
(7) |
| 2022 |
Jan
(25) |
Feb
(11) |
Mar
(35) |
Apr
(25) |
May
(17) |
Jun
(7) |
Jul
(7) |
Aug
(22) |
Sep
(17) |
Oct
(40) |
Nov
(19) |
Dec
(27) |
| 2023 |
Jan
(14) |
Feb
(21) |
Mar
(60) |
Apr
(16) |
May
(26) |
Jun
(18) |
Jul
(14) |
Aug
(19) |
Sep
(13) |
Oct
(19) |
Nov
(23) |
Dec
(13) |
| 2024 |
Jan
(14) |
Feb
(25) |
Mar
(42) |
Apr
(31) |
May
(20) |
Jun
(17) |
Jul
(12) |
Aug
(49) |
Sep
(8) |
Oct
(23) |
Nov
(36) |
Dec
(13) |
| 2025 |
Jan
(35) |
Feb
(27) |
Mar
(56) |
Apr
(20) |
May
(15) |
Jun
(21) |
Jul
(20) |
Aug
(12) |
Sep
(14) |
Oct
(5) |
Nov
(4) |
Dec
(7) |
| 2026 |
Jan
(7) |
Feb
(6) |
Mar
(22) |
Apr
(9) |
May
(2) |
Jun
(6) |
Jul
(7) |
Aug
(4) |
Sep
(9) |
Oct
(3) |
Nov
(2) |
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
|
1
|
2
|
3
|
4
|
|
5
|
6
|
7
|
8
(2) |
9
(3) |
10
|
11
|
|
12
|
13
|
14
|
15
|
16
|
17
|
18
|
|
19
|
20
|
21
|
22
|
23
(2) |
24
|
25
|
|
26
|
27
(1) |
28
(1) |
29
|
30
|
|
|
|
From: Demian K. <dem...@vi...> - 2026-04-28 13:08:09
|
Hello, everyone! The April, 2026 VuFind® newsletter is now available: https://vufind.org/wiki/community:newsletter:2026-04 Additionally, the next Community Call will be held on Tuesday, May 5, 2026 at 9am Eastern Daylight Time (13:00 GMT). Here is the full agenda: 1. Development Planning * Newsletter Highlights * Follow-Up to Past Discussions i. Solr 9.10 Upgrade ii. Laminas MVC End of Life iii. Improving Abstract Factories iv. Dark Mode PR v. Extension Module Skeleton / Best Practices vi. Cooke Consent * Release 11.0.3 * FontAwesome 7 * FOLIO Checkout Sorting * 11.1.0 Scope Finalization and Release Date * 12.0.0 Pull Request and JIRA Ticket Highlights i. Solr JSON Facet API ii. GVI Support 1. Accessibility SIG 2. Open Q&A / Other Topics? All are welcome to join the free online call, or to suggest additional agenda items. You can find information on joining here: https://vufind.org/wiki/community_call See you next week! - Demian |
|
From: Demian K. <dem...@vi...> - 2026-04-27 13:18:09
|
Hello, everyone! VuFind® 11.0.3 has been released today. This patch release fixes another batch of minor bugs, most visibly an issue that prevented search results from being visibly numbered in certain configurations. You can download the new release here: https://vufind.org/vufind/downloads.html As always, please let me know if you have any questions, concerns or problems! - Demian |
|
From: Mark T. <ma...@te...> - 2026-04-23 23:52:33
|
Hi Peter,
Yeah, that does seem like it should be fine. For what it's
worth, I tried loading your single record into an otherwise
empty Solr instance and I'm not seeing the same duplicates:
# curl -s 'http://localhost:8983/solr/biblio/browse?source=topic&rows=100' | jq '.. | .heading? // empty'
"Cat adoption Fiction."
"Cat adoption Juvenile fiction."
"Cats Fiction."
"Cats Juvenile fiction."
"Haiku."
"Haiku Juvenile fiction."
If it helps, here's a (horrible) command for just invoking
the bit of the browse indexing that pulls the values from a
specific Solr field (with `cat -vet` just to show the
multibyte spaces):
# export CLASSPATH="/usr/local/vufind/import/browse-indexing.jar:/usr/local/vufind/solr/vendor/server/solr-webapp/webapp/WEB-INF/lib/*:/usr/local/vufind/solr/vendor/modules/analysis-extras/lib/*"
# java -cp "$CLASSPATH" \
org.vufind.solr.indexing.PrintBrowseHeadings \
/usr/local/vufind/solr/vufind/biblio/index/ \
'topic_browse' \
/dev/stdout \
| cut -d$'\1' -f3 \
| tr -d '\r' | while read s; do \
echo "$s" | base64 -d; echo; \
done | cat -vet
Which with my single-record Solr index gives me:
Cat adoptionM-bM-^@M-^BFiction.$
Cat adoptionM-bM-^@M-^BJuvenile fiction.$
CatsM-bM-^@M-^BFiction.$
CatsM-bM-^@M-^BJuvenile fiction.$
Haiku.$
HaikuM-bM-^@M-^BJuvenile fiction.$
Mark
Peter Murray <pe...@in...> writes:
> Hey Mark. I'm running close to the stock `index-alphabetic-browse.sh` — we're running multiple VuFinds on the same server in places, so it has modifications for a unique temp-space path and it is using your suggested modifications to get the biblio index directory. The core of the script is the same, though, including
>
> build_browse "topic" "topic_browse" 0 "-Dbrowse.normalizer=org.vufind.util.TopicNormalizer"
>
> ...and the "build_browse" shell function.
>
>
> Peter
>
> On Thu, Apr 9, 2026 at 7:21 PM Mark Triggs <ma...@te...> wrote:
>
>
> Hi Peter,
>
> Are you running the stock index-alphabetic-browse.sh too? For the topic browse it has:
>
> build_browse "topic" "topic_browse" 0 "-Dbrowse.normalizer=org.vufind.util.TopicNormalizer"
>
> Which defines the "topic" browse to be populated from the "topic_browse" Solr field.
>
> Mark
>
> Peter Murray <pe...@in...> writes:
>
> Demain: The record is an attached XML file on my original email (https://sourceforge.net/p/vufind/mailman/message/59319398/ has it in the archive).
>
> Mark: I think that is the exact crux of the issue — where are the non-en-space variants coming from... On a whim, I used the same separator for the `topic` field, and the problem seems to have gone away:
>
> ```
> topic = custom, getAllAlphaSubfieldsUTF8Delimited(600:610:611:630:650:653:656:690, "\u2002") topic_browse = custom, getAllAlphaSubfieldsUTF8Delimited(600:610:611:630:650:653:656:690, "\u2002")
>
> ```
>
> (Note that these lines are adding the 690 field at the library's request.) So it seems like the variants were coming from the `topic` rule...but I verfied that there is no <copyField> from `topic` to `topic_browse` in the Solr schema.xml file. (There is a <copyField source="topic" dest="spellingShingle"/> and a <copyField source="topic" dest="topic_unstemmed"/> that comes from the VuFind source but that shouldn't have any impact.)
>
> Peter
--
Mark Triggs
<ma...@te...>
https://teaspoon-consulting.com/
|
|
From: Peter M. <pe...@in...> - 2026-04-23 15:49:29
|
Hey Mark. I'm running close to the stock `index-alphabetic-browse.sh` — we're running multiple VuFinds on the same server in places, so it has modifications for a unique temp-space path and it is using your suggested modifications <https://tsp.nz/d/41a23d1b42cc54aca3b879e6c790c55204b06f83.txt> to get the biblio index directory. The core of the script is the same, though, including build_browse "topic" "topic_browse" 0 "-Dbrowse.normalizer=org.vufind.util.TopicNormalizer" ...and the "build_browse" shell function. Peter On Thu, Apr 9, 2026 at 7:21 PM Mark Triggs <ma...@te...> wrote: > Hi Peter, > > Are you running the stock index-alphabetic-browse.sh too? For the topic > browse it has: > > build_browse "topic" "topic_browse" 0 "-Dbrowse.normalizer=org.vufind.util.TopicNormalizer" > > Which defines the "topic" browse to be populated from the "topic_browse" > Solr field. > > Mark > > Peter Murray <pe...@in...> writes: > > Demain: The record is an attached XML file on my original email ( > https://sourceforge.net/p/vufind/mailman/message/59319398/ has it in the > archive). > > Mark: I think that is the exact crux of the issue — where are the > non-en-space variants coming from... On a whim, I used the same separator > for the `topic` field, and the problem seems to have gone away: > > ``` > topic = custom, > getAllAlphaSubfieldsUTF8Delimited(600:610:611:630:650:653:656:690, > "\u2002") topic_browse = custom, > getAllAlphaSubfieldsUTF8Delimited(600:610:611:630:650:653:656:690, "\u2002") > > ``` > > (Note that these lines are adding the 690 field at the library's request.) > So it seems like the variants were coming from the `topic` rule...but I > verfied that there is no <copyField> from `topic` to `topic_browse` in the > Solr schema.xml file. (There is a <copyField source="topic" > dest="spellingShingle"/> and a <copyField source="topic" > dest="topic_unstemmed"/> that comes from the VuFind source but that > shouldn't have any impact.) > > Peter > > -- > Mark Triggs > <ma...@te...>https://teaspoon-consulting.com/ > > -- Peter Murray Open Source Community Advocate Index Data, LLC |
|
From: Mark T. <ma...@te...> - 2026-04-09 23:21:30
|
Hi Peter,
Are you running the stock index-alphabetic-browse.sh too?
For the topic browse it has:
build_browse "topic" "topic_browse" 0 "-Dbrowse.normalizer=org.vufind.util.TopicNormalizer"
Which defines the "topic" browse to be populated from the
"topic_browse" Solr field.
Mark
Peter Murray <pe...@in...> writes:
> Demain: The record is an attached XML file on my original email (https://sourceforge.net/p/vufind/mailman/message/59319398/ has it in the archive).
>
> Mark: I think that is the exact crux of the issue — where are the non-en-space variants coming from... On a whim, I used the same separator for the `topic` field, and the problem seems to have gone away:
>
> ```
> topic = custom, getAllAlphaSubfieldsUTF8Delimited(600:610:611:630:650:653:656:690, "\u2002")
> topic_browse = custom, getAllAlphaSubfieldsUTF8Delimited(600:610:611:630:650:653:656:690, "\u2002")
>
> ```
>
> (Note that these lines are adding the 690 field at the library's request.) So it seems like the variants were coming from the `topic` rule...but I verfied that there is no <copyField> from `topic` to `topic_browse` in the Solr schema.xml file. (There is a <copyField source="topic" dest="spellingShingle"/> and a <copyField source="topic" dest="topic_unstemmed"/> that comes from the VuFind source but that shouldn't have any impact.)
>
> Peter
--
Mark Triggs
<ma...@te...>
https://teaspoon-consulting.com/
|
|
From: Peter M. <pe...@in...> - 2026-04-09 21:54:20
|
Demain: The record is an attached XML file on my original email (https://sourceforge.net/p/vufind/mailman/message/59319398/ has it in the archive). Mark: I think that is the exact crux of the issue — where are the non-en-space variants coming from... On a whim, I used the same separator for the `topic` field, and the problem seems to have gone away: ``` topic = custom, getAllAlphaSubfieldsUTF8Delimited(600:610:611:630:650:653:656:690, "\u2002") topic_browse = custom, getAllAlphaSubfieldsUTF8Delimited(600:610:611:630:650:653:656:690, "\u2002") ``` (Note that these lines are adding the 690 field at the library's request.) So it seems like the variants were coming from the `topic` rule...but I verfied that there is no <copyField> from `topic` to `topic_browse` in the Solr schema.xml file. (There is a <copyField source="topic" dest="spellingShingle"/> and a <copyField source="topic" dest="topic_unstemmed"/> that comes from the VuFind source but that shouldn't have any impact.) Peter -- Peter Murray Open Source Community Advocate Index Data, LLC |
|
From: Demian K. <dem...@vi...> - 2026-04-09 11:18:30
|
Peter,
Could you share the source record that led to this result? Have you tried indexing this record into a totally clean installation to see if you get the same result, or if it might somehow be related to a customization? I’m happy to try that experiment next week when I get back from my conference, but I’m a bit tied up for the rest of this week.
- Demian
From: Peter Murray <pe...@in...>
Sent: Wednesday, April 8, 2026 3:15 PM
To: VuFind-General <vuf...@li...>
Subject: [EXTERNAL] [VuFind-General] Duplicate values for Solr `topic_browse` field
I have a site with VuFind 11.0.1, and I'm seeing issues with duplicate values in the `topic_browse` field of the Solr document. I've attached the XML of the record to the email. It has six MARC 650 fields. The Solr document has six `topic` fields but 11 `topic_browse` fields, and this is showing up in the AlphaBrowse display as duplicate entries — entries where the headings run together ("Cat adoption Fiction") and entries where the headings are separated by double dashes ("Cat adoption -- Fiction"). Here is the output from Solr:
<?xml version="1.0" encoding="UTF-8"?>
<response>
<lst name="responseHeader">
<int name="status">0</int>
<int name="QTime">0</int>
<lst name="params">
<str name="q">id:b2074646</str>
<str name="indent">true</str>
<str name="fl">id,topic,topic_browse</str>
<str name="q.op">OR</str>
<str name="rows">10</str>
<str name="wt">xml</str>
<str name="useParams"/>
<str name="_">1775667544232</str>
</lst>
</lst>
<result name="response" numFound="1" start="0" numFoundExact="true">
<doc>
<str name="id">b2074646</str>
<arr name="topic">
<str>Cats Juvenile fiction.</str>
<str>Cat adoption Juvenile fiction.</str>
<str>Haiku Juvenile fiction.</str>
<str>Cat adoption Fiction.</str>
<str>Cats Fiction.</str>
<str>Haiku.</str>
</arr>
<arr name="topic_browse">
<str>Cat adoption Fiction.</str>
<str>Cat adoption Juvenile fiction.</str>
<str>Cat adoption Fiction.</str>
<str>Cat adoption Juvenile fiction.</str>
<str>Cats Fiction.</str>
<str>Cats Juvenile fiction.</str>
<str>Cats Fiction.</str>
<str>Cats Juvenile fiction.</str>
<str>Haiku Juvenile fiction.</str>
<str>Haiku.</str>
<str>Haiku Juvenile fiction.</str>
</arr></doc>
</result>
</response>
No matter what I do in the `marc_local.properties` file, I always get 11 values. I've tried deleting the record between imports to make sure there is a fresh import each time.
Has anyone seen something like this before?
Peter
--
Peter Murray
Open Source Community Advocate
Index Data, LLC
|
|
From: Mark T. <ma...@te...> - 2026-04-08 23:11:21
|
Hi Peter,
I notice in your Solr response some of those spaces are
actually en-space characters. If I hex encode some of
them it's more obvious:
<str>Cat%20adoption%20Fiction.</str>
<str>Cat%20adoption%20Juvenile%20fiction.</str>
<str>Cat%20adoption%E2%80%82Fiction.</str>
<str>Cat%20adoption%E2%80%82Juvenile%20fiction.</str>
It looks like that's the separator that marc.properties is
using (\u2002):
https://github.com/vufind-org/vufind/blob/dev/import/marc.properties#L96
So I guess the question is where the non-en-space variants
are coming from...
Cheers,
Mark
Peter Murray <pe...@in...> writes:
> I have a site with VuFind 11.0.1, and I'm seeing issues with duplicate values in the `topic_browse`
> field of the Solr document. I've attached the XML of the record to the email. It has six MARC 650
> fields. The Solr document has six `topic` fields but 11 `topic_browse` fields, and this is showing
> up in the AlphaBrowse display as duplicate entries — entries where the headings run together ("Cat
> adoption Fiction") and entries where the headings are separated by double dashes ("Cat adoption --
> Fiction"). Here is the output from Solr:
>
>
> <?xml version="1.0" encoding="UTF-8"?>
> <response>
>
> <lst name="responseHeader">
> <int name="status">0</int>
> <int name="QTime">0</int>
> <lst name="params">
> <str name="q">id:b2074646</str>
> <str name="indent">true</str>
> <str name="fl">id,topic,topic_browse</str>
> <str name="q.op">OR</str>
> <str name="rows">10</str>
> <str name="wt">xml</str>
> <str name="useParams"/>
> <str name="_">1775667544232</str>
> </lst>
> </lst>
> <result name="response" numFound="1" start="0" numFoundExact="true">
> <doc>
> <str name="id">b2074646</str>
> <arr name="topic">
> <str>Cats Juvenile fiction.</str>
> <str>Cat adoption Juvenile fiction.</str>
> <str>Haiku Juvenile fiction.</str>
> <str>Cat adoption Fiction.</str>
> <str>Cats Fiction.</str>
> <str>Haiku.</str>
> </arr>
> <arr name="topic_browse">
> <str>Cat adoption Fiction.</str>
> <str>Cat adoption Juvenile fiction.</str>
> <str>Cat adoption Fiction.</str>
> <str>Cat adoption Juvenile fiction.</str>
> <str>Cats Fiction.</str>
> <str>Cats Juvenile fiction.</str>
> <str>Cats Fiction.</str>
> <str>Cats Juvenile fiction.</str>
> <str>Haiku Juvenile fiction.</str>
> <str>Haiku.</str>
> <str>Haiku Juvenile fiction.</str>
> </arr></doc>
> </result>
> </response>
>
>
> No matter what I do in the `marc_local.properties` file, I always get 11 values. I've tried
> deleting the record between imports to make sure there is a fresh import each time.
>
> Has anyone seen something like this before?
>
>
> Peter
--
Mark Triggs
<ma...@te...>
https://teaspoon-consulting.com/
|
|
From: Peter M. <pe...@in...> - 2026-04-08 19:45:02
|
I have a site with VuFind 11.0.1, and I'm seeing issues with duplicate
values in the `topic_browse` field of the Solr document. I've attached the
XML of the record to the email. It has six MARC 650 fields. The Solr
document has six `topic` fields but 11 `topic_browse` fields, and this is
showing up in the AlphaBrowse display as duplicate entries — entries where
the headings run together ("Cat adoption Fiction") and entries where the
headings are separated by double dashes ("Cat adoption -- Fiction"). Here
is the output from Solr:
<?xml version="1.0" encoding="UTF-8"?><response>
<lst name="responseHeader">
<int name="status">0</int>
<int name="QTime">0</int>
<lst name="params">
<str name="q">id:b2074646</str>
<str name="indent">true</str>
<str name="fl">id,topic,topic_browse</str>
<str name="q.op">OR</str>
<str name="rows">10</str>
<str name="wt">xml</str>
<str name="useParams"/>
<str name="_">1775667544232</str>
</lst></lst><result name="response" numFound="1" start="0"
numFoundExact="true">
<doc>
<str name="id">b2074646</str>
<arr name="topic">
<str>Cats Juvenile fiction.</str>
<str>Cat adoption Juvenile fiction.</str>
<str>Haiku Juvenile fiction.</str>
<str>Cat adoption Fiction.</str>
<str>Cats Fiction.</str>
<str>Haiku.</str>
</arr>
<arr name="topic_browse">
<str>Cat adoption Fiction.</str>
<str>Cat adoption Juvenile fiction.</str>
<str>Cat adoption Fiction.</str>
<str>Cat adoption Juvenile fiction.</str>
<str>Cats Fiction.</str>
<str>Cats Juvenile fiction.</str>
<str>Cats Fiction.</str>
<str>Cats Juvenile fiction.</str>
<str>Haiku Juvenile fiction.</str>
<str>Haiku.</str>
<str>Haiku Juvenile fiction.</str>
</arr></doc></result></response>
No matter what I do in the `marc_local.properties` file, I always get 11
values. I've tried deleting the record between imports to make sure there
is a fresh import each time.
Has anyone seen something like this before?
Peter
--
Peter Murray
Open Source Community Advocate
Index Data, LLC
|