Title: Message Title
|
|
|
|
|
Issue Type:
|
![Code Task]() Code Task
|
|
Affects Versions:
|
4.0
|
|
Assignee:
|
Unassigned
|
|
Created:
|
13/Nov/13 10:14 PM
|
|
Fix Versions:
|
4.0
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Tim Donohue
|
|
Now that Discovery is the new default Search/Browse (in 4.0), we may want to deprecate the older Lucene-based Java classes (org.dspace.search.*)
https://github.com/DSpace/DSpace/tree/master/dspace-api/src/main/java/org/dspace/search
It seems like after 4.0, we'd want to get rid of this old Lucene code and either:
1) Replace it with new Lucene code which works with Discovery (so that Lucene will be another Discovery backend)
2) OR, just do away with Lucene support altogether and concentrate on Discovery + Solr (and possibly other backends like ElasticSearch)
Either way, it sounds like the old Lucene-based Java code is likely to be removed/replaced in the near future, so we may want to deprecate those java classes in 4.0
Thoughts? Agree/Disagree?
|
|
|
|
|
|
|
|
------------------------------------------------------------------------------
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
