... | ... | @@ -47,9 +47,11 @@ Therefore while it does not make sense here to provide figures for the data tran |
|
|
1. This is the default when you deploy the B2SAFE package.
|
|
|
2. This option is enabled by the parameter _msiCurlEnabled_ in the rule set [_local.re_] [1].
|
|
|
3. This option is enabled by the parameter _authzEnabled_ (=False) in the [_local.re_] [1].
|
|
|
4. This option is just for comparison, because it implies a PID creation invoked outside the B2SAFE, relying only on the [B2HANDLE library](https://github.com/EUDAT-B2SAFE/B2HANDLE).
|
|
|
4. This option is just for comparison, because it implies a PID creation invoked outside the B2SAFE, relying only on the [B2HANDLE library] [2].
|
|
|
|
|
|
## PID service (EPIC, HSv8)
|
|
|
The current PID registry system in EUDAT is based on the [EPIC implementation of the REST API](https://github.com/pidconsortium/ePIC-API-v2) and the [HANDLE system version 8](https://www.handle.net/download_hnr.html) (HSv8). But a migration to a different implementation of the REST API is planned, therefore the B2SAFE python client is provided in two versions, the default compatible with the current system and the v2, compatible with the new API, which exploits the [B2HANDLE library] [2].
|
|
|
|
|
|
|
|
|
[1]: https://github.com/EUDAT-B2SAFE/B2SAFE-core/wiki/Rule-set-configuration "local.re" |
|
|
\ No newline at end of file |
|
|
[1]: https://github.com/EUDAT-B2SAFE/B2SAFE-core/wiki/Rule-set-configuration "local.re"
|
|
|
[2]: https://github.com/EUDAT-B2SAFE/B2HANDLE "B2HANDLE library" |
|
|
\ No newline at end of file |