... | ... | @@ -18,12 +18,6 @@ Client side orchestration of the process: |
|
|
|
|
|
![create PID](https://raw.githubusercontent.com/wiki/EUDAT-B2SAFE/B2SAFE-core/b2safe_flows_create-PID1.png)
|
|
|
|
|
|
Server side orchestration of the process:
|
|
|
|
|
|
![create PID 2](https://raw.githubusercontent.com/wiki/EUDAT-B2SAFE/B2SAFE-core/b2safe_flows_create-PID2_v2.png)
|
|
|
|
|
|
The boxes with red borders and labels represent new patterns which rely on b2safe metadata stored on json files.
|
|
|
|
|
|
**B2SAFE metadata**
|
|
|
|
|
|
attribute: eudat_dpm_checksum_date:cinecaRes1
|
... | ... | @@ -61,22 +55,6 @@ The boxes with red borders and labels represent new patterns which rely on b2saf |
|
|
EUDATCreatePID(*parent_pid, *path, *ror, *fio, *fixed, *newPID);
|
|
|
}}
|
|
|
|
|
|
**function preview**
|
|
|
|
|
|
It is possible to get back some basic metadata even with file system only browser clients like those supporting the protocols WebDAV and GridFTP. In fact the following json file is stored within the special collection ".metadata" for each registered object:
|
|
|
|
|
|
{
|
|
|
"checksum": "[sha2:nmDjK/7k1D5jjMUFoWHjX5qZmke9vpQbR6FaY9sk6eI=](http://sha2nmDjK)",
|
|
|
"ror": "None",
|
|
|
"pid": "842/6cff9eb8-47ef-11e5-a889-fa163e62896a",
|
|
|
"checksum_timestamp": "01440065311"
|
|
|
}
|
|
|
|
|
|
The json file is stored with the following path:
|
|
|
|
|
|
**<span style="color: rgb(128,0,0);">/path/to/data set/</span>.metadata/** object-name_metadata.json
|
|
|
|
|
|
|
|
|
***
|
|
|
|
|
|
### Register PIDs for a whole collection recursively
|
... | ... | @@ -100,7 +78,7 @@ Replication process triggered client-side without PID registration ( **registere |
|
|
|
|
|
![replication](https://raw.githubusercontent.com/wiki/EUDAT-B2SAFE/B2SAFE-core/b2safe_flows_replication_v2.png)
|
|
|
|
|
|
The red box with the label "Messaging system" is an experimental feature to provide back the results in case of asynchronous (server side triggered) process. The messages are posted to a queue which can be accessed via HTTP interface. The queue is provided by dweet.io.
|
|
|
The red box with the label "Messaging system" is an experimental feature to provide back the results in case of asynchronous (server side triggered) process. The messages are posted to a queue which can be accessed via HTTP interface.
|
|
|
|
|
|
**System metadata Zone A**
|
|
|
|
... | ... | |