While we break this out to a separate template, perhaps we
could pull the library name from context instead of having
it hardcoded. It will probably depend on each instance, ergo
hardcoding the generic "your library" for now should be fine.
Signed-off-by: Dan Scott <dbs@coffeecode.net>
</table>
</div>
<div style="float:right;width:353px;background:#ccc;padding:10px;margin-top:7px;">
- <p>
- <strong>Still not finding what you are looking for?</strong><br />
- Request that KCLS purchase the material you are looking for by making a
- <a href="javascript:;">Purchase Request</a><br />
- <strong>Note:</strong> You must be logged in to make a Purchase Request<br />
- </p>
+ [% INCLUDE "default/opac/parts/result/lowhits_purchase.tt2" %]
<p>
<strong>Keyword Search Tips</strong><br />
Change to <strong>Advanced Keyword Search.</strong>
--- /dev/null
+<p>
+ <strong>Still not finding what you are looking for?</strong><br />
+ Request that your library purchase the material you are looking for by making a
+ <a href="javascript:;">Purchase Request</a><br />
+ <strong>Note:</strong> You must be logged in to make a Purchase Request<br />
+</p>
--- /dev/null
+<p>
+ <strong>Still not finding what you are looking for?</strong><br />
+ Request that KCLS purchase the material you are looking for by making a
+ <a href="javascript:;">Purchase Request</a><br />
+ <strong>Note:</strong> You must be logged in to make a Purchase Request<br />
+</p>