Annotation Database Import App

From MediaWiki
Revision as of 00:01, 17 November 2023 by Rob (talk | contribs) (Created page with "= Background = Data for import is produced by principal investigators, annotators and NDST. As a final step, the importer will combine all of this data into a single importable dataset. There are three steps for this final import process. == Downloading Import Data == The [https://msea.dijital.ca/rov/admin/import_queue database import queue]...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Background

Data for import is produced by principal investigators, annotators and NDST. As a final step, the importer will combine all of this data into a single importable dataset.

There are three steps for this final import process.

Downloading Import Data

The database import queue page displays lists of jobs configured by principal investigators, annotators and NDST using their respective tools. You will see a table containing jobs for Principal Investigators and Annotators. Click the download button beside each one to download a JSON file containing the job data for the cruise you wish to import.

The NDST section has a button labeled, "Refresh from NDST Database". This will load the data from the Dive Logging App into a transitional table in the main database. If new equipment or personnel have been created in the Dive Logging App, a table for each will appear that will allow you to map the new equipment onto an extant piece of hardware in the database, or a new person into the personnel table. If the person or equipment haven't been created yet, you can create them by clicking the "+" button.

Below this, you will find a table marked "Current Cruises" containing complete metadata for the cruise, dives, transects, personnel and equipment configurations. Download the file for the cruise you'll be importing.

Configuration Files

The import program uses JSON configuration files. The main configuration file, named config.json by convention, though one may name them config_1.json, config_2.json, etc. if there are multiple legs.

The main config file loads a series of file [in progress...]