... | ... | @@ -50,7 +50,13 @@ Therefore while it does not make sense here to provide figures for the data tran |
|
|
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].
|
|
|
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].
|
|
|
|
|
|
The upgrade to the new handle library can be done as follows:
|
|
|
- install b2handle library
|
|
|
- create private/public keys, certificates and interacts with the PID registry administrator to get the public key uploaded
|
|
|
- test the new python client called _epicclient2.py_ alongside the working _epicclient.py_. It is enough to extend the existing credentials file with new parameters and add the certificates location in there.
|
|
|
- to switch over: change link _/var/lib/irods/iRODS/server/bin/cmd/epicclient.py_ to point to _/opt/eudat/b2safe/cmd/epicclient2.py_ .
|
|
|
|
|
|
|
|
|
[1]: https://github.com/EUDAT-B2SAFE/B2SAFE-core/wiki/Rule-set-configuration "local.re"
|
... | ... | |