... | ... | @@ -50,7 +50,7 @@ Following workflow was considered during the component development: |
|
|
value: EUDAT
|
|
|
units:
|
|
|
```
|
|
|
4. The user can modify the draft via B2SHARE or the drafted collection in B2SAFE. Once she is ready, she can add a specific metadata attribute to the collection:
|
|
|
4. The user can modify the draft via B2SHARE or the drafted collection in B2SAFE. What can be done by creating and filling a specific metadata file in the collection and using the **b2shareclient.py** to add these metadata to the draft. Once she is ready, she can add a specific metadata attribute to the collection:
|
|
|
`imeta add -C \<collection_X\> EUDAT_B2SHARE_PUBLISHME null`
|
|
|
|
|
|
5. The B2SAFE administrator executes a rule to scan the repository for publications:
|
... | ... | @@ -63,7 +63,7 @@ The publishing path is the restricted iRODS collection where are copied the data |
|
|
* the update of the draft with the new PIDs
|
|
|
* the publication in B2SHARE
|
|
|
|
|
|
Following assumptions was made:
|
|
|
Following assumptions were made:
|
|
|
* the collection hast flat structure. Sub collections will be ignored and needed to be published individually.
|
|
|
* there is just one owner for each collection.
|
|
|
* the drafts are registered in B2SHARE just one time, even if the rule to scan for draft is executed multiple times.
|
... | ... | |