Monday:
perMIT
Data Tables
"Qualifier modifies the scope within an A-spec."
...
URL to show some of the rules. Jim will send or put in wiki.
Tuesday:
perMIT:
Qualifiers vs. Object
Qualifiers belong to a heirarchy
Subject | Function | qualifier | |
Subject | Verb | object | |
Who | What | where |
Should permit add a second optional qualifier? (4 columns)
perMIT - Tuesday afternoon
Master Dept. Hierarchy
https://mv-ezproxy-com.ezproxyberklee.flo.org/mdept/\\
If Jim were redoing qualifier hierarchy section of Roles, he would implement it more like the master dept. hierarchy. Allows for multiple types in single heirarchy. Also means that certain objects don't need to be duplicated.
Should perMIT do this? We could put in the tables and columns, but have them default to the way that we have qualifiers implemented today.
Bigger meeting topic: should we change the data model of the qualifiers so that a single object can exist in two hierarchies.
Allows for some very sophisticaded reporting, but need think through the UI issues of creating the qualifiers.
Here's an object. What views do you want it to appear in? What are the parents and children in each of the views?
Friday: revisiting the DB schema. How to restructure the qualifiers