Skip to content

Oms API DELETE upload files

amc1999 edited this page Feb 1, 2024 · 4 revisions

DELETE upload files from the server.

This method only avaliable if server configured to allow uploads to the server by user.

Upload can be initiated through UI or by direct API call:

As result of workset upload oms service does:

  • upload archive, for example: RiskPaths.set.New-Data.zip
  • extract workset .csv files with parameters into RiskPaths.set.New-Data folder
  • extract workset .json metadata file
  • create new or update existing New-Data workset in RiskPaths model database

Methods:

DELETE /api/upload/delete/:folder
DELETE /api/upload/start/delete/:folder

First method deletes upload files from the server.

Second method will initiate deleting of upload files from the server. Actual delete performed in background and results can be checked through log file.

Arguments:

:folder - (required) upload folder file name, for example: RiskPaths.set.New-Data

Call example:

curl -v -X DELETE http://localhost:4040/api/upload/delete/RiskPaths.set.New-Data
curl -v -X DELETE http://localhost:4040/api/upload/start/delete/RiskPaths.set.New-Data

Home

Getting Started

Model development in OpenM++

Using OpenM++

Model Development Topics

OpenM++ web-service: API and cloud setup

Using OpenM++ from Python and R

Docker

OpenM++ Development

OpenM++ Design, Roadmap and Status

OpenM++ web-service API

GET Model Metadata

GET Model Extras

GET Model Run results metadata

GET Model Workset metadata: set of input parameters

Read Parameters, Output Tables or Microdata values

GET Parameters, Output Tables or Microdata values

GET Parameters, Output Tables or Microdata as CSV

GET Modeling Task metadata and task run history

Update Model Profile: set of key-value options

Update Model Workset: set of input parameters

Update Model Runs

Update Modeling Tasks

Run Models: run models and monitor progress

Download model, model run results or input parameters

Upload model runs or worksets (input scenarios)

Download and upload user files

User: manage user settings

Model run jobs and service state

Administrative: manage web-service state

Clone this wiki locally