new_code_run: Post entry to code_run table

In FAIRDataPipeline/rDataPipeline: Functions to Interact with the 'FAIR Data Pipeline'

Post entry to code_run table

Description

Upload information to the code_run table in the data registry

Usage

new_code_run(
  run_date,
  description,
  code_repo_url,
  model_config_url,
  submission_script_url,
  inputs_urls = list(),
  outputs_urls = list(),
  endpoint = "http://127.0.0.1:8000/api/"
)

Arguments

run_date	the date-time of the code_run e.g. Sys.time() or "2010-07-11 12:15:00 BST"
description	(optional) a string containing a free text description of the code_run
code_repo_url	(optional) a string specifying the URL of an object associated with the code_repo_release that was run
model_config_url	(optional) a string specifying the URL of an object associated with the working config file used for the code_run
submission_script_url	(optional) a string specifying the URL of an object associated with the submission script used for the code_run
inputs_urls	a list of object_component URLs referencing code_run inputs
outputs_urls	a list of object_component URLs referencing code_run outputs
endpoint	a string specifying the registry endpoint

See Also

Other new functions: new_author(), new_code_repo_release(), new_data_product(), new_external_object(), new_file_type(), new_issue(), new_keyword(), new_licence(), new_namespace(), new_object(), new_object_component(), new_quality_controlled(), new_storage_location(), new_storage_root(), new_user_author()

FAIRDataPipeline/rDataPipeline documentation built on Dec. 4, 2024, 4:09 a.m.