sitcomlab / ive Goto Github PK

Implementation of user accounts to create and manage own Scenarios.

Refactor search in Backend with a server-side full-text search

• Backend controllers
• Frontend controllers
• Remote controllers

A map showing all locations with markers (abstract, indoor, outdoor) and their related connected_to relationships.

• Main map view
  • Load all locations
  • Load related connected_to relationships (in a later version)
• Create location map to set coordinates by marker (working, but no marker is set; still in progress)
• Edit location map to set coordinates by marker (working, but no marker is set; still in progress)

For multi-seat usage in the context of using the IVE platform for remote / from-home studies, we need to separate the websocket events into session namespaces.

• socket.io has a feature just for that, this should be easy to implement
• server-side stored state in controllers/sockets.js also needs to be namespaced by session-ID
• Session IDs could be randomly generated could be passed via an URL parameter to the viewer and remote.
• For the remote, a further enhancement would be to
  • listing active sessions, so they can be easily switched without manually changing the URL.
  • creating new sessions

There is a bug that disables editing placement of overlays. Is related to previous changes made for video overlays.

to support spatial capabilities in Neo4j 3.x, using the point({latitude, longitude}) class as well as the built in function distance(point(a), point(b)): http://www.jexp.de/blog/html/full-text-and-spatial-search-in-neo4j-3.html

• Rename lat to latitude and lng to longitude in all apiControllers, controllers, templates and services
• Delete all lat and lng values in all indoor locations and introduce x, y values instead. This highlights the different reference systems of indoor & outdoor locations.

the production DB contains lots of trash, which makes navigating content difficult

Settings menu in the remote control app

in the Location details template, the show/hide button for connected locations does not work

• Add thumbnails for videos
• Add preview maps for locations

• CREATOR
• VIEWER

Translated names & descriptions for Scenarios, Locations, Videos (this includes some changes in the database schema):

1st example

Example location

• name: Institute for Geoinformatics in English
• name: Institut Für Geoinformatik in German

2nd example

Example location

• name: GEO1 - Lecture room in English
• name: GEO1 - Hörsaal in German

this is not a great idea, the Cache-Control HTTP header should be set

• attribute formatting in apiControllers
• Error messages in apiControllers
• Backend templates & controllers
• Fix translations (in progress)
• Renaming _id in _uuid

REST-API endpoints, which are an alternative way to interact with the IVE (Frontend) next to the already implemented websockets. The websockets are still used inside the apiControllers to forward the messages to the Frontend.

To evaluate studies, it's helpful to automatically store results.
What to store is rather study-specific, but having a general framework for action-logging (serverside?) would simplify implementations for specific studies: an ActionLogger interface, where specific data of an action can be selected for logging.

interface ActionLogger {
  onScenarioChange(new: State, old: State): any // if !!result, it will be passed to `outputHandler()`
  onLocationChange(new: State, old: State): any
  onOverlayChange(new: State, old: State):  any
  outputHandler(logdata: any): void // if not defined, output will be written to ./action_history.json
}

type State = {
  scenario: Scenario
  location: Location
  overlays: Overlay[]
}

Minimum output would be to store events in a JSON / CSV log file.
An enhanced implementation would provide a CRUD UI for these logs.
This feature would go well together with #64.

I tested new project cards on GitHub in relation with an issue.

• between remote instances
• on pageload from server state

Update Bootstrap 4 alpha 6 to Bootstrap 4 beta 1

..its deprecated since a long time.

When sourcing dependencies from npm instead, adding a buildsystem becomes necessary.
I started this work already, but lost it due to my failed-upgrade-lost-backup-fuckup.
I used esbuild as a build system, as it's far easier to configure than webpack, and also much faster.

(Vendoring all frontend dependencies does not require a build system, and is probably easiest, considering that these dependencies don't need frequent updates)

this is a really bad practice, not sure what's the idea here.

to more specific name property to avoid name conflicts in Cypher queries (especially in list all relationships queries).

Update database schema

• Scenarios: Rename name to scenario_name
• Locations: Rename name to location_name
• Videos: Rename name to videos_name
• Overlays: Rename name to overlays_name

Update apiControllers

• POST scenario
• PUT scenario
• POST location
• PUT location
• POST video
• PUT video
• POST overlay
• PUT overlay

Update controllers in Backend

• ...

Update services in

• ...

Write documentation for the missing sections:

• Installation
• Import data
• Graph structure
• Troubleshooting
• About

As a result, we already have breaking changes with threejs, and in the future more breakage is likely to ensue.

Loading failed for the <script> with source “http://localhost:5000/bower_components/three.js/examples/js/Detector.js”.

This script is not present anymore in the latest threejs version, needs some detective work to restore it from previous versions, or to migrate away from it. It doesn't seem to be required for core functionality of the viewer

with a small description and the link to the project site for installation and documentation

• no login form
  • every change to another page the alert "wrong username or password appears although no password or username has to be entered (#68)
• Adding location or Video the map is not displayed
• Overlays added via CMS are not shown in remote control (?)
• CMS: adding .obj overlay not working | obj overlay does not appear in video (+ while adding an obj overlay to a scenario it is not colored and difficult to position)

see also #69

• Add section about .env file
• Add section about video materials and public links to Sciebo drive for an example video file (GEO1 entrance)
• Add meta-graph + query

Implement pagination and filtering in the Backend: http://neo4j.com/docs/developer-manual/current/cypher/clauses/skip/

for testing, debugging and user studies

Remove multiple config.js in Backend, Frontend and Remote and unify them into a single config.js files in the public folder

We're currently stuck with unmaintained v3, because there are extensive changes between versions, including changes to the cypher query language.
Also migrating existing databases seems to be non-trivial, it might be easier to serialize DB content, and re-import it into a fresh DB.

Add a video file when creating a video and uploading in to the server.

Setup script to run install/install.cypher and install/import.cypher automatically.