| 1 | | Would be good to be able to have different types of users, such as paid/default user types. Not sure *how* this should be implemented but would be great if the User model had a straightforward method for accessing this. |
| | 1 | Requirements |
| | 2 | ------------ |
| | 3 | |
| | 4 | In the data hub plugin we require the ability to differentiate users between those that have paid for a service, and those that haven't. The distinction isn't boolean as there may be levels of service for paid users, so it may be that we need a 'type' of user where there are various grades of 'paid' which are likely to be strings (specific to the data hub). |
| | 5 | |
| | 6 | |
| | 7 | Required interface |
| | 8 | ------------------ |
| | 9 | |
| | 10 | Once changes have been made to the user schema, for a given user we want to be able to: |
| | 11 | |
| | 12 | * determine if they have a paid or a free account, and |
| | 13 | * get a string name of the type of paid account. |
| | 14 | |
| | 15 | Care should be taken to ensure that the 'paid' status of the user cannot be set through the API and only by the datahub plugin. |
| | 16 | |
| | 17 | User Stories |
| | 18 | ------------ |
| | 19 | |
| | 20 | None |
| | 21 | |
| | 22 | Tasks |
| | 23 | ----- |
| | 24 | |
| | 25 | [ ] Tests |
| | 26 | |
| | 27 | [ ] Plugin based migration |
| | 28 | |
| | 29 | [ ] Code |
| | 30 | |
| | 31 | [ ] Model |
| | 32 | |
| | 33 | [ ] API |
| | 34 | |
| | 35 | [ ] Documentation |
| | 36 | |
| | 37 | |
| | 38 | Estimates |
| | 39 | --------- |
| | 40 | |
| | 41 | |
