"Just Say No to Outsourcing" - Developing an In-House Info System to Take Care of Your Daily Needs
Mohyeddin Abdulaziz, University of Arizona James E. Rogers College of Law
Erica DeFrain, University of Arizona James E. Rogers College of Law
Lisa Wagenheim, University of Arizona James E. Rogers College of Law
Garnette Knoll, University of Arizona James E. Rogers College of Law
Paul G. Kealey, University of Arizona James E. Rogers College of Law

Abdulaziz began by providing an overview of why the Arizona team opted to build its own web systems for various law school services rather than simply purchase pre-built commercial solutions to meet their needs. For one thing, they had specific cost, need and availability requirements not met by other tools. They needed complete control over their systems, so only a flexible solution would do. All their systems would share core date, so integration among many systems was essential. With commercial tools, you only get what you pay for. Therefore, more functionality means more money. Similarly, with a commercial product, the ability to supplement the product is greatly inhibited. This means no customized interface or other enhancements.

The team opted instead to build its own systems using ColdFusion because it's very easy to learn. This allowed them to create browser-based applications, which meant no user training would be required.

The team's list of in-house systems built with this solution include dynamic websites, intranet sites, and services for academics, admissions, development, students, career services, financial services, IT, and the law library.

DeFrain and Wagenheim then discussed the in-house web development project in the library. They first noted that the librarians involved were not computer scientists, so they needed an easy learning curve. The projects were essentially being conducted in their spare time, so a time saving solution like a dynamic website was appropriate.

In the past, the library had a static site that was extremely time consuming to design and edit. There was no method for authenticating different users and there was no remote access provided for the the library's electronic resources. They designed the new site to have one starting point for all resources, dynamic content, fully searchable resources, and authentication for users, including remote access.

In addition, DeFrain worked on side project: ArizonaNativeNet, a web portal for indigenous resources including health, governance, law, and education. This site had limited funds and a part-time webmaster, however she was able to rework code from other law school sites to build the portal.

By working in an open environment, team members were able reuse and recycle their code for any need and could give and receive code to and from each other and other university members. ColdFusion was the key to this atmosphere of sharing.

Next, Kealey demonstrated how ColdFusion works in practice by demonstrating the University of Arizona Law School's On-Campus Interview system.

Under the old analog system, an employer would fill out a form and place it in a folder.
Students would select employers from the folder and drop their own materials into a box. Those materials were then sent to the employer who would select students to interview. Selected students would then choose an interview slot.

For the new system, a low price tag, minimal time investment, and absolute flexibility were the most important considerations. Several alternatives were considered, but they were all too costly and didn't do exactly what was needed. Instead, the team opted to create a one-stop integrated solution that was 100% web-based and provided comprehensive scheduling functionality.

Using little more than a series of web forms, the new system allows employers to register online. Students create web profiles and select from the employers' web-based materials. Employers review student materials and make selections within the system, and students then choose an interview slot, also entirely within the system. A schedule is then transmitted to the employer electronically.

Knoll wrapped up the discussion by covering how the project will work with third party expansions and other future development. Because they used ColdFusion, any SQL/Access based application can use data from other law school systems, including that generated by commercial applications. The team simply couldn't get the functionality it needed with off-the-shelf packages, and building its own system provides the law school with a fully customizable solution for today and the future.