Using XML and XSLT to Transform Access to Networked Electronic Resources


	As we began working with release 2.0 “out-of-the-box” we recognized that we would require significant customization of the interface in order to meet the needs of our user base. The product allowed for extensive customization through XSLT, which required a serious time commitment on the part of our team members with that expertise. As a development partner, we were also able to turn to Endeavor for consultation. We knew that starting down the road of customization would mean more complex maintenance and integration of upgrade enhancements in future, but we anticipated that the result would be a greatly improved product for our users.

	[PAUSE]

	We started building our new system interface in earnest in late summer of 2002, with the goal of coming up live the following May. By fall of 2002, we had incorporated most of the new features and had a prototype that was functional enough to warrant user testing. While we were still early in the interface design process and had plenty of useful input from members of our cross-functional project team, we knew that hearing from our users directly at this early stage was vital.