Notes from MCC elog
meetings
Thursday October 30th,
10:00am
Today we talked about pre-release requirements. They are:
- Edits
- Must
be able to edit entries made on day shift until 17:00, 01:00
for swing shift entries, and 09:00
for owl shift entries
- Entry
can be edited only by user who made entry and only during the shift time-window
defined above (or by ESD superuser upon request from Operations
management at any time).
- Shift
summaries can be edited at any time
- Entries
that have been edited are clearly marked as such. A link to the original entry is
included at the bottom of the edited entry
- Interface
- A
non-web, cow/calf based interface is needed
- Must
be able to enter, edit, and view entries.
View could be simplified version of the web view.
- Features
we want (but which need not hold up the initial release):
- Users
must be authenticated. User should
timeout 15 minutes after shift change
In addition to talking about pre-release requirements, the
following items were also discussed:
- Relationship
between the MCC elog and the other elogs
- Should
we separate the MCC elog from the others?
Would doing that make support/feature request easier? The other logs may be acceptable for
release now
- Additional
features
- We
should ask controls dept. about time accounting features already built in
to the log. They may also know of
additional features that we could use
- JLAB
operator opinion
- We
should ask JLAB operators what they think about the log
- Long
time between submission and inclusion
- Can
we speed this up? Three minutes is
too long