This service allows to filter the list of samples in the MasterARMS csv file on date range (start and end date in ISO format) and geographic location (lat and lon in decimal degrees). Moreover, also the selection of specific samples is permitted. It represents the Step 3 of the ARMS Workflow within the Internal Joint Initiative.

This service represents the Step 5.3 of the ARMS Workflow within the Internal Joint Initiative. It can be run optionally on the fasta files produced by Step 5.2 (PEMA Runner) and produces an all_sequences_grouped_fasta_output.csv file as output.

This service aims to download the sequences files (fasq files) that have been choosen in Step 4 (ARMS Choose and Parameterize) in order to run PEMA. It represents the Step 5.1 of the ARMS Workflow within the Internal Joint Initiative.

This service allows to choose which column of the MasterARMS file contains the specific data to process. Moreover, it permits to provide additional files or arguments as parameters. It represents the Step 4 of the ARMS Workflow within the Internal Joint Initiative.

This service aims at getting the ARMS collection file from the IMIS database. Since the URL of the ARMS file changes each time the file is updated, and this update is transmitted to the IMIS metadata record, it is necessary to always access the URL of the file from the field in the json format of the IMIS metadata record rather than via a fixed URL. This service represents the Step 1 of the ARMS Workflow within the Internal Joint Initiative.

This service aims to reformat and produce final output in variuos formats for human and machine2machine reading. It represents the Step 9 of the ARMS Workflow within the Internal Joint Initiative.

This service aims to uploading a local file in the ARMS validation case. It represents the Step 2 of the ARMS Workflow within the Internal Joint Initiative.

This service aims at running PEMA on all the sequences from the samples selected in Step 4 (ARMS Choose and Parameterize) of the ARMS workflow. It additionally requires a parameter file (a tsv file). The service can take some hours to run. It represents the Step 5.2 of the ARMS Workflow within the Internal Joint Initiative.

This service aims at creating an OTU table with species information that can be processed by WoRMS and WRIMS (steps 7 and 8). It represents the Step 6 of the ARMS Workflow within the Internal Joint Initiative.

This step of the ARMS IJI workflow does the following: - Input: the OTU tables from the previous step (running the omics pipeline), containing taxa (usually genus or species names) obtained from the databases used by the pipeline; - Check: using the WoRMS taxon match webservice to check for the WoRMS match to those taxa; - Output: the WoRMS match (yes or not) and, if matched, the scientific name and aphiaID. It represents the Step 7 of the ARMS Workflow within the Internal Joint Initiative.