As Thomas Berezansky suggests, sites are likely to want to customize the
display of copy counts depending on whether they're consortial sharers,
how deep they want to display, whether they want to just show the
matching search scope... make it easy to customize by moving the
copy counts portion of the results table into a separate template.
Signed-off-by: Dan Scott <dan@coffeecode.net>
Signed-off-by: Thomas Berezansky <tsbere@mvlc.org>
--- /dev/null
+[%- depths = attrs.copy_counts.size;
+ depth = 0;
+ WHILE depth < depths;
+%]
+<div class="result_count">
+ [% l('[_1] of [quant,_2,copy,copies] available at [_3].',
+ attrs.copy_counts.$depth.available,
+ attrs.copy_counts.$depth.count,
+ ctx.get_aou(attrs.copy_counts.$depth.org_unit).name) | html
+ %]
+</div>
+[%- depth = depth + 1; END %]
[% END %]
[% END %] <!-- END detail_record_view -->
</table>
- [%- depths = attrs.copy_counts.size;
- depth = 0;
- WHILE depth < depths;
- %]
- <div class="result_count">
- [% l('[_1] of [quant,_2,copy,copies] available at [_3].',
- attrs.copy_counts.$depth.available,
- attrs.copy_counts.$depth.count,
- ctx.get_aou(attrs.copy_counts.$depth.org_unit).name) | html
- %]
- </div>
- [%- depth = depth + 1; END %]
+ [% PROCESS "opac/parts/result/copy_counts.tt2" %]
</div>
</td>