:eek: Is this for chemistry teachers or all teachers?
Well handled. My current work number is one digit different from City Animal Control and one digit different from the main PD non-emergency line. I get roughly one animal call per week and a few PD calls per year. This is the reason that I no longer use our department’s template greeting.
If you give a long canned speil that includes “Public Works”, people ignore it or don’t know what public works includes and they launch into their complaint about their neighbor’s dog. If you just say “Yllaria, How can I help you?” Most of them say “Oh, I was trying to get the pound.” Then I can give them the correct number quickly.
I used to be annoyed by these wrong numbers. Now I’m usually relieved because this call won’t be adding to my work load.
Sometimes I miss being a temp. Except for those days when you’d show up and nobody’s actually ready for you, so you spend the entire morning sitting at an empty desk with no computer, wondering if they forgot you.
Step 1> New manager complained that we have too much access under our individual IDs and this presents too much of a risk. When pointed out that we need it to do our fucking jobs, he said we needed to work out a solution.
Step 2> I work out a solution to give the access we have to a master ID that we can ‘check out’ and log use of. (Every other proposed solution was a ludicrous amount of work and inconvenience) Once on that ID, we will remove it from our own IDs. Of course, this does absolutely nothing to mitigate any risk. We still have access, as we need to have, it just slightly inconveniences us and adds work to audit the new ID.
Step 3> I send it to his boss for approval, since the process requires him to approve IDs owned by our boss (who insisted that HE would own the ID). Grandboss’s response can best be summed up as “So what the fuck is the point of this?” I explained HOW it will work but said boss will have to explain the WHY.
We used to have that problem years ago with a complex major mainframe system: the accounting department would call about 20-30 minutes before the end of the day and say “we’ve been trying all day, but we can’t get last mights run to balance”.
So then we had to rush to look into it, we had to quickly modify the production schedule to put tonights’ run on hold, and if we needed assistance from others (like database or operations or data security) that was hard because they would have left for the day (and this long before you could login from home – you had to drive back to the office).
That problem ended when our boss told the head accountant that some senior person on their staff would also have to stay late, to verify the balance after we fixed the problem and re-ran the job. (And the first time he did this, it was late enough that the head accountant was the only one still there, so she had to stay late!).
From then on, we got problem calls much earlier – by lunchtime, at the latest. Which made it much easier for everyone to deal with such problems.
No, it also happens at the anniversary assignment date (like when it was a 1-year assignment and they extend it for another year, but security department never updates the expiration date on all your computer files, building access card, etc.)
We do database support. As part of this, we need to figure out why people’s queries aren’t running or providing the correct results. That means that WE have to have access rights to those databases. Which contain customer data. Our boss is firmly convinced that this is an untenable and unacceptable risk because - despite four months of every damned person on the team trying to explain this to him and two of us fighting him tooth and nail over it - he seems to believe that we have no business reason to have access to customer data.
Apparently, doing our fucking jobs isn’t enough of a business reason. :rolleyes:
You know, despite the owners of those databases having approved our individual accesses because they believed we had a business reason to have that access. :smack:
Another way around this:
Have each database owner set up a special Id for you to use to access their database. Thus to access Sales db’s, you use sales-support-id; for Accounting db’s you use accounting-support-id, etc.
The advantage of this is that setting up these id’s can be approved by the owners of these db’s, without requiring the approval (or even the knowledge) of your boss.
Still has disadvantages:
multiple people using one Id is a risk.
you will have to logout and login under a different id for each different area you support.
only 1 person at a time can use the id to work on a problem in that area.
But at least you can get the work done.
Isn’t it astounding that sometimes the biggest obstacle for workers is their own manager!
My former manager hired a replacement for my position. She’s tended to hire a lot of part-time grad students who just want a job for a couple years and to work with some doctors who’ll eventually write a letter of recommendation. So instead of hiring the woman with over 25 years of experience, she hires the newbie out of college going into part-time grad school, because that’s the cheaper hire. And now both of her staff in that job description will be inclined to up and leave within a year or so and have no particular ties to the job as a career. Good plan!
Access for an individual has to be approved by that person’s manager, so we can’t do this.
That’s the funniest part of the whole thing. I proposed the group ID be owned by our team lead. If we’d have gone with that, as manager he would have approved it and conversation over, it happens. But no, he insisted that HE had to own it, so that means his boss has to approve it, and therein we arrive at the “what the fuck is this?” bit.
I explained HOW it will work but said boss will have to explain the WHY. 
