Does anyone have ideas on how this should be fixed?
The old logic went through each subfield and built the series links by creating a new <a> for each subfield, that included all the previous subfields in the search link for that specific subfield.
Should the new displayfield code in templates/opac/parts/record/series.tt2 handle this?
Should it just split the string on ; and build out the multiple links from there?
Or should the displayfield definition for series exclude the subfield v?
Does anyone have ideas on how this should be fixed?
The old logic went through each subfield and built the series links by creating a new <a> for each subfield, that included all the previous subfields in the search link for that specific subfield.
Should the new displayfield code in templates/ opac/parts/ record/ series. tt2 handle this?
Should it just split the string on ; and build out the multiple links from there?
Or should the displayfield definition for series exclude the subfield v?
Josh