http://localhost/query?milestone=datahub-july&group=status&order=resolution The open source data portal software en-US http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png http://localhost/query?milestone=datahub-july&group=status&order=resolution Trac 0.12.3 http://localhost/ticket/2548 http://localhost/ticket/2548 Mon, 18 Jun 2012 11:02:11 GMT ross <h2 id="Requirements">Requirements</h2> <p> We need to be able to easily determine who the owner of a dataset or group is. Datasets and Groups should have an Owner, who may change over time but is a specific user within the CKAN instance. It should be easy for CKAN components to determine the user and for the initial version we should ignore the can of worms labelled 'ownership transfer'. </p> <p> At this point migration is likely to be the biggest issue, and would suggest that it is acceptable that the last user to edit a dataset be set as the current owner. </p> <p> More tickets should arise as a result of this work where we may be able to optimise some queries to use the new feature. </p> <h2 id="Interface">Interface</h2> <p> None </p> <h2 id="UserStories">User Stories</h2> <p> None </p> <h2 id="Tasks">Tasks</h2> <p> [ ] <a class="missing wiki">Analysis/Clarification?</a> </p> <p> [ ] Tests </p> <p> [ ] Migration </p> <p> [ ] <a class="missing wiki">Code/Schema?</a> changes </p> <p> [ ] Documentation </p> <h2 id="Estimates">Estimates</h2> Results http://localhost/ticket/2548#changelog http://localhost/ticket/2550 http://localhost/ticket/2550 Mon, 18 Jun 2012 11:06:30 GMT ross <h2 id="Requirements">Requirements</h2> <p> 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). </p> <h2 id="Requiredinterface">Required interface</h2> <p> Once changes have been made to the user schema, for a given user we want to be able to: </p> <ul><li>determine if they have a paid or a free account, and </li><li>get a string name of the type of paid account. </li></ul><p> 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. </p> <h2 id="UserStories">User Stories</h2> <p> User stories related to the management, setting and changing of a user's payment level, as well as historical information on payments should be done as part of the work that includes actually allowing purchases. For now it is adequate that we can manually control these things through paster commands. </p> <p> Payments types should be linear as I don't believe for this type of service a pick-and-mix modular model would work well. Organizations will inherit the payment level of their owner, so currently there is no requirement for it to affect organizations at all. </p> <ul><li>As a sysadmin I would like to be able to use a paster command to manually set a user's payment level, or remove it entirely. </li></ul><ul><li>As a sysadmin I would like to be able to run a paster command to view a list of users who have a payment plan, grouped by the plan that they have. </li></ul><ul><li>As a sysadmin I would like to be able to use the API to change the payment status of a specific user through user_create and user_update. This shouldn't be available to anybody else. </li></ul><ul><li>As a user, and only if I have one, I'd like to see my current payment level on my user profile page. </li></ul><p> </p> <h2 id="Tasks">Tasks</h2> <p> [x] Tests </p> <p> [x] Plugin based migration </p> <p> [x] Code </p> <blockquote> <p> [x] Model </p> </blockquote> <blockquote> <p> [x] API </p> </blockquote> <p> [x] Documentation </p> <h2 id="Estimates">Estimates</h2> Results http://localhost/ticket/2550#changelog