More appropriate indexing def defaults for topic and name subjects

Bug #1270262 reported by Mike Rylander on 2014-01-17
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Evergreen
Low
Unassigned

Bug Description

With the addition of authority-enhanced bib browse, we need to be more careful about bib-side subject indexing. In particular, name and topic subjects, which often carry subdivisions, are not being matched to their full authority heading values in the browse interface. This defeats the logic's attempts to improve browse via authority.

We can fix this with the following updates:

update config.metabib_field set xpath = $$//mods32:mods/mods32:subject[mods32:name]$$ where id = 12;
update config.metabib_field set xpath = $$//mods32:mods/mods32:subject[mods32:topic]$$ where id = 14;

The risk of blindly applying these is, of course, it assumes the stock setup for those two index defs. We can't assume that, though, so some scripting (or documentation for users to follow) is warranted.

A bib reingest is indicated after this update, of course.

Revision history for this message
Mike Rylander (mrylander) wrote :

The above xpath could be improved, and made safe for the other subject types, by testing that the first (element-type) child of the mods32:subject node is of the type we care about for the definition in question. I leave that as an exercise for the reader, however, as I could not formulate the appropriate xpath expression before deciding that the above was good enough for a short-term fix. Assistance on that front would be greatly welcomed!

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers