TIDO issueshttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues2021-11-24T09:56:01Zhttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/197Collect Error Message Types2021-11-24T09:56:01ZKristine VoigtCollect Error Message TypesThere may be different errors with different notification, that might be interesting for the user. We need to collect them.
* Panel content not loading
* Entry point not set
* loading time of panel content exceeds 1 secondThere may be different errors with different notification, that might be interesting for the user. We need to collect them.
* Panel content not loading
* Entry point not set
* loading time of panel content exceeds 1 seconddindigaladindigalahttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/59Test-Issue (API)2020-09-11T09:33:17ZMichelle WeidlingTest-Issue (API)This issue is simply for playing around with the API.
DO NOT CLOSE MANUALLY.This issue is simply for playing around with the API.
DO NOT CLOSE MANUALLY.Michelle Weidlingschneider210Michelle Weidlinghttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/113Easy configurabilty2021-08-25T07:43:16Zschneider210Easy configurabilty# Feature Requests
## Description
**Goal**: ease the config option for a project
## User Stories
As project I need a single place in order to configure the viewer most conveniently.
## Classification
Is this feature an enhancement ...# Feature Requests
## Description
**Goal**: ease the config option for a project
## User Stories
As project I need a single place in order to configure the viewer most conveniently.
## Classification
Is this feature an enhancement of existing code or a completely new feature?
* [x] enhancement
* [ ] new feature
## Related Tickets
Add all related issues.
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)Ahikar Version 0.14.0schneider210schneider210https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/48removal of ahikar specific configuration2020-09-10T18:43:27ZKristine Voigtremoval of ahikar specific configurationahikar specific configuration; not generic enough (remove gitlab CI config);
needs to be discusses when Michelle is backahikar specific configuration; not generic enough (remove gitlab CI config);
needs to be discusses when Michelle is backAhikar Version 0.11.0https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/66Linting Scss (and config)2020-10-01T08:18:03ZNils WindischLinting Scss (and config)# Feature Requests
## Description
Just leave a short summary what the feature is about.
## User Stories
As a dev i want clean Scss code.
## Classification
Is this feature an enhancement of existing code or a completely new feature?...# Feature Requests
## Description
Just leave a short summary what the feature is about.
## User Stories
As a dev i want clean Scss code.
## Classification
Is this feature an enhancement of existing code or a completely new feature?
* [x] enhancement
* [x] new feature
## Related Tickets
Add all related issues.
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)Ahikar Version 0.11.0Nils WindischNils Windischhttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/60Dark-Mode Support2020-09-29T08:45:13ZNils WindischDark-Mode Support# Feature Requests
## Description
well, dark-mode like implemented by almost all modern OS, be it PC or mobile.
* https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-color-scheme
* https://developer.apple.com/design/human-...# Feature Requests
## Description
well, dark-mode like implemented by almost all modern OS, be it PC or mobile.
* https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-color-scheme
* https://developer.apple.com/design/human-interface-guidelines/ios/visual-design/dark-mode
*
## User Stories
As user at night or in the dark I need a adapted display of the app in order to be less annoyed and have a smoother UX.
## Classification
Is this feature an enhancement of existing code or a completely new feature?
Enhancement
## Related Tickets
Add all related issues.
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)Ahikar Version 0.11.0Nils WindischNils Windischhttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/61Make Scss great again2020-09-28T10:58:58ZNils WindischMake Scss great againAhikar Version 0.11.0Nils WindischNils Windischhttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/69Don't require Scss variable name pattern2020-10-05T05:31:12ZNils WindischDon't require Scss variable name pattern# Feature Requests
## Description
Ignore the Scss Stylelint Rule to have a specific variable nameing pattern
## User Stories
see above
## Classification
Is this feature an enhancement of existing code or a completely new feature?
...# Feature Requests
## Description
Ignore the Scss Stylelint Rule to have a specific variable nameing pattern
## User Stories
see above
## Classification
Is this feature an enhancement of existing code or a completely new feature?
* [x] enhancement
* [ ] new feature
## Related Tickets
Add all related issues.
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)Ahikar Version 0.12.0Mathias GoebelMichelle WeidlingNils Windischschneider210dindigalaMathias Goebelhttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/374Implement lists in remaining metadata objects2022-04-04T15:36:50ZPaul PestovImplement lists in remaining metadata objectsIn #367 we introduces metadata lists for the manifest item level. We should also switch to this style for collection and page level.In #367 we introduces metadata lists for the manifest item level. We should also switch to this style for collection and page level.Paul PestovPaul Pestovhttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/2104042023-12-17T20:36:03ZKristine Voigt404https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/206Message: Entry point not set2021-04-23T12:13:00ZKristine VoigtMessage: Entry point not setschneider210schneider210https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/207500 if the API isn't working due to an error2023-12-17T21:42:24ZKristine Voigt500 if the API isn't working due to an errorhttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/208503 if the server is in maintenance2023-12-17T20:36:16ZKristine Voigt503 if the server is in maintenancehttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/163Clearify Concept for Variants/ Functional Requirements2023-12-12T11:55:54ZKristine VoigtClearify Concept for Variants/ Functional Requirementsdiscussion with the scholarsdiscussion with the scholarsMathias GoebelMichelle WeidlingKristine VoigtMathias Goebelhttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/259refactor smallcaps css2021-05-18T12:09:57ZNils Windischrefactor smallcaps cssmoving some global css to a component, because it's used only there… very small changes. Aims to makes things more resilient and graspable.moving some global css to a component, because it's used only there… very small changes. Aims to makes things more resilient and graspable.Nils WindischNils Windischhttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/257Notificaton: no annotations2021-06-10T09:00:31ZKristine VoigtNotificaton: no annotationsuser should be informed if there is no annotation in the text, that can be displayed by the annotation panel.user should be informed if there is no annotation in the text, that can be displayed by the annotation panel.dindigaladindigalahttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/266mark annotations in text panel2021-05-21T08:14:57ZNils Windischmark annotations in text panelmake strings with annotations visible in text panel. not as in highlighted as in selected, but generally visible my giving them a grey background.make strings with annotations visible in text panel. not as in highlighted as in selected, but generally visible my giving them a grey background.Nils WindischNils Windischhttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/264icons (info, lang, colour scheme) move when header string is deactivated2021-06-10T17:26:33ZKristine Voigticons (info, lang, colour scheme) move when header string is deactivated# Bugs
## Description
If we switch off the Header string via config, the former footer icons (info, lang, colour scheme) move.
### I expected the following to happen
The icons should stay in a postition (right bound?)
…
### On the ...# Bugs
## Description
If we switch off the Header string via config, the former footer icons (info, lang, colour scheme) move.
### I expected the following to happen
The icons should stay in a postition (right bound?)
…
### On the contrary, I observed
…
## How to reproduce the bug
Please describe briefly how you discovered the bug and what a developer has to do to reproduce it.
_Steps:_
* switch off the Header string via config
* take a look at the viewer
* ...
## Severity
How much impact does this bug have on the product or further development?
* [x] Minor
* [ ] Major
* [ ] Critical
* [ ] Blocker
## Platform
* [ ] Unix
* [ ] Windows
* [x] MacOS
## Browser
* [ ] Safari
* [x] Chrome/Chromium
* [ ] Firefox
* [ ] Other: ?
## Program and – if applicable – dependency version
Which version of the software did you use?
1.9
## Related Tickets
Add related issues.
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)Nils WindischNils Windischhttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/261save space in annotations list2021-05-19T14:55:52ZNils Windischsave space in annotations listNils WindischNils Windischhttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/256default not highlight anything2021-05-19T10:59:23ZKristine Voigtdefault not highlight anythingdindigaladindigalahttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/214panel content needs to be translated2021-05-12T10:50:30ZKristine Voigtpanel content needs to be translatedschneider210dindigalaschneider210https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/213default language should be configurable2021-05-12T10:50:19ZKristine Voigtdefault language should be configurableschneider210dindigalaschneider210https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/92enable #42 - test panel styling2020-10-28T20:32:10ZMathias Goebelenable #42 - test panel stylingto enable text styling, we have to ensure a static file is included in SCSS.
text panel styling SHOULD be added in project specific builds from project specific repositories, see for example [Ahikar/frontend](https://gitlab.gwdg.de/subug...to enable text styling, we have to ensure a static file is included in SCSS.
text panel styling SHOULD be added in project specific builds from project specific repositories, see for example [Ahikar/frontend](https://gitlab.gwdg.de/subugoe/ahiqar/frontend)
(While webpack added static resources in an earlier version automatically, this behaviour somehow changed)Ahikar Version 0.12.0Mathias GoebelMathias Goebelhttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/107cool name for Emo2020-12-03T06:26:50ZKristine Voigtcool name for EmoTine sends 4 ideas to Mustafa and he has to decide till Friday (2020-11-27).Tine sends 4 ideas to Mustafa and he has to decide till Friday (2020-11-27).Ahikar Version 0.14.0Kristine VoigtKristine Voigt2020-11-26https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/331TIDO isn't able to diplay single manifest2021-08-30T09:48:47ZKristine VoigtTIDO isn't able to diplay single manifesthttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/330No Tooltip on Fool2021-08-26T14:11:27ZKristine VoigtNo Tooltip on FoolInvestigated that if you choose the last motif in annotation panel "wise fool sinful" there appeares no mouse over in text panel: https://ahikar-dev.sub.uni-goettingen.de/syriac/#/?source=external&redirectUrl=https%3A%2F%2Fsubugoe.pages....Investigated that if you choose the last motif in annotation panel "wise fool sinful" there appeares no mouse over in text panel: https://ahikar-dev.sub.uni-goettingen.de/syriac/#/?source=external&redirectUrl=https%3A%2F%2Fsubugoe.pages.gwdg.de%2Fahiqar%2Fwebsite%2Fdevelop%2F&itemurl=https%3A%2F%2Fahikar-dev.sub.uni-goettingen.de%2Fapi%2Ftextapi%2Fahikar%2Fsyriac%2F3r84d-67r%2Flatest%2Fitem.json
same with "meekness/ showing respect"dindigaladindigalahttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/105EMo release via npm2021-01-25T08:40:21Zschneider210EMo release via npmA project needs a convenient way to integrate the Viewer
**Goals:**
- 1) publish the Viewer as npm package
- 2) install the Viewer as npm package
- 3) integrate the Viewer
**Publish**
- [x] what to publish (build && statics && usua...A project needs a convenient way to integrate the Viewer
**Goals:**
- 1) publish the Viewer as npm package
- 2) install the Viewer as npm package
- 3) integrate the Viewer
**Publish**
- [x] what to publish (build && statics && usual suspects): setup *package.json*
- [x] setup package scope (*GitLab*)
- [x] create access token (*GitLab*)
- [x] configure registry setup / *.npmrc*
- [x] configure publishing setup in *package.json*
**Install**
- [x] setup registry according to package scope
- [x] install the npm package
**Integrate**
- [x] import js modules (main.js)
- [x] import css (main.scss)
- [x] copy config-object (project's entrypoint)
**TODOs**:
- [x] (automate) renaming of build files from checksums to readable names to ease the integration
- [x] patch / change build pipeline to end up with a single js / css file instead of 3 (if applicable)
- [x] release the Viewer as **standalone** package
- [ ] accordance on **licensing**Ahikar Version 0.14.0schneider210schneider210https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/109Title Objects for items as heading not supported2023-09-21T10:33:57ZMichelle WeidlingTitle Objects for items as heading not supported# Bugs
## Description
The TextAPI specifies that titles consist of Title Objects which have a `title` key and a `type` key[1]. The viewer doesn't seem to support this data structure which can be observed in the main heading in Michelle...# Bugs
## Description
The TextAPI specifies that titles consist of Title Objects which have a `title` key and a `type` key[1]. The viewer doesn't seem to support this data structure which can be observed in the main heading in Michelle's test viewer which consumes test data.
[1] Cf. https://subugoe.pages.gwdg.de/emo/text-api/page/specs/#title-object.
### I expected the following to happen
The title of https://mrodzis.pages.gwdg.de/test/sampledata/document1/1/latest/item.json, "A letter from X to Y.", should have been displayed as the main title of the viewer.
(BTW I'm not sure if the main heading shouldn't be the heading of the whole collection, which would be "The Example Collection" in case of the test data. Currently the item's title is taken for filling in the heading.)
### On the contrary, I observed
The whole Title Object has been parsed to a string.
## How to reproduce the bug
https://mrodzis.pages.gwdg.de/Qviewer/develop/#/?itemurl=https%3A%2F%2Fmrodzis.pages.gwdg.de%2Ftest%2Fsampledata%2Fdocument2%2F3%2Flatest%2Fitem.json
## Severity
How much impact does this bug have on the product or further development?
* [x] Major
## Screenshot
![Screenshot_2020-11-25_14-53-57](/uploads/5ad0a769e33f383e94bc949c7a62c15c/Screenshot_2020-11-25_14-53-57.png)
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)Paul PestovPaul Pestovhttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/110Improve breadcrumb navigation for missing n-key on item level2023-09-21T10:31:59ZMichelle WeidlingImprove breadcrumb navigation for missing n-key on item level# Feature Requests
## Description
The TextAPI sets the `n` key on item level as optional: https://subugoe.pages.gwdg.de/emo/text-api/page/specs/#item-object
This key seems to be used for the breadcrumb navigation in the header for inf...# Feature Requests
## Description
The TextAPI sets the `n` key on item level as optional: https://subugoe.pages.gwdg.de/emo/text-api/page/specs/#item-object
This key seems to be used for the breadcrumb navigation in the header for informing users where there are at the moment:
![Screenshot_2020-11-25_14-53-57](/uploads/ccc176085df865f51b1ab40821464767/Screenshot_2020-11-25_14-53-57.png)
If `n` isn't present, we currently display a "No itemlabel :(" notification. Since `n` is optional we should discuss if such a prominent feature as the breadcrumb nav should depend on it.
## User Stories
As a project that doesn't provide a `n` key for my items I need a breadcrumb navigation that doesn't contain error messages in order to avoid the impression that my data is faulty.
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/111Use the same source for sheet labels2023-09-21T11:12:44ZMichelle WeidlingUse the same source for sheet labelsIt seems like we use different sources for the sheet labels:
- the `n` key on item level for the breadcrumb navigation
- the item's `id` in the tree view
Example:
![Screenshot_2020-11-25_14-53-57](/uploads/833b87c09bdf7126b11989c001ad...It seems like we use different sources for the sheet labels:
- the `n` key on item level for the breadcrumb navigation
- the item's `id` in the tree view
Example:
![Screenshot_2020-11-25_14-53-57](/uploads/833b87c09bdf7126b11989c001ad213c/Screenshot_2020-11-25_14-53-57.png)
![Screenshot_2020-11-25_15-07-34](/uploads/8089b031f67f635f02993277c7fc9d82/Screenshot_2020-11-25_15-07-34.png)
([Source](https://mrodzis.pages.gwdg.de/Qviewer/develop/#/?itemurl=https%3A%2F%2Fmrodzis.pages.gwdg.de%2Ftest%2Fsampledata%2Fdocument2%2F3%2Flatest%2Fitem.json))
This is a bit confusing and might contradict itself (as it is the case in the sample data).https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/112Clarify dependencies between metadata offered and displayed2023-09-21T11:14:36ZMichelle WeidlingClarify dependencies between metadata offered and displayedAs someone offering data to the viewer I'm kind of lost when it comes to the metadata. From the README I can guess, that the following information will be displayed at some point:
- the collection's collector
- the collection's title
- ...As someone offering data to the viewer I'm kind of lost when it comes to the metadata. From the README I can guess, that the following information will be displayed at some point:
- the collection's collector
- the collection's title
- the collection's description
https://mrodzis.pages.gwdg.de/test/sampledata/collection.json offers all of these and the respective values are switched t o `true`, nevertheless the metadata panel is empty for all items.
See https://mrodzis.pages.gwdg.de/Qviewer/develop/#/.https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/114easy configurabilty2020-12-04T16:39:59Zschneider210easy configurabiltyAhikar Version 0.14.0schneider210schneider210https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/115Consider new repo name for ahiqar-tido2020-12-11T08:39:20ZMichelle WeidlingConsider new repo name for ahiqar-tidoThe name and path of subugoe/ahiqar/frontend changed to subugoe/ahiqar/ahiqar-tido for clarity.
This has to be considered in this repo's pipeline.The name and path of subugoe/ahiqar/frontend changed to subugoe/ahiqar/ahiqar-tido for clarity.
This has to be considered in this repo's pipeline.Ahikar Version 0.14.0Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/116TIDO Backend in das npm Paket einbinden2023-09-21T11:15:18ZKristine VoigtTIDO Backend in das npm Paket einbindenhttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/119Use generic back end for TIDO2021-02-01T20:59:16ZMichelle WeidlingUse generic back end for TIDOUp until now we still use the Ahiqar endpoints for the viewer instead of querying the back end endpoint at https://subugoe.pages.gwdg.de/emo/backend/sampledata/collection.json.
At some stage we should change that so that we distribute t...Up until now we still use the Ahiqar endpoints for the viewer instead of querying the back end endpoint at https://subugoe.pages.gwdg.de/emo/backend/sampledata/collection.json.
At some stage we should change that so that we distribute the viewer's URL in public.Ahikar Version 0.15.0Kristine VoigtKristine Voigthttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/121Missing HTML meta description2023-09-21T11:16:03ZNils WindischMissing HTML meta description![Screenshot_2021-01-21_at_11.43.13](/uploads/9d2f8c03ac5d7aa2ef19a5d0d39cf2eb/Screenshot_2021-01-21_at_11.43.13.jpg)![Screenshot_2021-01-21_at_11.43.13](/uploads/9d2f8c03ac5d7aa2ef19a5d0d39cf2eb/Screenshot_2021-01-21_at_11.43.13.jpg)https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/122robots.txt missing2023-12-17T20:37:17ZNils Windischrobots.txt missing![Screenshot_2021-01-21_at_11.44.13](/uploads/20968b0b8da1081471c64a5418218903/Screenshot_2021-01-21_at_11.44.13.jpg)![Screenshot_2021-01-21_at_11.44.13](/uploads/20968b0b8da1081471c64a5418218903/Screenshot_2021-01-21_at_11.44.13.jpg)https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/123Text compression not enabled2023-12-17T20:37:31ZNils WindischText compression not enabled![Screenshot_2021-01-21_at_11.45.16](/uploads/415321d6f05509acbc9648cd7c4e010c/Screenshot_2021-01-21_at_11.45.16.jpg)![Screenshot_2021-01-21_at_11.45.16](/uploads/415321d6f05509acbc9648cd7c4e010c/Screenshot_2021-01-21_at_11.45.16.jpg)https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/125HTTP cache-control header is missing or empty2023-12-17T20:37:46ZNils WindischHTTP cache-control header is missing or empty![Screenshot_2021-01-21_at_11.48.09](/uploads/0e47a7ae0943695abed248225ba153fc/Screenshot_2021-01-21_at_11.48.09.jpg)![Screenshot_2021-01-21_at_11.48.09](/uploads/0e47a7ae0943695abed248225ba153fc/Screenshot_2021-01-21_at_11.48.09.jpg)https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/126X-Content-Type-Options header not used2023-12-17T20:37:58ZNils WindischX-Content-Type-Options header not used![Screenshot_2021-01-21_at_11.48.52](/uploads/6b214dd58dee7b45d1e36b4a471d0a04/Screenshot_2021-01-21_at_11.48.52.jpg)![Screenshot_2021-01-21_at_11.48.52](/uploads/6b214dd58dee7b45d1e36b4a471d0a04/Screenshot_2021-01-21_at_11.48.52.jpg)https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/127ARIA main landmark missing2023-12-17T20:38:11ZNils WindischARIA main landmark missing![Screenshot_2021-01-21_at_11.51.00](/uploads/6a0c772391b16449bc407d496124b2b8/Screenshot_2021-01-21_at_11.51.00.jpg)![Screenshot_2021-01-21_at_11.51.00](/uploads/6a0c772391b16449bc407d496124b2b8/Screenshot_2021-01-21_at_11.51.00.jpg)https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/128Automatically close environments after some time2023-12-17T20:42:58ZMichelle WeidlingAutomatically close environments after some time# Feature Requests
## Description
Currently every branch creates an environment (see https://gitlab.gwdg.de/subugoe/emo/Qviewer/-/environments) which runs in eternity unless stopped.
It would much more convenient (and tidier) if an en...# Feature Requests
## Description
Currently every branch creates an environment (see https://gitlab.gwdg.de/subugoe/emo/Qviewer/-/environments) which runs in eternity unless stopped.
It would much more convenient (and tidier) if an environment stopped
a) if no longer needed
b) after some time (if a) isn't achievable)
## User Stories
As a developer and/or product owner I need a neat overview of the environments enabled. A tidy list helps me finding things faster.
## Classification
Is this feature an enhancement of existing code or a completely new feature?
* [x] enhancement
* [ ] new feature
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/130Toggle Panel Button not keyboard-focusable2021-06-25T10:04:05ZNils WindischToggle Panel Button not keyboard-focusable![Screenshot_2021-01-21_at_11.53.10](/uploads/bfd317cd97fe41f9fd541d83cbd05154/Screenshot_2021-01-21_at_11.53.10.jpg)![Screenshot_2021-01-21_at_11.53.10](/uploads/bfd317cd97fe41f9fd541d83cbd05154/Screenshot_2021-01-21_at_11.53.10.jpg)https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/185configurability of the Metadata Panel content2023-12-17T21:25:04ZKristine Voigtconfigurability of the Metadata Panel content# Feature Requests
## Description
it should be possible to display all fields in the header
it must be configurable which fields are displayed
## User Stories
as a project I want to be able to display certain fields from the header ...# Feature Requests
## Description
it should be possible to display all fields in the header
it must be configurable which fields are displayed
## User Stories
as a project I want to be able to display certain fields from the header of my TEI document in the metadata panel of the viewer.
## Classification
Is this feature an enhancement of existing code or a completely new feature?
* [ ] enhancement
* [x] new feature
## Related Tickets
Add all related issues.
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/307Text panel: padding for RTL2023-12-17T21:25:28ZMichelle WeidlingText panel: padding for RTL# Feature Requests
## Description
Currently (v1.13.0) we have only very little padding left and right in the text panel. This looks a bit off if we have RTL and the annotation panel has been switched off:
![image](/uploads/1683edbcc54...# Feature Requests
## Description
Currently (v1.13.0) we have only very little padding left and right in the text panel. This looks a bit off if we have RTL and the annotation panel has been switched off:
![image](/uploads/1683edbcc5498c0af918589035a70336/image.png)
## User Stories
As a user of the edition I need more padding on the sides in order to have a visually pleasing experience when using TIDO.
## Classification
Is this feature an enhancement of existing code or a completely new feature?
* [x] enhancement
* [ ] new feature
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/134Restrict automatic updates to ahiqar-tido to TIDO's `main` branch2021-01-27T12:39:12ZMichelle WeidlingRestrict automatic updates to ahiqar-tido to TIDO's `main` branchCurrently the ahiqar-tido submodule pointing to this repo gets updated every time a commit is made on this repo's `develop` branch.
It's sufficient if this takes place at the end of the sprint, i.e. after a merge on TIDO's `main` branch.Currently the ahiqar-tido submodule pointing to this repo gets updated every time a commit is made on this repo's `develop` branch.
It's sufficient if this takes place at the end of the sprint, i.e. after a merge on TIDO's `main` branch.Ahikar Version 0.15.0Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/136Key/Value pairs not considered for metadata panel2023-12-17T21:25:48ZMichelle WeidlingKey/Value pairs not considered for metadata panel# Bugs
## Description
At some point (before using Quasar) the viewer supported the key/value pairs as defined for the Metadata Object in the TextAPI (cf. https://subugoe.pages.gwdg.de/emo/text-api/page/specs/#metadata-object). This fea...# Bugs
## Description
At some point (before using Quasar) the viewer supported the key/value pairs as defined for the Metadata Object in the TextAPI (cf. https://subugoe.pages.gwdg.de/emo/text-api/page/specs/#metadata-object). This feature should be re-introduced.
### I expected the following to happen
When providing key/value pairs in the Metadata Object, these should be displayed in the viewer.
### On the contrary, I observed
If key/value pairs are provided they are not displayed.
## How to reproduce the bug
Aly has more information about this.
## Severity
How much impact does this bug have on the product or further development?
* [x] Major
## Program and – if applicable – dependency version
1.5.0
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)Ahikar Version 0.16.0https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/144default language should be configurable2021-11-24T09:24:48ZKristine Voigtdefault language should be configurablecurrently the default language is english.
projects should be able to decide which language is set as default and whether they want to offer more than one language at all.currently the default language is english.
projects should be able to decide which language is set as default and whether they want to offer more than one language at all.https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/152Message/Notification if no entrypoint is set2023-12-17T21:26:03ZNils WindischMessage/Notification if no entrypoint is setIf no entrypoint is set, the frontend is partially empty and not usable. Users shoudl get a message about that and instructions on how to set a valid entrypoint (link to docu).If no entrypoint is set, the frontend is partially empty and not usable. Users shoudl get a message about that and instructions on how to set a valid entrypoint (link to docu).schneider210schneider210https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/155TIDO should be able to show the GfL Metadata2022-06-24T08:58:33ZKristine VoigtTIDO should be able to show the GfL Metadatahttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/156Scrollbar missing in Metadata panel2023-12-17T21:26:17ZMichelle WeidlingScrollbar missing in Metadata panel# Bugs
## Description
Currently there is no scrollbar displayed in the Metadata panel. Users might not understand that there is more metadata available because they don't have a visual cue indicating this.
### I expected the following...# Bugs
## Description
Currently there is no scrollbar displayed in the Metadata panel. Users might not understand that there is more metadata available because they don't have a visual cue indicating this.
### I expected the following to happen
If we have more info than the vertical space in the Metadata panel allows for, a scrollbar should be displayed.
### On the contrary, I observed
![image](/uploads/3f297d1af1e1c1b20331025ddd929c58/image.png)
## Severity
How much impact does this bug have on the product or further development?
* [x] Major
## Browser
* [x] Firefox 85.0.1 (64-bit) (for Ubuntu), 1920x1080
## Program and – if applicable – dependency version
1.6.0
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/41Annotation Panel: person & place names2021-05-17T14:01:01ZKristine VoigtAnnotation Panel: person & place names# Feature Requests
## Description
The idea is to display annotations in an extra panel in addition to (image, text, metadata and treeview). Like all other panels, this panel should
- [ ] only be shown if annotations are present
- [x]...# Feature Requests
## Description
The idea is to display annotations in an extra panel in addition to (image, text, metadata and treeview). Like all other panels, this panel should
- [ ] only be shown if annotations are present
- [x] be configurable on the project side whether it is shown or not
- [x] be user configurable to show and hide it.
By default
- [x] the panel should be displayed next to the text
- [ ] the annotation panel is connected with the text panel
- [ ] the annotation panel shows the annotations of the current displayed text
- [ ] show the person and place names
## User Stories
As a user, I would like to have annotations (meaning all kinds of additional information about the text) displayed clearly and close to the text.
## Classification
Is this feature an enhancement of existing code or a completely new feature?
* [ ] enhancement
* [x] new feature
## Related Tickets
Add all related issues.
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)schneider210schneider210https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/356Bug: Brackets in link text and lists of links cause an error (in metadata tab)2022-04-04T15:36:53ZRafael Maria RaschkowskiBug: Brackets in link text and lists of links cause an error (in metadata tab)# Bugs
## Description
There are still some issues with Tido when there are brackets in the link text as brackets are used by Tido for specifying links. See the attached image.
![Bildschirmfoto_vom_2021-11-25_02-56-17](/uploads/64a37f2...# Bugs
## Description
There are still some issues with Tido when there are brackets in the link text as brackets are used by Tido for specifying links. See the attached image.
![Bildschirmfoto_vom_2021-11-25_02-56-17](/uploads/64a37f2e006c596a749c0dcb24cd40b6/Bildschirmfoto_vom_2021-11-25_02-56-17.png)
**At the moment** Tido is able to handle Links like the following:
`30. März 1822. Hegel an Kultusministerium (https://dev.gfl.sub.uni-goettingen.de/id/Z_1822-03-30_k)`
**What we often have** in TEI documents are something like the following:
`22. Juli 1820. Hardenberg an Altenstein (Ausfertigung) (https://dev.gfl.sub.uni-goettingen.de/id/Z_1820-07-22_k)`
which could not be handled by Tido.
**Apart from that** we may have a list of links like the following image where each of the links are separated by a semicolon.
![Bildschirmfoto_vom_2021-12-08_14-29-24](/uploads/35e443be5d7f78736cb80486a847ae3c/Bildschirmfoto_vom_2021-12-08_14-29-24.png)
E.g. in [this document](https://dev.gfl.sub.uni-goettingen.de/id/Z_1822-06-21_k#/?searchTerm=altenstein&page=1&source=gfl&redirectUrl=http%3A%2F%2Fdev.gfl.sub.uni-goettingen.de%2Fsuche&itemurl=https%3A%2F%2Fdev.gfl.sub.uni-goettingen.de%2Ftido%2Fgfl%2FZ_1822-06-21_k_page1%2Flatest%2Fitem.json) in "Dokumentdaten">"Metadaten">"Zugehöriges" the last link starts with a semicolon.
`; 22. Juli 1820. Hardenberg an AltensteinAusfertigung) (`
All of these lead to the problems mentioned.
### I expected the following to happen
- Show the full link text including the brackets.
- Either TIDO must be adapted to handle such a link list or be adapted to handle list of links in proper manner like array and we on GFL side provide such an array.
### On the contrary, I observed
See screenshot above
## How to reproduce the bug
Compare issue:
https://gitlab.gwdg.de/farbenlehre/gfl-app-new/-/issues/27
## Severity
How much impact does this bug have on the product or further development?
* [ ] Minor
* [X] Major
* [ ] Critical
* [ ] Blocker
## Related Tickets
https://gitlab.gwdg.de/farbenlehre/gfl-app-new/-/issues/27
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)asajediasajedihttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/368convention how to provide lists to TIDO2022-03-21T11:31:05ZKristine Voigtconvention how to provide lists to TIDOA convention between backend and frontend is required to represent the recursive metadata objects as a list in TIDO.A convention between backend and frontend is required to represent the recursive metadata objects as a list in TIDO.Mathias GoebelPaul PestovdindigalaMathias Goebelhttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/329double selection in annotation panel motifs2023-12-17T21:26:34ZKristine Voigtdouble selection in annotation panel motifshttps://ahikar-dev.sub.uni-goettingen.de/syriac/#/?source=external&redirectUrl=https%3A%2F%2Fsubugoe.pages.gwdg.de%2Fahiqar%2Fwebsite%2Fdevelop%2F&itemurl=https%3A%2F%2Fahikar-dev.sub.uni-goettingen.de%2Fapi%2Ftextapi%2Fahikar%2Fsyriac%2...https://ahikar-dev.sub.uni-goettingen.de/syriac/#/?source=external&redirectUrl=https%3A%2F%2Fsubugoe.pages.gwdg.de%2Fahiqar%2Fwebsite%2Fdevelop%2F&itemurl=https%3A%2F%2Fahikar-dev.sub.uni-goettingen.de%2Fapi%2Ftextapi%2Fahikar%2Fsyriac%2F3r84d-77v%2Flatest%2Fitem.json
If you choose "self examination/-reflection" you automatically also "choose parable (plants)" (both highlighted gray).
And if I choose more motifs like "parable (animals)". Only the tooltip for "parable plants" is displayed in text panel. Maybe because it is the motif in which all otheres are embedded.Paul PestovPaul Pestovhttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/162Implement List of Annotations in the Annotation Panel2021-11-24T09:58:57ZKristine VoigtImplement List of Annotations in the Annotation Panel**Goal**
Annotations should be displayed according to the annotation type/s selected (persons, places, comments)
It should be a **multiselect** scenario, e.g. clicking persons and names should display both types.
The **type toggles** ...**Goal**
Annotations should be displayed according to the annotation type/s selected (persons, places, comments)
It should be a **multiselect** scenario, e.g. clicking persons and names should display both types.
The **type toggles** at the top of the panel have to be **fixed**, whereas the **list** has to be **scrollable**https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/159connection between annotation - HTML2021-04-30T11:23:34ZKristine Voigtconnection between annotation - HTMLmake connection between annotation and HTML via IDmake connection between annotation and HTML via IDschneider210schneider210https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/158Implement toggle functionality2021-06-03T14:06:43ZKristine VoigtImplement toggle functionalityschneider210schneider210https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/179De/highlight text entities on data type change2021-11-24T09:59:37ZKristine VoigtDe/highlight text entities on data type change**goal** the highlighting state has to be adjusted whenever the selection of the annotation types changes.
**presumption**: persons, places and the option **highlight all** are selected.
**result**: all the annotations in the annotatio...**goal** the highlighting state has to be adjusted whenever the selection of the annotation types changes.
**presumption**: persons, places and the option **highlight all** are selected.
**result**: all the annotations in the annotation list are highlighted as well as the appropriate text entities.
**use case**: a user **toggles** an annotation type, e.g. **places**
**expectation**: places are removed from the annotation list and the text entities will get **dehighlighted**
**TODO**: de/highlight all text entities in the text panel whenever the annotation types are toggledMathias GoebelMathias Goebelhttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/180Track Annotation option on item change2021-08-25T07:48:08ZKristine VoigtTrack Annotation option on item change**goal**: whenever an item changes, the options (highlight all|none, sorting order) have to be kept**goal**: whenever an item changes, the options (highlight all|none, sorting order) have to be keptschneider210schneider210https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/190annotation panel shows annotation about current text type2021-06-10T08:58:38ZKristine Voigtannotation panel shows annotation about current text typeAnnos are always related to the actual text type shown. when switching to another tab the anno panel should get updated accordingly
viewer needs to update the annotations.
watch the contenturls changingAnnos are always related to the actual text type shown. when switching to another tab the anno panel should get updated accordingly
viewer needs to update the annotations.
watch the contenturls changingschneider210dindigalaschneider210https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/195loading: propose solution based on Quasar components2021-04-15T13:17:20ZKristine Voigtloading: propose solution based on Quasar components, wireframe/prototype/flow, wireframe/prototype/flowNils WindischNils Windischhttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/165Enable TIDO to display more (+n) text types as tabs2021-06-10T07:56:41ZKristine VoigtEnable TIDO to display more (+n) text types as tabsdindigaladindigalahttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/192Links in TIDO: agree on behaviour2021-04-22T06:10:43ZKristine VoigtLinks in TIDO: agree on behaviour1 st suggestion: opens the url in a new tab in the browser1 st suggestion: opens the url in a new tab in the browserNils WindischNils Windischhttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/172Re-use CSS from text styling in text to keys in modal/dialog2023-12-17T20:59:16ZKristine VoigtRe-use CSS from text styling in text to keys in modal/dialoghttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/173Add Translation to keys modal/dialog2023-12-17T21:26:48ZKristine VoigtAdd Translation to keys modal/dialogTranslate text from intranet page from EN to DE (whatever is required). To be used in the keys modal/dialogTranslate text from intranet page from EN to DE (whatever is required). To be used in the keys modal/dialoghttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/171Transfer intranet info to key2023-12-17T20:39:06ZKristine VoigtTransfer intranet info to keyhttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/118Contents in Panels not fully visible2021-06-10T07:54:54ZMichelle WeidlingContents in Panels not fully visible# Bugs
## Description
In case we have a lot of manifests, not all of them are visible if their number exceeds a certain amount (probably depending on your screen resolution).
### I expected the following to happen
All manifests shoul...# Bugs
## Description
In case we have a lot of manifests, not all of them are visible if their number exceeds a certain amount (probably depending on your screen resolution).
### I expected the following to happen
All manifests should be visible in the treeview. If this isn't the case, users should be able to scroll.
### On the contrary, I observed
There is no scrollbar, and I cannot see all manifests.
## How to reproduce the bug
Please describe briefly how you discovered the bug and what a developer has to do to reproduce it.
_Steps:_
* go to https://ahikar-test.sub.uni-goettingen.de/
## Severity
How much impact does this bug have on the product or further development?
* [x] Major
## Browser
* [x] Firefox 84.0.2 (64-bit) on Linux
## Program and – if applicable – dependency version
TIDO commit 9b8ce7f4d0ccbf3b3e29c1f7036380b364243b13.
## Screenshot
![Screenshot_2021-01-14_08-31-50](/uploads/9d571da7d54f0ac034f1e0d97604ce8a/Screenshot_2021-01-14_08-31-50.png)
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)dindigaladindigalahttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/182Move the keys button to the bottom of the panel2023-12-17T20:38:47ZKristine VoigtMove the keys button to the bottom of the panelKristine VoigtKristine Voigthttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/183Style alert to choose annotation type2021-03-25T09:24:34ZNils WindischStyle alert to choose annotation typeNils WindischNils Windischhttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/186Follow-up from "feature/#165: Enable TIDO to display more (+n) text types as ...2021-06-10T07:58:38ZNils WindischFollow-up from "feature/#165: Enable TIDO to display more (+n) text types as tabs"The following discussion from !126 should be addressed:
- [ ] @nwindis started a [discussion](https://gitlab.gwdg.de/subugoe/emo/Qviewer/-/merge_requests/126#note_295258): (+1 comment)
> The margin-bottom of the tabs could be a li...The following discussion from !126 should be addressed:
- [ ] @nwindis started a [discussion](https://gitlab.gwdg.de/subugoe/emo/Qviewer/-/merge_requests/126#note_295258): (+1 comment)
> The margin-bottom of the tabs could be a little smaller. Like same margin as text size button to text.
>
> ![Screenshot_2021-03-30_at_08.21.47](/uploads/f8f37f559513a99fb337532912cfce19/Screenshot_2021-03-30_at_08.21.47.jpg)dindigaladindigalahttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/187Follow-up from "feature/#165: Enable TIDO to display more (+n) text types as ...2021-06-10T17:12:54ZNils WindischFollow-up from "feature/#165: Enable TIDO to display more (+n) text types as tabs"The following discussion from !126 should be addressed:
- [ ] @nwindis started a [discussion](https://gitlab.gwdg.de/subugoe/emo/Qviewer/-/merge_requests/126#note_295266): (+1 comment)
> If i click the currently not active tab, th...The following discussion from !126 should be addressed:
- [ ] @nwindis started a [discussion](https://gitlab.gwdg.de/subugoe/emo/Qviewer/-/merge_requests/126#note_295266): (+1 comment)
> If i click the currently not active tab, the text needs up to 3 seconds to change. There is not indication for users their click was successful and the app just needs a moment. This is confusing. I propose to use a loading indicator and or the Quasar skeleton component https://quasar.dev/vue-components/skeletondindigaladindigalahttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/188Follow-up from "feature/#165: Enable TIDO to display more (+n) text types as ...2021-08-12T08:25:57ZNils WindischFollow-up from "feature/#165: Enable TIDO to display more (+n) text types as tabs"The following discussion from !126 should be addressed:
- [ ] @nwindis started a [discussion](https://gitlab.gwdg.de/subugoe/emo/Qviewer/-/merge_requests/126#note_295252): (+1 comment)
> I don't see the need for muting the text if...The following discussion from !126 should be addressed:
- [ ] @nwindis started a [discussion](https://gitlab.gwdg.de/subugoe/emo/Qviewer/-/merge_requests/126#note_295252): (+1 comment)
> I don't see the need for muting the text if there is only one item. I propose to not mute it, but skip (as in remove) the blue underline.
>
> ![Screenshot_2021-03-30_at_08.20.01](/uploads/d76b5a38b1d9ac660f589b3ad8d939eb/Screenshot_2021-03-30_at_08.20.01.jpg)dindigaladindigalahttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/189Follow-up from "feature/#165: Enable TIDO to display more (+n) text types as ...2023-12-17T20:39:24ZNils WindischFollow-up from "feature/#165: Enable TIDO to display more (+n) text types as tabs"The following discussion from !126 should be addressed:
- [ ] @nwindis started a [discussion](https://gitlab.gwdg.de/subugoe/emo/Qviewer/-/merge_requests/126#note_295251): (+1 comment)
> The text gets cut of if the panel doesn't p...The following discussion from !126 should be addressed:
- [ ] @nwindis started a [discussion](https://gitlab.gwdg.de/subugoe/emo/Qviewer/-/merge_requests/126#note_295251): (+1 comment)
> The text gets cut of if the panel doesn't provide enough width:
>
> ![Screenshot_2021-03-30_at_08.18.57](/uploads/f3d094cebf310018e5c0398f7dba310e/Screenshot_2021-03-30_at_08.18.57.jpg)Paul PestovPaul Pestovhttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/198Implement Error Messages2021-04-14T20:17:38ZKristine VoigtImplement Error Messagesdindigaladindigalahttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/200Follow-up from "feature/#172: Created a new keys button and modal to display ...2023-12-17T20:39:55ZMichelle WeidlingFollow-up from "feature/#172: Created a new keys button and modal to display text style labels"The following discussion from !129 should be addressed:
- [ ] @mrodzis started a [discussion](https://gitlab.gwdg.de/subugoe/emo/Qviewer/-/merge_requests/129#note_299347): (+2 comments)
> Probably unrelated to your MR, but what ar...The following discussion from !129 should be addressed:
- [ ] @mrodzis started a [discussion](https://gitlab.gwdg.de/subugoe/emo/Qviewer/-/merge_requests/129#note_299347): (+2 comments)
> Probably unrelated to your MR, but what are these grey-ish bars at the bottom of the panels?
>
> ![image](/uploads/596c14c7b21471f9ff2b06322fd9a29a/image.png)https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/201Follow-up from "feature/#172: Created a new keys button and modal to display ...2023-12-17T20:40:06ZMichelle WeidlingFollow-up from "feature/#172: Created a new keys button and modal to display text style labels": move highlight.js to ahiqar-tidoThe following discussion from !129 should be addressed:
- [ ] @mrodzis started a [discussion](https://gitlab.gwdg.de/subugoe/emo/Qviewer/-/merge_requests/129#note_299348): (+4 comments)
> The whole `src/components/textstyles/highl...The following discussion from !129 should be addressed:
- [ ] @mrodzis started a [discussion](https://gitlab.gwdg.de/subugoe/emo/Qviewer/-/merge_requests/129#note_299348): (+4 comments)
> The whole `src/components/textstyles/highlights.js` file probably belongs to ahiqar-TIDO because this is project specific (and not generic) information.https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/202CI: fix artifact size2021-04-14T12:36:07ZMichelle WeidlingCI: fix artifact size# Bugs
## Description
### I expected the following to happen
The pipelines should not fail because of an artifact that's too large.
### On the contrary, I observed
The current artifact size is 1.3 GB which blocks the pipeline.
## S...# Bugs
## Description
### I expected the following to happen
The pipelines should not fail because of an artifact that's too large.
### On the contrary, I observed
The current artifact size is 1.3 GB which blocks the pipeline.
## Severity
How much impact does this bug have on the product or further development?
* [x] Blocker
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/203CI: remove entry point at merge2021-04-27T06:08:16ZMichelle WeidlingCI: remove entry point at merge# Feature Requests
## Description
Developers could/should provide an entry point in `index.html` so that reviewers can start their review easily. The entry point should be automatically removed when merging the feature/fix into `develo...# Feature Requests
## Description
Developers could/should provide an entry point in `index.html` so that reviewers can start their review easily. The entry point should be automatically removed when merging the feature/fix into `develop`.
## User Stories
As developer I need an automatic removal of my local entry point in order to make reviewers' lives easier and not introduce errors to the code base..
## Classification
Is this feature an enhancement of existing code or a completely new feature?
* [x] enhancement
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/221Follow-up from "WIP: feat: annotations"2023-12-17T20:59:31ZNils WindischFollow-up from "WIP: feat: annotations"The following discussion from !132 should be addressed:
- [ ] @nwindis started a [discussion](https://gitlab.gwdg.de/subugoe/emo/Qviewer/-/merge_requests/132#note_300954): (+5 comments)
> Options get cut of at the bottom:
>
...The following discussion from !132 should be addressed:
- [ ] @nwindis started a [discussion](https://gitlab.gwdg.de/subugoe/emo/Qviewer/-/merge_requests/132#note_300954): (+5 comments)
> Options get cut of at the bottom:
>
> ![Screenshot_2021-04-14_at_12.22.21](/uploads/111d6fb90211e2479e7b8118a005021e/Screenshot_2021-04-14_at_12.22.21.jpg)https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/222Follow-up from "WIP: feat: annotations"2021-04-21T05:07:18ZMichelle WeidlingFollow-up from "WIP: feat: annotations"The following discussion from !132 should be addressed:
- [ ] @schneider210 started a [discussion](https://gitlab.gwdg.de/subugoe/emo/Qviewer/-/merge_requests/132#note_301826): (+1 comment)
> yes, that's right. I removed them, whe...The following discussion from !132 should be addressed:
- [ ] @schneider210 started a [discussion](https://gitlab.gwdg.de/subugoe/emo/Qviewer/-/merge_requests/132#note_301826): (+1 comment)
> yes, that's right. I removed them, when we agreed on not having "A person's name" several times over and over again in the list. So, the opposite is needed here, but for the comments only?Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/223Styling of the panel contents2021-04-21T08:47:20ZMichelle WeidlingStyling of the panel contentsThe panel contents have to be styled (options sticky at the bottom)
(This ticket's content has been a TOOD in the MR description of subugoe/emo/Qviewer!132)The panel contents have to be styled (options sticky at the bottom)
(This ticket's content has been a TOOD in the MR description of subugoe/emo/Qviewer!132)https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/225Follow-up from "WIP: feat: annotations": icons2021-04-30T11:23:34ZMichelle WeidlingFollow-up from "WIP: feat: annotations": iconsThe following discussion from !132 should be addressed:
- [ ] @nwindis started a [discussion](https://gitlab.gwdg.de/subugoe/emo/Qviewer/-/merge_requests/132#note_300968): (+1 comment)
> Icons in text panel are icon font instead o...The following discussion from !132 should be addressed:
- [ ] @nwindis started a [discussion](https://gitlab.gwdg.de/subugoe/emo/Qviewer/-/merge_requests/132#note_300968): (+1 comment)
> Icons in text panel are icon font instead of SVG.https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/227Follow-up from "WIP: feat: annotations": implement references2023-12-17T21:27:22ZMichelle WeidlingFollow-up from "WIP: feat: annotations": implement referencesThe following discussion from !132 should be addressed:
- [ ] @manikanth.dindigala started a [discussion](https://gitlab.gwdg.de/subugoe/emo/Qviewer/-/merge_requests/132#note_301031): (+8 comments)
> Using Syriac end point, i do n...The following discussion from !132 should be addressed:
- [ ] @manikanth.dindigala started a [discussion](https://gitlab.gwdg.de/subugoe/emo/Qviewer/-/merge_requests/132#note_301031): (+8 comments)
> Using Syriac end point, i do not see icon for some of the items in List of Annotations. I tried to toggle the item but nothing happened.
>
> ![Screenshot_2021-04-14_at_13.21.12](/uploads/5ff0bcd53a0a001a24d37a72aed6907c/Screenshot_2021-04-14_at_13.21.12.png)https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/228Implement nested annotations2023-12-17T21:01:20ZMichelle WeidlingImplement nested annotationshttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/230Follow-up from "WIP: feat: annotations": re-check this after loading spinner ...2023-12-17T21:27:30ZMichelle WeidlingFollow-up from "WIP: feat: annotations": re-check this after loading spinner have been mergedThe following discussion from !132 should be addressed:
- [ ] @mrodzis started a [discussion](https://gitlab.gwdg.de/subugoe/emo/Qviewer/-/merge_requests/132#note_301097): (+5 comments)
> Having a fresh page and clicking "highligh...The following discussion from !132 should be addressed:
- [ ] @mrodzis started a [discussion](https://gitlab.gwdg.de/subugoe/emo/Qviewer/-/merge_requests/132#note_301097): (+5 comments)
> Having a fresh page and clicking "highlight > none" yields the following:
>
> ![image](/uploads/7bc86c522f86e94ce28175728a7ff210/image.png)
>
> I would expect to have all highlighting to be removed, not only the icons.https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/232Refactor Annotations2021-05-31T13:43:57ZMathias GoebelRefactor Annotationssee: https://gitlab.gwdg.de/subugoe/emo/Qviewer/-/merge_requests/132#note_307500see: https://gitlab.gwdg.de/subugoe/emo/Qviewer/-/merge_requests/132#note_307500Mathias GoebelMathias Goebelhttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/233Create Favicon2021-04-27T05:59:46ZNils WindischCreate FaviconNils WindischNils Windischhttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/234CI: finetune pipelines after removing entry points2023-12-17T21:28:01ZMichelle WeidlingCI: finetune pipelines after removing entry points# Bugs
## Description
After removing the entry point in `index.html`, all stages of the current pipeline should be aborted.
### I expected the following to happen
After removing the entry point in `index.html`, all stages of the curr...# Bugs
## Description
After removing the entry point in `index.html`, all stages of the current pipeline should be aborted.
### I expected the following to happen
After removing the entry point in `index.html`, all stages of the current pipeline should be aborted.
### On the contrary, I observed
Only the `build` stage is omitted, while the process still tries to create a page in the `pages` job. This results in an error because the site hasn't been built in the first place.
## How to reproduce the bug
_Steps:_
* create a branch that has an entry point set in `index.html`
* merge this branch to `develop`
* the `pages` job fails, but the pipeline is fixed by the next pipeline triggered by the automatic commit
## Severity
How much impact does this bug have on the product or further development?
* [x] Minor
## Related Tickets
Cf. #203
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/235Follow-up from "feature/#172: Created a new keys button and modal to display ...2023-12-17T21:01:37ZNils WindischFollow-up from "feature/#172: Created a new keys button and modal to display text style labels"The following discussion from !129 should be addressed:
- [ ] @nwindis started a [discussion](https://gitlab.gwdg.de/subugoe/emo/Qviewer/-/merge_requests/129#note_306841): (+1 comment)
> What's with this odd CSS code (to the very ...The following discussion from !129 should be addressed:
- [ ] @nwindis started a [discussion](https://gitlab.gwdg.de/subugoe/emo/Qviewer/-/merge_requests/129#note_306841): (+1 comment)
> What's with this odd CSS code (to the very right in the screenshot.
>
> ![Screenshot_2021-04-23_at_15.11.13](/uploads/25b82bbcd3ef720e052751be766fbd4b/Screenshot_2021-04-23_at_15.11.13.jpg)https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/236Scroll bar issue | Follow-up from "Feature/merge panels"2023-12-17T21:02:01ZMathias GoebelScroll bar issue | Follow-up from "Feature/merge panels"In the Tree View and the annotation panel there are some issues with the scroll bar.
Behavior observed so far:
- multiple scroll bars for a single panel (next to each other)
- no scroll bar at all (so content not reachable)
- scroll bar ...In the Tree View and the annotation panel there are some issues with the scroll bar.
Behavior observed so far:
- multiple scroll bars for a single panel (next to each other)
- no scroll bar at all (so content not reachable)
- scroll bar present, but very bottom not reachable (like if we have `height: 100vh` what cannot work in a panel below a header
Recommendation is to solve this for all panels or containers inside a panel by a set of CSS rules.
Needs documentation how to use flexbox correctly in this case.
The following discussion from !139 should be addressed:
- [ ] @mrodzis started a [discussion](https://gitlab.gwdg.de/subugoe/emo/Qviewer/-/merge_requests/139#note_308760): (+2 comments)
> I have two scrollbars now.
>
> ![image](/uploads/2636f9d68cf177f9418740c0f930b39e/image.png)
>
> If this is the intended behavior, I'll approve.https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/244missing dark mode for panel title2021-05-12T06:16:44ZNils Windischmissing dark mode for panel title# Bugs
## Description
Just leave a short summary what the bug is about and in which context you noticed it.
Feel free to delete sections that doesn't suit the case you're dealing with.
### I expected the following to happen
…
### On...# Bugs
## Description
Just leave a short summary what the bug is about and in which context you noticed it.
Feel free to delete sections that doesn't suit the case you're dealing with.
### I expected the following to happen
…
### On the contrary, I observed
…
## How to reproduce the bug
Please describe briefly how you discovered the bug and what a developer has to do to reproduce it.
_Steps:_
* Step 1
* Step 2
* ...
## Severity
How much impact does this bug have on the product or further development?
* [ ] Minor
* [ ] Major
* [ ] Critical
* [ ] Blocker
## Platform
* [ ] Unix
* [ ] Windows
* [ ] MacOS
## Browser
* [ ] Safari
* [ ] Chrome/Chromium
* [ ] Firefox
* [ ] Other: ?
## Program and – if applicable – dependency version
Which version of the software did you use?
## Related Tickets
Add related issues.
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)Nils WindischNils Windischhttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/245refactor docu after footer has been removed2023-12-17T21:28:11ZNils Windischrefactor docu after footer has been removedrewrite footer references, because there is no footer anymorerewrite footer references, because there is no footer anymorehttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/248Annotations: Update annotations according to text type.2021-05-17T12:34:34ZdindigalaAnnotations: Update annotations according to text type.# Feature Requests
## Description
Just leave a short summary what the feature is about.
Only showing the annotation about the current displayed text type
## User Stories
As (role of the user) I need (what has to be done) in order to...# Feature Requests
## Description
Just leave a short summary what the feature is about.
Only showing the annotation about the current displayed text type
## User Stories
As (role of the user) I need (what has to be done) in order to (what I want to achieve with this feature).
## Classification
Is this feature an enhancement of existing code or a completely new feature?
* [ ] enhancement
* [ ] new feature
## Related Tickets
Add all related issues.
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)dindigaladindigalahttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/251make tabs in various panel look the same2021-05-11T10:46:08ZNils Windischmake tabs in various panel look the same# Feature Requests
## Description
right now tabs look different in various panels (e.g. text panel), they should look like in contents and metadata panel
## Classification
* [x] enhancement# Feature Requests
## Description
right now tabs look different in various panels (e.g. text panel), they should look like in contents and metadata panel
## Classification
* [x] enhancementhttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/249Config: let projects decide which languages they want to have in TIDO2021-11-24T09:53:13ZMichelle WeidlingConfig: let projects decide which languages they want to have in TIDO# Feature Requests
## Description
GFL doesn't have an English version, so the next step after implementing #65 would be to make the languages available configurable (so that they can have a German only version of TIDO).
## User Storie...# Feature Requests
## Description
GFL doesn't have an English version, so the next step after implementing #65 would be to make the languages available configurable (so that they can have a German only version of TIDO).
## User Stories
See above.
## Classification
Is this feature an enhancement of existing code or a completely new feature?
* [ ] enhancement
* [x] new feature
## Related Tickets
Cf. 65.
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/250Chore: remove unnecessary config from root dir2021-08-12T08:23:48ZMichelle WeidlingChore: remove unnecessary config from root dir# Feature Requests
## Description
Over time a lot of config files have been created in the root directory of this repository. By now, this dir is pretty cluttered.
For clarity's sake we should move all config files (if possible) to a ...# Feature Requests
## Description
Over time a lot of config files have been created in the root directory of this repository. By now, this dir is pretty cluttered.
For clarity's sake we should move all config files (if possible) to a separate directory called `config` or the like.
## User Stories
As a developer I need a well structured repository in order to quickly find the files I need without drowning in information.
## Classification
Is this feature an enhancement of existing code or a completely new feature?
* [x] enhancement
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)Mathias GoebeldindigalaMathias Goebelhttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/253Test TIDO Integration in vue sec try2021-05-12T10:47:02ZKristine VoigtTest TIDO Integration in vue sec trydindigaladindigalahttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/254work on a concept for operating Ahiqar in the long run2021-05-12T11:34:08ZKristine Voigtwork on a concept for operating Ahiqar in the long runMichelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/272Implement Motif Tab in Annotation Panel2021-06-10T09:10:18ZKristine VoigtImplement Motif Tab in Annotation PanelAC: Tab for motifs (for now no content required)AC: Tab for motifs (for now no content required)dindigaladindigala