Changes between Version 37 and Version 38 of BluePrintOrganisationRegistry
- Timestamp:
- 08/15/12 23:34:59 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
BluePrintOrganisationRegistry
v37 v38 16 16 Most of this functionality has already been implemented. 17 17 18 == To Do == 19 * How to handle permissions for site resources - should they inherit permissions from an organisation resource? 20 * No, they have their own permissions which are more specific than the organisation permissions, but... 21 * Have an deployment_setting to switch between: 22 a. Sites having their own permissions according to the staff of that site 23 a. All sites inheriting their permissions from the organisation's staff (site's owned_by_role = org_organisation_staff role) 24 * Allow staff for Organisation to be marked as "admin" (or something) and have them ALWAYS have permissions for any site belonging to the organisation 18 == To Do == 19 * Use the organisation register to provide specific contact list functionality: 20 * For Organisations & Offices 21 * Focus on contact details information 22 * Clearly & Easily show focal people 25 23 * if a single person is assigned as staff to multiple sites or organisations, there will be multiple site records for this person. This may cause confusion when creating staff lists. Perhaps the data structure should be revised to accommodate this. 26 24 * Make S3PersonAutocompleteWidget work with the filter criteria of the field.requires (this is required to ensure only unique staff can be added to each site) 27 25 * Organigram creator from the Staff 28 26 * ID cards from the Staff 29 * Support Organisation Groups:30 * Red Cross Movement -> Red Cross Japan31 * UN -> UNDP -> UNDP Afghanistan32 27 * Examine the represents for different sites to ensure that the provide adequate information in different context. 33 28 * This my include appending the site type and/or location name. … … 39 34 ''I'd rather not have a deployment setting here. I think we should have 1 obvious way of doing the right thing - if at all possible.'' 40 35 36 == Organisation Permissions == 37 See: S3AAA/OrgAuth for implementation details 38 39 * How to handle permissions for site resources - should they inherit permissions from an organisation resource? 40 * No, they have their own permissions which are more specific than the organisation permissions, but... 41 * Have an deployment_setting to switch between: 42 a. Sites having their own permissions according to the staff of that site 43 a. All sites inheriting their permissions from the organisation's staff (site's owned_by_role = org_organisation_staff role) 44 * Allow staff for Organisation to be marked as "admin" (or something) and have them ALWAYS have permissions for any site belonging to the organisation 41 45 42 46 == Tables == … … 76 80 * Last Name 77 81 * Title 78 79 === Projects (previously Activities) ===80 The [wiki:BluePrintProjectManagement Project Management module] will be the main repository for Projects information.81 82 ''These fields are take from a WASH (Water Health and Sanitation) Cluster form''83 * Organization (link to Org Table)84 * Location85 * Sector86 * Sub-Sector (opt)87 * Description88 * Beneficiaries (number)89 * Start Date90 * End Date91 * Funded (Y/N)92 93 4x [wiki:BluePrintMany2Many Many-to-Many] tables to link them94 * structured like {{{t2_membership}}}95 82 96 83 === Sector-to-Organisation ===