Tips On Setting Up Security Groups And Access To Your HRIS, HRMS Or HR Software

I am not an IT person so I can’t speak intelligently about how hosted, SQL or other database applications HRIS, HRMS or HR Software applications rank on a security scale. What I want to address with this article is a few important tips on setting up security groups or SQL roles for your HR Software application.
It could be easily argued that the data contained in your HR application should be the most guarded information in your organization. Social Security numbers are obvious but equally important data to protect includes payroll data, performance history, medical history, and EEO related data. As I mention above, I am not going to address protecting this information from an IT perspective. There is simply too much liability for me to make any statements or recommendations for something on which I am not qualified to offer advice.

What Should I Choose...Python 2 or Python 3 ?

At the time of writing (June 24, 2010), both are still under development. There’s at least one more 2.x release planned (2.7), but the 2.x branch probably won’t see any new major releases after that. 3.x is under active and continued development.

3.x is the newest branch of Python. People decided to clean up Python 2.x properly, with less regard for backwards compatibility than new releases in the 2.x range. Nick Efford has a nice writeup about why you might like Python 3.x as a language here: http://www.comp.leeds.ac.uk/nde/papers/teachpy3.html

Python has amassed a pretty big amount of quality software over the years. The downside of breaking backwards compatibility in 3.x is that a lot of that software doesn’t work on 3.x (yet).