Close, but I think more accurate is that the goal is to show that our department has bent over backwards to make the process as easy for the enduser as we possibly can without having to invest any additional funds (my time isn't equated directly to funds, it's already budgeted).

I'll have our antivirus person check into the CSS option. Although from what I can tell from their white pages (which isn't much), I'm betting that it would be more cost effective to go with NAV mass licensing so we don't incur the added costs/headaches that go along with installing/maintaining multiple servers necessary to handle the administrative tasks ourselves.

As for the hospitals, nearly all of the critical administrative functions are done via dummy terminals to an IBM mainframe. But the "less essential" computing functions will still fall in Academic Computing's realm. Also, this is a University which is currently under proration and is being throttled by the foundation established to nurture it.

As for upper management, I really really like my job and want to keep it. My boss is great and will always try to do the right thing. Unfortunately, the final decisions are not always his alone and I'll probably end up doing this project anyway for political reasons.

"University politics are vicious precisely because the stakes are so small." -- Henry Kissinger

In reply to Re: Re: Small Project Definition by jlongino
in thread Small Project Definition by jlongino

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.