I did a bit of digging here. It seems that all the problematic browse entries all have the same config.metabib_field. Its ID is 37 in our system. Here it is:
id | field_class | name | label | xpath | weight | format | search_field | facet_field | browse_field | browse_xpath | facet_xpath | restrict | authority_xpath | browse_sort_xpath | joiner | display_xpath | display_field
----+-------------+---------+--------------+--------------------------------------------------------------------------+--------+--------+--------------+-------------+--------------+--------------+-------------+----------+-----------------+-------------------+--------+------------------------------+---------------
37 | author | creator | All Creators | //mods32:mods/mods32:name[mods32:role/mods32:roleTerm[text()='creator']] | 1 | mods32 | t | f | t | | | f | | | | //*[local-name()='namePart'] | t
It looks pretty similar to all the other author metabib_fields. Could the MARC->MODS transform be at fault here?
I did a bit of digging here. It seems that all the problematic browse entries all have the same config. metabib_ field. Its ID is 37 in our system. Here it is:
id | field_class | name | label | xpath | weight | format | search_field | facet_field | browse_field | browse_xpath | facet_xpath | restrict | authority_xpath | browse_sort_xpath | joiner | display_xpath | display_field ------- ----+-- ------- +------ ------- -+----- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------+ ------- -+----- ---+--- ------- ----+-- ------- ----+-- ------- -----+- ------- ------+ ------- ------+ ------- ---+--- ------- ------- +------ ------- ------+ ------- -+----- ------- ------- ------- ----+-- ------- ------ mods/mods32: name[mods32: role/mods32: roleTerm[ text()= 'creator' ]] | 1 | mods32 | t | f | t | | | f | | | | //*[local- name()= 'namePart' ] | t
----+--
37 | author | creator | All Creators | //mods32:
It looks pretty similar to all the other author metabib_fields. Could the MARC->MODS transform be at fault here?