Systems Frontend issueshttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues2024-01-09T16:18:45+01:00https://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/844Deleting assets if still in use?2024-01-09T16:18:45+01:00Hansen, ChristianDeleting assets if still in use?There is no information in the asset store if an asset is in use, and you can delete it without any warning. If you open a related timeline afterwards, you only get an initial warning, that no record was found for file X (screenshot belo...There is no information in the asset store if an asset is in use, and you can delete it without any warning. If you open a related timeline afterwards, you only get an initial warning, that no record was found for file X (screenshot below), and the whole annotation won't be loaded (including comments/tags/...).
<br />
<br />
![Bildschirmfoto_2021-10-08_um_18.15.37](/uploads/3b4e8d5e300957acd205eef3aa985a37/Bildschirmfoto_2021-10-08_um_18.15.37.png)
<br />
<br />
So, we need some delete-handling for assets that are in use. An idea is to replace the deleted asset with an message like "file was deleted". So if there were some comments under this asset (= annotation) they could still exist and be reachable.Usability UX Improvementshttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1000projects: Card overlay handling on touch devices?2024-01-09T16:03:17+01:00Hansen, Christianprojects: Card overlay handling on touch devices?How do we handle card overlays on touch devices when hovering the cards is not an option? Open the overlays when touching the preview image/thumbnail?
![Bildschirmfoto_2021-10-29_um_17.40.21](/uploads/5023f0f319a883d2d1a5b846e0c634db/Bil...How do we handle card overlays on touch devices when hovering the cards is not an option? Open the overlays when touching the preview image/thumbnail?
![Bildschirmfoto_2021-10-29_um_17.40.21](/uploads/5023f0f319a883d2d1a5b846e0c634db/Bildschirmfoto_2021-10-29_um_17.40.21.png)Feature: Timeline Viewerhttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/2059loop specific timerange2023-07-03T13:44:58+02:00Hansen, Christianloop specific timerangeHansen, ChristianHansen, Christianhttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1137How to display annotations which overlap with videos in the Timeline Viewer?2023-06-28T16:39:53+02:00Rittershaus, DavidHow to display annotations which overlap with videos in the Timeline Viewer?If a special way of sharing a Timeline ("view only"/"article mode" or even as static website) should replace MoSys-Grids (#843) we would need a solution for how we want to display annotations which overlap with a video on the Timeline an...If a special way of sharing a Timeline ("view only"/"article mode" or even as static website) should replace MoSys-Grids (#843) we would need a solution for how we want to display annotations which overlap with a video on the Timeline and mostly refer to a specific moment in the video (and which are not displayed in the Timeline Viewer).
From my point of view it doesn't make sense in that case if you have to "open up" the Post-Annotator, especially if it is supposed to be an "exported" static website or something like that (the viewer is probably not supposed to add annotations). Maybe there could be something like a reduced version of the Post-Annotator (a "view only" or a "view and comment only" Post-Annotator) that you can access if a Timeline is shared with you, maybe even in an overlay and not on a new screen.Feature: Timeline Viewerhttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1753rethink filter for speech-to-text annotations2023-06-28T16:35:15+02:00Milan Gressrethink filter for speech-to-text annotationsFeature: Data Viewshttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1838Integrate text data from ML pipeline, possible subtitles feature to video player2023-06-22T15:15:41+02:00Hansen, ChristianIntegrate text data from ML pipeline, possible subtitles feature to video playerFeature: Data ViewsHansen, ChristianHansen, Christianhttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1832Swimlane feedback Helena: cluster issues and overall usability feedback2023-02-02T15:42:18+01:00Rittershaus, DavidSwimlane feedback Helena: cluster issues and overall usability feedbackWe had a longer Zoom meeting with Helena and she was sharing a bit of her impressions working with the new and old swimlane und I think we should consider her feedback. First, because she is using the swimlane intensly for the labeling p...We had a longer Zoom meeting with Helena and she was sharing a bit of her impressions working with the new and old swimlane und I think we should consider her feedback. First, because she is using the swimlane intensly for the labeling process with wizai. Second, she first went through a detailed annotation process with the previous version of the swimlane and now again with the vortanz version.
I already tried to translate some of the feedback into more concrete issues. But the rest of the feedback requires maybe a bit more discussion.
Although she didn't say it like that, it seems as if working with the previous swimlane version was a bit more convenient for her. But she also framed a lot as her personal preference and also mentioned that she just got used to few things.
She is **mostly struggling with the annotation clusters**. For her it seems to be very difficult to find the right zoom level. When she has zoomed in to see each annotation and then adds a new annotation which is a bit too "close" to an existing one, they immediatley build a new cluster and she first has to zoom in again to keep on working (e.g. to rearrange the new annotation etc.).
**Compared to the previous version the clusters makes it also more difficult for her to get an overview because the cluster is hermetic. **Since she has quite a few annotations in her videos which are pretty close to each other, there are often more or less 1-3 larger "hermetic" clusters with only a few single annotations.
We've been looking more closly at the density lane together with her and she thinks it's helpful to get the overview, close to the overview provided by the previous swimlane. But on the other hand, there is no preview for the annotations and you can't select them in the density lane(s), so she recognised that it does not exactly do what she is looking for (or missing compared to the previous version).
I was referring to performance issues with the previous swimlane version, but Helena has quite the opposite experience: from the overall user experience the previous version was more fluent (might also be related to video playback and buffering, see also #1830). However, Christian and I were wondering how big the difference really is between rendering a density lane and making the annotations "available" (preview, select, move etc.)?
In terms of overview she sort of preferred that the annotations in the previous version were all rendered in one lane as grey dots and bars (partly overlapping and creating sort of a density vizualisation as well). The advantage she sees is the slim and dense layout of each lane, which also helps to get an overview when you have several users. As mentioned above, the new density lanes partly offers a similar overview but not exactly. Form her point of view, it was better that annotations with and without duration were rendered in the same lane when it was collapsed. In the vortanz version you can't compare the lanes of 2 or more users if they used ranged annotations (except in the multi user density lane). On the other hand, the expanded waterfall version is also not a perfect solution from my (david) point of view.
Last but not least she mentioned that she personally preferred the small grey dots and slim bars, also in terms of overview, while the triangles appear a bit clumpsy to her (the density lanes seemd more appealing to her compared to the normal annotation lane in the vortanz version). Here I have to mention, that there is a difference in regard to mobile use and there was also some negative feedback regarding the dots in the previous version in terms of precision. I also mentioned this in the exchange with Helena and she can understand both aspects and again emphasised that she got quite used to the previous version and that it might be her personal preference. I (david) can also imagine that some of the "clumpsy" feeling comes from her issues with the clusters. At the same time I have to agree that the annotations and lanes could look a bit slimmer and more compact.
@maximilian.mittermei: just sharing it in this form for now. I think the clusters are somehow the most critical usability issue that should be addressed (maybe with a new issue). Other aspects could be discussed.Mittermeier, MaximilianMittermeier, Maximilianhttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1787Shared timelines: Can I remove timelines from other creators (with full access)?2022-11-18T13:04:35+01:00Hansen, ChristianShared timelines: Can I remove timelines from other creators (with full access)?I'm cleaning up my account at the moment, and I have full access to some timelines that were shared with me. It seems that I can delete them (I haven't tried it), and if so, we should prevent that. Only the creator should be able to dele...I'm cleaning up my account at the moment, and I have full access to some timelines that were shared with me. It seems that I can delete them (I haven't tried it), and if so, we should prevent that. Only the creator should be able to delete its own timeline, otherwise some massive damage could happen in my opinion.https://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1755Swimlane: software generated annotations should also get a separate track2022-11-14T13:40:19+01:00Rittershaus, DavidSwimlane: software generated annotations should also get a separate track@maximilian.mittermei: maybe this could be considered in #1734? Since adding an automatic transcipt will make it more difficult to keep an overview we should make use of the possibilities of the swimlane and might handle a "generator" (s...@maximilian.mittermei: maybe this could be considered in #1734? Since adding an automatic transcipt will make it more difficult to keep an overview we should make use of the possibilities of the swimlane and might handle a "generator" (software; whisper) like a "creator" with a seperate lane?Feature: SwimlaneMittermeier, MaximilianMittermeier, Maximilianhttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1687Swimlane: default size depending on annotations?2022-10-27T09:07:11+02:00Rittershaus, DavidSwimlane: default size depending on annotations?I still think it's a bit weird that I always have to adjust the the swimlane size if I have no annotations with duration (and no other lanes). The video is way too small to work with it while there is a lot of black/white space in the sw...I still think it's a bit weird that I always have to adjust the the swimlane size if I have no annotations with duration (and no other lanes). The video is way too small to work with it while there is a lot of black/white space in the swimlane by default.
![Bildschirmfoto_2022-10-17_um_09.52.56](/uploads/104e90f114be5fc6c6fab2facd544a12/Bildschirmfoto_2022-10-17_um_09.52.56.png).
I also see the issue that users might not understand where they can find their annotations with duration if you can't see that lane by default or if it's so small, so that you can only see one or two annotations with duration. This might be tricky coding wise, but I'm wondering if the default size of the swimlane could depend on amount of annotations with duration? If there are no annotations with duration the second lane could be quite small, only offering enough space to drop an annotation from the lane above etc.Feature: SwimlaneMittermeier, MaximilianMittermeier, Maximilianhttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1701Simple bounding box annotations should not target the Timeline2022-10-19T12:07:55+02:00Koch, AntonSimple bounding box annotations should not target the TimelineThe text annotations we were using so far did target the parent Timeline with an absolute timestamp so that a text annotation can correlate with one or more videos simultaneously.
I think this is no longer useful for bounding boxes, as ...The text annotations we were using so far did target the parent Timeline with an absolute timestamp so that a text annotation can correlate with one or more videos simultaneously.
I think this is no longer useful for bounding boxes, as they result from analysing one specific video. Layered on top of a second camera perspective, the annotation is useless.
This is different for tracking as people can be seen from different angles, but automatically identifying someone is impossible with our current tracking solution (id by order of appearance, no unique identifier)... We'll get to that later.Feature: Data Viewshttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1141Bring back Live-Annotator in frontend2022-10-19T11:06:25+02:00Rittershaus, DavidBring back Live-Annotator in frontendI think it would be good to again offer the option to live-annotate a Timeline.
You need some knowledge, otherwise you won't understand what it does and how it is supposed to work. If the annotations are visible in the Timeline Viewer ...I think it would be good to again offer the option to live-annotate a Timeline.
You need some knowledge, otherwise you won't understand what it does and how it is supposed to work. If the annotations are visible in the Timeline Viewer that's maybe not such a big thing. Nevertheless, I think it would be important to add some information about how it is supposed to work. If you access the Live-Annotator for the first time there could be a dialog with a few infos and a "don't show again" option?! Or something similar. Without such "helpers" I would not bring it back. We can also discuss if it should be a tab in the top bar like it was before or if it's just just a button in the Timeline Viewer or on the projects page (and main menu).Feature: Timeline Viewerhttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1067Position file on Timeline: "after last file" should be replaced by "after oth...2022-10-19T11:06:10+02:00Rittershaus, DavidPosition file on Timeline: "after last file" should be replaced by "after other file"I think when #1063 is addressed, it would be good to revise the current option "after last file" at the same time.
It would be better if you can select after which file that is already linked to the timeline you want to position the fil...I think when #1063 is addressed, it would be good to revise the current option "after last file" at the same time.
It would be better if you can select after which file that is already linked to the timeline you want to position the file.
During the revision, issue #1009 could be considered.Feature: Timeline Viewerhttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/988"return to timeline" button in timeline navigation2022-10-19T10:58:53+02:00Hansen, Christian"return to timeline" button in timeline navigation"Still wondering if a "return to Timeline" would be sufficient? Not sure, but when I'm in the Post-Annotator (both on mobile and desktop) it feels a bit as if I have a file open and before I want to live-annotate or see/edit the timeline..."Still wondering if a "return to Timeline" would be sufficient? Not sure, but when I'm in the Post-Annotator (both on mobile and desktop) it feels a bit as if I have a file open and before I want to live-annotate or see/edit the timeline details I would return to the Timeline overview anyway. That's really subjective but for me it feels more as if I would need a "return to overview" button (or an option to "close" the post-annotator)."
– @david.rittershausFeature: Timeline Viewerhttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1064Mobile/Tablet-Android. Voice note tool tip: "Keep pressed to talk" is misleading2022-10-19T10:52:12+02:00Isabela DimarcoMobile/Tablet-Android. Voice note tool tip: "Keep pressed to talk" is misleadingNot urgent! For commenting with voice notes, tool tip says Keep pressed to talk. When pressing nothing happens, only tool tip appears, the actual movement that triggers the recording is a tap, not a press.
Also, when recording voice an...Not urgent! For commenting with voice notes, tool tip says Keep pressed to talk. When pressing nothing happens, only tool tip appears, the actual movement that triggers the recording is a tap, not a press.
Also, when recording voice annotation, icon turns red which feels like it's not recording which makes you want to double-check and loose the voicenote.
![rn_image_picker_lib_temp_71884372-0466-4d77-a1ea-adf2df0482b6](/uploads/7466b9deb110820c47a9350909368784/rn_image_picker_lib_temp_71884372-0466-4d77-a1ea-adf2df0482b6.jpg)3.0.0-beta Releasehttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/83bookmarking2022-10-19T09:39:52+02:00Rittershaus, Davidbookmarkinginstead of highlighting something it would be great to set a bookmark(-annotation) and then have a list with all bookmarks to quickly go back to these momentinstead of highlighting something it would be great to set a bookmark(-annotation) and then have a list with all bookmarks to quickly go back to these momenthttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1683Bounding boxes: add "No people could be detected in this screen" indicator...2022-10-18T14:56:53+02:00Hansen, ChristianBounding boxes: add "No people could be detected in this screen" indicator......when not a single person was detected? Does this make sense?...when not a single person was detected? Does this make sense?Feature: Data Viewshttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/879post-annotator. Swimlane button behavior2022-09-15T14:58:09+02:00Böhm, Jeanpost-annotator. Swimlane button behaviorWhen clicking on the icon next to the custom-video-bar the swimlane appears.
![Screenshot_2021-10-14_at_16.07.13](/uploads/830bdc4671d0b0bd8eb1fe76ac2fa038/Screenshot_2021-10-14_at_16.07.13.png)
Now when I want to close the swimlane I...When clicking on the icon next to the custom-video-bar the swimlane appears.
![Screenshot_2021-10-14_at_16.07.13](/uploads/830bdc4671d0b0bd8eb1fe76ac2fa038/Screenshot_2021-10-14_at_16.07.13.png)
Now when I want to close the swimlane I have to click a smaller close-icon to close the swimlane again. The custom-video-bar now is 100% width
![Screenshot_2021-10-14_at_16.07.19](/uploads/16dce84230202e5bd5a576f1401dc37a/Screenshot_2021-10-14_at_16.07.19.png)
I accidentally entered the fullscreen mode when I was trying to close the swimlane again, I expected a toggle button next to the custom-video-bar. For me that felt more intuitive.
Is there a reason why it's not a toggle? The same could be used for the annotaions icon button.Feature: SwimlaneMittermeier, MaximilianMittermeier, Maximilianhttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1635AI Accuracy Feature: Target video reference in backend2022-09-15T10:40:22+02:00Milan GressAI Accuracy Feature: Target video reference in backendThe Accuracy Feature #1630 currently only allows to reference videos that are on the same timeline.
We would prefer instead that you can just upload any (video) asset or select one of your (video) assets and compare that to the current ...The Accuracy Feature #1630 currently only allows to reference videos that are on the same timeline.
We would prefer instead that you can just upload any (video) asset or select one of your (video) assets and compare that to the current video.
But we need some sort of link between the source video timeline and the target video… so the ACL works and the asset can be retrieved
So, maybe we need a different way to link the video to the timeline or just place the target video as an annotation on the source video?
Will discuss this with Anton when he is backFeature: Data Viewshttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1514Video should pause on click of text field and un-pause when annotation has be...2022-06-02T16:27:19+02:00Isabela DimarcoVideo should pause on click of text field and un-pause when annotation has been enteredWhen writing an annotation the video just keeps running. This usually means users miss parts of the video and have to go back to the point where they left at. What I've seen users do is just pause the video altogether and move from one p...When writing an annotation the video just keeps running. This usually means users miss parts of the video and have to go back to the point where they left at. What I've seen users do is just pause the video altogether and move from one point they want to comment on to the other on the video play bar with their mouse.
I wouldn't say this behaviour is critical, but I've personally wondered about this before. Is there any background on this decision? How do you @david.rittershaus for example add long annotations? And generally, what are your thoughts on this? @jean.boehm2 @christian.hansenUsability UX Improvements