Also tipping the balance in Bugzilla’s favor was the support of Eric Sisler, a systems librarian for Westminster Public Library, who provided the Auraria staff with support in launching Bugzilla. Given the lack of Library resources available for managing this type of tool, this level of responsive external community support was crucial. Extensive community support was also available via a newsgroup, a mailing list, and an IRC channel. It allowed for quick, local customization and rapid launch without extensive programming or specialized knowledge of Perl, neither of which were available in the Library at the time. The primary tools evaluated included Bugzilla ( ), SugarCRM ( ) Request Tracker (aka RT, ), h2desk ( ), OTRS ( ), and Eventum ( ).īugzilla was the final choice because it was compatible with the local server environment, it was easy to install and customize, and its broad user base ensured future development. The most desirable criteria included ease and speed of deployment, low cost-both in terms of money and staff resources, and suitability of the current server environments available to the Library IT staff. In order to find an appropriate tool, IT staff investigated half a dozen or so open source or low-cost options. To accommodate these drastic personnel changes and achieve this improved efficiency, the Library’s IT staff recognized the need to modernize workflow management using a powerful communication and tracking tool. This necessitated a more formal means of tracking, delegating, and resolving reported issues. As the responsibilities of the Systems Department (re-titled the Division of Technology Strategy and Learning Spaces) were re-envisioned, its director sought ways to improve efficiency and communication both within the department and beyond to the entire Library. In particular, this would allow the IT Manager to pursue larger-scale projects that would benefit the library technology environment such as server virtualization and thin clients for public workstations. In January of 2009, the Network Administrator and Desktop Support Technician positions were re-filled and four student workers were hired with the intent that this team would be able to provide most of the library-wide desktop support, freeing other Systems staff members from these operational duties. A dedicated phone line, checked frequently during the Library’s open hours, served as the primary means of reporting technology issues. ![]() Prior to the reorganization, the six-person Systems department had managed desktop support in an ad hoc fashion. These factors emphasized the need to coordinate technology issue reporting and resolution effectively across the Library as the greatest concentration of technology skills was no longer centralized in one department. In addition, two employees with over 50 combined years of institutional knowledge retired from the department in this year. In 2008, the recommendations of an external consulting effort aimed at improving library workflows prompted a reorganization of the Auraria Library Systems Department, embedding a number of systems staff members into other departments and introducing the use of student assistants for the first time ever. Network support, including email and wireless networks available in the Library, is provided via the UCD Information Technology Services department, the UCD campus-level IT unit. The 169 public computers are always in high demand. The campus is also almost entirely a commuter campus, which puts a premium on Library space there are no dorms to which students may retreat in between classes, and the Library is quite busy during most days of the academic year. ![]() The combined student FTE is 28,000 however, part-time enrollment on campus is very high, which makes for a total student enrollment of nearly 50,000. ![]() Right, you should be able avoid using a canvas from inside the page at all.The Auraria Library is the academic library for three institutions of higher learning: the University of Colorado Denver (UCD), Metropolitan State College of Denver, and the Community College of Denver. but I don't think that is relevant from the point of view of the extension api. We would have to either re-work that or (my preference) remove that step - see. In some cases we also use it to re-encode as JPEG if some capture size threshold is exceeded. The canvas context we use to call drawWindow is pretty much just used to get a data-uri from. Yeah, we have a hard-coded opaque white background, don't think there's need to enable changing that for now: Is a background-color implicit in captureTab or might we get transparent screenshots without? Otherwise it looks like this should work. ![]() Screenshots currently calls drawWindow(window, left, top, width, height, "#fff"). The only issue I see is the lack of a bgColor option. (In reply to Sam Foster (he/him) from comment #1)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |