Jim,
I didn't do any experimenting with the 710. We did not receive any
complaints or any interest in the 710. I noticed that the 700 and the
710 were right next to each other in the LOC xslt definition and had the
exact same selector query and therefore offered our solution to the 700
as a possible solution to the 710. It looks like they are both treated
exactly the same in the LOC xslt template.
Glad you got it figured out!
-Blake-
Conducting Magic
MOBIUS
573-234-4513
877-312-3517
On 10/9/2015 2:58 PM, Jim Taylor wrote:
Appreciate the reply….oddly our 700 (non-t) tags didn’t need any work.
I made the 710 (non-t) tags work by adding
type="text">creator
since it looks like it requires a role for the index but the 700’s
seems to indicate the same thing but they work without a role.
Needless to say it is a bit confusing from where I stand.
So your 710’s with a subfield “t” show in your Author browse index
without any tweaking?
Jim
*From:*Open-ils-general
[mailto:open-ils-general-boun...@list.georgialibraries.org] *On Behalf
Of *Blake Henderson
*Sent:* Thursday, October 08, 2015 4:45 PM
*To:* open-ils-general@list.georgialibraries.org
*Subject:* Re: [OPEN-ILS-GENERAL] Browse Indexes - 710
Jim,
We had this same issue. Be design, the mods32 xlst from LOC contains
this line:
(we addressed the 700 instead of the 710 but the solution is probably
the same)
We updated that line in the xlst to:
This makes it match the stock Evergreen indexes even with the presence
of the subfield "t".
Furthermore, we wanted to include the 700t in our title index. So we
created an index:
INSERT INTO config.metabib_field ( field_class, name, label, format,
xpath, search_field, authority_xpath, browse_field, browse_sort_xpath
) VALUES ('title', 'alternative_700t','Title Alternative (700t)',
'marcxml', $$//marc:datafield[@tag='700']/marc:subfield[@code="t"]$$,
TRUE, null, TRUE, null);
Hope this helps!
-Blake-
Conducting Magic
MOBIUS
573-234-4513
877-312-3517
On 10/8/2015 4:23 PM, Jim Taylor wrote:
I am wondering if there is anyone using the Browse Indexes and, if
so, have you verified that the 710’s with a subfield “t” and
without (they are handled differently) are working. As far as I
can tell they will not work as configured in Evergreen right out
of the box. I have gotten the 710, without a “t”, to work, with a
little tweaking, but still no luck with the 710 with a “t”. I
am reasonably sure this isn’t limited to the 710’s but am working
down the list trying to make sure all the indexes are working and
are configured correctly and this is the current problem.
So, if, *you know*, your 710 browse indexes work and you are
willing to share the mod32 xslt from the config.xml_transform
table I would greatly appreciate it. Unless you know of some
other reason the indexes aren’t working by default…I supposed
Evergreen could be configured by default to not have the 710’s
work but that doesn’t seem likely since they are part of the mod2
transformation and the index configuration seems appropriate???
In any event, any information that could point me in the right
direction would be appreciated. Thank you.
Jim
