In attendance for all or part of the meeting were
Colocho began with a review of some of the recent changes made by Boyes (et.al.) in the web log viewer which tried to eliminate much of the blank white space shown. This is seen as tremendous progress in as much as it demonstrates the ability to make functional changes in the PHP code which drives the web viewer. (Proof of principal for the Sandbox).
Example of that (under continuous development) viewer can be seen here.
After the meeting it was recognized that there would be several of these "sandbox" viewers (Boyes, Cyterski, Milanovich? Hoobler?). Those with a sandbox shall work together to make a viewer one level higher in the directory chain which incorporates the combined product of each sandboxer's work.
Colocho next presented a (non-PHP -- rather "dry" hardcoded) presentation of ELOG data generated by Hoobler. The presentation was radically different then the present viewer and intended to outline a desirable scheme (starting from scratch) for presenting the oracle data.
This presentation can be seen here.
People generally liked the sort of scheme Hoobler came up with, and it was widely viewed that a PHP version similar to this should be experimented with.
The topic of superseding entries with a new entry was discussed. Boyes' idea of doing this with the viewer software rather than changing the oracle database was widely deemed a viable way to proceed.
The idea would be that if two entries have the same event time and same title (or some other similar criteria) that the viewer would only display the later entry. Would need a fill in form for superseding which fills in the existing entry's database into an entry form such that modifier could then change content. It appear consensus was near that this would be the way to go. Chestnut reportedly liked this scheme as well
Some discussion about searches being unable to find the superseded entries occured, and it appears that this would not be a problem.
There was some discussion of concerns about building an entirely new database viewer for Operations Group use only being a duplication of effort (and maintenance) of the existing viewer. This comes in light of other groups using the existing viewer and expectedly not being happy with changes we impose on them. No clear resolution of this topic was arrived upon.
There was discussion about color schemes with little clear idea of a favored approach to use of color.
There was discussion of Auto Entries. Smith suggested using the user name field as a flag that the entry was automatically generated, and that further a different user name be indicated for each of the different types of automatic entries. Concern that too many auto entry user names would be confusing surfaced.
Colocho reviewed VanHoover's list of ideas about the ELOG from her use of the existing production viewer. Most of her ideas were well recieved. Her list pointed out that many of these ideas require effort. This calls for effort evaluation with subsequent prioritization.
On the topic of flags for entries: Without necessarily coming to agreement that we want to flag entries in general, it was recognized that if we did want to flag entries then the criteria list would be:
It was thought by by both Milanovich (for the TCL viewer) and Boyes (for the web/php viewer) that such flaging could be achieved in the viewer software completely without having to make modifications to the oracle database.
It was recognized that the shift change entry form should inherit as event time the time entered in the form field. Colocho also reviewed some of the other changes to the shift entry form from the previous meeting, and there was little discussion about those changes.
There was concensus that another meeting should be held next week to go over the expectedly interesting progress by that time, and to address the issues of evaluating and prioritizing the actions which are being called for.
Next meeting is tentatively scheduled for Thurs Oct 27 2005 10:00 AM in MCC Conference room. This is tentative pivoting on staffing needs for BSY search and interlock checks which are scheduled for that day.