From 4a7223985ca5539fbea1cba88281af7fa0cd60bb Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Thu, 11 Jun 2020 14:51:17 +0000 Subject: [PATCH] --- ayanova/devdocs/todo.txt | 30 ++++++++++++++++++------------ 1 file changed, 18 insertions(+), 12 deletions(-) diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index b7ce953c..42457eaf 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -31,19 +31,25 @@ todo: License testing (I know it's working when these things all pass) Upon login it goes to an launch page that iterates through a set of tasks: todo: Launch page with stepper control vertical and linear steps through each step First step is welcome to AyaNova in [language] - 1) - 2) Client checks if there is a registered key for this db via server route: - EMPTY DB AND EXISTING LICENSED KEY IN RF If this DBID is already present in ROCKFISH as *licensed* and FETCHED previously then: - Form displays a message, at top about restoring with link to the manual for restoring db - Rest of form is related to releasing a previously fetched key: - Has a FETCH button on it for forcing a fetch when they have requested it or know it's coming or whatever and below that - A form to fill out to request it be released for re-fetch: - User must fill out form stating reason why and their contact info for verification - The request is emailed to us via Rockfish - We decide to release or not and can contact them etc to handle it - We can release it for refetch and then it's all automatic once daily check (maybe more frequent when unlicensed?) or they can force it + 1) done + 2) DETERMINE STATE Client checks if there is a registered key for this db via server route: + + STATE: NO KEY AND EXISTING LICENSED KEY IN RF + If this DBID is already present in ROCKFISH as *licensed* and FETCHED previously then: + Form displays a message, at top about restoring with link to the manual for restoring db + Rest of form is related to releasing a previously fetched key: + Has a FETCH button on it for forcing a fetch when they have requested it or know it's coming or whatever and below that + A form to fill out to request it be released for re-fetch: + User must fill out form stating reason why and their contact info for verification + The request is emailed to us via Rockfish + We decide to release or not and can contact them etc to handle it + We can release it for refetch and then it's all automatic once daily check (maybe more frequent when unlicensed?) or they can force it + + STATE: NO KEY AND EXISTING REVOKED KEY IN RF + We issued a license for this dbid but then revoked it for non-payment + Display a link to the contact form with message "There is a problem with your license, contact support with this dbid: " - EMPTY DB AND DBID NOT IN ROCKFISH + STATE: NO KEY AND DBID NOT IN ROCKFISH User gets a form for requesting a trial - by filling out a form in RAVEN (or using api tool) - see "trial process" below for details