Good morning all, The current DSpace has a nice system whereby you can register an additional, or replace a search provider by registering the class in the dspace.cfg file and configuring what kind of events that class wants to receive. Somehow I miss something like this for statistics. We are currently using ElasticSearch in addition to Solr for our stats recording. In our current DSpace I hard-wired ElasticSearch in the relevant places to make it update. Now I am working on code which might one day become part of core DSpace - hard-wiring local peculiarities does not sound like the correct way forward.
Is there any reason why making statistics 'plug-in-able' via the dspace.cfg is not a good idea? Best regards, Anja ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk _______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
