Difference between revisions of "Adding an Auto-Completer to a non-workflow page"

From EPrints Documentation
Jump to: navigation, search
Line 12: Line 12:
  
 
<code>
 
<code>
  <ul class="journals">
+
 
  <li class="">University of Leeds<br />
+
  <ul class="journals">
    [University of Leeds] http://iss.leeds.ac.uk/  
+
    <li class="">University of Leeds<br />
    <ul>
+
      [University of Leeds] http://iss.leeds.ac.uk/  
    <li id="for:value:component:_oid">17259</li>
+
    <ul>
    <li id="for:value:component:_ocname">University of Leeds</li>
+
      <li id="for:value:component:_oid">17259</li>
    <li id="for:value:component:_oname">University of Leeds</li>
+
      <li id="for:value:component:_ocname">University of Leeds</li>
    <li id="for:value:component:_ourl">http://iss.leeds.ac.uk/</li>
+
      <li id="for:value:component:_oname">University of Leeds</li>
    <li id="for:value:component:_oacronym"></li>
+
      <li id="for:value:component:_ourl">http://iss.leeds.ac.uk/</li>
    <li id="for:value:component:_onamepreferred"></li>
+
      <li id="for:value:component:_oacronym"></li>
    <li id="for:value:component:_oaltname">University of Leeds</li>
+
      <li id="for:value:component:_onamepreferred"></li>
    <li id="for:value:component:_oalturl"></li>
+
      <li id="for:value:component:_oaltname">University of Leeds</li>
    </ul>
+
      <li id="for:value:component:_oalturl"></li>
  </li>
+
    </ul>
  <li class="">
+
    </li>
    .....
+
    <li class="">
  </li>
+
      .....
  </ul>
+
    </li>
 +
  </ul>
 +
 
 
</code>
 
</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:

foo