Difference between revisions of "Adding an Auto-Completer to a non-workflow page"
| Line 11: | Line 11: | ||
An unordered list of records to display, with each "fill-in" item part of a sub-list: | An unordered list of records to display, with each "fill-in" item part of a sub-list: | ||
| + | <code> | ||
<ul class="journals"> | <ul class="journals"> | ||
<li class="">University of Leeds<br /> | <li class="">University of Leeds<br /> | ||
| Line 29: | Line 30: | ||
</li> | </li> | ||
</ul> | </ul> | ||
| − | + | </code> | |
foo | foo | ||
Revision as of 09:18, 12 April 2010
Adding an Auto-Completer to a non-workflow page
In a workflow, adding an auto-completer is relatively sinple:
<field ref="publication"
input_lookup_url="{$config{perl_url}}/get_journals"/>
.... and the EPrints application takes care of all the "stuff" on the main page.
The return format is fairly simple too: An unordered list of records to display, with each "fill-in" item part of a sub-list:
- University of Leeds
[University of Leeds] http://iss.leeds.ac.uk/
- 17259
- University of Leeds
- University of Leeds
- http://iss.leeds.ac.uk/
- University of Leeds
-
.....
foo
