Contains the legacy asset management spreadsheets. These are not to be updated and exist only as a reference. Once migration to the new asset management is complete, this ARCHIVE should be removed.
This folder is for any incomplete files which are not ready for ingestion. Once the file is complete it should be moved to the appropriate folder based on file type.
This folder contains the bulk CSV file(s). The bulk file defines each asset in the system.
This folder contains calibration CSV files. These files are organized by the five character instrument class plus the one character series. Each file shall contain a complete set of calibration values for a single calibration of a single instrument. The filename must comply with the following convention:
Where the ASSET_UID is the unique identifier for the specific asset as defined in the bulk CSV file and the CALIBRATIONDATE is the date of calibration in the format YYYYMMDD.
Internally, the calibration sheet contains the following columns:
The serial number MUST match the serial number as defined the in the bulk CSV.
All calibration values are expected to be valid JSON. For example:
- [2, 3, 4]
- [[1, 2], [3, 4]]
Any calibration values longer than the Excel single cell size limit of 32,767 characters shall be represented in a separate CSV file. Currently this is utilized for the OPTAA taarray and tcarray values. In this case, the value entry in the calibration CSV should take the form:
The corresponding calibration values shall be placed in a separate CSV file using the following naming convention:
For example, for the Apr 9, 2015 calibration of A00595 (OPTAAC), the base file name is:
And the files containing CC_taarray and CC_tcarray are:
Notes are free form, limited to 256 characters.
The cruise CSV file contains data specific to OOI cruises. The columns in the cruise CSV file are:
- CUID (cruise number)
The notes are free-form.
Each deployment CSV contains one or more rows, each representing the deployment of a single asset. The columns in the deployment CSV are as follows:
- Reference Designator
The CUID_Deploy and CUID Recover fields shall contain a cruise identifier defined in the cruises CSV file. Deployment start and stop timestamps shall be in RFC 3339 format:
At a minimum, the reference designator, deployment number, version number, deployment start, mooring uid and sensor uid must be provided.
All files MUST end in _Deploy.csv. Beyond that, file naming is not restricted, but should follow a convention. The existing files all use the following scheme:
This folder contains unit and integration tests associated with asset management data. All unit tests will be executed automatically upon receipt of a pull request with the results viewable through the github pull request interface.
This folder is a temporary home to the scripts used to convert the existing data to the new format. This folder will be removed when the ARCHIVE data is removed.
This folder contains scripts used to transform this CSV data into XLSX files as expected by edex.
This folder contains scripts used to transform calibration data sheets from instrument manufacturers into calibration CSV files. These are organized by instrument type.