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/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 TypeScripthttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/422Use sequence indexes instead of item IDs2024-01-26T11:11:22ZPaul PestovUse sequence indexes instead of item IDshttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/421`target` holds array, not single object2024-03-06T09:32:33ZMichelle Weidling`target` holds array, not single objectFor rendering the annotations, TIDO currently expects an object as value for `target` instead of an array as specified in the TextAPI.
TIDO should conform to the TextAPI and switch to an array here. (This is also needed for implementing...For rendering the annotations, TIDO currently expects an object as value for `target` instead of an array as specified in the TextAPI.
TIDO should conform to the TextAPI and switch to an array here. (This is also needed for implementing the biblical references in Ahiqar.)
TIDO Code: [https://gitlab.gwdg.de/subugoe/emo/tido/-/blob/develop/src/utils/annotations.js?ref_type=heads#L290](https://gitlab.gwdg.de/subugoe/emo/tido/-/blob/develop/src/utils/annotations.js?ref_type=heads#L290 "https://gitlab.gwdg.de/subugoe/emo/tido/-/blob/develop/src/utils/annotations.js?ref_type=heads#L290")
TextAPI specs: https://subugoe.pages.gwdg.de/emo/text-api/page/annotation_specs/#annotation-item-objecthttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/420Configuration for labels in tido-config.js not working2024-01-10T11:35:51ZMichelle WeidlingConfiguration for labels in tido-config.js not workingWhen embedding TIDO, we have the possibility to set global labels for `item` and `manifest`.
In EUPT, we use
```json
labels: {
item: "Kolumne",
manifest: "Tafel"
}
```
These values are not used in TIDO, however. Instead "Sheet" fo...When embedding TIDO, we have the possibility to set global labels for `item` and `manifest`.
In EUPT, we use
```json
labels: {
item: "Kolumne",
manifest: "Tafel"
}
```
These values are not used in TIDO, however. Instead "Sheet" for `item` and "Manuscript" for `manifest` are used.
(Hint from @paul.pestov: translatable default labels)https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/419Make `support` object optional2024-01-10T10:32:51ZTillmann DönickeMake `support` object optionalError shown in TIDO viewer: `support.forEach is not a function`
Assumed cause: The `support` object is optional in the TIDO specification, but required in the TIDO implementation.
Assumed solution: Make The `support` object optional in t...Error shown in TIDO viewer: `support.forEach is not a function`
Assumed cause: The `support` object is optional in the TIDO specification, but required in the TIDO implementation.
Assumed solution: Make The `support` object optional in the TIDO implementation.https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/418Don't request manifests in sequence at init2023-09-21T09:43:15ZPaul PestovDon't request manifests in sequence at initFor various features we currently request all manifests with a collection at init time. This is not a scalable apporoach since there can be many sequence items in a collection. So we need to make sure that we retrieve the same informatio...For various features we currently request all manifests with a collection at init time. This is not a scalable apporoach since there can be many sequence items in a collection. So we need to make sure that we retrieve the same information with other methods.
- [x] One issue was already resolved by adding the `label` key to sequence items so the TreeView doesn't need the list of manifests anymore. (See #397)
- [ ] Check header
- [ ] Check metadatahttps://gitlab.gwdg.de/subugoe/emo/tido/-/issues/417Selecting all annotations leads to text panel scroll to the last highlighted2023-09-21T08:58:57ZPaul PestovSelecting all annotations leads to text panel scroll to the last highlightedFix: Do not scroll the text panel when performing "select all annotations"Fix: Do not scroll the text panel when performing "select all annotations"https://gitlab.gwdg.de/subugoe/emo/tido/-/issues/416Offer/show more than one facsimile for one document in TIDO2023-09-20T08:45:25ZRafael Maria RaschkowskiOffer/show more than one facsimile for one document in TIDO# Feature Requests
## Description
In the Sogdian Ahiqar we have a document with two different scans. They both need to be offered or shown in a way (e.g. either both are same time visible or switch picture by click on a reference or s....# Feature Requests
## Description
In the Sogdian Ahiqar we have a document with two different scans. They both need to be offered or shown in a way (e.g. either both are same time visible or switch picture by click on a reference or s.th. else).
>> Es gibt in der SUB Göttingen Bilder von 2 Fragmenten, die ein Wissenschaftler im Jahr 1941 erstellt hat. Ich habe mit der SUB über die Nutzung und Veröffentlichung dieser Bilder gesprochen und es gibt hierzu keine Einwände (auch von rechtlicher Seite nicht). D.h. wir haben in 2 Fällen für eine Transkription jeweils 2 Bilder.
> Hier haben wir (ausnahmsweise ;) ) eine einfache Lösung: Mehrere Facsimiles können über mehrere URIs in @facs angegeben werden:
> <pb n="1r" facs="textgrid:uri1 textgrid:uri2"/>
> Die URIs müssen nur durch ein Leerzeichen voneinander getrennt sein. Darüber, wie wir das in TIDO darstellen müssen wir uns noch Gedanken machen (@Rafael Maria).
## User Stories
As a scientist I need to be able to compare the text with the respective picture where it is written originally even when the text is split in two pictures.
## 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)