Displaying report 1-1 of 1.
Reports until 08:36, Wednesday 30 June 2010
Logbook Admin Feature Requests
david.barker@LIGO.ORG - posted 08:36, Wednesday 30 June 2010 - last comment - 09:20, Wednesday 30 June 2010(46)
David Shoemaker's additional feature list
cut-paste from David's email 03:07 30/6/2010

1) Threads, displayed as a tree format so that you can follow threads, with the 
tree organized either alphabetically or by date (and with filters for author, 
entry age, etc.), one could follow what has been written in a recent thread 
about the system they are working on and then add another entry to that thread. 
No need for users to type a matching keyword, since the "Add Entry To This 
Thread" does that automatically. One would like to be able to title a thread -- 
this could just be the first entry title, but it would be useful to be able to 
edit that to cover the thread content and to make it easier to search for

2) searching across the installations (certainly LLO and LHO) is needed. I think 
it would be neat to be able to search the Virgo Cascina installation as well -- 
that is a question of international politics, I suspect. We would need a 
pull-down list to know which one(s) were being searched, and would want to be 
able to identify several or all.

3) reduced Recent Author list for searches, and autocompletion on author names, 
ideally making reference to the recent author list to order options

4) can an individual's input and search settings be remembered for the next 
login from that individual? Hugh works on SEI at LHO -- would be a nice way to 
get things on the right foot. Could be a big thing software wise, but would 
reduce a lot of the effort in getting going.

5) notifications: ability to put in aliases here (maybe trivial, could be 
maintained elsewhere), but would allow subsystems and the team to be notified 
for certain entries

SNS has these 'features'; are there some we want to plan to integrate?

   1.

      BulletIntegrates with work orders -- if nothing else, having all work
      orders appear as logbook entries would be quite valuable, I think.

   2.

      BulletGroup notification, daily orders and required readings

   3.

      BulletUser bookmarked entries

Also, one can filter at the view page by ordered posting time, author, or 
priority, a nice feature.

Their initial data message entry keyword/category input looks like this.



I think something like this would be very good for us; sounds like a database 
dimensionality question, though, so to be resolved soon if so. Breaking things 
down into more columns seems attractive.

entry types: Progress (default), Problem, Repair, Maintenance, Status

Categories:
Safety (might want to impose notification to all recent authors, or all authors, 
or something for this entry?)
QA
SYS
IOO
PSL
SUS
SEI
COC
AOS
ISC
DAQ
DCS
FMP
INS

Location: L1, H1, H2, LHO, LLO, MIT, CIT, Other

Priority: Urgent, high, normal (default)
Comments related to this report
david.shoemaker@LIGO.ORG - 09:20, Wednesday 30 June 2010 (48)
Snapshot from SNS log
Images attached to this comment
Displaying report 1-1 of 1.