Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)

The loop controller offers segments of a configureable length.

When adding a new annotation (category or text) the annotation should have the in and out time of the current loop, if this option is selected.

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/25

Originally reported by: Daniel Ebbert (Bitbucket: danielebbert, GitHub: danielebbert)

At the moment the title of the video is not shown in the annotation tool. As a user I would like to have this information while in the annotation tool. It could maybe be in the top left where it now states "Annotating Academic Video".

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/38

Originally reported by: Daniel Ebbert (Bitbucket: danielebbert, GitHub: danielebbert)

Google Chrome shows a download button in the video player, that button should not be visible to the user

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/43

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)

at least when increasing the height like in #31 described the labels of one category should be close to each other and on the same height if possible within a track.

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/32

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)

Currently public categories are added to "mine" as soon as they are used. That should be avoided.

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/5

Originally reported by: Julian Kniephoff (Bitbucket: JulianKniephoff, GitHub: JulianKniephoff)

In the context of pull request #14, @rrolf raised the issue that the highlighting of the active annotation(s) by a small red border is maybe not distinguished enough.

I would add that we might need to differentiate the highlighting a bit more, because annotations might be "active" for different reasons in different contexts (selecting it, the play head reaching its start time, commenting, ...).

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/40

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)

the (admin) user should be able to select which tracks (from which users) and which categories he wants to export.

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/18

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)

Keyboard shortcuts could be used to set the start point for a label. A suggestion would be to use the 0-9 keys as a configureable shortcut for categories

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/7

Also maybe space for pausing the video.

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)

general UI settings (like which UI elements is visible and not) and video specific settings (like which annotations are currently open) should be stored in the local storage so that when a user comes back to a recording it is more or less in the same state where he left it.

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/27

Originally reported by: Julian Kniephoff (Bitbucket: JulianKniephoff, GitHub: JulianKniephoff)

The frontend might be as well, but that's not as severe.

Using manual REST calls outside the UI you could probably get to and update/delete almost everything. Now of course security might not be the biggest priority for the tool, but I still have a lot of tickets ahead of me that concern themselves with privacy of the various resources in the system. This is basically nonexistent at the moment.

A couple of examples:

• I can only list tracks that I have access to, sure, but when I have the ID, I can still get the tracks data from the API. I can even delete it!
• I can create annotations on tracks that I don't have access to when I have their IDs.
• I can CRUD any annotation given its ID
• Other fun things like creating annotations on nonexistent tracks; foreign key constraints are not enforced anywhere.
• etc.

Also the few things that are checked, are checked in inconsistent locations. Some in the REST service, some in the persistence layer.

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/39

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)

With the external API groups can be managed:
https://docs.opencast.org/develop/developer/api/groups-api/

This could be used in the annotation tool to let users with annotation-admin rights (or other appropriate rights) to create new groups with selected users.

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/13

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)

1. Download categories by using the "Edit Mode", and then the down-arrow. You will get a json file.
2. Delete the categories, or go to a new Recording and import the categories, with the up-arrow in the "Edit Mode"
3. Nothing happens, where the categories are expected to show up.

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/1

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)

Users should be able to reply to a comment.

Optionally it might be an option to have a reply to a reply too.

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/16

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)

When I create a new annotation (text or category label) the new entry in the item list should be open by default, so that data can be quickly accessed there.

Probably an item that was opened this way, should be closed as soon as a new item was added (keeping manually opened items open)

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/6

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)

If a new item (text or category annotation) was created a shortcut (maybe ctrl+r) should pause the video and open and focus the comment field for this item.

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/8

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)

Tracks are currently added above the current track. It would be better to say where they should be added and to rearrange tracks with drag and drop.

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/33

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)

Additional to private and public tracks also an additional visibility option should be added, where the track is viewable for the person who created the track and all users with the ACL action "annotation-admin".

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/11

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)

Admins should be able to export all data available except private tracks of user users.

Regular users should only be able to export their tracks and tracks of their groups.

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/17

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)

Single tracks should be able to be imported (and probably exported for this purpose).

The use-case for such tracks is demo data, that should explain new users how annotations should/could be used.

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/22

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)

Items in the item list should be open, if the current playtime is covered by them. They should be closed if the playtime is beyond their OUT time (Items without an OUT time should probably have a default length for this feature, maybe 5s).

Items opened manually should not be closed automatically.

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/15

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)

Excel might encounter problems in parsing the CSV file. Sven Stauber has a patch to export an XLS already

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/20

Originally reported by: Matthias Neugebauer (Bitbucket: mtneug, GitHub: mtneug)

The annotation tool assumes that the current Opencast instance has a running external API. This is not the case when running within the presentation distribution which is part of a multi-node setup. Using admin's external API would work as the session cookies will not be transferred.

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/50

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)

The categories should have an eye-icon to show or hide the entries for all labels within the categories on all timelines and the item list.

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/4

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)

in "other public tracks" I can select users whose tracks should be displayed.

This should be more fine grained to allow also a separate selection of their tracks (including the own tracks of the current user).

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/34

Originally reported by: Daniel Ebbert (Bitbucket: danielebbert, GitHub: danielebbert)

Changing the visible categories leads to no annotations being shown in the timeline. The tracks are empty.

Based on commit b5e4eeb and used with Opencast 3.2.

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/48

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)

Somehow not all data is exported. It is restricted to a start and end-time somehow.

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/21

Originally reported by: Julian Kniephoff (Bitbucket: JulianKniephoff, GitHub: JulianKniephoff)

Currently, only one annotation can be in "add a comment"-mode. When I initiate commenting an annotation (either by the "speech bubble"-button or by the commenting shortcut) while working on a comment for another annotation, I will lose what I have already written up to that point.

It is unclear to me, though, what the desired behavior should be:

• Do we annoy the user whenever they cancel editing a comment by any means possible?
  • i.e. also when they start creating another comment, which would then fail?
• Do we just allow multiple WIP comments and let them clutter the interface?

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/41

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)

If more than 3 annotations are at the same time they are printed above each other and might be shown in the track above.

So more that 3 annotations at the same time should be displayed differently. There should be probably the first annotation and a triangle icon that indicates that there are more annotations at this time. Maybe a number could show the amount of hidden annotations.

If the user hovers the triangle a bubble could come up showing the hidden annotations.

If the user clicks on the triangle the tracks height is adapted so that all annotations can be shown.

One specific label can only be available at a time once. If it is added multiple times only the label with the longest duration will remain.

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/31

Originally reported by: Julian Kniephoff (Bitbucket: JulianKniephoff, GitHub: JulianKniephoff)

When there are users without an email address (i.e. their email address is NULL in the users table), the export throws an exception:

java.lang.Error: null must not be wrapped in a some
  at org.opencastproject.util.data.Option.some(Option.java:193)
  at org.opencastproject.util.data.Option$1.fmap(Option.java:209)
  at org.opencastproject.util.data.Option.map(Option.java:57)
  at ch.entwine.annotations.endpoint.AbstractExtendedAnnotationsRestService.writeExport(AbstractExtendedAnnotationsRestService.java:1899)
  at ch.entwine.annotations.endpoint.AbstractExtendedAnnotationsRestService.access$1200(AbstractExtendedAnnotationsRestService.java:105)
  at ch.entwine.annotations.endpoint.AbstractExtendedAnnotationsRestService$46.write(AbstractExtendedAnnotationsRestService.java:1851)
  at org.apache.cxf.jaxrs.provider.BinaryDataProvider.writeTo(BinaryDataProvider.java:107)
  at org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor.serializeMessage(JAXRSOutInterceptor.java:248)
  at org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor.processResponse(JAXRSOutInterceptor.java:139)
  at org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor.handleMessage(JAXRSOutInterceptor.java:78)
  at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)
  at org.apache.cxf.interceptor.OutgoingChainInterceptor.handleMessage(OutgoingChainInterceptor.java:78)
  at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)
  at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:110)
  at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:98)
  at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:423)
  at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:139)
  at org.apache.cxf.transport.servlet.AbstractCXFServlet.invoke(AbstractCXFServlet.java:142)
  at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:179)
  at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:108)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:575)
  ...

To quote @mtneug (see #21):

This happens because Option with the user id (a some value) is mapped to the E-Mail address, which is null in AbstractExtendedAnnotationsRestService.java line 1899.

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/37

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)

Use ACL actions to restrict the access:
https://docs.opencast.org/develop/admin/configuration/acl/#additional-acl-actions

Suggestion would be to use "annotation" and "annotation-admin" as custom actions.

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/3

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)

compare to #18 but not for export but print

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/19

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)

If UI elements are hidden, the available space is not used.

The remaining UI elements should make better use of the free UI space

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/23

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)

There should be UI templates to switch between different work modes:

• Fullscreen of Timeline
• Switching the timeline and the new annotation area

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/24

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)

if the loop controller is activated the loops are aligned to the current playtime, which results in the problem that the first loop has not the expected loop duration.

Loops should start at the video beginning and only the last loop might be shorter.

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/26

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)

In Opencast /info/me.json provides all neccessary user information.

This data should be used instead of the login dialog if it is available.

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/2

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)

Tracks should have the option to be shared with an Opencast group.

The groups that could be selected for sharing should have the following properties:

• the current user (if only with annotation actions) should be part of the group.
• the groups should have annotate actions on the current recording

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/14

Originally reported by: Julian Kniephoff (Bitbucket: JulianKniephoff, GitHub: JulianKniephoff)

The tool currently filters the tracks of the media package it receives by certain flavours. Instead we should probably use tags for that. We could look for engage-download (or engage-streaming if/when we support streaming ;)) or invent our own tag. (I have no idea how we would get that tag onto videos yet, though. #opencastnoob)

This would also make the tool work with the fast Opencast testing workflow, which it currently doesn't because the flavours that this creates are ignored by the filtering mentioned above.

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/36

Originally reported by: Julian Kniephoff (Bitbucket: JulianKniephoff, GitHub: JulianKniephoff)

It should not be necessary to explicitly type index.html as part of the URL for the annotation tool. It actually is not strictly necessary in the sense that /annotation-tool is redirected to /annotation-tool/index.html, but during this redirection, the URL parameters, which are currently used to pass the media package ID to the tool, are forgotten.

While we are at it, we might also rethink the way the tool gets ahold of the ID and the video itself.

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/45

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)

Currently elements in the print view overlap or are not formated as expected.

The University of Münster will provide a mock-up how the print should look like.

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/28

Originally reported by: Matthias Neugebauer (Bitbucket: mtneug, GitHub: mtneug)

The about dialog has a missing string:

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/49

Originally reported by: Julian Kniephoff (Bitbucket: JulianKniephoff, GitHub: JulianKniephoff)

This is only an idea at the moment since I don't know what all this would entail, but here are some stray thoughts to delineate what I am driving at:

It is not nice that we either have to use a specific version of Opencast to work on things that touch the backend,namely the one that is currently stated in the pom.xml of the backend components, or we have to change said pom.xml like I did in pull request #6. The users even might have to change that version, too, because they might use yet another Opencast version. (Specifically they probably run a non-snapshot version, right?)

The fact that we have to physically copy the backend components into Opencast is not all that nice as well. I currently have them symlinked, which might actually be good enough. This is more important for the developers convenience as it is for the users' because they typically only do this once (in a while). However, simplifying this one time setup would not hurt the users, either. ;) The least we could do is provide better documentation for the development workflow with the backend and maybe even a script or Grunt task to simplify it.

Related to that, there is also the question of whether we really want a built version of the frontend in the repository, which should normally not contain any build artifacts, in my opinion. Maybe this is worth another issue, though.

There might be more and I will try to update this issue as I learn more, because honestly I don't know enough about Grunt, Maven and OSGi at the moment. ;)

Thoughts and opinions are welcome. :)

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/35

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)

Include a lib that will allow a translation of the annotation tool.

Use the lib to translate every text in the UI.

Use Crowdin for the translation of the UI.

Add configuration to pull new translations from Crowdin automatically.

Make sure to use the full qualified language identifiers (like en-US) as we have several users in the Opencast community that use sub-languages.

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/29

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)

Make sure the loop controler checkbox is focused for the keyboard. Use the spacebar to activae the checkbox: the checkbox is checked, but the loop-controller settings do not show up. Probably this is triggered with a "clicked" and not with "checked" event.

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/42

Originally reported by: Daniel Ebbert (Bitbucket: danielebbert, GitHub: danielebbert)

Changing the visible tracks using the track management leads to the correct tracks being visible, but without annotations. The tracks are empty.

Based on commit b5e4eeb and used with Opencast 3.2.

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/47

Originally reported by: Daniel Ebbert (Bitbucket: danielebbert, GitHub: danielebbert)

Upon clicking on the delete button the confirmation pop-up shows up. When I then click on "delete" the annotation is being deleted but the pop-up stays visible. I have to click on "cancel" after that to close the pop-up.

Based on commit b5e4eeb and used with Opencast 3.2.

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/46

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)

A user with the ACL action annotation-admin should see all annotations in all tracks, except private tracks of other users.

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/10

Originally reported by: Julian Kniephoff (Bitbucket: JulianKniephoff, GitHub: JulianKniephoff)

Switching to "edit mode" in the category browser does not show the controls to add new ones. Editing existing ones still works, though. (At least for me. @rrolf ?)

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/44

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)

Admins should be able to delete categories and labels, even if they have been created by other admins.

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/30

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)

A keyboard shortcut should set the OUT time of the last created annotation to the current play-time. Mabe CTRL+o would be an option for this.

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/9

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)

Tracks marked as public are not viewable to other users

• Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/12