This is a non-issue. People use google.com's website of their own volition. The search results come from Google's database, there is no hindering of businesses or anti-trust issue here at all since all of the information gleaned on the internet is already present. Google merely presents it how they deem necessary to match the search keywords.

TL;DR: Fuck off.

Do ensure that it has nearby and adequate washroom facilities. Nothing worse than having to travel up a couple flights of stairs every time personnel has to take care of nature, know what I mean?

Adequate lighting, and ventilation / heating / air conditioning is also something to consider. Nothing worse then working in winter with cold fingers, let me tell you.

I've been NOC for just shy of 3 years now, and I can tell you the environment you work in plays a huge role in how comfortably you handle the workflow. Its nice to focus on the more technical bits such as equipment and infrastructure, monitors, etc, but do not forget that people have to comfortably be there for hours at a time. We do 12 hour shifts here, and the most important consideration would be the temperature and air quality, imho.

Don't want to try an ancient filesystem? Mac OS X also makes use of Extended File Attributes, as do most modern filesystems. All it takes is a little bit of work with the help of some great command line or even gasp, GUI programs to do properly manage the media collection.

Hell, I was editing my own mp3 collection using BeOS 3.1 in 1999 because it was EASY back then to do so.

There's more tools out there than you can shake a stick at, and if just because you haven't thought of it, doesn't mean someone else hasn't already wrote it.

I currently work for an ISP and can tell you from experience that using a simple Wiki (such as mediaWiki) to document each segment of the network works very well.

You can further break it down by recurring issues, objectives and repairs/upgrades as you go along, making good use of the built-in version tracking feature as well.

Don't underestimate even simple ASCII representations and tables of IP / login information too, as long as you can lock down the wiki itself to a select few, you'll be ok.

I currently work for an ISP where our shifts are split into 4 12hour portions across 2 alternating weeks.

Week 1 is: 2 days on, 2 days off, 3 days on.
Week 2 is: 2 days off, 2 days on, 3 days off.

Shifts go from 11am - 11pm (Day NOC), and 11pm - 11am (Night NOC).

So on average you do end up working 42 hours per week but you get every second weekend off, and you only work at most 3 days in a row, with at least 2 days off bracketing that.

It works fairly well for day noc's, but if you're not used to shift work, working nights can be killer.

Wondering if anyone has ever heard of this style of split-week schedule before?