| 26 | | 2. if no project attached, prompt credential input. this screen can accommodate Google sing in later. |
| 27 | | 3. project selection. multiple choice. project info screen opens with (long) click on project |
| 28 | | 4. attaching. using previously supplied data. tries login, if fails, try registration. give users introduction/hints in the mean time. |
| 29 | | 5. successful. if no conflict. |
| 30 | | 6. conflict resolution. one screen for every project that returned "bad password" (account exists but password is wrong). give user a change to correct his data (name or email if not users account; password if user registered before with different password), only for this specific project. |
| 34 | | Concerns with initial proposal: |
| 35 | | * Users that already have different accounts with various projects or prefer having separate id-password combinations with all project accounts |
| 36 | | -> offer to supply login information separately for each project. add button to screen 2. possible to pre-populate name/email field from previous data. |
| 37 | | * Storing the users password for further attaches raises concerns |
| 38 | | -> add checkbox to screen 2 to opt-out |
| 39 | | -> or do not store password in general. require re-type if further attaches and later point in time. |
| 40 | | * Conflict resolution needs to be adapted based whether project uses name or email as identifier |
| 41 | | -> "uses_name" attribute allows distinction |
| 42 | | * WCG does not allow registration on client. Treat separately. |
| 43 | | -> prompt screen that forwards users to WCG homepage. |
| | 30 | |
| | 31 | 2. project selection. multiple choice. (long) clicking on one item brings up project description (not modeled). |
| | 32 | |
| | 33 | [[Image(b.PNG)]] |
| | 34 | |
| | 35 | |
| | 36 | 3. initial credential input. use these credentials to run registration RPC on all selected projects (excepts for those with disabled account creation, try login RPC for those). alternatively, allow user to manage accounts individually (brings up sequence at 4.2). |
| | 37 | |
| | 38 | [[Image(c.PNG)]] |
| | 39 | |
| | 40 | |
| | 41 | 4.1. batch attach. use provided credentials to run registration RPC on all selected projects (try login RPC for projects with disabled account creation). show useful hints about BOINC, swipeable through multiple hints. (what hints are useful?? ) |
| | 42 | |
| | 43 | [[Image(batch-a.PNG)]] |
| | 44 | |
| | 45 | [[Image(batch-b.PNG)]] |
| | 46 | |
| | 47 | |
| | 48 | 4.1.1. batch attach successful. |
| | 49 | |
| | 50 | [[Image(batch-success.PNG)]] |
| | 51 | |
| | 52 | |
| | 53 | 4.1.2. batch attach has conflicts. offer user distinction between registration and login for clarity. multiple conflicts possible, show sequence of resolution screens for each (conflicting) project individually. three scenarios possible... |
| | 54 | |
| | 55 | 4.1.2.1. project allows account registration. registration RPC returned "bad password": |
| | 56 | |
| | 57 | [[Image(conflict-1.PNG)]] |
| | 58 | |
| | 59 | 4.1.2.2. project does not allow account creation. login RPC returned "bad password": |
| | 60 | registration button opens project website |
| | 61 | |
| | 62 | [[Image(conflict-2.PNG)]] |
| | 63 | |
| | 64 | 4.1.2.3. project does not allow account creation. login RPC retunred "unknown user": |
| | 65 | retry button takes user back to input, i.e. to correct data or to use just created account |
| | 66 | skip button continues to next project in sequence |
| | 67 | |
| | 68 | [[Image(conflict-3.PNG)]] |
| | 69 | |
| | 70 | |
| | 71 | 4.2. individual attach. user has clicked corresponding button in 3. bring up sequence with login credential for every project. |
| | 72 | |
| | 73 | [[Image(individual-a.PNG)]] |
| | 74 | |
| | 75 | [[Image(individual-b.PNG)]] |
| | 76 | |
| | 77 | |
| | 78 | Remarks: |
| | 79 | * always store user name and email address of last input to pre-populate fields. |
| | 80 | * never store password |
| | 81 | * further attaches bring up same sequence (without 1. of course) |
