IHRIS Manage Development

From IHRIS Wiki
Revision as of 09:58, 13 February 2008 by Sturlington (talk | contribs) (Initial report; please update as needed)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Development Update – iHRIS Manage - As of March 2008

iHRIS Manage Core

Developers: Luke, Carl

Status: version 3.0 is undergoing bug testing; expect to have all documentation updated on project website and most bugs fixed by March

Next milestone: release version 3.1 (or next major release) by June to include competency model module, in-service training management module, miscellaneous improvements; there may be incremental releases before

Immediate to-do’s

  • Create a download package that includes README, install instructions, the license and changes list and post on project website
  • Update the demo on the project website
  • Announce 3.0 release on announcements mailing list/blog with changes list
  • Distribute on CD to those who requested it
  • Publicize project on Freshmeat and other websites

Would be nice (by June):

  • Add customized report builder tool (Carl; see Customizing Reports)
  • Add support for customizing roles (Carl)
  • Add import/export data functions based on offline version
  • Enable customization of field names such as district (state/province) or county (sector)
  • GIS integration
  • Add organizational chart support (see Organizational Charts)
  • See other items on wishlist (bug tracker in Launchpad)


Competency Model and In-Service Training Modules

Developer: Carl

Status: requirements have been gathered; see Blue Prints and use cases in iHRIS Manage package; development should be started

Next milestone: pilot test TBD in Tanzania (probably after June); public release expected with 3.1 release of iHRIS Manage in June

To-do’s:

  • Initial bug testing with Carl
  • Get technical reviews from IntraHealth experts (Ummuro, Cathy M., Pam M.)
  • Update documentation (based on testing results) for release
  • Write help and add to user manual for release

Would be nice:

  • Compare to the version written by local development team for the Kenya implementation of iHRIS Manage (in Java); see if any reuse or collaboration is possible
  • Spec out a version for inclusion in Qualify; see Pam for help with requirements


Offline (Windows-based) Version

Developer: Mark

Status: beta version is finished with some minor bugs remaining; will be piloted in Rwanda in February; see Offline iHRIS blueprint and use cases (in iHRIS Manage under “iHRIS Common”)

To do’s (after pilot testing and final fixes):

  • Link to download on the project website (public release)
  • Update the help manual with instructions for use
  • Announce release on mailing list/blog

Would be nice

  • Create a version for Qualify

Ongoing issues

  • Determine which data fields to lock out from decentralized changes and exclude from import/export
  • Synchronization issues still need to be addressed


IntraHealth iHRIS Manage Installation

Developers: Mark (support from Luke, Dave H., Mario); note: Mark has 20 days from Overhead HR to work on this

Status: upgraded to latest version by Carl

To do’s for Mark:

  • One-time data import from Active Directory to create records for non-US employees (coordinate with Luke and Mario)
  • Set up regular data export to propagate data to other IntraHealth internal systems and Active Directory so that the HRIS is the authoritative source of all IntraHealth employee data (coordinate with Mario, Luke and David H.)
  • Create access roles for employees and supervisors: supervisors can view records and reports, and employees can view records and update some data; see Employee, Supervisor and Manager Roles for iHRIS Manage
  • Create access role for job applicants so that applicants can log in via IntraHealth website and complete job applications; see Employee, Supervisor and Manager Roles for iHRIS Manage

Would be nice:

  • Integrate improvements into iHRIS Manage core (3.1 or later release)
  • Upgrade IntraHealth’s version to 3.1 to include competency model/in-service training modules
  • Begin gathering requirements for a benefits module (with Sarah I.)


Internationalization Support

Developer: Carl (this is a lower priority and may not be completed by June)

To-do’s:

  • Update PO files to support translations
  • Have French translator identify appropriate translations already in Launchpad
  • Have remaining text translated into French