While drawing a line, region or segment it should be possible to move the page, e. g. by using the arrow keys or something like Shift + left mouse.

There seems to be a problem with images of different pixel sizes.
Cuts, region polygons and fixed segments created in the web view are sometimes processed with the wrong scale factor by the server.

It should be possible to define two separate RoIs recto/verso (odd/even) pages.

Scrolling via mouse on firefox will make the page vanish.
Seems to be a problem with the value provided by firefoxs scroll wheel.

The webapplication does currently not support creating or changing the reading order.
Files created by export to PageXML are lacking this order.

When the user clicks somewhere on the page where no segments are located the already selected segments shouldn't get deselected if Ctrl is still pressed.

It should be possible to quickly jump to a certain page. Since the numbering of the pages depends on the file names and might be inconsistent the best solution would probably be a extendable drop down menu showing the file names. This menu should also indicate which pages have already been segmented.

• It should be possible to deselect a single segment while keeping the rest of the selected segments (Ctrl + left click).
• Selected segments should get deselected when the user clicks at a spot where no segments are located.
• It should be possible to add several segements to a selection by holding down Ctrl and selecting the additional segments by drawing a rectangle.

It would be helpful if a tooltip could show the filename of an image in the left bar of the viewer.

The hover effect of polygons is active while creating a new polygon.
This is an unneeded distraction and should be prevented

• Create/Delete region sometimes gets ignored. Also happens when using Firefox.
• Sometimes the image region can be deleted, which shouldn't be possible.

When right clicking on an inactive segment it should become active and the type dropdown should open right away.
Right now it sometimes requires two clicks (left click to activate, right click for dropdown). This seems to depend on the operating system as the problem never (?) occurs when running windows.

Add a flexible select functionality

• Select everything inside a box
• Select everything between last selected and "Shift" selected

The maxOccurence region parameter seems to be buggy (and kinda useless) and should be temporarily disabled/removed.
It's misspelled anyways :-).

A user should be able to move and resize polygons for regions and fixed segments.
Such a operation currently requires the user to delete and recreate the polygon.

Current goals are to add options for:

• moving polygons for regions and fixed segments
• resizing/expanding rectangle polygons of regions
• resizing/expanding polygons of fixed segments

A distinction between rectangle polygons and un-regular polygons has to be made.
It must be possible to scale/expand a rectangular polygon at his edges and corners while maintaining a rectangular shape.
Resizing the polygons of fixed segments could be a more complicated issue. Those polygons do not have to be rectangles and un-regular polygons should behave differently than rectangles.

There should be shortcuts for saving (Ctrl+S) and Exporting (Ctrl+E) a segmentation result.

I'm not sure if it is necessary to be able to zoom in to about 10,000,000%. A cap might be in order.
Furthermore, anti aliasing looks weird and should be turned off,

Already finished (= result has been stored as PageXML) pages should be marked with a green border in the page overview.

It should be possible to merge several selected segments:

• Each segment should get connected to its closest neighbour.
• After merging, the type dialogue should pop-up so a new type can be assigned right away. Alternatively, the initial type of the biggest single segment could be assigned.

It should be possible to zoom while drawing a polygon/rectangle/cut line.

• When saving the final result via "Export PageXML" (should be renamed to "Save Result" or something similar) the corresponding page should be marked by a symbol (just like when downloading the PageXML).
• When returning to a page whose final result has been already saved, the final result should be displayed instead of the result that was produced by the automatic segmentation.
• A keyboard shortcut would be nice.

thx very much

While the RoI should always be permanent, ignore rectangles or polygons by default should only be valid for the current page. Optimally, the user should be able to choose between permanent and non-permanent.

Moving, scaling and deleting an object can only be done by selecting the object and pressing the keys m, s or del respectively. The access to those functionalities is not obvious enough.

The following change to the context menu is proposed:

Creating a region object or fixed segment could still open the current context menu, while right clicking existing objects would open the enhanced context menu.

Add Page XML-Export per page.

If a new images is added to a book diretory while LAREX is running and the book is open in the LAREX editor, an exception is thrown when clicking on the new image (or the last image of the book):
java.lang.IndexOutOfBoundsException: Index: 7, Size: 7
at java.util.LinkedList.checkElementIndex(LinkedList.java:555)
at java.util.LinkedList.get(LinkedList.java:476)
at com.web.model.Book.getPage(Book.java:46)
at com.web.facade.LarexFacade.segmentPages(LarexFacade.java:106)
at com.web.controller.ViewerController.segment(ViewerController.java:86)

Categories to create a region polygon, fixed segment and cut are not clear enough.
The display seems to be un-intuitive and should be changed.

It should be possible to assign a new type to several selected segments at once.

It should be possible to add fixed segments without re-running the segmentation.
When the result is saved/exported fixed segments which have been added after the last segmentation run should be treated as final segments. Obviously, this could lead to overlapping segments but to deal with this lies within the responsibility of the user.

Moving or scaling fixed segments will change the opacity of the segments body to "selected".
Reopening the page or segmenting will reset it to normal.

Edit: Same happens occasionally when working with the reading order.

Aborting to move or scale a segment can cause it to be highlighted, even if the cursor is no longer above the segment. Hovering over the segment again will solve this.

e. g.: Switch the page, click on a properties button, ...

Book pages are not loaded alphabetically and are displayed randomly.
A short sort before the processing will be added.

It should be possible to hide the current segmentation result (keyboard shortcut...) as it can be distracting when manually marking an image etc.
This setting should stay active until the user disables it (shortcut), runs the segmentation or switches to another page.

The applications slows down while moving the document if many segments with many points are selected.

A different more performant design should be used.

It should be possible to save and load parameter and region settings for an individual book so they can be used again after closing the tool.

If a region/segment is very small, it is cumbersome to select its border.
There should be a minimum value for the catchment area while resizing.

If a directory in the book folder contains a 'special character' such as an ö it is ignored in the list of books.

It seems that already deleted segments still get saved in the PageXML result. Obviously, this shouldn't happen.

It is possible to zoom while creating a polygon.
The polygon stays in relation to the screen instead of the page image.
It would be better if it stayed in relation to the page.

Opening a book currently loads all of its pages in full resolution from the server.
This can lead to unwanted and unneeded web traffic and should be avoided

Current goals are:

• only loading page images by demand
• using down scaled images for the page preview

In order to exclude page periphery (if present) a RoI modus is required.
The user should be able to mark the interesting region of the page by drawing a rectangle. The remaining borders should then be marked as an ignore region.

When using the PageXML Button of the file menu bar, the page is downloaded twice. This behavior is confirmed on chrome and firefox.
The Export as PageXML Button on the side panel works as expected

It should be possible to choose between different segmentation modi:

• none (detected image contours are ignored)
• contour only (the original image contour is used)
• straight rect (a straight bounding rectangle is fitted around the detected contour)
• rotated rect (a rotated ...)

• Region types which are already in use shouldn't be displayed in the "create region" dialogue.
• Region types should be displayed in alphabetical order.

Add the functionality to add and edit a reading order for each page.

Current goals are to add options for:

• auto generate a reading order top to bottom
• edit the current reading order
• hide reading order
• creating a new reading order via mouse

Scaling and moving region polygons or fixed segments is at the moment restricted to the object last selected.
Scaling and moving multiple objects should be implemented and tested.

Colors for the regions page_number, image, paragraph, marginal and ignore are set manually, the other regions are getting a computer generated color assigned.
This leads to different regions sharing a similar color.

Current goals are:

• unique colors for every region by default (at least as unique as possible) (03b768e)
• settings for the user to change a region's color (9bd2288)

The webapp currently only supports image types common to webapplications.
TIF is not supported.
This should be changed given the importance of the TIF format in digitization workflows.

When selecting a new page the corresponding thumbnail should be centered vertically (if possible) so the user doesn't have to scroll all the time while working through the scans.

When a position of a default region (e. g. the page-number position at the top of the page) gets resized or moved it stops working ->comprised segments aren't classified correctly anymore.
User created positions can be resized or move without any problems.