Tuesday October 21st , 10:00am

 

 

  • Edits
    • Should entries be editable for some set time period (one shift, for example)?
      • I think we decided that no user edits would be allowed.
    • How do follow-ups work for one entry made into many logbooks?
    • Which should be the primary entry display, original or follow-up?
      • The majority of us feel that the original should be displayed.
    • Summary-when/if we can edit
      • We’d like to be able to edit the summary at any time.
    • Superuser administrative edits
      • We need a list of people who can officially ask Bob Hall to edit

 

  • Data Storage
    • Will it be easy to upgrade the logbook software?
    • What software can read a raw oracle database?
      • Our main concern is whether or not we’ll be able to upgrade from oracle to the next generation of database. 

 

  • Source Code
    • What level of support do we have?
      • Will the controls department support this like they do the SCP?  YES
      • Call in list? YES
    • Can we add features/update software?
      • Will controls only support this as-is, or will they add major features for us?
    • Who is responsible for software, SCS or controls?  Who owns/admins hardware?

 

  • Archives
    • Who backs it up? (which group)
    • How does it get backed up?
    • Are copies of entries links or additional entries?
    • Different restrictions on MCC and other logs
      • Does it save time or effort to not have the same archiving requirements for non-MCC logs?

 

  • Permissions
    • Does each log have unique write permissions?
      • We need to restrict MCC log entries.

 

    • Reading and Writing
    • Is it true that you must be inside the firewall to read?
      • This seems like the right thing to us.  Maybe access with NT account also.
    • Use Unix password to write—must be on list provided by operations
      • We need to control the list of people who can write to the MCC log.

 

  • Ownership
    • Can we change/update our log software without changing the other logs?
      • We need to have the ability to make feature changes to our log without consequence.  The other logs should either be independent or understand that the MCC log has priority for feature changes.

 

  • Ease of use
    • Spellchecker
    • Scanner
    • Tablet PC
    • X-windows interface – JLAB has one right now.  It might be better than web.

 

  • Features
    • Summary
      • Similar to our current 24 hour shift reports
    • Shift header
      • Similar to our current sticker listing EOIC, ops, PD,  and program
    • Time accounting / artemis
      • It would be VERY nice to have these two programs linked together.  One suggestion was to have artemis IDs listed in log entries be links to actual artemis entries.  This topic requires more discussion.