Skip to content
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

Set and edit consumption timeout #202

Closed
trentmc opened this issue Nov 3, 2020 · 3 comments · Fixed by #324
Closed

Set and edit consumption timeout #202

trentmc opened this issue Nov 3, 2020 · 3 comments · Fixed by #324
Assignees

Comments

@trentmc
Copy link
Member

trentmc commented Nov 3, 2020

Issues:

  1. In 'publish' form, there is no way to specify length of access control. It defaults to timeout = 0, which is perpetual. I'm not sure if many people realize this. Lack of visibility could lead to contract disputes.
  2. The buyer doesn't know how long they're buying for either, unless they look into the metadata and see timeout = 0. (And know that this interprets to 'perpetual'). Lack of visibility could lead to contract disputes.
  3. The default is timeout = 0, which means that the publisher is on the hook to provide the data perpetually. This is too onerous of a default.
  4. The terms don't have language on timeout at all. And, do they distinguish between "can I use the data I've downloaded for x length of time or forever" versus "here's how long I promise to make the data (updated or not) available for you to access"?
  5. (Maybe an issue? I can't tell.) In consume, if timeout is not perpetual, can the user tell if they've timed out or not?

The solution needs to address each of these issues.

Towards a solution, the starting point is addressing (1). The GUI should have a means to make it easy to specify the time span for the license. There could be a few good defaults, e.g. 1 hour, 1 day, 1 week, 1 month, maybe 1 year. And perhaps a "custom" field. I would steer clear of giving a 'perpetual' license in terms of ability to access (though it's ok to give perpetual in terms of the right to use, once you've downloaded it).

Marking this a bug because not doing it could lead to contract disputes and onerous conditions to the publisher.

UI Spec

  • add new field to publish form, show in preview too: timeout
    • label: Download Allowance (draft)
    • help: Define how long buyers should be able to download the data set for 1 buy (draft)
    • make it a select with options: Forever, 1 week, 1 month, 1 year
  • add timeout to editable fields in edit asset screen
  • output set timeout as part of text under Buy button
  • logic for buy button needs to be adapted to decide when to show Buy, and when Download
@trentmc trentmc changed the title Length of access control is not clear for publisher or for buyer of data. Time span for access is not clear for publisher or for buyer of data. Nov 3, 2020
@trentmc trentmc added the Type: Bug Something isn't working label Nov 3, 2020
@trentmc trentmc changed the title Time span for access is not clear for publisher or for buyer of data. Time span for access is unclear; default is too onerous Nov 3, 2020
@trentmc trentmc changed the title Time span for access is unclear; default is too onerous [EPIC] Time span for access is unclear; default is too onerous Nov 3, 2020
@kremalicious kremalicious added Type: Enhancement New feature or request and removed Priority: High Type: Bug Something isn't working labels Nov 5, 2020
@trentmc trentmc added this to the V3.x milestone Nov 24, 2020
@kremalicious kremalicious removed this from the V3.x milestone Nov 24, 2020
@kremalicious kremalicious changed the title [EPIC] Time span for access is unclear; default is too onerous Set and edit consumption timeout Jan 12, 2021
@alexcos20
Copy link
Member

blocked by oceanprotocol/ocean.js#544

@alexcos20 alexcos20 added the Status: Blocked Blocked by dependency, platform requirement, etc (add comment to detail the reason) label Jan 14, 2021
@KatunaNorbert KatunaNorbert linked a pull request Jan 15, 2021 that will close this issue
@claudiaHash
Copy link
Contributor

What about this approach of displaying the timeout?

Screenshot (456)
Screenshot (457)

@kremalicious
Copy link
Contributor

great, that placement makes sense. The spacing below it could be reduced slightly by /1.5 or /2 so both sentences look more belonging to each other, but not fully.

As for exact wording, I'm still not sure. Either we find something short making it more clear what it means, or we add a tooltip behind it describing it in a longer sentence.

Starting to collect some here, any other suggestions?:

  • Allowed for 1 week
  • Download allowance for 1 week
  • Download within 1 week
  • Access for 1 week

@LoznianuAnamaria LoznianuAnamaria removed the Status: Blocked Blocked by dependency, platform requirement, etc (add comment to detail the reason) label Jul 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants