Metadata
All objects
All metadata objects support the following fields:
* Mandatory
Projects
The following metadata fields are recognized by different interfaces for Projects:
Project Features
Metadata with additional information and features about the project:
* Mandatory
Project System Metadata
Metadata entries automatically set by MiGA:
* Mandatory
‡ By default the base name of the project path
Project Flags
Metadata entries that trigger specific behaviors in MiGA:
° By default:
blast+
. Other supported values:blast
,blat
,diamond
(except for ANI), andfastani
(only for ANI),no
(only for hAAI). If usingdiamond
and/orfastani
, the corresponding software must be installed. Important: These defaults will change in v1.0 to:blast+
for hAAI,diamond
for AAI, andfastani
for ANI.+ One of:
dupont_2012
(default), orlee_2019
Project Hooks
Additionally, hooks can be defined for projects as arrays of arrays containing the action name and the arguments (if any). For example, one can define:
or
Supported events:
on_create()
: When createdon_load()
: When loadedon_save()
: When savedon_add_dataset(object)
: When a dataset is added, with nameobject
on_unlink_dataset(object)
: When dataset with nameobject
is unlinkedon_result_ready(object)
: When any result is ready, with keyobject
on_result_ready_{result}()
: Whenresult
is readyon_processing_ready()
: When processing is complete
Supported hooks:
run_lambda(lambda, args...)
run_cmd(cmd)
Datasets
The following metadata fields are recognized by different interfaces for Datasets:
Dataset Features
Metadata with additional information and features about the dataset:
‡ Multiple values can be provided separated by commas or colons
° This is not a valid type, but it represents the closest available dataset to material that is unavailable and unlikely to ever become available. See also Federhen, 2015, NAR
Dataset System Metadata
Metadata entries automatically set by MiGA:
* Mandatory
Dataset Flags
Metadata entries that trigger specific behaviors in MiGA:
* When searching best-matching datasets, include these datasets even if they are not visited using the medoid tree
Dataset Hooks
Additionally, hooks can be defined for datasets as arrays of arrays containing the action name and the arguments. See above (project hooks) for examples.
Supported events:
on_load()
: When loadedon_save()
: When savedon_remove()
: When removedon_inactivate()
: When inactivatedon_activate()
: When activatedon_result_ready(object)
: When any result is ready, with keyobject
on_result_ready_{result}()
: Whenresult
is readyon_preprocessing_ready()
: When preprocessing is complete
Supported hooks:
run_lambda(lambda, args...)
clear_run_counts()
run_cmd(cmd)
Last updated