Simon,
Please see below
> On May 25, 2020, at 1:02 AM, Simon Opper
> wrote:
>
> Hi there
>
> We need to optimise Lucene in a text search App and I want to run some tests
> and explore the configuration options for Lucene on a text corpus, datagraph
> and/or ontology.
>
> Part 1 of my
>
>
> Yes, it runs on local host.
>
> I can’t reproduce your issues.
>
> One possibility is that you have no data in the asset collections you set
> to be indexed. From Rob’s e-mails, I know that he uses files and asset
> collections in EDG are simply “wrappers” for these files. If you are
>
Thanks very much for the reply Irene.
Could you please fix the broken image links in the documentation link you
sent please. The guidance on customising the facets is not visible and I
believe this is the info I need
[image: image.png]
Re: data wrapping, it's not the issue per se it seems
> On 26 May 2020, at 04:43, Rob Atkinson wrote:
>
> OK - solved the style issue - I wasnt looking wide enough and a colleagues
> code had polluted the styles in a mod to the main menu - so at leas the
> checkboxes are back and I've learned how to force scope for CSS - another
> layer of
Probably ought to wind up this topic is the answer is "Lucene works on
local development server" and "Lucene needs data to be in the graph, not in
imports" - that said, I guess we'd still be interested in seeing if we can
open up that easily.
Its another thread to work out how much work it
Hi Rob,
I think the scenario you describe is already supported by the free-text
search if you are in individual asset collections. The Lucene-text index
there does include all imported files. However, the Search the EDG index
has the goal to drive the navigation into asset collections, so it
OK - solved the style issue - I wasnt looking wide enough and a colleagues
code had polluted the styles in a mod to the main menu - so at leas the
checkboxes are back and I've learned how to force scope for CSS - another
layer of contract UI mods have to adhere to.
On Friday, 22 May 2020
