Title: Message Title
|
|
|
|
Apparently XMLUI needs configuration for this just as JSPUI does. We can't just use the same configuration, because it just selects one plugin or another, and both plugins contain JSP-dependent code not easily removed. So the quickest fix I can see would be to create a new configuration setting for XMLUI to tell it which search provider to use in this place. Ugh.
If after 4.0 we decide to carry the old search provider along for a while, then for 5.0 it would be well to separate the search logic from the display logic, just have one plugin or service interface which provides all searching, and inject either the old or the new as desired. The UIs *should not know* which search infrastructure is employed; at the most they should be able to query the search infrastructure as to whether it implements some desired but optional function.
|
|
|
|
|
|
|
|
The search box inside the item mapper functionality in XMLUI not work when only discovery is enabled (and this will be the default in dspace 4.0).
|
|
|
|
------------------------------------------------------------------------------
DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
Free app hosting. Or install the open source package on any LAMP server.
Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
