Access to Services
AS 300.1 Proposals for New Software
Adopted Date:
06/16
Revision Type:
Requests and proposals for new software should be directed to the staff person’s supervisor. Supervisors may then discuss the request with location assistant managers or managers, or departmental leadership. If it is determined the software is needed for library-related business, and the budget permits, a request may be made in writing to the Director of Information Technology for consideration. A response will be provided within 30 days.
Previous Versions & Supporting Files:
- Log in to post comments
Comments
What if a committee/team composed of tech-savvy staff from across the system (including someone from IT and Leadership Team) is created to field & research these requests before they make it to the LT? The team could meet, physically or virtually, as needed & present their results to LT.
That's a great idea, Tim!
I'm not sure I understand what this Policy is for. This seems to say "If you have ideas, tell your boss", specifically about automation of services. Telling your supervisor about good ideas is excellent (and hopefully, obvious) advice, but why is it a policy?
Edit: re-reading it, it doesn't actually suggest that you tell ideas to your supervisor. It says to bring them directly to an Ad team member, which, at the time of writing, referred to Deputy Executive Directors and above, I think. That seems an odd chain of communication to me.
I am also a little confused by this policy. Based on the fact that it was last revised in 1994, I read it as "Jimmy is inventing CyberMARS as fast as he can, and he can't work with everyone calling him about features he needs to add."
Does anyone else have an alternate reading? Given that we no longer create automation solutions from scratch, but deal with vendors, should this policy be scrapped, or at least rewritten to reflect the current state of the system's relationship with our software?
A little background/history might be helpful. At one time, before Carl X, we had a committee of staff from all areas that addressed tech concerns on a monthly or quarterly basis. and yes, it was to assist Jimmy in tweaking CyberMARS, as staff came up with suggestions. that's the history of this, short and sweet - someone else might be able to give a better more concise answer than me.
In response to Todd's comment that we no longer create automation solutions from scratch, but deal with vendors - we still can give input to the vendor, thru IT (Anne.)
I think Debbie gives a good answer, and since the arrival of the new system, it has been surprising that there doesn't seem to be a way to give input, some type of "suggestion box." I have friends who work for other library systems who do call their vendor and offer suggestions. To me if we're the customer, wouldn't ideas, tips, and questions be expected and encouraged, even it didn't happen right away? (It didn't happen right away with Jimmy either, by the way). It seems if there was some type of group within the library, not all IT people, but a those with a variety of tech skills, who could pass these ideas along, that would be helpful.
Hi staff!
Thanks for your comments-- we appreciate your input.
This policy has been converted to a procedure (effective August 1) and updated/re-worded. I'll be posting the new procedure (AS 300.1, Proposals for New Software) later this afternoon.