On 7/19/2012 11:18 AM, helix84 wrote: > On Thu, Jul 19, 2012 at 6:14 PM, Richard Rodgers <[email protected]> wrote: >> If SOLR were made optional, and the stack footprint essentially the same as >> the old OAI, I'd recast my vote to #1 > > I already wrote it in this thread while it was on dspace-release: Solr > is optional. Database backend is a simple configuration switch.
To this end, if it made folks more comfortable, we could release OAI-2.0 with the database backend by default (and give the option of enabling Solr backend if you want the benefits provided by Solr). OAI-2.0 seems as though it is 100% backwards compatible with current OAI, plus it offers many new features and fixes lots of old bugs in the current OAI. Here's the list of old JIRA issues that OAI-2.0 resolves: https://jira.duraspace.org/browse/DS-1202?focusedCommentId=25390&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-25390 Again, in my mind, it seems like a obvious replacement to the existing OAI implementation, as long as we can get a few more folks to review it. If for some reason we found it to *not* be backwards compatible, than I'd agree that we wouldn't want to completely replace the existing OAI. But, so far, from all I've seen/read, it seems like Lyncode has gone out of the way to make sure it is 100% backwards compatible. - Tim ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
