Changes between Initial Version and Version 2 of Ticket #2549


Ignore:
Timestamp:
06/26/12 09:41:22 (22 months ago)
Author:
ross
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #2549

    • Property Owner changed from kindly to ross
    • Property Status changed from new to accepted
    • Property Milestone changed from ckan-v1.8 to current-ckan-sprint-2012-06-25

  • Ticket #2549 – Description

    initial v2  
    1 There seems little point in keeping groups and organizations separate.  We should merge whatever we actually need from orgs into the group model and use that as default (regardless of which security option has been set up). 
    21 
    3 Might also be cool if we could remove the need for membership and instead use FKs? 
     2== Requirements == 
     3 
     4Merge the organizations plugin into the core groups functionality. Most of this is templating and a small number of changes to the group controller. 
     5 
     6Investigate the possibility of removing the Membership model and using FKs. 
     7 
     8== Interface == 
     9 
     10This is likely to consist of: 
     11 
     12 * Updating the templates in templates/group/ 
     13 
     14 * Configuring whether we want to constrain datasets to a single group (as per organizations) 
     15 
     16 * Implementing the separate user management (add users to group). 
     17 
     18 * Checking the publisher auth to not necessarily rely on group type = 'organization' 
     19 
     20 * Making sure that the changes still work with publisher auth. 
     21 
     22 
     23== User Stories == 
     24 
     25None 
     26 
     27== Tasks == 
     28 
     29 
     30[ ] Code 
     31  
     32    [ ] Configuration 
     33   
     34    [ ] Model/Migration 
     35   
     36    [ ] Fix templates 
     37 
     38[ ] Documentation 
     39 
     40 
     41== Estimates ==