An update..
tested this on a colleagues machine using the exact same version and build
of TBC, and the search works fine out of the box. I created a fresh repo
and reran the same configuration script and it still fails.
The UI is different too - i have a gear icon and a broken CSS and he has a
series of icons in the tab. (both using chrome).
Will try on some other machines and compare.
Wondering if it some cached stuff as i have used all previous versions.
On Thursday, 21 May 2020 12:12:05 UTC+10, Rob Atkinson wrote:
>
> oops - forgot to update item #6 - thats doesnt work if a filter is
> included if data is included - but does work if data is copied into graph
>
> On Thursday, 21 May 2020 12:09:04 UTC+10, Rob Atkinson wrote:
>>
>> Ok - a few layers of challenges here - gradually unpicking it:
>>
>> Query in both the UI and GraphiQL return data if not filter text is
>> specified.
>>
>> The graphql schema shows properties that are queryable, but if i put any
>> sort of filter against these in Graphql or the UI Free text search returns
>> no results
>>
>> A few UI glitches made this harder to track down, The CSS for checkboxes
>> is broken in 6.3.2.
>>
>> here are the things i'd suggest reviewing
>> 1) The CSS for the checkbox on the "use local results" is
>> element.style {
>>
>>
>> }
>> wiring_rule….editor:156
>> input[type="checkbox"] {
>>
>> 1. position: absolute;
>> 2. /* left: -9999px; */
>>
>> }
>>
>> i have switched it off as above and lo and behold the checkbox appears
>>
>> 2) hiding the indicator for whether local results are used under the gear
>> icon seems suboptimal.
>>
>> 3) Need to know how to set the value of this setting by default when
>> generating an Asset collection as a wrapper that includes the data of
>> interest
>>
>> 4) possibly want to have a special type of include that limits queries to
>> included data, not all included shapes
>>
>> 5) New button on instances only works with graphql:publicSchema defined
>>
>> 6) Graphql UI doesnt work (finds schema but get no results if data
>> included via an import) - after setting graphql:publicSchema
>>
>> The functionality issues I need a solution for are #3 and #6
>>
>> On Wednesday, 20 May 2020 23:34:45 UTC+10, Irene Polikoff wrote:
>>>
>>>
>>>
>>> On May 20, 2020, at 4:50 AM, Richard Cyganiak <ric...@topquadrant.com>
>>> wrote:
>>>
>>>
>>> On 20 May 2020, at 09:25, Rob Atkinson <robatki...@gmail.com> wrote:
>>>
>>> OK search is _nearly_ working using the shapes once I save them and
>>> force them to be imported.
>>>
>>> I had to set the graphql:publicClass and force-refresh the editor to
>>> pick up changes.
>>>
>>> If I put in no search term it finds everything - but anything in the
>>> free text box gets zero results. Is there some other step required to make
>>> individual fields searchable ( this is the field! in the graphql schema ?)
>>>
>>>
>>> I'm not sure. I know that rdfs:label is indexed, and I believe (but not
>>> sure) that *all* literals are indexed.
>>>
>>>
>>> Yes, by default all text literals are indexed. This can be configured to
>>> be less.
>>>
>>>
>>> Sometimes, Server Administration > Text Indices > Rebuild can resolve
>>> problems with the search. In theory that shouldn't be necessary.
>>>
>>>
>>> In my experience, this step is only needed if asset collections are
>>> brought in through project import into TBC workspace e.g., if you download
>>> and install samples - as described in the instructions. But do try to see
>>> if it helps.
>>>
>>>
>>> Also i can find any indicator showing if search is local. At any rate
>>> I will want to set a flag to force it to allow search on imported graphs -
>>> is there such a property that sets that as default? and/or one that forces
>>> it (disables option)
>>>
>>>
>>> Like in the Instances panel, results from included graphs are shown by
>>> default, but that can be turned off via “Return local results only” in the
>>> search panel's “gear” menu (here for a Glossary but should be the same for
>>> Data Graphs):
>>>
>>> <local-results-only.png>
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "TopBraid Suite Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to topbrai...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/topbraid-users/6B57C884-5773-4897-A85C-A74CDDA2E19A%40topquadrant.com
>>>
>>> <https://groups.google.com/d/msgid/topbraid-users/6B57C884-5773-4897-A85C-A74CDDA2E19A%40topquadrant.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>>
>>>
--
You received this message because you are subscribed to the Google Groups
"TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to topbraid-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/a0e1d646-2f72-4ba8-ab41-fe36de367db3%40googlegroups.com.
