There was a discussion on how independent various tasks were. During this
discussion several unanswered questions were raised:

            What should happen when low-level event data is missing?
            How do we include operational problems in the bookkeeping?
            Can we not re-use the SRB for bookkeeping?
            Do we really need to develop a whole new bookkeeping schema?
            Where do we get the authoritative source for lumis?
            Should we use MyODBC to be RDBMS-independent?
            Do optimization requirements preclude being RDBMS independent?
            What language should we use?

Action item: Urge people to be ODBC compliant..
Action item: Restrict development to Perl..
Action item: Take grids into account but do not get tied into a 
             specific implementation.

A short discussion ensued about the need to synchronize the bookkeeping with
what was actually in the Root database. The consensus was that there
probably wopuld not be a workable way of doing this immediately but at the
very least there would be a need to compare information for discrepancies.

The question "should we throw away skim tools" was posed. The caused a
discussion about redesigning the skim tools and keeping the core tables (or
perhaps a bit more than that) in place. In the end people agreed that
everything was likely to change anyway so the question was moot.

Action item: Specifics need to be developed in the next two months.

A discussion about collection names and how that relates to merged Kanga
file was started. There was no agreement on this topic other than features
would need to be built in a hierarchical way.

Action item: Schedule a weekly phone meeting of the gang of seven point
fives every Wednesday at 9AM PST. An 8-port callin hub would be needed and
the first meeting should start net week. Jacek and Alessandra would
coordinate to start things off.

Action item: Start a new HyperNews forum called Bookkeeping-hn.

Action item: The following people will be responsible for collecting
requirements:

            Data Distribution: Time
            Operations - Antonio and Martino
	    Storage Jacek and Andy
            User - Alessandra and Paul
            SP - Douglas