Current Tasks
- [GRP-12] Provide more efficient means of retrieving all child groups and/or stems (short)
- [GRP-6] Fix subject caching (medium)
- [GRP-10] Modify membership indices (short)
- [GRP-11] StemFinder#internal_isChild generates spurious error logging (short)
- [GRP-22] Minimize member queries (medium)
- [GRP-19] Refactor privilege resolution (medium)
- [GRP-24] Reorder privilege resolvers to restore prior behavior (short)
- [GRP-7] Simplify UI for browsing (medium)
- [GRP-21] Add Group attribute caching (short)
- [GRP-17] Release Grouper API 1.2.1
Grouper Product Backlog
Most of these tasks are currently not sufficiently specified to provide an estimate on how long they will take to complete.
- [GRP-18] Update Ldappc to use better child group query filter (short)
- [GRP-14] Poor integration with Ldappc: Null DTO error message in Ldappc run causes run to fail (medium)# [GRP-15] Alter query workflow to restrict by scope before searching (medium)
- Integrated QuickStart package (? days)
- Changes/history (? days)
- Subject API v1.0 (? days)
- Multi-valued group attributes (5 days)
- blair@uchicago.edu: This will require a schema change. By adding three new columns (klass, attribute_type and is_system) to the
grouper_attributes
table the API could support a) multi-valued group attributes, b) simplify thegrouper_stems
table, c) simplify thegrouper_groups
table, d) possibly simplify thegrouper_composites
table, e) treat group type assignments as normal attributes and f) allow fields to be assigned to more than one group type. I think. Not all of these changes would need to be performed immediately but modifying the schema appropriately would allow the rest of these changes to be made on an incremental basis.- Do we need to restrict whether attributes are single- or multi-valued on a per attribute basis? If so, the complexity grows.
- Another option would be to a) make the schema change so as to allow all of secondary benefits but b) not allow normal group attributes to be multi-valued at this time.
- blair@uchicago.edu: This will require a schema change. By adding three new columns (klass, attribute_type and is_system) to the
- Add change history support to ldappc (? days)
- Subject API v1.1 (? days)
- People Picker (? days)
- Standardized Java and web services interfaces (? days)
- Signet-Grouper combined UI (? days)
- Aging & reactivation (? days)
- Hooks (? days)
- Namespace transition (? days)
- Audit (? days)
- Integrate with collaboration platform (? days)
- Multiple groupers (? days)
- Grouper should work with Hibernate 3 (4 days)
- DRY "create()", "delete()" and "update()" in DAO (2 days)
- Relocate GrouperTest out of the public API (1 day)
- Fields can be associated with more than one group type (5 days)
- Add SAX-based XML import tool (15 days)
- Do not hand generate XML during export (15 days)
- Web services interface for querying and management (? days)
- Assume
immediate='true'
in XML import (3 days) - Allow full Subject tuple to be specified in XML export-and-import tools (2 days)
- Allow subject id to be used instead of subject identifier in XML export-and-import tools (2 days)
- Add special logic to SubjectFinder.findById(id) and SubjectFinder.findByIdentifier(idfr) for GrouperAll and GrouperSystem (1 day)
- Don't write privileges to database when granting privileges to "GrouperSystem" in default privilege adapters (4 days)
- Add DAO dependency injection (10 days)
Source: blair@uchicago.edu - Review error logging so that faults, but not contingencies, are logged (2 days)
Source: blair@uchicago.edu - Database ERD (1 day)
Source: James Cramton @ Brown - Dynamic Groups (30 days)
- Some way of honoring FERPA in the API and UI (30 days)
Source: Shilen Patel @ Duke - Make subject id of current grouper session available in the Subject API (30 days)
- Improved Integration Between I2MI Components (30 days)
Source: blair@uchicago.edu- blair@uchicago.edu: This could be as simple (to begin with) as adding an "install" target to the Grouper API, Grouper UI , the Subject API and Ldappc. Perhaps even gsh? A common directory structure would also help.
Questions or comments? Contact us.