ufal / perl-pmltq-web

Simple web build on the top of the PML Tree Query server
https://lindat.mff.cuni.cz/services/pmltq/
0 stars 0 forks source link

Tree navigation confusion #125

Open matyaskopp opened 6 years ago

matyaskopp commented 6 years ago

There is two ways of navigation among trees: 1) Query result navigation 2) File exploration screen shot 2017-10-24 at 12 17 34 copy

Is file exploration necessary?

dan-zeman commented 6 years ago

I think I've never used it. Just my two cents.

Ansa211 commented 6 years ago

What about changing the "sentences in a file" to just two buttons, preceding context and following context? That should make it clear enough that we are not talking about a "preceding/following sentence matching the query" but about sentences in the file.

The user has other ways to find out the file and sentence number if he/she needs them.

matyaskopp commented 6 years ago

Can it be done in this way? image

It contains onmouse title as @Ansa211 suggested

(deployed on https://lindat.mff.cuni.cz/services/pmltq/#!/home)

dan-zeman commented 6 years ago

Fine with me.

matyaskopp commented 6 years ago

There is one other confusion: When somebody execute a query result firstly appears. Then he/she clicks on following/preceding context. Now it is not possible to distinguish whether currently displayed tree is a result of the query. There should be some indication whether currently displayed tree is in the result

Ansa211 commented 6 years ago

It would be nice if the context could be appended to the query output, so that multiple trees would be shown simultaneously. This would mean that in any corpus that contains coreference arrows between different trees, the pml-tq stylesheet would have to be extended to handle them correctly when both trees are shown in a single view. For example, the "preceding context" on http://hdl.handle.net/11346/PMLTQ-D4IP would give preceding_context

(The "preceding context" and "following context" buttons would then extend the context view to more preceding or following trees; so if the "preceding context" button would be pressed again, we would get view with trees 190-192, while the "following context" would give 191-193.)

Ansa211 commented 6 years ago

One more related comment: the left and right arrows in the "Result" part now have mouseover saying "Preceding/Following sentence matching the query". Actually, with simple queries, they often lead to a different node within the same sentence. More exact wording of the mouseover would be "Preceding/following set of nodes matching the query" or at least "Preceding/following node(s) matching the query".

Ansa211 commented 6 years ago

A simpler idea for a visually simple way of indicating whether the tree shown is actually a tree matching the query or a tree in its context: By default - when showing the tree matching the query - the left part with the two arrows and the word Result is in bold and the right part with the word Context is not. What about swithing it when the user moves to a sentence in the context? Result and the numbers nead it would NOT be in bold and Context and the sentence number near it would be in bold.