http://localhost/query?status=!closed&keywords=~tdh&desc=1&order=type The open source data portal software en-US http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png http://localhost/query?status=!closed&keywords=~tdh&desc=1&order=type Trac 0.12.3 http://localhost/ticket/2552 http://localhost/ticket/2552 Mon, 18 Jun 2012 11:26:10 GMT ross <h2 id="Requirements">Requirements</h2> <p> To provide a freemium service it is necessary to be able to provide differing <span class="underline">levels</span> of functionality based on the <strong>type</strong> of user (see <a class="assigned ticket" href="http://localhost/ticket/2550" title="enhancement: User types (assigned)">#2550</a>). These levels can be specific to the data hub but may require overriding functionality from core to provide these checks. </p> <p> Initial implementation should focus on limiting access to datastore disk space. </p> <h2 id="Interface">Interface</h2> <p> These changes are currently only for the data hub and should be kept as much as possible within the data hub extension. </p> <h2 id="UserStories">User Stories</h2> <ul><li>As a system component I want to find out if the current user has access to a feature (i.e. storage) and if so to what extent (xMb, xGb or unlimited). </li></ul><ul><li>As a system administrator I don't expect to need to manage the levels of users <strong>or</strong> the features that this applies to. </li></ul><p> </p> <h2 id="Tasks">Tasks</h2> <p> [ ] Clarification of requirements/analysis </p> <p> [ ] Tests </p> <p> [ ] Code </p> <blockquote> <p> [ ] Model </p> </blockquote> <blockquote> <p> [ ] API </p> </blockquote> <p> </p> <blockquote> <p> [ ] UI </p> </blockquote> <p> [ ] Documentation </p> <h2 id="Estimates">Estimates</h2> Results http://localhost/ticket/2552#changelog