SPP 2143 Learning Through Connecting issueshttps://gitlab.cceh.uni-koeln.de/groups/spp-2143-learning-through-connecting/-/issues2022-01-27T17:09:03Zhttps://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_website/-/issues/98queries: adopt new API for entitiesMultiFilter2022-01-27T17:09:03ZAleksander Marcicqueries: adopt new API for entitiesMultiFilter* entitiesMultiFilter in branch "filterByMultiplePeriods" of ltc_hub replaced parameter "period: String" with "periods: [String]".
* to use the new features of the branch, please refactor the code of the explorer accordingly.
* afterwar...* entitiesMultiFilter in branch "filterByMultiplePeriods" of ltc_hub replaced parameter "period: String" with "periods: [String]".
* to use the new features of the branch, please refactor the code of the explorer accordingly.
* afterwards ltc_hub branch "filterByMultiplePeriods" should be merged into masterAleksander MarcicElisabeth ReuhlAleksander Marcic2021-11-23https://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_website/-/issues/54Timeline: display periods that last until "present"2021-11-16T11:24:31ZElisabeth ReuhlTimeline: display periods that last until "present"https://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_website/-/issues/49d3timeline: position labels2021-11-16T11:24:02ZAleksander Marcicd3timeline: position labelsfind a way to position the labels that does not hinder the readability of the timeline. implement the positioning.find a way to position the labels that does not hinder the readability of the timeline. implement the positioning.d3 timelineAleksander MarcicElisabeth ReuhlAleksander Marcichttps://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_website/-/issues/96Graph: correct the "center" of the svg2021-11-09T11:04:02ZElisabeth ReuhlGraph: correct the "center" of the svgthe panning does not make sense: the graph can be moved outside the visible area on the left while on the right it is stopped at the borderthe panning does not make sense: the graph can be moved outside the visible area on the left while on the right it is stopped at the borderElisabeth ReuhlElisabeth Reuhlhttps://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_website/-/issues/94switching between timeline and histogram sometimes causes bugs in timeline2021-11-08T09:29:15ZAleksander Marcicswitching between timeline and histogram sometimes causes bugs in timelineoften when switching back to the timeline, it will not be displayed.
like to be caused by resizeObserver logic (it renders correctly when console log on change of dimensions of observed element outputs "undefined" before the actual width...often when switching back to the timeline, it will not be displayed.
like to be caused by resizeObserver logic (it renders correctly when console log on change of dimensions of observed element outputs "undefined" before the actual width and height; when it outputs some other numbers first, a ghost timeline renders(can be found in DOM, but not visable))Aleksander MarcicAleksander Marcichttps://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_website/-/issues/95useResizeObserver: changing height does not trigger the event2021-11-08T09:27:27ZAleksander MarcicuseResizeObserver: changing height does not trigger the eventchanging window width triggers the event correctly, but changing height does notchanging window width triggers the event correctly, but changing height does notAleksander MarcicAleksander Marcichttps://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_website/-/issues/93tile height css calculation conflicts with height calculation in useResizeObs...2021-10-27T12:55:39ZAleksander Marcictile height css calculation conflicts with height calculation in useResizeObserverheight calculation in style.js, fullHeightTile and halfHeightTile results in height of timeline svg set to default 150height calculation in style.js, fullHeightTile and halfHeightTile results in height of timeline svg set to default 150Aleksander MarcicElisabeth ReuhlAleksander Marcichttps://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_website/-/issues/90Graph: zooming and panning2021-10-14T12:20:20ZElisabeth ReuhlGraph: zooming and panningElisabeth ReuhlElisabeth Reuhlhttps://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_website/-/issues/85Graph: set boundaries for nodes to prevent them from escaping the screen2021-10-12T09:19:26ZElisabeth ReuhlGraph: set boundaries for nodes to prevent them from escaping the screenElisabeth ReuhlElisabeth Reuhlhttps://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_website/-/issues/83Dashboard: tabs for different views on monitors2021-10-05T12:08:35ZAleksander MarcicDashboard: tabs for different views on monitorsbackground info: on each monitor of the dashboard different views on the data can be displayed. the different views on the monitors can be flipped by clicking arrows. but now preview/overview of available views is given.
task: replac...background info: on each monitor of the dashboard different views on the data can be displayed. the different views on the monitors can be flipped by clicking arrows. but now preview/overview of available views is given.
task: replace the current interface for flipping through the different views with tabs. this way the user has a better grasp what/how many views are available on each monitor.Elisabeth ReuhlElisabeth Reuhlhttps://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_hub/-/issues/39some Arachne entityTypes not returning results2021-09-13T14:45:03ZElisabeth Reuhlsome Arachne entityTypes not returning resultsExample query for Hub playground:
```graphql
query entitytypes {
entitiesMultiFilter(searchString: "*", entityTypes: [Buecher]) {
identifier
name
}
}
```
For entityTypes _MehrteiligeDenkmaeler_, _Buecher_, or _dreiDModelle_ ...Example query for Hub playground:
```graphql
query entitytypes {
entitiesMultiFilter(searchString: "*", entityTypes: [Buecher]) {
identifier
name
}
}
```
For entityTypes _MehrteiligeDenkmaeler_, _Buecher_, or _dreiDModelle_ no results are returned, instead you get the errors `GraphQLError: Syntax Error: Cannot parse the unexpected character "\u00FC".` and `Uncaught TypeError: T is undefined`.
These seem to be the entity types where the spelling of the enum values varies from Arachne's spelling (no Umlaute/numbers).Aleksander MarcicAleksander Marcichttps://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_website/-/issues/79data for timeline: handle value "present"2021-08-18T14:56:28ZAleksander Marcicdata for timeline: handle value "present"when preparing the data for the timeline:
the value "present" (for end of time span) needs to be replaced with a value that can be positioned on the timeline.when preparing the data for the timeline:
the value "present" (for end of time span) needs to be replaced with a value that can be positioned on the timeline.d3 timelineAleksander MarcicAleksander Marcichttps://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_website/-/issues/80timeline, svg dimensions: tl collapses when switched to (i.e. from histogramm)2021-08-17T11:32:30ZAleksander Marcictimeline, svg dimensions: tl collapses when switched to (i.e. from histogramm)only on initial load the dimensions can be read correctly. if the user switches to the timeline from a different view, all elements are placed in 0,0 since the reading of the dimensions results in NaNonly on initial load the dimensions can be read correctly. if the user switches to the timeline from a different view, all elements are placed in 0,0 since the reading of the dimensions results in NaNd3 timelineAleksander MarcicAleksander Marcichttps://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_website/-/issues/42Timeline: correctly find the timeRange2021-08-12T10:30:43ZElisabeth ReuhlTimeline: correctly find the timeRangeCorrectly find the earliest and latest years that need to be displayed on the timeline.
At the moment we sort in ascending order of the start dates of all timespans. Then we determine the timeRange based on the first value of the firs...Correctly find the earliest and latest years that need to be displayed on the timeline.
At the moment we sort in ascending order of the start dates of all timespans. Then we determine the timeRange based on the first value of the first object and the second value of the last object in the sorted data. But there are cases where objects start earlier but last longer than the latest-starting object, ergo the end of timeRange is currently incorrect.https://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_website/-/issues/46Dashboard view2021-07-12T17:57:46ZElisabeth ReuhlDashboard viewDraft a dashboard view of the application, similar to for example https://experience.arcgis.com/experience/478220a4c454480e823b17327b2bf1d4
--> better overview, more compact
--> boxes can be maximized by user if needed
--> possib...Draft a dashboard view of the application, similar to for example https://experience.arcgis.com/experience/478220a4c454480e823b17327b2bf1d4
--> better overview, more compact
--> boxes can be maximized by user if needed
--> possible con: map/markers too small in this view?https://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_hub/-/issues/36deprecate all use of Bestandsname for project data selection2021-04-07T13:21:44ZAleksander Marcicdeprecate all use of Bestandsname for project data selectionsince data from SPP and from single SPP projects will be fetched through catalogs now, the use of Bestandsname should be deprecated and removed from all parts of the hub and queries from the explorer
* Bestandsname was used in entitiesMu...since data from SPP and from single SPP projects will be fetched through catalogs now, the use of Bestandsname should be deprecated and removed from all parts of the hub and queries from the explorer
* Bestandsname was used in entitiesMultiFilterAleksander MarcicElisabeth ReuhlAleksander Marcichttps://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_hub/-/issues/30replace project filter on bestandsname by using catalogs2021-04-07T13:19:41ZAleksander Marcicreplace project filter on bestandsname by using catalogs* we used bestandsname to filter by project. this is not feasible (since bestandsname is not applicable to all kinds of data, etc)
* we will use catalogs to retrieve data coming from SPP projects
* existing graphql queries have to be cha...* we used bestandsname to filter by project. this is not feasible (since bestandsname is not applicable to all kinds of data, etc)
* we will use catalogs to retrieve data coming from SPP projects
* existing graphql queries have to be changed accordingly
* new queries have to be implementedAleksander MarcicAleksander Marcichttps://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_hub/-/issues/31filter by project: provide shared object with project specific ids to all que...2021-04-07T13:18:58ZAleksander Marcicfilter by project: provide shared object with project specific ids to all queries that filter by project* if we want to be able to filter all data by project before delivering it to the client, we need to know the IDs of all project related entities in iDAI.objects
* these IDs are not expected to change during the time of a session
* since...* if we want to be able to filter all data by project before delivering it to the client, we need to know the IDs of all project related entities in iDAI.objects
* these IDs are not expected to change during the time of a session
* since modification of the project filter is expected frequently, it would reduce cost to fetchAleksander MarcicAleksander Marcichttps://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_hub/-/issues/16dating extraction: keep and handle dating items bundled together when they co...2021-03-18T11:55:33ZAleksander Marcicdating extraction: keep and handle dating items bundled together when they come from a single entry in the sections* dating sections in iDAI.objects can have multiple entries
* each entry can contain several dating items
* the information which dating items stem from a shared entry in the sections is lost right now
* since different entries can refer...* dating sections in iDAI.objects can have multiple entries
* each entry can contain several dating items
* the information which dating items stem from a shared entry in the sections is lost right now
* since different entries can refer to different instances of the entity (i.e. original and replica) the information is valuable
* thus we should maintain the information in the structure of the hub data
several tasks follow from this reasoningAleksander MarcicElisabeth ReuhlAleksander Marcichttps://gitlab.cceh.uni-koeln.de/spp-2143-learning-through-connecting/ltc_hub/-/issues/33test adding catalog filter to entitiesMultiFilter2021-03-18T11:48:09ZAleksander Marcictest adding catalog filter to entitiesMultiFiltertest if the catalog filter can be added to the entitiesMultiFilter query in the hubtest if the catalog filter can be added to the entitiesMultiFilter query in the hubAleksander MarcicAleksander Marcic