oceandatatools / sealog-server Goto Github PK

Store the ASNAP interval within the sealog-server database and add the ability to change the interval via API call.

An increasing number of vessels are using OpenRVDAS coupled with InfluxDB/Grafana. This provides an opportunity to leverage these technologies to build a more robust mechanism for associating position/sensor data with events.

Develop a boiler plate for querying position/sensor data for a particular timestamp and generating one or more aux_data records to submit to a sealog server.

Add the boiler plate to the ./misc folder in the sealog-server repo.

Currently there are separate scripts for creating a production DB vs devel database. Would be preferred to only have one set of scripts that automatically adjust behavior based on an environment variable.

The standard way to implement JWT authentication is to present the requestor with a JWT token that expires and a refresh JWT token. An expiring token ensures a user can't be authorized to the server indefinitely. If the user leaves the site but returns some time later after the JWT has expired then the site will require the user to re-authenticate.

The refresh JWT token is use to get a new JWT token automatically when the current JWT token expires. Token's received using the refresh token are consider "not-fresh". The idea of refresh vs not-fresh has to do with disabling certain operations without fire re-requesting the user's login credentials.

For example...
If someone logs into a site and after an hour the user walks away, somebody else could use their current session to change their password. With fresh/not-fresh token schema, the site could specify that the user's password can only be changed if the token provided is a fresh token. If the original user does actually want to change their password after an hour, the site would require them to present their login credentials (to obtain a new fresh token) before allowing the user to reach the change password form.

Given the use of bots in the Sealog-server ecosystem there would still need to be a method for obtaining a JWT that does not expire.

The standard way to present JWTs to a server that uses JWTs for authentication is to add the following header key/value pair:
Authorization: Bearer

Currently sealog only requires:
Authorization:

This will require coordination between the server and all client repos that will use this new format.

An increasing number of vessels with dedicated vehicle systems are using sealog at the ship AND vehicle levels.

Ideally it would be advantageous for the sealog servers linked to vessels to push their cruise records to any/all sealog servers associated with vehicles. This ensures the cruise records match and eliminates the need for techs to re-enter cruise records on multiple servers.

A suggestion from WHOI which have moved the server error logging from the native hapi "Boom" package to the hapi/pino package.

In looking at the code, hapi-pino is ~50 lines shorter but it's worth investigating what other pros/cons exist.

Refactor codebase for deployment via docker.

Related to a feature request on sealog-client-vehicle.

Add a section to the sealog-server API for storing items for pre-check and post-check checklist items.

Add a section to the cruise and lowering records for storing pre-check and post-check checklist results.

Make sure that when a checklist item is updated that the updated cruise/lowering record is pushed to the all connected clients.