TIDO issueshttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues2020-12-04T16:39:59Zhttps://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/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/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/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/102content panel bug2021-11-24T09:57:01ZKristine Voigtcontent panel bug# Bugs
## Description
position in tree is lost when entering image fullscreen (and back) and if switch vom contents to metadata tab and back
### I expected the following to happen
same behaviour with fullscreen view.
…
### On the c...# Bugs
## Description
position in tree is lost when entering image fullscreen (and back) and if switch vom contents to metadata tab and back
### I expected the following to happen
same behaviour with fullscreen view.
…
### 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)Ahikar Version 0.14.0https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/101how to version/changelog etc2021-11-23T11:59:30ZKristine Voigthow to version/changelog etcTalk about how to do version/changelog etc -
"As team we need to get guideline/rules to all act on the basis"
**Goals:**
* having consistent commit messages in order to automatize everything as far as possible
* we want to create the...Talk about how to do version/changelog etc -
"As team we need to get guideline/rules to all act on the basis"
**Goals:**
* having consistent commit messages in order to automatize everything as far as possible
* we want to create the CHANGELOG automatically, e.g. by conventional-changelog
**Problems:**
* how to deal with merge commits? squashing locally?
**TODOs:**
* [x] @nwindis creates a repository for playing around and exploring how commitizen works
* cf. <https://gitlab.gwdg.de/subugoe/emo/committest>
* [x] @nwindis looks into pre-commit hooks
* [x] @mrodzis looks into checking commit messages via the CI/on server-sideAhikar Version 0.14.0Mathias GoebeldindigalaMathias Goebelhttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/76Release Management for EMO Viewer2021-11-23T11:59:09ZKristine VoigtRelease Management for EMO ViewerAhikar Version 0.14.0https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/65Implementation of multilingualism2021-08-25T06:01:08ZKristine VoigtImplementation of multilingualismThe viewer should support a German and English display.
The viewer should work stand alone and embedded (language selection is triggered by the website).The viewer should support a German and English display.
The viewer should work stand alone and embedded (language selection is triggered by the website).Ahikar Version 0.14.0schneider210schneider210https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/40Test Backend for EMO-Demo2020-12-03T06:23:02ZKristine VoigtTest Backend for EMO-Demo# Feature Requests
## Description
Currently the EMO-Viewer uses the Ahikar backend. EMO-Viewer Demo needs its own backend.
Should work like this: http://demo.tify.rocks/demo?manifest=https://manifests.sub.uni-goettingen.de/iiif/present...# Feature Requests
## Description
Currently the EMO-Viewer uses the Ahikar backend. EMO-Viewer Demo needs its own backend.
Should work like this: http://demo.tify.rocks/demo?manifest=https://manifests.sub.uni-goettingen.de/iiif/presentation/PPN857449303/manifest
## User Stories
As an interested person (stakeholder, project partner, product owner) I would like to be able to display various test documents via the EMO Viewer, we need a backend for the EMO Viewer Demo.
## Classification
Is this feature an enhancement of existing code or a completely new feature?
* [ ] enhancement
* [x] new feature
## Related Tickets
https://gitlab.gwdg.de/subugoe/emo/Qviewer/-/issues/29
/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.0Michelle WeidlingMichelle Weidlinghttps://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/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/410Refactoring: Move away from Quasar Framework2024-01-26T11:04:16ZMichelle WeidlingRefactoring: Move away from Quasar Framework3.1.0https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/409Collect user stories for comparing several manifests2023-02-24T11:21:42ZMichelle WeidlingCollect user stories for comparing several manifests4.0.0https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/252Roadmap about Implementation of the Variants in Annotations Panel2023-12-11T12:36:19ZKristine VoigtRoadmap about Implementation of the Variants in Annotations PanelWe already have wireframes and a concept. We need a roadmapping for the implementation steps.
Respective Ahiqar-ticket: [TIDO: implement concept for variants (AP2.b)](https://projects.academiccloud.de/projects/ahiqar/work_packages/18873...We already have wireframes and a concept. We need a roadmapping for the implementation steps.
Respective Ahiqar-ticket: [TIDO: implement concept for variants (AP2.b)](https://projects.academiccloud.de/projects/ahiqar/work_packages/18873/activity)3.1.0https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/141fix mandatory metadata fields2021-02-10T20:33:33ZKristine Voigtfix mandatory metadata fieldsAhikar Version 0.16.0Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/139fix an order for the metadata fields (viewer)2021-02-05T13:48:06ZKristine Voigtfix an order for the metadata fields (viewer)Ahikar Version 0.16.0Michelle WeidlingKristine VoigtMichelle Weidlinghttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/137Remove Ahiqar specific metadata2022-02-25T11:28:12ZMichelle WeidlingRemove Ahiqar specific metadata## Description
Currently we have code in `metadata.vue` that refers to the Ahiqar specific adaptation of the TextAPI. This encompasses:
- `x-date`
- `x-editor`
- `x-location`
- `x-origin`
These belong in the Ahiqar specific viewer, no...## Description
Currently we have code in `metadata.vue` that refers to the Ahiqar specific adaptation of the TextAPI. This encompasses:
- `x-date`
- `x-editor`
- `x-location`
- `x-origin`
These belong in the Ahiqar specific viewer, not in the generic one.Ahikar Version 0.16.0dindigaladindigalahttps://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/424Nested Metadata Object not working for nesting depth > 22024-03-08T09:12:40ZMichelle WeidlingNested Metadata Object not working for nesting depth > 2**TIDO version**: 3.2.2 (locally with `npm run serve:dev`)
Tested on `develop` branch.
---
I have a manifest that has nested metadata. Here's what it looks like (MWE):
```json
{
"@context": "https://gitlab.gwdg.de/subugoe/textapi/s...**TIDO version**: 3.2.2 (locally with `npm run serve:dev`)
Tested on `develop` branch.
---
I have a manifest that has nested metadata. Here's what it looks like (MWE):
```json
{
"@context": "https://gitlab.gwdg.de/subugoe/textapi/specs/-/raw/main/jsonld/manifest.jsonld",
"textapi": "1.1.0",
"id": "http://localhost:8001/api/eupt/KTU__1.14/manifest.json",
"label": "KTU 1.14",
"sequence": [
{
"@context": "https://gitlab.gwdg.de/subugoe/textapi/specs/-/raw/main/jsonld/sequence.jsonld",
"id": "http://localhost:8001/api/eupt/KTU__1.14/1/full.json",
"type": "item",
"label": "Volltext"
}
],
"support": [
{
"@context": "https://gitlab.gwdg.de/subugoe/textapi/specs/-/raw/main/jsonld/support.jsonld",
"type": "css",
"mime": "text/css",
"url": "http://localhost:8001/api/eupt/css/styles.css"
}
],
"license": [
{}
],
"metadata": [
{
"key": "Bibliographie",
"metadata": [
{
"key": "Fotos",
"metadata": [
{
"key": 1,
"value": "Virolleaud 1936, pl. III-IV"
},
{
"key": 2,
"value": "CTA, pl. XX-XXI"
},
{
"key": 3,
"value": "Schweich, pl. XXXVII"
},
{
"key": 4,
"value": "MOu II, CD:03 RS 2[003]+ i"
},
{
"key": 5,
"value": "ColUF"
}
]
}
]
}
]
}
```
As you can see, we have a nesting depth of 3 (technically, the TextAPI specs allows you to nest infinitely).
**What I expected**: I expected the viewer to show all levels of nesting in the Metadata Panel
**What happened**:
Nothing is displayed at all.
![image](/uploads/40205c7d045afba5aa338370d205ef74/image.png)
Also, I cannot switch to the content overview, so it seems like the manifest above causes TIDO to crash. (?)Orlin MalkjaOrlin Malkjahttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/423Use TypeScript2024-01-26T11:37:03ZPaul PestovUse TypeScript