Menu
▾
▴
#48 Make document viewing and navigation easier
Currently it is very cumbersome to navigate between documents within a corpus: it is necessary to click several times for this: to display the list of documents for a corpus, load the document, display the document, re-arrange the annotation windows and interesting annotations view as before.
Instead, it would be useful to have a way to specify that one wants to view documents from within a corpus and have them be displayed in a similar way as now.
In addition there should be navigation buttons for skipping to the previous, next document in the corpus according to the current sorting order or according to a result list from a search.
It should be possible in this mode to also make the way how annotation windows are shown and which annotations are highlighted in the document "sticky", so that the view is kept when changing from one document to the next.
The last selected annotation sets from the annotation sets view are now automatically saved.
When you shift +click on the annotation sets view button in the document editor you get the same selection as before.
+1 for this. It's more intuitive for users if the documents that make up the corpus appear as children of the corpus node.
Some of this has been fixed and the rest can't be fixed so I'm closing the issue.
The "can't be fixed" relates to the fact that documents aren't children of a corpus. Instead a corpus can reference a document, and a document can be referenced by more than one corpus. As such it's impossible to have a next document button as that could be undefined or have multiple options depending on which corpus you look in. The same for the resource tree, displaying a document under a corpus isn't possible as it could be under multiple corpora.
This is probably rather a feature request to add a corpus-based document viewing GUI which is perfectly possible and which I actually have implemented at least 10 years ago (but for a specific application, so it did not get published open source).
Since a corpus is a list of documents, there is no problem at all to have an element (document) viewer that allows navigation based on the list.
True I suppose. You could certainly imagine having a new VR for corpus that is basically the document viewer with the next previous buttons (that might be fairly trivial to implement) but we certainly don't want to group documents under corpora in the resources tree. I've reopened and will add the corpus viewer as a feature request when I move them to github