User Story 2: As a user I would like to request access to a dataset via Bexis (email)

[DavidBlaa]

request dataset access and reply should be handled via bexis.

Who should get notified (owner)?

• There should be an owner identification algorithm that looks at the dataset’s metadata, parties, user (that committed the latest version), activity logs, and grant holders to decide who is the owner. (@sventhiel ; 1 week for clarifying the owner concept and develop ONE algorithm to resolve the owners of a given dataset + 2 days for implementation)
• All the owners would be contacted and requested to decide and reply (done already)
• Only the first reply is processed and then the request is closed.(Sven; 3 days)
• This story may lead to requirements such as request timeout, request monitoring, and request state management.
• Each metadata structure should have a mapping to the BEXIS concept of owner (similar to title and description), so that the algorithm is able to utilize it. (covered by User Story 18: As a user, I want to automatically determine and apply rights on a dataset during dataset creation. #29)
• During metadata entry/upload the designated attributes (people) should be mapped to system persons, so that later the above-mentioned algorithm is able to extract and use them. (It is possible that these persons obtain a GRANT right on the dataset) (covered by User Story 18: As a user, I want to automatically determine and apply rights on a dataset during dataset creation. #29)

[sventhiel-zz]

Instead of contacting all owners, there is currently the implementation that ONLY the first owner gets asked to decide the entity request.

[sventhiel-zz]

Currently, there is no proper management of additional properties, e.g. request timeout or request monitoring. May that will come as extension in next release / future.

[javadch]

This item is intentionally postponed: This story may lead to requirements such as request timeout, request monitoring, and request state management.