Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • L ltc_hub
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 15
    • Issues 15
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • SPP 2143 Learning Through Connecting
  • ltc_hub
  • Issues
  • #38

Closed
Open
Created Aug 05, 2021 by Aleksander Marcic@aleksanderOwner

period order and indirect relations: get overview by fetching all periods for a timespan

scenario: when a number of random periods from ChronOntology is given, only the direct relations among them are accessible on the individual data sets. it is not possible to know if one of the periods succeeds or derives from (etc.) another through periods not included in the current set. for the purpose of visualizations and further analysis this is problematic.
one way of dealing with the problem is taking each period in the set and fetching all related periods recursively. this is very costly.
another possibility would be to take the temporal extend of the periods given and send a query for all periods of this time frame to ChronOntology. with the fetched data should it should be possible to fill in the missing links without recursive fetching.

  • fetching periods by beginning and end time ** filters to focus query (i.e. Africa, SPP, etc.)
  • building an overview structure in which periods are related to another (or just add missing link periods to the result set of periods?)
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking