Extra data column in KWIC for sentence structural attributes

[jroxendal]

Beläggställena till träffarna måste visas synligt och i sammanhang i konkordanserna, lämpligen i ett referensfält (separat kolumn), som i ITG-versionen. Att motsvarande uppgifter kan sökas fram i sidopanelen för en träff i taget är bra i och för sig, men det räcker inte! Man måste kunna se beläggställena i sammanhang när man arbetar med konkordansen. Samma platsinformation måste också finnas i visningen av sammanhängande text. ASU har ju en fast radindelning av texten, som i ITG-versionen används samordnat för beläggställen i konkordanser och textvisning. Jag vet ju inte hur programmet för Korp fungerar, men tydligen har det referensfält som finns i den lagrade texten tagits bort när ASU har lagts in i Korp. Det behöver läggas in!

[janiemi]

Do you have plans to implement this feature in the near future? This has been a wish of ours, too, and was now again asked by a user of the Korp of the Language Bank of Finland. If this feature isn’t on your roadmap, I might try to see if I’d be able to implement it myself.

Some ideas:

• A simple(?) implementation might be to add a fixed first column to the KWIC table containing the value of the desired attribute. It could perhaps use the CSS position: sticky, or would that limit the feature to too recent browsers?
• The user should be able to choose the attribute(s) to be shown.
• It would be nice to be able to select more than one attribute to be shown.
• Also attributes from structures longer than the sentence (paragraph, text) should be allowed.
• The attribute selection could be in the KWIC result header, and the user might change the attribute(s) without having to perform a new search, as the information is in the KWIC result anyway (if I understand correctly).
• The structure columns might have headings on rows containing corpus names.
• In the context view (reading mode), the attributes would need to be represented differently, perhaps as a separate paragraph before the paragraph containing the hit and its context.

[majsan]

Not in the near future, no (since we are focusing on configuration right now). Thanks for the ideas, I think they all sound great. As you point out, the data is already fetched and (probably) available in the KWIC code, it's just a question of showing it. So it should be quite straight-forward to implement.

And position: sticky is fine, after having checked https://caniuse.com/css-sticky, supported by the major browsers since a few years back.