Just a follow-up to say that I've been casually keeping an eye open for use cases where this model might apply. A few have come to my attention. Rather than describing the model as a worksheet, it might be more clear to say a model where data elements are laid out along X axis and Y axis, like a chart.
For example:
1. Student attendance summary, where the X axis represents class periods where attendance is recorded, and the Y axis represents calendar dates.
2. Budget summary, where the X axis represents months of the year, and the Y axis represents business entities & accounts.
3. Product comparisons, where the X axis represents product attributes & functional requirements, and the Y axis represents individual vendor solutions.
Anyway, it may be helpful to think in terms of X axis, and Y axis, modeling. Can you think of more use cases?
-Nathan.
----- Original Message ----
From: Nathan Andelin <nandelin@xxxxxxxxx>
To: midrange list <midrange-l@xxxxxxxxxxxx>
Sent: Fri, April 9, 2010 3:08:12 PM
Subject: Worksheet Database Maintenance Model
I'm interested in hearing your thoughts about using a "worksheet" for database inquiry and maintenance, where each "cell" in a worksheet represents a "record" in a database table. We're just beginning to implement a worksheet model for viewing and entering grades & scores on student assignments. See the screen-shot:
http://www.radile.com/rdweb/temp/worksheet.pdf
In this example, worksheet data comes from three (3) related tables or SQL views - Students, Assignments, and Grades; where grades may be entered and maintained, using a worksheet format. Actually the record may contain more than one field, which are displayed in a popup when the F2=Change key is pressed.
My question is, what other types of inquiry & maintenance applications might the worksheet metaphor might apply to? Can you come up with other use cases?
We're implementing a fair amount of JavaScript to support worksheet navigation, horizontal and vertical scrolling, individual and block cell selection, auto fill, and editing.
I'm considering structuring the browser and server components in a manner that would make them more reusable - adaptable to other use cases. That might make sense, if there are enough potential use cases.
My gut feel is that a Worksheet model could be applied to different types of applications - but that's mostly based on the fact that so many people seem interested in transferring IBM i data to Excel, and back again. What are some use cases?
Thank's for you thoughts,
-Nathan.
midrange.com
