Sorry for missing the meeting. Catching up on this thread... [20:57] <tdonohue_> PeterDietz -- just catching up here. maybe you could enable two versions of XMLUI? One with Discovery and one without? Not tried that myself, but it could be a way to promote the differences between Discovery and normal XMLUI [20:58] <tdonohue_> PeterDietz -- what I mean is actually creating a 'http://demo.dspace.org/xmluiDisc/ path (or similar), to go alongside the existing http://demo.dspace.org/xmlui/ [20:58] <mhwood> Yes, would not like to see Discovery left out, but if there can be only one then it should be the default one. [20:59] <PeterDietz> That might involve some tomcat trickery that might give the user the misleading impression that they can run both in tandem. It would be better to have seperate instances, or to change things up on people each day. Theme of Day One: Discover whats new with DSpace, Theme of Day Two:.... [20:59] <kshepherd> tdonohue_: yeah, i think teh tricky bit we're worried about it making sure users know it's switched off by default, and that it may not be production-ready [21:02] <sandsfish> discovery: who would be the one to configure a separate instance? the one who has to do the work should probably decide if it's feasible. [21:03] <grahamtriggs> it would be possible to have the discovery applications alongside the non-discovery applications... but the non-discovery applications wouldn't update the discovery indexes if you add/change an item (and possibly vice versa)... so, they would have to be entirely separate 'repositories' [21:04] <PeterDietz> ...could emulate that by having a cron task run every hour to keep the discovery-solr-index in sync [21:05] <tdonohue> grahamtriggs -- that's an idea. Have a separate testathon install with Discovery enabled -- and send people there for testing of it [21:06] <PeterDietz> ...so, if anyone is going to host their own testathon let me know. This would be easy to help people see the difference between dspace-plain, and dspace + discovery [21:09] <tdonohue> PeterDietz -- if there are no takers to setup another testathon instance, technically we could just install a second DSpace on demo.dspace.org, and enable Discovery in that second DSpace only [21:10] <tdonohue> i.e. you could still end up with a demo.dspace.org/xmluiDisc/ path -- but it would actually point at an entirely separate install of DSpace. Not sure if that would get way too confusing for testers though (so, a separate site may be better, if we have a volunteer) [21:15] <PeterDietz> also, I think I'll change the update-discovery-index to do solr.search.autocommit. As I mentioned to a few last week, you get a 10x performance boost for the initial indexing [21:16] <PeterDietz> I'll leave to hard solr.committing after every update/delete so that though happen "for sure"
Enabling Discovery as a separate webapplication is possible if we make the following concessions: 1.) Enable the "Discovery Consumer" by default in dspace.cfg and accept that all apps including the traditional xmlui use it. 2.) Create a second war project under modules called something like "xmlui-beta" 3.) copy the xmlui.xconf into xmlui-beta/src/main/webapp/WEB-INF 4.) Configure the discovery aspects there. This would give you a second XMLUI instance with discovery enabled within it and be usable in the testathon without having to do any of the installation steps. Mark p.s. Peter, I think that we want to consider batch processing and the DiscoveryConsumer in changing to autocommit. Ideally, we would seek a configuration that will optimize solr commits when processing a large number of items. Note, until we get Browse completely out of the picture, we are stuck with that original problem with Browse interfering with batch loading scalability. -- Mark R. Diggory @mire - www.atmire.com 533 2nd Street - Encinitas, CA 92024 - USA Technologielaan 9 - 3001 Heverlee - Belgium ------------------------------------------------------------------------------ The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev _______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel