# Opencast Annotation Tool (OAT) - Meetings | References | Link | | -------- | -------- | | GitHub OAT | [opencast/annotation-tool](https://github.com/opencast/annotation-tool) | | Mailinglist OAT | [Google Groups](https://groups.google.com/a/opencast.org/g/annotation-tool) | | Opencast Community Calendar | [Google Calendar](https://calendar.google.com/calendar/embed?src=opencast.org_tje2fm34ernnbm0f9saiogp8g0%40group.calendar.google.com&ctz=Europe%2FAmsterdam) | | Use Cases & Feature list (Annotation Tools) | [Public collaboration list](https://pad.uni-muenster.de/RUlu61FsR9u4w2Eo-rdZsg?both) | | Meeting Room | Room | Password | Schedule | | -------- | -------- | -------- | -------- | | [meet.opencast.video](https://meet.opencast.video/) | Opencast Room - 1 | welcome | 1st Tuesday, 3-4 pm CE(S)T every second even month (= February, June, October). Additional meetings can be requested via the [mailinglist](https://groups.google.com/a/opencast.org/g/annotation-tool). | | Time zone info| | --- | | CET: UTC+1 [= last sunday of october till last sunday of march] | | CEST: UTC+2 [= last sunday of march till last sunday of october] | --- ## Upcoming meeting ### 2024-06-04, 3 pm CEST #### Agenda Feel free to add your topic to the list: - ... --- ## Current Tasks - [ ] All: Community Test of merged version, document issues in github (the test plan items could be used as a ticket template) - [ ] All: Check if open issues are already resolved in current merge build ### Continuous Tasks - Got any existing user manuals / documentation? Share it in [ticket #587](https://github.com/opencast/annotation-tool/issues/587). The manuals will be published in the [github wiki](https://github.com/opencast/annotation-tool/wiki/Resources). - Add use cases and features to the new [feature list](https://pad.uni-muenster.de/RUlu61FsR9u4w2Eo-rdZsg?both) for annotation tools in general (could be used, if a next generation annotation tool is build from bottom up) - Are you aware of any video annotation tools like OAT? Please add them: [List of annotation tools](https://pad.uni-muenster.de/s/znLcY72jf) --- ## Past meetings ### 2024-01-06, 3 pm CET Participants: Julian Kniephoff, Till Rauterberg (UM), Manuel Oellers (UM) - New git branch structure was introduced - next: stable next version - stable: stable previous version - master: dev (rolling release) - release: master -> next -> stable - Deployment of an official public test instance with test users ([issue#583](https://github.com/opencast/annotation-tool/issues/583)) - Auto deploy / Ansible - Stable.opencast.org? - Julian requests - Next steps - Testing - Cleaning up open github issues - Change of schedule - once per quarter - Course contexts - ... ### 2023-12-06, 3 pm CET *Cancelled* ### 2023-10-10, 3 pm CEST Participants: Manfred Holodynski (UM), Julian Kniephoff (ELAN e.V.), Till Rauterberg (UM), Manuel Oellers (UM), Matthias Neugebauer (UM) #### Release and versioning policy - [Initial proposal](https://groups.google.com/a/opencast.org/g/annotation-tool/c/Y2dPpw8UCj0/m/0O_Uso9OAAAJ) - Current model: Rolling releases - One version of annotation tool (stable master) - Features in branches, reviewed and merged - New Release model proposal: Versioning - Controlled release of versions at specific points in times - Releases will be quality tested with the community - Establish workflows - Mutual roadmap? - 3 branches, kind of: - stable/legacy: maintenance phase, still supported - main/next/staging: current support phase - features/develop #### State of review - Establish new release model ### 2023-08-01, 3 pm CEST Participants: Manuel Oellers (WWU), Matthias Neugebauer (Educast.nrw), Julian Kniephoff (ELAN e.V.), Kasia Potocka (TU Wien), Till Rauterberg (WWU), Manfred Holodynski (WWU) **OAT Review** - Timeline yet unknown - Local test deployment by Arne - Will there be DB changes within the review? - Probably not - Migration path -> depends on the version - Deployment: Semester based rollout - Realistic timeframe October 23? **Presentation (DACH)** - Presentation of OAT at Opencast DACH (14/15 August 23) - Which version is deployed at the test env? - Which oc version is running? - Is the native OC13/14 patch included? - Topics - Feature introduction - Use cases? - Who would use the Community Version? - Were there internal requests for annotation tools? - How to use? - Embedding in LMS? ### 2023-07-04, 3 pm CEST Participants: David Graf, Manuel Oellers #### OAT Review - Due date: End of July 23? (ask Julian) - Presentation of OAT at [Opencast DACH](https://opencast.org/2023/05/15/dach-meeting-2023/) (14/15 August 23) - reviewed version? - use cases? - feature rewrite? - Migration to new oat version - Bern: February 24? - Münster: Q4/2023? ### 2023-06-06, 3 pm CEST *Postponed to the 4th of July* ### 2023-04-04, 3 pm CEST - OC Summit 2023 (Julian) - Perspectives for the OAT (Julian) - What does the future of the tool look like? - And what does that mean in concrete terms? - State of the Community Version (University of Münster) - Review in progress ### 2023-04-04, 3 pm CEST Participants: Julian Kniephoff (ELAN e.V.), Matthias Neugebauer (WWU), David Graf (Bern), Till Rauterberg (WWU), Manfred Holodynski (WWU), Manuel Oellers (WWU) #### OC Summit 2023 (Julian) - Report from the Opencast Summit 2023 [(Presentation and context)](https://groups.google.com/a/opencast.org/g/annotation-tool/c/uBNhAFhwk0c) #### Perspectives for the OAT (Julian) Discussion: What does the future of the tool look like? And what does that mean in concrete terms? - Related to the discussion of the summit: - how is the demand in the community? - list of annotation tools to evaluate - h5p is a different use case - Funding for future (e.g. rewrite) - could be difficult without strong backing - there should be one university leading the way - a possible rewrite is an obstacle for getting users on board - Bern would accompany the way (but not lead) - Goal: Build a community around the OAT? - How to promote the OAT? - How could a community buildung be done? - Ideas: - [VIGOR](https://vigor.studiumdigitale.uni-frankfurt.de/) and [CLIPSS](https://www.uni-due.de/clipss/) - Collect: - Who is using opencast? - Which videos are hosted? - Elaborate use cases in subject fields (Therapy, Psychology, Medicine, German studies, ...) - Are the use cases for annotation tool in these opencast instances? - What other Annotations Tools are in productive use? - e.g. see [german list of annotation tools shared](https://pad.uni-muenster.de/s/znLcY72jf) - How would a future annotation tool look like? / Should there be a rewrite? - Basic features would require roughly estd. 200-300k fundings - Related to discussions from [2022-03-24-10-am-CET](#2022-03-24-10-am-CET) and [2022-04-25-2-pm-CEST](#2022-04-25-2-pm-CEST) - A rewrite makes sense from a technical point of view ### 2023-02-07, 3 pm CET - Community Test of merged version - [test plan - german version](https://uni-muenster.sciebo.de/apps/onlyoffice/s/vbmsXj9sKQFSGtY?fileId=3030444926) - [test data (categories, annotation templates) - download (zip)](https://uni-muenster.sciebo.de/s/vbmsXj9sKQFSGtY/download?path=%2FCommunity%2FTestdaten&files=testdaten.zip) - Discussed open tickets / github issues (needs to be continued in tickets) - [595](https://github.com/opencast/annotation-tool/issues/595) (OAT compatibility with OC 13) - scale deletion behaviour in [issue #540](https://github.com/opencast/annotation-tool/issues/540) - Community Todo: Check if any open issues are already resolved in current merge build - New time schedule? Vote: Current schedule should be maintained ### 2022-12-06, 3 pm CET Feel free to add your topic to the list: - Community Test of merged version ([test plan - german version](https://uni-muenster.sciebo.de/apps/onlyoffice/s/vbmsXj9sKQFSGtY?fileId=3030444926)) - The merged version is close to release, so we introduce some ways to test it and give feedback - Context-feature - We continue to discuss the concept and implementation details - Research with the OAT (current use case @ WWU - presentation) --- ### 2022-10-04, 3 pm CEST Participants: Sarah Schotemeier, Manuel Oellers, Manfred Holodynski, Till Rauterberg, Matthias Neugebauer ***OAT - advanced use cases in higher education*** - Feedback for students (Speech/Rhetoric/Terms/comprehensibility...) - DSHS Köln **TBD** - An own (not public) category shared with all users cannot be edited by the user with access level "ANNOTATE" (classified as bug not feature; fixed) - Deleting scale that is used in category - prohibit, user needs to remove scale from category first - mark as deleted and - still show with previously associated resources or - also remove scale from all associated categories MH: if scale gets deleted, but category is still in use, this could be problematic SH: there should be at least a note that the scale is associated with categories TR: a public scale used in private categories might cause issues upon deletion This needs [to be discussed in ticket #540](https://github.com/opencast/annotation-tool/issues/540#issuecomment-1267126294). **New toggable options?** - Toggle annotation-options area - issue with overflow and tabs - integrate in menu as toggable options instead?  Discussion: As the feature is related to video player it should be integrated in another area as its blocked from the viewport (scroll if larger label lists) and also not visible in annotation template/questionnaire-mode - Variant I:: Integrate in menu - Variant II: Integrate as/in tab (compareable to loop control) [prefered] - Variant III: Leave it where it is #### Annotation user manual WWU introduced a user manual (partially outdated) and accepted the request to share the file which could be found in [ticket #587](https://github.com/opencast/annotation-tool/issues/587). Note: The community manual will also be added to the [github wiki](https://github.com/opencast/annotation-tool/wiki/Resources). #### Temporary Demo instance (WIP - Community Version) There is a temporary demo instance where WIP-drafts of merged Community Version (WWU) will be showcased in near future. Later on we will announce a review-phase through mailing list. The Community Version is still a WIP and not all known bugs are fixed yet. **Still in progress:** - Annotation template-feature - Context-feature - Fix of further known bugs **List of users** [username:password (OAT-ACL)] - oat-admin-1:oat-admin-1 (ANNOTATE, ANNOTATE_ADMIN) - oat-admin-2:oat-admin-2 (ANNOTATE, ANNOTATE_ADMIN) - oat-user-1:oat-user-1 (ANNOTATE) - oat-user-2:oat-user-2 (ANNOTATE) **Demo-Links:** To authenticate visit [login page](https://ocdev.uni-muenster.de/admin-ng/login.html) before visiting one of the following demo links to OAT. * [OAT-Demo: teacher, Series: OAT-Series-v1](https://ocdev.uni-muenster.de/annotation-tool/index.html?id=b7df0000-fd70-4e4b-9c91-033448684fc9) - anonymous: *not authenticated* (*none*) [does not load when not authenticated] * [OAT-Demo: Sintel, Series: OAT-Series-v1](https://ocdev.uni-muenster.de/annotation-tool/index.html?id=6a1dde84-bb70-4902-8027-35425c6ca46d) - anonymous: *not authenticated* (ANNOTATE) * [OAT-Demo: teacher v2, Series: OAT-Series-v2](https://ocdev.uni-muenster.de/annotation-tool/index.html?id=a8054ee5-8ce1-4873-92fa-871441782f07) - anonymous: *not authenticated* (*none*) [does not load when not authenticated] * [OAT-Demo: Big Buck Bunny, Series: *none*](https://ocdev.uni-muenster.de/annotation-tool/index.html?id=3d66e53a-a30e-402f-9401-39d6a65a0578) - anonymous: *not authenticated* (ANNOTATE_ADMIN, ANNOTATE) --- ### 2022-08-02, 3 pm CEST - Discussed changes from upcoming merge (WWU) - Demo instance will be prepared - Discussed quality assurance process / workflow and release model; proposal: - Rolling release model will be maintained - Main-Branch should contain working version with QA review - Features/Development should be discussed in this working group (e.g. to check use cases) - Before a new version is going to be pushed to master -> Feedback phase through mailing list and a deploy on future Demo/Test instance for QA review - TBD - tags should be use to clarify larger releases and changes to main bra, especially breaking changes, incl. deployer notes, summerized changelog, migration scripts --- ### 2022-06-07, 3 pm CEST - Participants: David Graf, Julien Kniephoff, Lars Kiesow, Manfred Holodynski, Till Rauterberg, Manuel Oellers #### Summary We discussed the introduced changes from the upcoming merge (WWU features) and the related UI/UX changes. This was accepted by consensus provided that.... a) ... previous usage scenarios functionally co-exist b) ... the functional behavior is expected to be consistent. In particular, interim solutions are to be finalized. In the case of changes that must be made within libraries used, these should be realized as PR in the corresponding repositories. The participants consider it useful to create a common code basis on which further developments can be coordinated in the future. Instructional elements (tooltips) have been noted as improvements that may be done with the [tippy.js library](https://atomiks.github.io/tippyjs/). It is planned to create a public demo instance for quality assurance, testing purposes and showcase. There might be an instance by ELAN e.V. for that case which is not decicded yet. The WWU proposed a blank template [feature list](https://pad.uni-muenster.de/RUlu61FsR9u4w2Eo-rdZsg?both) to collect use cases and features of annotation tools in general which could be used if there will be a new next-generation tool in the future. --- ### 2022-04-25, 2 pm CEST - Participants: Daniel Ebbert, David Graf (Uni Bern), Julien Kniephoff, Lars Kiesow, Matthias Neugebauer, Frank (Uni Jena), Till Rauterberg, Manuel Oellers #### Summary **Who will be able to merge the MCA?** ELAN e.V. can merge, WWU will prepare a PR; could take some time to check funding (summer?); Git of OAT could be opened to selected parties for writing access to support process of technical reviews / merge process (suitable parties for that needs TBD; see below) **Which companies are able to work on the OAT?** ssystems did not reply yet, otherwise ELAN e.V. and 3rd party developers/freelancers **How do we want to organize quality control?** - Who is doing technical reviews? - ELAN e.V. (small stuff) - educast.nrw - Who is doing usability reviews? - via Community / Mailinglist - Who takes care of updates for new releases? - open for upcoming meeting ****Development process**** - Ideas/Plans should be presented in regular meeting - Open PR should be discussed in regular meetings - An auto-build system would be nice to have for dev and reviews **Organisational** Next meetings will be organized by WWU **Features** Questionnaire builder can be found in [luniki/oat-questionnaire-creator @ GitHub](https://github.com/luniki/oat-questionnaire-creator), could be finished as opencast module; via API or by importing the structure **Future of OAT?** Do we want a rewrite of the OAT? - initial development was about ~150k - funding unclear - A feature list should be created; WWU will share initial one --- ### 2022-03-24, 10 am CET - Participants: Daniel Ebbert, David Graf (Uni Bern), Daniel Ziegenberg, Sascha Nösberger (Uni Bern), Matthias Horstmann, Sebastian Spicker (HfMT Köln), Manfred Holodynski (WWU Münster), Julian Kniephoff (ELAN e.V.), Lars Kiesow, Till Rauterberg, Manuel Oellers #### Summary **State of development** - Discussed how the community can work together on the OAT - Julian presented current state of development; currently two different branches - Newest version and features by University of Bern; Another version by University of Münster with Multi-Content-Annotations (MCA), Guided annotation with a questionnaire - Short-term goal: Merge the branches into a single community version - Conclusion of discussion: MCA are compatible with existing usage scenarios, feature could be included in community version - Guided annotations is optional and therefore does not interfere with existing usage scenarios either; however feature not yet finished as questionnaires cannot be defined by other teachers; as soon as this is possible, feature can be included in community version **Suggested improvements** - adoption of course contexts - old look & feel, a more modern interface is desired - loading times **Status ELAN e.V.** - On the part of the ELAN e.V. it was remarked that due to the old technical any further development of the tool would require considerable additional effort. Furthermore there is no capacity at the ELAN for a further development of the tool in 2022. This brought up the question of which persons or companies could otherwise work on the tool. - In addition, the idea was raised that in the long run it would be a good idea to **Rewrite OAT in future?** - Idea was raised to rewrite the OAT completely. This would require that we define exactly what the tool should be able to do. This topic was discussed but no decision was made and the topic was postponed to the next meeting. The topic was postponed to the next meeting. **Quality control process** - It was also mentioned that there should be a process for quality control process. However, this topic could not be discussed and was postponed to the next meeting. **Regular meetings** - It was decided that there should be regular meetings, but no rhythm was but no rhythm was set yet. *[MCA]: Mutli-Content-Annotation *[OAT]: Opencast Annotation Tool *[PR]: Pull request *[TBD]: To be discussed *[TBA]: To be announced *[UI]: User Interface *[UX]: User Experience *[WWU]: University of Münster *[UM]: University of Münster