A lot of new projects didn't get completed this week. It was more of a maintenance week.
Monday was eventful. I found a couple problems with the event tracking system that I had to correct right before we moved it to production. This took up most of my day. I also worked on created a new report for the event tracking system and did some maintenance on out work order system .
Tuesday morning was the day to move the automated email system for event tracking to production. I put in on production, but couldn't get it working. After a couple hours, I finally got it set up and working. It turns out that I didn't have access to write to a directory, so the whole process was bombing. I finally got it up Tuesday for I left and had everything working 100%
Wednesday through Friday were basically maintenance days. I modified several programs and made some bug fixed. I also worked to par the Phone Directory Department list down. I'm hoping to get it down to 200 or fewer choices that way the new drop down box won't be too cluttered.
That pretty much sums up this week. There wasn't a lot of new projects, but the old ones always have to be maintained.
Tuesday, September 27, 2011
Monday, September 19, 2011
Sept 12 - 16
What a hectic week!
This week I mainly focused on programming an automated email system for event tracking. I had worked on it in previous weeks, but really set out to make it work this week. I had a goal of getting it working by friday.
This may seem like a lot of time to integrate an automated email system, but believe me, it's not. We didn't have any examples of this working at Austin Peay.
The main problem I had with setting up the system was sending attachments from Oracle. This is not an easy thing to do as there are no built in functions. I had to research and find multiple ways to do it. Eventually, I found a way to get it working, but the max attachment size was only 32k. This would hold data for about 500 students. Seeing no other ways to get it working, I implemented this process and tested it.
It worked!!! Now to test the size limit.
I made a file with 10k student records and tried to send it..... It Worked!!! Perplexed, I did further research on the size limit. It turns out that the size limit imposed is per line. Since I'm building the attachment with multiple line (CSV File), it have me no problems.
I finally got the automated email system up. It should be live on production by Tuesday!
This week I mainly focused on programming an automated email system for event tracking. I had worked on it in previous weeks, but really set out to make it work this week. I had a goal of getting it working by friday.
This may seem like a lot of time to integrate an automated email system, but believe me, it's not. We didn't have any examples of this working at Austin Peay.
The main problem I had with setting up the system was sending attachments from Oracle. This is not an easy thing to do as there are no built in functions. I had to research and find multiple ways to do it. Eventually, I found a way to get it working, but the max attachment size was only 32k. This would hold data for about 500 students. Seeing no other ways to get it working, I implemented this process and tested it.
It worked!!! Now to test the size limit.
I made a file with 10k student records and tried to send it..... It Worked!!! Perplexed, I did further research on the size limit. It turns out that the size limit imposed is per line. Since I'm building the attachment with multiple line (CSV File), it have me no problems.
I finally got the automated email system up. It should be live on production by Tuesday!
Friday, September 9, 2011
Sept 6 - Sept 9
This was a short week! With that being said, plenty of work got started.
This week, I worked some more with the Event Tracking. I tested to make sure all the data was getting to us and getting in the correct tables. I found an issue with events that aren't booked using the room reservation system. Currently, we are having problems linking an Event to and Event ID if the event wasn't booked using the room reservation system. I have created several solutions and began testing them. I'm hoping to implement one of the sometime next week. I will begin working on automatic emails to the event creator next week.
I have also been working on the phone directory. I'm attempting to get everyone with the same department to have the same department name. I'm setting this up so that I can have a department dropdown box requested by Dr. Luck. Hopefully I can get this up and running next week too. We currently have over 300 departments and I deem that a little too many to scroll through when looking for a specific department.
I also created and automated several reports for different faculty and worked with the faculty to ensure that the reports are being delivered in a readable format. I had to walk several people through opening reports in different programs.
Even though it was a short week, I moved forward on several projects and created some additional reports.
This week, I worked some more with the Event Tracking. I tested to make sure all the data was getting to us and getting in the correct tables. I found an issue with events that aren't booked using the room reservation system. Currently, we are having problems linking an Event to and Event ID if the event wasn't booked using the room reservation system. I have created several solutions and began testing them. I'm hoping to implement one of the sometime next week. I will begin working on automatic emails to the event creator next week.
I have also been working on the phone directory. I'm attempting to get everyone with the same department to have the same department name. I'm setting this up so that I can have a department dropdown box requested by Dr. Luck. Hopefully I can get this up and running next week too. We currently have over 300 departments and I deem that a little too many to scroll through when looking for a specific department.
I also created and automated several reports for different faculty and worked with the faculty to ensure that the reports are being delivered in a readable format. I had to walk several people through opening reports in different programs.
Even though it was a short week, I moved forward on several projects and created some additional reports.
Monday, September 5, 2011
Aug 29 - Sept 2
The main project I worked on this week was Event Tracking. I'm currently trying to set up an Event Tracking system that many departments around APSU will use to track student events. It consists of an iPod touch in a housing that contains a bar code reader and magnetic strip reader. The students card will be scanned and later uploaded to a database on our servers. Once this is complete, the event creator will be able to pull reports of every event attended. It's actually a pretty complicated process. I'm simplifying it quite a bit.
Other activities that I worked on last week included report creating for several faculty and fixed to the APSU phone directory.
I'll continue working on the event tracking system next week.
Subscribe to:
Posts (Atom)