Please goto to https://github.com/OceanDataTools/openvdm for current releases of OpenVDM.

OpenVDMv2 is a ship-wide data management platform. It is comprised of a suite of programs and an accompanying web-application that provides vessel operators with a unified at-sea solution for retrieving and organizing files from multiple data acquisition systems into a unified cruise data package. Once the files are within the cruise data package they are immediately and safely accessible by crew and scientists. In addition OpenVDM can perform regularly backups of the cruise data package to one or more backup storage location/devices such as NAS arrays, external hard drives and even to shore-based servers.

OpenVDMv2 includes a plugin architecture whereby vessel operators can develop and install their own data processing plugins used to web-based visualizations, perform data quality assurance (QA) tests and collecting data statistics at the file-level. In practice the output data from plugins is ~5% the size of the raw data files, making the architecture ideal for projecting situatitional off-ship to institute or cloud-based servers over low-bandwidth connections.

OpenVDMv2 includes a hooks architure whereby vessel operators can link custom processes to run at key milestones during a cruise such as the start/end of a cruise, after a specific data transfer or after a data processing plugin completes. The allow vessels operators to design and deploy potentially very sophisticated and asynchronous data processing workflows.

OpenVDMv2 includes full RESTful API, allowing vessel operators to build their own custom web-based and stand-alone applications that leverage information stored within OpenVDMv2 for their own, vessel-specific needs.

• Support for running on Ubuntu 20.04 LTS
• Moved all python code from Python2.7 to Python3.8
• Moved all php code from 5.x to 7.3
• All python code now linted for improved quality control, support and troubleshootting.
• Improved file/directory filtering.
• Improved verbose messaging from worker processes.
• Improved OpenVDM messaging to help troubleshoot configuration issues.
• Refactored plugin architecture to simplify development and support.
• Numerous bug fixes and subtile UI improvments.

Various UI refinements and bug fixes

Slight modification to the OpenVDM database schema for Cruise Data Transfers.

Support for SMBv2.1

Added support for vessel with dedicated vehicles such as ROVs and AUVs. This supoort includes the ability to define multiple lowerings within a cruise. Lowerings have their own ID, start and stop times. Collection System Transfers can be configured to save data on a cruise-basis or lowering basis.

Added ability to define whether a the source directory for a collection system transfer from a local directory is a mount point. This is useful is the source directory is actually an externally connected device such as a USB HDD.

Added ability to define whether a the destination directory for a cruise data transfer to a local directory is a mount point. This is useful is the destination directory is actually an externally connected device such as a USB HDD.

1. The vessel operator tells OpenVDM where the data files live on the ship's network and howto connect to it (Direct connection, Samba, Rsync or SSH).
2. The vessel operator defines which remote data files to pull (include/exclude filters)
3. The vessel operator defines how pulled data files should be organized within the cruise directory on the OpenVDM Server
4. At the start of a cruise the vessel operator sets the cruise ID and start/stop dates.
5. Finally the operators sets the System Status to "On" and SHAZAAM!!!... OpenVDM starts pulling in data files and organizing per the vessel operator's specification.

As the data files roll in, OpenVDM ensures the crew and shipboard science party have immediate, safe and read-only access via http and Samba share. This workflow reduces the workload for marine techicians and improves access for the science party. (No more waking up techs in the middle of the night to get scientists their data!!!)

If the technician has setup backup locations for the data, OpenVDM use that information to continuously sync the cruise data directory with the backup locations. Continuously sync'ing the cruise data directory to its backup locations reduces the time/work needed to provide data copies for scientists and archival facities.

OpenVDM includes provisions for sending user-defined subsets of the cruise data directory to a shore-based server. These ship-to-shore transfers include a priority ranking that help ensure mission-critical data/information are pushed to shore in a timely manner and not "stuck" behind lower-priorty files. Defining new dataset to send to shore is as simple as filling out a form within the OpenVDM web-interface and clicking the "On" button.

For installation instruction please read the INSTALL.md file located in this repository.

Want to join in the fun? Please join the #openvdm Slack channel! You'll need an invite so please send a email request to oceandatarat at gmail dot com. Once in the channel please introduce yourself and let us know how you're using OpenVDM and how you'd like to contribute to the project.

• R/V Endeavor (URI Graduate School of Oceanography)
• R/V Falkor (Schmidt Ocean Institute)
• R/V Annie (Global Foundation for Ocean Exploration)
• R/V Atlantic Explorer (Bermuda Institute of Ocean Sciences)
• R/V Helmer Hanssen (UiT The Arctic University of Norway)
• R/V OceanXplorer1 (OceanX)

OpenVDM has been made possible largely by the generosity of the Schmidt Ocean Institute (SOI) who have continuously donated to the project since 2012. OpenVDM currently is the primary data management solution for SOI's R/V Falkor and the ROV Subastian In addition to financial support the marine technician aboard R/V Falkor continue to prove themselves invaluable to the development process by identifying on OpenVDM's deficiencies and providing ways to improve OpenVDM's functionality.

Thanks also to the University of Rhode Island and OceanX for their financial contributions to the project as well as the technicians aboard the R/V Falkor, R/V Endeavor, R/V Atlantic Explorer and R/V OceanXplorer1 for their patience during the early days of development and their continued support and enthusiasm for this project.

Lastly thanks the UNOLS community who have helped the project since the beginning by sharing their wealth of experience and technical ability.