... | ... | @@ -124,7 +124,7 @@ If the B2SAFE administrator needs to change the local path of a collection, it c |
|
|
***
|
|
|
Those are examples of possible solutions to implement the most common data policies. They are not granted to work as they are, they could require to be adapted to the specific B2SAFE environment. But they intend to show that B2SAFE provides the building blocks to support the various data workflows and it is flexible enough to meet different scenarios.
|
|
|
|
|
|
[1]: https://github.com/EUDAT-B2SAFE/B2SAFE-core/wiki/Workflows "workflows"
|
|
|
[2]: https://github.com/EUDAT-B2SAFE/B2SAFE-core/blob/master/rulebase/pid-service.re "pid ruleset"
|
|
|
[1]: https://gitlab.eudat.eu/b2safe/B2SAFE-core/-/wikis/Workflows "workflows"
|
|
|
[2]: https://gitlab.eudat.eu/b2safe/B2SAFE-core/-/raw/master/rulebase/pid-service.re "pid ruleset"
|
|
|
[3]: http://datafed.org/dev/wp-content/uploads/2016/05/DFC-policy-examples.pdf "workbook"
|
|
|
[4]: https://docs.irods.org/master/plugins/dynamic_policy_enforcement_points "dynamic PEP" |
|
|
\ No newline at end of file |