... | ... | @@ -67,7 +67,8 @@ Following assumptions were made: |
|
|
* the drafts are registered in B2SHARE just one time, even if the rule to scan for draft is executed multiple times.
|
|
|
* the collections are copied and published just one time, even if the rule to publish them is executed multiple times.
|
|
|
|
|
|
# The rule will call the methods of the python script **b2shareclientCLI.py** to execute the workflow, this methods can also be called directly.
|
|
|
# scripts
|
|
|
The rule will call the methods of the python script **b2shareclientCLI.py** to execute the workflow, this methods can also be called directly.
|
|
|
|
|
|
The B2SAFE B2SHARE client has 3 major functions: draft, meta, publish; to create a draft, add metadata to and publish it. Further it has helping functions to list all names of communities available in B2SHARE, to get the schema of a community, to understand possible key value pairs of metadata file user has to fill, to get a specific draft to check it before publishing and to delete a draft if it is not correct.
|
|
|
The arguments that are needed to be specified for every call are the `--collection_path` the path to the collection in B2SAFE to operate on and the `--user` name of the user in iRODS, to get the B2SHARE access token of the user from his meta data.
|
... | ... | |