More PAR

Today I wrote a script to populate the performance standards lookup table and ran it. We had several meetings and discussion to coordinate work on the PAR project. As a result of the information I gathered, I revised the blank for to add weigths selectable by radio buttons (3, 2, and 1) and then I added javascript pagination to the form. (Though this is not done.)

Paruser

Today Greg created the database tables for the PAR and I populated the user table (paruser) with nformation from ldap.

PAR Form Finished

I finished the blank PAR form and shipped it off, asking for revisions. I was asked to increase the height of some fields, which I did. Greg and Tony defines the Zope account in the database and Greg created the Sybase connector. Then Greg started working on a Javascript procedure to simulate a multi-page form, so we can avoid all the usual issues with multi-page forms.

Chugging Along

Once again I missed my target for getting the form converted to clean html. But I've finished the first 7 out of 9 pages and the rest should be pretty simple. I will be finished tomorrow morning. Greg has figured out how to set up permissions to restrict unauthorized access to the PAR. Since we're using LDAP to authenticate, there should be no need to create new user accounts.

PAR Continues

I continued working on the formatting of the blank PAR form. I didn't get all the way through, as I had forcat yesterday. I got bogged down in formatting the goals section, which is arguably the hardest part of the form. The problem that I'm trying to resolve is that css styling is only being applied to the first goal. I hope to get done tomorrow and I'm thinking about turning the rest of the work over to Greg so I can move onto creating the database tables. Greg got the LDAP user folder installed, which means we won't have to create passwords for everyone at the Institute.

PAR and LDAP

I started work on importing the PAR form into Zope. Work was temporarily suspended until a meeting was convened to evaluate the alternative solutions to the PAR process. In the mean time I worked on resolving several problems with the reports I produce from LDAP. I was asked to remove the automatic addition of the 516 extension to phone numbers of employees in Bloomberg and I did so. I was asked to revise the staff report to sort by division and branch and that was also done. I was asked to solve a problem with two users appearing always appearing in the list of new accounts. I couldn't reproduce that problem, so I added myself to the list of people who receive the report so I can watch for it in the future.

After the meeting I resumed work on the PAR form. I stripped the MS Word markup and placed the blank form on the HR web site. The form still needs a lot of formatting work, but from what I see now, I expect to be able to complete that work tomorrow.

Cleaning Up

I finished setting up access control for the COS TWiki and notified the user it was done. I resolved the remaining problem with my cgi script by determining that it was an artefact of how the test system was configured. We held the initial meeting on the PAR project and unless I'm told otherwise I'll start working on it when I get back from vacation on Tuesday.

Two Fronts

I worked on two things today, getting the COS Twiki configured and testing my cgi scripts on Omaha. I got the COS TWiki running by following directions and a little head scratching. I started configuring access control, but had to stop when chart got too slow to work on. So I moved over to testing my cgi scripts. I only seem to have two scripts to be ported: twogyro.pl and ywogyro_v4.pl. As the name suggestes they're variations on a theme. They work except for the code that fetches the script's name from CGI.pm. So I hope to have both done tomorrow before I leave for a four day weekend.

Script Conversion

I did more configuration of the COS TWiki, mostly updating the httpd.conf file. I asked for a restart, but haven't got it yet. Then I turned to updating my cgi scripts. I revised twogyro.pl but ran into IDL licensing problems when I tested it.

TWiki Again

I put together manpower estimates for the PAR task. Then I briefly turned to porting my cgi scripts to omaha. Then I was asked to install a TWiki for the COS group on chart, so I downloaded the latest version and started configuring it.