Version 1.9.0.0

Warning

This release introduces changes to the database schema that are not supported in a simple migration when using SQLite as the back-end. The release requires that the data is exported, the database is dropped and re-created with the new schema and the data is then re-imported. Instructions on how to do this are given, below.

Non-IMO Vessel Identifiers

• Support vessel identifiers that are not IMOs
• This allows logging of sightings of vessels such as military vessels, that do not have IMOs

Applying the Changes

• Before updating, use version 1.8.0.0 of the application to run an "all data" export
• Backup and then delete the existing database
• Edit the exported vessels CSV file and add a second column, "Is IMO", with the value "True" on each row
• Using version 1.9.0.0 of the application:
  • Re-create the database using the management application and the "--update" option
  • Use the management application to re-add users
  • Re-import the data using the management application, in the following order:
    • Countries
    • Locations
    • Operators
    • Ports
    • Vessel Types
    • Vessels
    • Voyages
    • Sightings

Version 1.8.0.0

Data Exchange and Management Improvements

• Ensure import and export of the following data is available in the management application, API and UI:
  • Countries
  • Locations
  • Voyages and associated events
  • Ports
• Added the "All" export type to export all data to multiple CSV files in one operation
• Added the port maintenance pages to the UI

Version 1.7.4.0

Voyage Picker

• Implement a popup voyage selector in the sightings addition/editing wizard
• Fix issue where navigating from the first page of the wizard to the second then back lost sighting details

Version 1.7.3.0

Port Selector

• Implement the port selector popup in the voyage event editor

Version 1.7.2.0

Sighting Editor Error

• Fix error editing sightings that have no associated voyage

Version 1.7.1.0

Voyage Builder Improvements

• Fix error submitting sighting details with missing values
• Ensure the voyage association isn't lost when editing a sighting
• Constrain IMO to 7 numeric characters on the "Sighting Search by Vessel" page
• Enforce correct UN/LOCODE format on input in the event editor
• Don't allow the "None" event type when editing events
• Retain event date between visits to the event editing page
• Added the "add same day departure" option to the event editing page

Version 1.7.0.0

Voyage Builder

• Added the voyage builder to capture published voyage details:
  • Core voyage properties
  • Voyage events (arrival at/departure from port)
• Added the ability to associated voyages with sightings

Version 1.6.0.0

Data Export via the UI

• Implement API endpoints and corresponding UI to export the following data:
  • Locations
  • Operators
  • Sightings
  • Vessels
  • Vessel Types

Version 1.5.0.0

UI-Based Data Import

• Added the ability to import the following data via the UI and API:
  • Locations
  • Countries
  • Operators
  • Vessel Types
  • Vessels
  • Sightings
  • Ports

Version 1.4.0.0

In-Application Reporting

• Implement vessel information popup on the sightings search results page
• Added the following in-application reports:
  • Job Status
  • Location Statistics
  • Sightings By Month
  • "My Voyages"
  • Operator Statistics
  • Vessel Type Statistics
  • Flag Statistics