Systems Frontend issueshttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues2024-01-19T12:57:48+01:00https://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/44live/post annotators: arrow key navigation in vocab list is broken2024-01-19T12:57:48+01:00Jenett, Florianlive/post annotators: arrow key navigation in vocab list is brokenbefore it was possible to move between terms in the vocabs using arrow keys…before it was possible to move between terms in the vocabs using arrow keys…https://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/2200input field -> voice input: add "running process" indicator (spinner) after s...2023-12-13T14:53:08+01:00Hansen, Christianinput field -> voice input: add "running process" indicator (spinner) after stopping a record until record is readySometimes between record stop and having access to this record in the input field (= submit/clear buttons appear) some seconds go by without any indicator, that a converting process is running in the background. This confused me several ...Sometimes between record stop and having access to this record in the input field (= submit/clear buttons appear) some seconds go by without any indicator, that a converting process is running in the background. This confused me several time, because I thought the record broke in some way. That's why we need an "something is happening" indicator as done in the magic menu.https://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1780Does it make sense to change the start time of a live annotation if the annot...2022-11-17T12:42:44+01:00Hansen, ChristianDoes it make sense to change the start time of a live annotation if the annotations won't be moved as well?In my opinion this edit feature can be disabled to prevent misunderstandings if you do not read the text properly:
<br /><br />
![Bildschirmfoto_2022-11-16_um_19.55.50](/uploads/ac1ba386e7f27fc75a902a344a0cf3c3/Bildschirmfoto_2022-11-16_...In my opinion this edit feature can be disabled to prevent misunderstandings if you do not read the text properly:
<br /><br />
![Bildschirmfoto_2022-11-16_um_19.55.50](/uploads/ac1ba386e7f27fc75a902a344a0cf3c3/Bildschirmfoto_2022-11-16_um_19.55.50.png)https://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/947Live Annotate: could previous annotations remain visible?2022-02-24T17:47:26+01:00Rittershaus, DavidLive Annotate: could previous annotations remain visible?I'm really not sure about this suggestion, but I was wondering if the Live Annotator could still show the annotations one recently added?
- You still see the annotations you added if you leave the Live Annotator and resume (just a mome...I'm really not sure about this suggestion, but I was wondering if the Live Annotator could still show the annotations one recently added?
- You still see the annotations you added if you leave the Live Annotator and resume (just a moment) later.
- Especially as long as the Timeline Viewer for now only displays videos it could be nice to revisit some of your more recent live annotations, especially as long as you did not yet upload the corresponding video.
Maybe in that regard in makes sense to somehow model in the data that annotations were added "live" or using the live annotator? Would be interesting anyway both for making that visible in the interface and for the evaluation of the data.
I created a small photoshop mockup, just to visualise that I have something in mind that should ideally not mess up the purity of the live annotation interface
![Bildschirmfoto_2021-10-26_um_09.07_Kopie](/uploads/ca08a81835fd7c46feeeebecda661667/Bildschirmfoto_2021-10-26_um_09.07_Kopie.jpg)
The stream with previous annotations could be limited to the bottom (half faded) and anyway be "pushed" off the screen as soon as new annotations fill the screen. Really not sure though.https://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/498live annotation, mosys, "no annotations yet"2021-01-09T09:32:03+01:00Jenett, Florianlive annotation, mosys, "no annotations yet"From the team in Canada, Michael English
> I have a question about the Live Annotation – because when we run a Livestream test, adding Live Annotations, and then insert that session into the Mosys grid it returns “no annotations yet” (s...From the team in Canada, Michael English
> I have a question about the Live Annotation – because when we run a Livestream test, adding Live Annotations, and then insert that session into the Mosys grid it returns “no annotations yet” (see attached screencap).
>
> Is this something we are doing wrong, or perhaps a known issue already?
![Screen_Shot_2020-06-12_at_10.29.42_AM](/uploads/1655357afb5691d48cf78a589c5a067c/Screen_Shot_2020-06-12_at_10.29.42_AM.png)Koch, AntonKoch, Antonhttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/245vocabulary: "hide selected vocabularies" button breaks input field2020-05-08T13:58:57+02:00Hansen, Christianvocabulary: "hide selected vocabularies" button breaks input fieldAdvanced VocabulariesHansen, ChristianHansen, Christianhttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/286add predicate functionality to annotator entry field2019-11-19T17:24:58+01:00Koch, Antonadd predicate functionality to annotator entry fieldhow about adding a bit of semantic vocab to the post annotator input field?
- if first key is a #, purpose is "tagging"
- if first key is a ?, purpose is "questioning"
- if first key is a !, purpose is "identifying" (or rather "highligh...how about adding a bit of semantic vocab to the post annotator input field?
- if first key is a #, purpose is "tagging"
- if first key is a ?, purpose is "questioning"
- if first key is a !, purpose is "identifying" (or rather "highlighting"?)
- if first key is a @, purpose is "classifying"
- if first key is a =, purpose is "describing"
- if first key is a :, purpose is "commenting"
- paste a url and the body purpose switches to "linking"
- entering hashtags within the annotation text creates "tagging" type annotations referring to the main freetext body annotation (not the timeline!)
in addition one should be able to set the current default predicate (and also change it when editing annotations)
the whole edit/setting workflow should be as unobtrusive as possible though. shouldn't be mandatory to decide on this, default is always "commenting"https://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/33keyboard layout display2019-03-04T21:45:24+01:00Koch, Antonkeyboard layout displaymight be nice to have something like this some day:
https://dev.to/gksander/a-keyboard-display-using-css-grid-2k2n
https://codepen.io/attilahajzer/pen/kydqJmight be nice to have something like this some day:
https://dev.to/gksander/a-keyboard-display-using-css-grid-2k2n
https://codepen.io/attilahajzer/pen/kydqJhttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/75some kind of scene / subscene structure for annotations2019-03-04T21:44:56+01:00Rittershaus, Davidsome kind of scene / subscene structure for annotationsideally in live and post annotatorideally in live and post annotatorKoch, AntonKoch, Antonhttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/77key event handling is a mess2019-03-04T21:39:43+01:00Koch, Antonkey event handling is a messone million ways to catch keys... choose one!one million ways to catch keys... choose one!Koch, AntonKoch, Anton