issues

You are currently browsing articles tagged issues.

MH Operations

We have been getting these messages for months. Some good folks at Blackboard have caused them to stop for a while, but they just resume. Probably it is multiple cases of the same issue.

LDAP Issues: Dear Valued Customer, The MH Operations team has determined that your MH application server(s) are not able to communicate with your local LDAP server infrastructure. Please notify your TSM when LDAP service is available so that we can confirm that there are no other issues with your hosted Blackboard environment.

The last time, alerts for Valdosta State’s Transaction System (a different product than we run) were being sent to us. A DBA for Vista was listed as a technical contact for TS which she doesn’t run or even know she was considered a technical contact. No one working with TS at Valdosta State had been getting these alerts. So they were excited at the prospect of knowing when there was a problem! I put Blackboard in touch with the people at Valdosta.

In a way, I understand my organization is involved in purchasing the licensing. However, Blackboard needs to do a better job of making sure their customers are informed.

  1. Put the name of the affected product in the notice.
  2. Put the name of the affected URL or IP in the notice.
  3. Put the name of the customer’s organization in the notice.

Blackboard Vista tracks student activity. This tracking data is viewed as a critical feature of Vista. Our instructors depended on the information until we revoked their ability to run reports themselves due to performance issues. Campus administrators can still generate reports (though some still fail). We doubt the solution to this is Blackboard improving the queries to create the reports. We favor deleting tracking data (data preserved outside of Vista) to resolve the performance issues.

We developed SQL reports to look at the tracking data where the user in question was not a student. Yes, the data is limited, but in determining when and where a user was active, can help determine where to look in logs. When we hit the performance issues we started using these reports where the user interface reports failed to generate.

My understanding was the user interface and SQL reports on tracking were the same. Both looked at the same data. The user interface reports were just sexier wrapped in HTML and using icons. I compared a user interface report to a SQL report. Just prior to doing this, I was thinking, WebCT was stupid for not tracking when students look at the list of assessments. Turns out “Assessment list viewed” was tracked in the user interface all along but was missing in our sqlplus queries. WTF?

The data has to be there. The problem has to be our approach in sqlplus is inadvertently excluding the information from the reports. Because these reports must be accurate, I’ll crack this nut… Or become nuts myself.

CRACKED THE NUT: So, part of the data WebCT collected was the name of pages. There is a page name table which was inner joined to the user action table. So pages without a name were not reported. George suggested an outer join. I placed it on the page name table which now lets us see the formerly missing tracked actions. For the specific case where I found this, I now get all the missing actions.

Considering a Blackboard (it’s their problem now) feature request to ensure every page in the application has a title. I consider it developer laziness (someone else said worthlessness) that some pages might not have something so core and simple.

ANOTHER TRICK: Oracle’s NVL function displays a piece of text instead of a null value. Awesome for the above.

Warm fuzzies abound when support uses this as the last item for when something occurs.

Some form of dark wizardry

I know this was meant to be funny. I even found it funny. Seriously…. There is a lot of dark wizardry….

Previously I have seen usability describing ease of using a web site. These four essences of usability are interesting.

I believe that to satisfy customers, a Web site must fulfill four distinct needs:

  • Availability: A site that’s unreachable, for any reason, is useless.
  • Responsiveness: Having reached the site, pages that download slowly are likely to drive customers to try an alternate site.
  • Clarity: If the site is sufficiently responsive to keep the customer’s attention, other design qualities come into play. It must be simple and natural to use – easy to learn, predictable, and consistent.
  • Utility: Last comes utility — does the site actually deliver the information or service the customer was looking for in the first place?

Web Usability: A Simple Framework

The first two items deal with system administration issues like the network, server(s), database, or application. Redundancy and proactive dealing with problems before they impact the system hopefully maximizes availibility. Optimization for performance hopefully maximizes responsiveness. An unhealthy database could fail to deliver information.

The last two items deal with design issues. More utility issues are likely based in design than tuning.


UPDATE: In my past life as a “Webmaster,” my fingers were dirty in all four aspects of usability. These were my servers and while not my design, I certainly influenced it by cleaning up the HTML and presentation. We created in-house everything except some outsourced photography and the Apache web server.

Blackboard’s Vista is a proprietary application with decent opportunities for instructional designers to provide clarity and utility. As much as it provides, clients often purchase or create additional applications to integrate with Vista to fill in holes Blackboard left. Okay, technically, WebCT left those holes, but Blackboard took the same model with Academic Suite. Blackboard doesn’t really intend to fill in those holes. They should for issues affecting most of their customers on each platform. This is the same approach taken by open source products with the caveat that third party companies are not filling in the holes, customers are developing their own solutions and providing back to the community.

The declining responsiveness of Vista over time definitely seems to create one frustrating difficulty for some clients. As the database tables get larger, responsiveness of the sites declines. Ouch. Delete it all… Oh, wait… Can we really do that?