Last week, we had a wondrous meeting in the department head's office wherein the Division of Continuing Education (DCE) tech in charge of distance learning systems asked me if I could please reproduce the errors I was getting.
- 1. I explained that I sometimes renamed lectures because they populated from old PowerPoint file names even after I renamed lectures, but that this crashed the system.
- 2. The DCE tech asked me to show them what I was doing to get the "obsolete" names. I loaded
Lecture-03-20050829.pptfrom CIS 730, went to File -> Save As, and saved as
Test.ppt. I then clicked the Start New Web Recording from the Tegrity menu in PowerPoint. The default name that came up was
Lecture-03-20050829. I pointed this out to the tech.
- 3. "Oh, that's a Tegrity feature." I have learned that the term "Tegrity feature" usually precedes design flaws of OMGWTFPOLARBEAR, coyote leg-chewing proportions. The DCE tech showed me that if one right-clicks on the PowerPoint file and looks at the Properties tab, the "Title" field is what Tegrity actually gets the file name from. Now, I've since opened PowerPoint files and tried Save As, and also just renamed them from Windows Explorer, and neither one seems to update the title field. Does anyone know what, besides editing the field in the Properties tab with the file closed, can update the title? I'm asking because I could have sworn that Tegrity does this automatically when we rename the talk in the "Web Recording" dialog, and later save the marked-up version. If that's the case, it explains my confusion, because few things mess me up as much as inconsistent "automatic" features.
- 4. The DCE tech then asked me how I renamed files. I said that I edit the folder name
D:\Temp\Recordingsand then the top-level
FooBarBaz.htmfile with the same name in
D:\Temp\Recordings\NewFooBarBaz, and noted that this worked for me in the past. The DCE tech averred that this was correct, whereupon I said "no, that crashes Tegrity now", started up "Tegrity Batch Upload", browsed to a
NewFooBarBazI had previously created, and watched the Batch Upload app quit without warning.
- 5. "Okay, I see - that's not crashing; that's quitting." While I boggled, the DCE tech continued: "Did you hit `Upload Later'?" I replied that I had. "Then it isn't really a lecture. Here, you have to go to Tegrity Editor, open it, and save it---" I made like Alice in Dilbert for a moment and wrapped my brain around what he was saying. "You mean that it needs to finish postprocessing?" I said softly, so that the implications would not echo as loudly in my clustertrasked head. "Yes," came the reply. "You mean that it doesn't postprocess automatically when we actually go to upload, but that we have to open an intermediate application by hand and make it postprocess." Quoth the techie, "yes, that's right". Still refraining from unleashing Russell Crowe, Strong Bad, and a couple of taped-together-ninjas-that-are-one-big-n
inja, I asked: "Would you tell me one thing? Is this documented anywhere?" Yep, you guessed it, "No, it isn't. Tegrity documentation is spotty at best." Aaaaaauuuuurrrrghh!
Now, here's the situation:
- 1. The default Administrator upload destination on the mobile Tegrity cart in our department is set to the head Division of Continuing Education (DCE) facilitator's home if we log in as ourselves (
bhsuin my case) and upload to our own directories (e.g.,
bhsu/CIS_73x). I have no way to get it to populate correctly.
- 2. Students are reporting that watching Tegrity lectures on the Windows computers in Nichols 126 causes them to reboot. This is more likely an issue for the CIS Help Desk, but I am not aware of any special configuration on the CIS Windows lab systems.
- 3. Until today, I was missing three lectures from CIS 732, fall 2005 (02, 03 and 12) and three from CIS 732, fall 2005 (02, 03 and 11). I believe 02 in both courses was lost due to the Tegrity error that kept Tegrity from starting, and persisted for about three days until someone came over from DCE to fix on 29 Aug 2005. I discovered today that the postprocessing problem above accounted for two of these six lectures.
- 4. The rest went into various wrong directories. How do we fix those? Might there be a "move" or "rename" feature? Only from one directory of one course to another - and no renaming on the server side. No batch operations at all. The way to move or rename a lecture is to upload the entire 65Mb-250Mb directory again and delete the old one. Until this year, we even had to call DCE to delete things!