Page History

Roles Roadmap

Environment:

1. Move roles db off of Solaris and onto Linux VMware
2. Migrate DB from ASCII to Unicode (UTF-8)
   

In support of customer projects:

1. (done, Summer 2010) SUBJ qualifier heirachy into roles test, followed by roles production. (In support of AMPS and Online Grade submission projects)
2. (done, Summer 2010) Function category for AMPS course content
3. (done, Summer 2010) Justification for access to course registration data for AMPS?
4. Math department - implied authorization usage (waiting to hear back from Math department)
5. online grade submission (in progress) (Jim Repa is working as the primary contact with the customer) 
6. Roles to SAP feed: handle people with too many profiles without breaking the entire feed
   1. (improve Roles to SAP feed program to avoid problem of people with too many profiles, and handle error situations without stopping  the whole data feed)
7. Web app for batch file processing
   1. This was a request from George P.
   2. Paul suggest doing this as a grails application calling the Roles web service

 General service improvements:

1. Program for defragmenting a qualifier type (qualifier_id number  ranges) This program is written and has been tested on the test Roles  DB.  It will be
        useful when qualifiers of a given type run out of their number  range of qualifier_ids.  
   1. 1. Things to be added:
         1. Make sure we have good documentation
         2. Spend a couple of hours to allow a different option, to support  moving qualifier IDs to a different range
2. Expand qualifier code character limit from 15 characters to 64?
   1. Are there stored procedures or feed programs that examine the length of the qualifier code?
      1. Identify the stored procedures that would need updating
   2. Are there applications receiving data that will break if they encounter a qualifier code longer than 15 characters?
      1. Should we try to take an inventory? Or should we create a new view that would filter out codes longer than 15 characters?
         

Misc:

1. Release source to permit (in progress, 9/7/2010)
   1. Marilyn Smith and Steve Buckley have given the go ahead. Pat has provided Paul Hill with the links to the process that must be followed.
   2. Paul Heffernan has been assigned to this task.
      
      

• The odd report - look at how it changes over time. Can we improve the output of the report so that it is meaningful to more people?

• Knowledge  transfer / documentation?

• Short term Implied authorizations enhancements:
  • Rule maintenance
    • Put rule-driven EHS implied authorizations into production. (EHS implied authorizations used by the Warehouse currently use a pre-rule hard-coded SELECT statements.  The rules facility 
      has been tested for these EHS authorizations on the test Roles 
      Database.  The rule-driven implied authorizations could be re-tested and 
      moved to production in a few hours.  It would be a good way of putting 
      rule types 1a and 1b into production.  This is something Elena would like 
      to see moved to production.)

• • Minor enhancements to nightly data feed program for implied 
    Authorizations (The nightly data feed program extauth.pm needs some minor 
    Enhancements to support Function_groups in rule types 1a and 1b)

• Elena's requests (some are short-term and others may be longer-term 
  concerns)
  • accommodate a "2nd qualifier" for some HR authorizations

• • put EHS rule-driven implied authorizations into production
    
• Longer-term implied authorizations enhancements:
  • Add a UI or improve documentation for qualifier sub-types and 
    Related configuration tables (There is no UI for defining qualifier "sub-types" and links to 
    other object types.  Qualifier sub-types definitions are needed for some 
    rule types. Consider either expanding the documentation to better explain 
    this, or write a simple UI to maintain the additional configuration 
    tables, or both.)

• • Do we need more documentation about rule maintenance in general?
  • The existing four rule types support requirements for EHS and  Library, but could be made much more powerful if we allowed for  "composite" rules, i.e., rules that "and" together two or more rules of 
    existing types (e.g., you get this implied authorization if two different rule 
    conditions both fit)

• Improved qualifier schemas - better support for qualifier sub-types (rather than pattern matching of qualifier_codes used in current rules support) and better integration with Master Department 
  Hierarchy

• Qualifier maintenance
  • Exploration of moving to real-time qualifier maintenance rather 
    than batch feeds.  Could use existing stored procedures for new web 
    services, but we might want to enhance the stored procedures to update links in primary_auth_descendent table

• Adding web service methods for Qualifier maintenance
  • Check to see if existing stored procedures are sufficient to 
    support web service "wrappers", or if some enhancements need to be done for server and end-user level authorization checking