New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
DavidBlaa opened this Issue May 22, 2018 · 3 comments

Comments

Projects
None yet
4 participants
@DavidBlaa
Member

DavidBlaa commented May 22, 2018

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 #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 #29)

@DavidBlaa DavidBlaa self-assigned this May 22, 2018

@DavidBlaa DavidBlaa added this to the 2.12.0/1 milestone May 29, 2018

sventhiel added a commit that referenced this issue Jun 18, 2018

DavidBlaa added a commit that referenced this issue Jun 20, 2018

sventhiel added a commit that referenced this issue Jun 26, 2018

sventhiel added a commit that referenced this issue Jun 27, 2018

sventhiel added a commit that referenced this issue Jun 28, 2018

@sventhiel

This comment has been minimized.

Show comment
Hide comment
@sventhiel

sventhiel Jun 28, 2018

Member

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

Member

sventhiel commented Jun 28, 2018

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

@sventhiel

This comment has been minimized.

Show comment
Hide comment
@sventhiel

sventhiel Aug 13, 2018

Member

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.

Member

sventhiel commented Aug 13, 2018

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 comment has been minimized.

Show comment
Hide comment
@javadch

javadch Aug 21, 2018

Member

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

Member

javadch commented Aug 21, 2018

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

@javadch javadch closed this Aug 21, 2018

@romangerlach romangerlach changed the title from User Story 2: As a user I would like to request access to a dataset via Bexis (mail) to User Story 2: As a user I would like to request access to a dataset via Bexis (email) Sep 21, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment