SPP 2143 Learning Through Connecting issueshttps://gitlab.cceh.uni-koeln.de/groups/spp-2143-learning-through-connecting/-/issues2019-10-16T15:37:47Zhttps://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/idai.chronontology-schema/-/issues/1"$id" value not a valid url2019-10-16T15:37:47ZAleksander Marcic"$id" value not a valid url"$id": "http://...incomplete" needs to be replaced with a valid url"$id": "http://...incomplete" needs to be replaced with a valid urlhttps://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_website/-/issues/87a11y: fix keyboard navigation focus when tile gets maximized2021-10-04T13:31:13ZElisabeth Reuhla11y: fix keyboard navigation focus when tile gets maximizedProblem: when a dashboard tile is maximized the keyboard focus is no longer on it but instead in a different (not maximized) tile insteadProblem: when a dashboard tile is maximized the keyboard focus is no longer on it but instead in a different (not maximized) tile insteadhttps://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_website/-/issues/72Accessibility → enable users to navigate by keyboard2021-08-09T17:39:34ZElisabeth ReuhlAccessibility → enable users to navigate by keyboardas much as possible, but this seems to be not very good right now
Is it possible to navigate a Leaflet (markercluster) map by keyboard?
Is it possible to navigate inside of SVGs by keyboard? (to trigger onClick/onHover actions)as much as possible, but this seems to be not very good right now
Is it possible to navigate a Leaflet (markercluster) map by keyboard?
Is it possible to navigate inside of SVGs by keyboard? (to trigger onClick/onHover actions)https://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_website/-/issues/70Add bibliographic information/links from Zenon to dashboard?2021-08-09T17:39:33ZElisabeth ReuhlAdd bibliographic information/links from Zenon to dashboard?This would be an easy additional data source and could direct users to further informationThis would be an easy additional data source and could direct users to further informationhttps://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_website/-/issues/36add option to color code displayed markers to indicate dating information2020-12-03T17:24:37ZAleksander Marcicadd option to color code displayed markers to indicate dating informationfeature suggestion:
* we could color code markers to make visible the temporal relation between sides/finds on the map
* that would require a legend that indicates what color represents which time span or period
** legend should be dynam...feature suggestion:
* we could color code markers to make visible the temporal relation between sides/finds on the map
* that would require a legend that indicates what color represents which time span or period
** legend should be dynamic depending on the displayed markers
* "time heat map" could be based on these color coded markershttps://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_website/-/issues/69Add some sort of explanatory text for users to the page2021-08-09T17:39:33ZElisabeth ReuhlAdd some sort of explanatory text for users to the pageThere should be something like a short „about“ or „help“ section or similar to explain the purpose and roughly the usage of the page, with links to other SPP stuff. Limitations (such as that only some sources of SPP data are included in ...There should be something like a short „about“ or „help“ section or similar to explain the purpose and roughly the usage of the page, with links to other SPP stuff. Limitations (such as that only some sources of SPP data are included in the Explorer) should be made clear as well as where to find the primary sources of the data (links to iDAI systems etc.?).
This issue might depend on where the site is hosted and how users access it (through links from where).https://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_website/-/issues/23Add translations for filter labels2023-06-01T15:59:56ZElisabeth ReuhlAdd translations for filter labelshttps://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_hub/-/issues/40add type Literature/Reference2021-11-16T17:22:16ZAleksander Marcicadd type Literature/ReferenceAleksander MarcicAleksander Marcichttps://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_website/-/issues/11Archaeo sites mode: Add option to show siblingSites, linkedObjects2023-06-01T15:59:57ZElisabeth ReuhlArchaeo sites mode: Add option to show siblingSites, linkedObjects(similar to the relatedObjects button in objects mode)(similar to the relatedObjects button in objects mode)https://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_hub/-/issues/3charakter encoding in GQL query results2020-04-14T09:42:21ZAleksander Marciccharakter encoding in GQL query resultsquery results contain ? instead of umlautequery results contain ? instead of umlauteAleksander MarcicAleksander Marcichttps://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_website/-/issues/77Check that we avoid an impression of completeness/absoluteness of the visuali...2021-08-09T17:39:35ZElisabeth ReuhlCheck that we avoid an impression of completeness/absoluteness of the visualizations / try to represent vagueness/incompleteness of dataDashboards/visualizations can give the impression that they are showing „facts“ when in actuality the underlying data is often incomplete/not perfectly machine-readable etc.
Maybe guidelines for how (not) to employ visualizations can be ...Dashboards/visualizations can give the impression that they are showing „facts“ when in actuality the underlying data is often incomplete/not perfectly machine-readable etc.
Maybe guidelines for how (not) to employ visualizations can be helpful.https://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_website/-/issues/18context hook to provide state to subcomponents2020-08-27T15:07:01ZAleksander Marciccontext hook to provide state to subcomponentssuggestion: if the code is split up into several sub-components it might be helpful to provide the application state through the context hook to the sub-components.suggestion: if the code is split up into several sub-components it might be helpful to provide the application state through the context hook to the sub-components.https://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_website/-/issues/51d3 timeline sort periods2021-07-28T14:11:12ZAleksander Marcicd3 timeline sort periodsadd options to sort the periods on the timeline
* by beginning (end?)
* by nameadd options to sort the periods on the timeline
* by beginning (end?)
* by named3 timelineAleksander MarcicAleksander Marcichttps://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_website/-/issues/52d3 timeline zoom2021-07-29T10:50:20ZAleksander Marcicd3 timeline zoom* implement zoom for the timeline
* implement navigation when zoomed in* implement zoom for the timeline
* implement navigation when zoomed ind3 timelineAleksander MarcicAleksander Marcichttps://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_website/-/issues/53d3 timeline: display relations between periods2021-08-03T11:47:14ZAleksander Marcicd3 timeline: display relations between periods* temporal (follow, include)
* spatial* temporal (follow, include)
* spatiald3 timelineAleksander MarcicAleksander Marcichttps://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_website/-/issues/58DashboardTile: change zoom icon to a more appropriate one2021-08-09T17:39:31ZElisabeth ReuhlDashboardTile: change zoom icon to a more appropriate oneThe user is not actually zooming but changing the size of the tile so the icon should reflect that.The user is not actually zooming but changing the size of the tile so the icon should reflect that.https://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_website/-/issues/57DashboardTile: place zoom into/out of tile button so it takes up less space2021-08-09T17:39:31ZElisabeth ReuhlDashboardTile: place zoom into/out of tile button so it takes up less spacehttps://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_hub/-/issues/22dating extraction, extractChronOntologyIds: extract ids as nested array2020-10-26T15:12:44ZAleksander Marcicdating extraction, extractChronOntologyIds: extract ids as nested arrayfollow up to #21
* on function extracChronOntologyIds in datingExtraction.js
* bundle ids from a common entry into a nested array
* is: ids from all entries of the dating section are extracted into a flat array; return value is a...follow up to #21
* on function extracChronOntologyIds in datingExtraction.js
* bundle ids from a common entry into a nested array
* is: ids from all entries of the dating section are extracted into a flat array; return value is a flat array
* should be: ids from the same entry should be bundled into the same subarray; return value shoud be nested array
* include temporary fixes for consuming functionsAleksander MarcicAleksander Marcic2020-10-22https://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_hub/-/issues/25dating extraction: decide wheter/how to parse irregular datings2020-10-22T12:43:34ZElisabeth Reuhldating extraction: decide wheter/how to parse irregular datingsList of datings which are not supported by dating extraction so far (extract from query results):
```json
{
"data": {
"entitiesByString": [
//a) Teil in Klammern von letztem onDating-Element wird nicht komplett erfasst
...List of datings which are not supported by dating extraction so far (extract from query results):
```json
{
"data": {
"entitiesByString": [
//a) Teil in Klammern von letztem onDating-Element wird nicht komplett erfasst
{
"identifier": "1120932",
"onDating": [
"Vorbild: 5. Jh. v. Chr.",
"Umbildung: Mitte, 2. Jh. v. Chr.",
"Umbildung: 2. Viertel, 2. Jh. v. Chr. (Ende des 2. Viertels des 2. Jahrhunderts v. Chr.) / nach: M. Kruip"
],
"dating": [
[
"Vorbild: 5. Jh. v. Chr."
],
[
"Umbildung: Mitte, 2. Jh. v. Chr."
],
[
"Umbildung: 2. Viertel, 2. Jh. v. Chr.",
" des 2. Jahrhunderts v. Chr."
]
],
"datingSpan": [
[
"-499",
"-400"
],
[
"-166",
"-133"
],
[
"-149",
"-2"
]
]
},
//b) es wird nichts erfasst
{
"identifier": "1178152",
"onDating": [
"um 480, v. Chr."
],
"dating": [
[]
],
"datingSpan": []
},
//c) es wird nichts erfasst
{
"identifier": "1177841",
"onDating": [
"480-460, v. Chr."
],
"dating": [
[]
],
"datingSpan": []
},
//d) erstes onDating-Element wird nicht komplett erfasst, zweites onDating-Element wird nicht erfasst
{
"identifier": "1101001",
"onDating": [
" 480-470 v. Chr. / nach: Schild-Xenidou",
" 470 -460 / nach: Hiller"
],
"dating": [
[
"480-470 v. Chr."
],
[]
],
"datingSpan": [
[
"-480",
"-480"
]
]
},
//e) es wird nichts erfasst
{
"identifier": "4076412",
"onDating": [
"480, 460, v. Chr."
],
"dating": [
[]
],
"datingSpan": []
},
//f) wird nicht komplett erfasst
{
"identifier": "1169227",
"onDating": [
" (480-460 v. Chr. ) / nach: Beazley "
],
"dating": [
[
"480-460 v. Chr."
]
],
"datingSpan": [
[
"-480",
"-480"
]
]
},
//g) 'um' wird nicht erfasst
{
"identifier": "1187303",
"onDating": [
" (um 480 v. Chr.)"
],
"dating": [
[
"480 v. Chr."
]
],
"datingSpan": [
[
"-480",
"-480"
]
]
}
]
}
}
```
Double check that cases like these are handled like they are supposed to be:
```json
{
"data": {
"entitiesByString": [
//korrekt (falls nur das in Klammern beachtet werden soll)
{
"identifier": "1115446",
"onDating": [
"Anfang, 5. Jh. v. Chr. (480-460)"
],
"dating": [
[
"Anfang, 5. Jh. v. Chr. (480-460)"
]
],
"datingSpan": [
[
"-480",
"-460"
]
]
},
//korrekt (falls dass so zusammengefasst werden soll)
{
"identifier": "1111088",
"onDating": [
"2. Viertel, 5. Jh. v. Chr. (ca. 460-450 v. Chr.) <br/>- Argument: Stil / nach: D. Doepner"
],
"dating": [
[
"2. Viertel, 5. Jh. v. Chr.",
"460-450 v. Chr."
]
],
"datingSpan": [
[
"-460",
"-425"
]
]
}
]
}
}
```https://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_hub/-/issues/21dating extraction: keep relations from section entry among linked Periods2020-10-21T13:38:32ZAleksander Marcicdating extraction: keep relations from section entry among linked Periodsrelated to #16
* keep the information which ChronOntology entites have been extracted from one entry in the dating sections
* this will be relevant when we want to insert additional periods where spans across several periods are indi...related to #16
* keep the information which ChronOntology entites have been extracted from one entry in the dating sections
* this will be relevant when we want to insert additional periods where spans across several periods are indicatedAleksander MarcicAleksander Marcic