Tbird 3.0 is here, I could not resist

I was compelled to upgrade Thunderbird to 3.0 today. Maybe my desktop has a thing for odd numbers. Windows 7, Firefox 3.55, Office 2007.

So far I can say that my settings and local mail are all intact. The layout of things is a bit different. It does the “smart folder” thing that has been part of Outlook and Mail.app for a while. This can be nice as I have three separate accounts set up in Tbird. Smart folders automatically allow me to display all three inboxes merged together.

My Lightning calendar plugin had to be disabled but I wasn’t using that anymore anyway.

Time will tell – we’ll see what else I find!

Wikispaces Private Label

Patrick and I watched a web seminar today on Wikispaces Private Label. This is a pay service from Wikispaces targeted at business and education clients. Essentially we would get a web-based tool to manage a lot of users and a lot of wiki “spaces”, which are collaborative web documents shared by an enumerated list of users.

The product looked fine, but I feel like the demand for wiki has dried up on the IWU campus. Most people are just using Google Docs to collaborate. Am I wrong here? Do we still need a wiki solution that is more manageable than free ad-supported wiki accounts online?

Wireless Broadband at IWU

Linda in Telecommunications made the following announcement today:

The Telecommunications Office is offering rental of an AT&T broadband wireless card.  This device allows your computer to connect to the Internet at broadband speed without a cable or WiFi – it works anywhere that an AT&T cell phone works! The rental fee is $5.00 a day.  If you are traveling and would like to reserve the card or have questions about how it works please call Linda at 309-556-3430.

Wireless broadband is a cool technology but pretty expensive. It means fast connections anywhere without having to pay WiFi hotspot fees or getting onto disreputable free wireless at hotels and businesses. This is a great way to share the benefits and the cost of this device across campus!

Long Footers in Excel: Trouble in Paradise?

I was working on a long spreadsheet the other day. It was destined to become a PDF with nice formatting which would live on the web. I set it up to be formatted as a table, repeated the top row on each page, and set margins. All smooth sailing until I tried to add a disclaimer at the bottom of each page.

Apparently footers in Excel don’t depend on the amount of space they take up. I kind of expected that you could have as much text as you want as long as it fit within the footer space. My plan was to pop the text in there and drop the font size to 8 or 9. Unfortunately Excel has a 255 character (including spaces and formatting characters!) limit for headers and footers. Why? I don’t know.

There is a way to work around this limit. I pasted the text into Word, changed the page orientation to landscape, hit enter 5 or 6 times, then hit Alt-PrintScreen. This captured an image of the document to my computer’s clipboard. I hit enter a few times so my screen capture wouldn’t have the Word insertion point cursor right next to the text. I pasted the screen shot into an image editor and cropped out the excess. In the Excel footer dialog, I inserted my image, which was paradoxically bigger than the text I wanted to display.

Works fine, but kind of annoying!

Malware Defense-in-Depth

We’ve been discussing the ever-present problem of malware in our Desktop Support team meetings. We need a coordinated “Defense-in-Depth” strategy to address this problem. There is no single tool that one of us can use as a magic bullet to prevent or clean malicious software. Instead we need to define and implement a multilayered approach to prevention, incident response, and education.

Here is an interesting PDF document from Microsoft on the Defense-in-Depth concept.

…and a nice article about computing behaviors and habits that can prevent malware incidents.

Wiki options at IWU

A few people have contacted me lately about using wiki tools to collaborate with others on a project. We don’t have an “official” wiki at IWU so there is always a bit of confusion at the outset.

Many people have opted for Google Docs instead of wiki. This makes a lot of sense if your group is just collaborating on internal work. If you want to publish the work to the web later, wiki tools are a better fit.

What wiki is the right wiki? I don’t know. We have used Confluence (a commercial tool that costs money) and Wikispaces (basic wiki is free, extra features cost you). There is also a basic wiki built in to Moodle. I’ve used MediaWiki (the engine that powers Wikipedia) on my own server with great results. So I must be a wiki expert, right? Not even close. Here is an article naming some of the wiki farms on the web today.

So what tool is the right tool? There are a few factors that are important when stacking these tools and services up for comparison. First is access. There are two sorts of access for a wiki – read and write. Clearly your own people will need to both read and write if they are going to collaborate. Can the tool allow or disallow public reading, writing, or both? Can you use it to make this choice on a page-by-page basis?

I’d also look for a tool that permits downloading a backup copy of your wiki, at least in HTML form. That way the end product of your collaboration can be retained, even if the company hosting the service goes out of business.

Last but not least, find something that is easy to sign up for and easy to use. I have some concerns about the usability of the Moodle wiki. On my first visit I couldn’t figure out how to make a new page without looking it up. When comparing usability I’d stack any wiki up against Wikipedia. Everyone should know how to modify a Wikipedia entry by now – it is very easy – and if your wiki service makes it confusing you might shop elsewhere.

Sharing is caring: Google Reader

I’ve written about Google products before, including Google Docs and Google Presentations. I haven’t had much to say about Google Reader since until recently I used either Thunderbird or Bloglines Beta to pull in news and feeds from various websites. I switched to Reader for three reasons.

First, I noticed that some nice people had written Firefox extensions to customize the GReader experience. I found Thunderbird to be slow and Bloglines Beta OK but a little buggy (it is a beta, after all) and I liked the idea of tweaking things here and there to improve my experience.

Second, I heard that GReader’s mobile interface was very good. Thus far I feel that it is much faster than the Bloglines mobile site. There are still some feeds that contain images that don’t load properly on my admittedly old mobile device.

Third, GReader allows me to share with others. I can selectively “fling” certain articles that I like, with my own annotation, into a publicly viewable queue. Google displays this shared queue of information in a few different ways. First, there is a Google URL just for your shared items. This can be viewable to the whole world. They also give you code to publish a little “badge” on your own website. Lastly, my friends who also use GReader can click “Rick’s Shared Items” in their own feed list to see what I’ve added.

You can see the GReader badge, among other things, on my personal website. Notice the middle part that says “Rick’s Shared Items”? That list dynamically changes as I share new things in GReader.

Let me know if you already use Google Reader and I’ll add you as a friend.

What would do you do with 50,000 digital images?

We have a problem that is probably common at similar institutions. Now that we’ve begun to produce digital media, what the heck do we do with it? For example, the University photographer at IWU has thousands of digital images that need to be distributed around campus for various purposes.

These images need to be placed in the hands of our corps of web contributors. There are a few individuals in every department that work on the web to varying degrees. It isn’t practical for the photographer to e-mail relevant images to each department, or even to produce proof sheets. New digital images come in faster than they can be sorted.

To solve this problem, we began to use a product called iView Media Pro. This software was designed to catalog media files. It can store and categorize sound, video, still images, and other digital stuff. Catalogs include thumbnail images, keywords, categories, and a connection to the full-sized image.

The Pro version of the software was purchased and installed for the photographer, and others around campus got the free Reader application that can open and browse these catalogs. The images live on a Mac OS X server where all the end users get read-only access.

This worked great until the Mac server crashed and was replaced with another newer Mac server. Now the catalogs that are made on a Mac and stored on a Mac can’t be correctly viewed from Windows. The images haven’t moved. The thumbnails and metadata are there, but the Windows computers looking for them can’t find the full sized image.

Did I mention that somewhere along the line Microsoft bought iView and changed the name? Now it is called Expression Media. They have issued two versions and a service pack update under the new branding. We’ve tried the new versions to see if the Windows bug is fixed, but tech support indicates it is under investigation.

I can’t shake the feeling that there should be a better way to do this. At home I use Flickr to catalog and share images and couldn’t be happier. Another web-based tool is SmugMug, which is powered by the Amazon.com cloud computing platform. Unfortunately there is no way to directly import the iView images into these services without losing the valuable metadata – keywords, categories, and other tags would be separated from their images. I can’t imagine how many hours it would take to redo this work.

For now, I’ll wait for the Microsoft techs to fix this bug. Anyone have other ideas on storing, cataloging, and sharing large amounts of images?

Checkout: A handy LCMS feature

Most documents in LCMS (Luminis Content Management System) at IWU are web page documents. These documents are stored in a format that can be edited directly. When you click “edit” for a web page, the Edit-On Pro window loads up, which gives you all the tools you need to manipulate text, make links, and insert pictures.

But what happens when you need to edit or replace a picture, Word document or PDF? One way you might do this is:

  1. Save a copy of the old file to your hard drive
  2. Make your changes to the new file.
  3. Import and submit the new file with a new name
  4. Change all the referring pages to point to the new file
  5. Submit all those same referring pages
  6. Delete the old file

This is a totally functional way to go but leaves a few loopholes open. What if another web page links to your picture or PDF? Those links will be broken since you have changed to a file with a different name. What if you forget a couple of the 17 different places on your own site that refer to your form or document?

Even worse, what if you find a mistake in the new file and have to do it all over again? What if the picture needs to be cropped a little more? This method can be very tedious.

Instead, you might try using the “Checkout” feature. If you do this for a normal web page nothing will happen. If you check out a picture or some other file that Edit-On Pro can’t handle, something much cooler occurs.

LCMS will send a copy of the file in question to the hard drive of whatever computer you are using. It will be saved in the “C:/Documentum/Checkout” folder. (Vista users, you may have to “trust” iwu.edu servers to convince your computer to allow this. Call us if you need a hand working this out.)

Once the file is on your hard drive, you can edit it with whatever program you prefer. I like to use Photoshop Elements for images, and I have Adobe Acrobat Professional for working on PDFs. Once the file has been edited, save it in the same place you found it with the same name.

When you go back to LCMS, click “Checkin” which will automatically pull the new version from your hard drive. You can then add a comment to describe the changes you made. The new updated version will need to be submitted, but none of the pages that link to it need to be touched at all!

Another nifty trick is to check out a file, then replace it with another one. As long as the new file goes into the Documentum Checkout folder and has the same name as the file you checked out, LCMS doesn’t care. The new file will appear in the same place as the old, with the same name, keeping all links and image insertions intact. If for some reason you have specified a height and width value for an image in LCMS (something I don’t recommend) you will need to make your new image match those dimensions.