... | ... | @@ -29,7 +29,7 @@ As described in the “Example Workflow” section, the iRODS rules will trigger |
|
|
There are two major scripts for the B2SHARE connection component b2shareclient.py and create_md_file.py that are using the configuration files b2safe_b2share.conf” and “create_md_file.conf” accordingly. The configurable options are identical. The configurations were only separated as the scripts could be used independently. It consists of 3 parts. The first tow sections `Logging` and `B2SHARE_HTTP_API` are prefilled with default values.
|
|
|
* `Logging` - with 2 values needed to be specified: log level, default is **log_level=DEBUG**, and the file where to safe the logging information, default value is **log_file=log/ b2safe_b2share.log**, so in a file named b2safe_b2share.log in folder log under the installation path.
|
|
|
* `B2SHARE_HTTP_API` - with 1 value needed to be specified: host_name of the B2SHARE instance, default is the address of the training instance of B2SHARE **host_name=https://trng-b2share.eudat.eu/**. Should the HTTP API of B2SHARE be changed in the meantime, than the values for the required endpoints are needed to be adapted.
|
|
|
* `iRODS` - connection information of the iRODS instance: the name of the iRODS zone like **zone_name=cinecaDMPZone** and the endpoint consisting of the host_name:port information like **zone_ep=dmp1.novalocal:1247** and the information about the iRODS **resources** to be used as well as the logical home directory in iRODS like **irods_home_dir=/cinecaDMPZone/home**.
|
|
|
* `iRODS` - connection information of the iRODS instance: the name of the iRODS zone like **zone_name=Zone1** and the endpoint consisting of the host_name:port information like **zone_ep=localhost:1247** and the information about the iRODS **resources** to be used as well as the logical home directory in iRODS like **irods_home_dir=/Zone1/home**.
|
|
|
|
|
|
# Example Workflow
|
|
|
Following workflow was considered during the component development:
|
... | ... | @@ -43,7 +43,7 @@ Following workflow was considered during the component development: |
|
|
```
|
|
|
AVUs defined for collection collection_X:
|
|
|
attribute: EUDAT_B2SHARE_RECORD_ID
|
|
|
value: f77de1f5ff5c434d97a54c116737e7d7
|
|
|
value: f77de1f5ff5c4****
|
|
|
units:
|
|
|
\----
|
|
|
attribute: EUDAT_B2SHARE_DRAFT
|
... | ... | @@ -55,7 +55,7 @@ Following workflow was considered during the component development: |
|
|
|
|
|
5. The B2SAFE administrator executes a rule to scan the repository for publications:
|
|
|
`irule "EUDATScanForPublishingOnB2share(*publishingPath, *user)"
|
|
|
"*publishingPath=/cinecaDMPZone1/publishing%*user=rods" ruleExecOut`
|
|
|
"*publishingPath=/Zone1/publishing%*user=rods" ruleExecOut`
|
|
|
The publishing path is the restricted iRODS collection where are copied the data to be published, the user in this case is the B2SAFE administrator.
|
|
|
The result of this action is:
|
|
|
* the copy of the collection to the publishing path
|
... | ... | |