Open davidzbiral opened 6 months ago
Just one note here for the first point:
Even though the entity might have been anchored through the "statement list" box
@adammertel Oh we need it! No waiting. We need to jump in the text to where the anchor is (start anchor). I don't understand here - I thought anchors are created only in Annotator, not Statement list. Most Ts will only have one anchor ever. I want to jump in Annotator there where the start anchor is. Perhaps I somewhat misled you in No. 1 by my disquisition on the opening of subT. But the basic thing is that I want to jump in Annotator to the start anchor from Detail, where I want to have the opportunity to click on the anchor and jump there. If the entity (e.g. a Location or Person) has more anchors, all will appear in Detail (paginated), and I will be able to decide based on text span snippet to which one I want to jump.
Link to the design in Figma
@adammertel This is a list of Resources. Rather, what I need is a list of anchors. For instance, let's say that Location "Bologna" is anchored 200 times in one Document, and 5 times in one. Thus, what I need to see here is 205 records (paginated), introduced with the anchor icon probably, and identify the anchor with the text it spans, just as you do now - the spanned text will be the first "column" of the display. It will also be possible to click on the anchor, and this will bring me to that specific anchor in the fulltext in Annotator. Otherwise the structure is good, i.e. to each anchor, add Resource, full-text opener. But in addition, add the subT entity in which the anchor sits (if the subT exists). Heading should be "205 Anchors", not "2 Documents (anchors)".
(EDITED.) We need a list of anchors in Detail, where the entity is anchored - similar to the list of statements in which an entity is used. Function buttons/icons:
(I am so clever :-) .)