Transcript codalog_for_halld

Logbooks/Notebooks for
Hall D
E.Wolin
Indiana University
14-Dec-2002
Logbooks vs Notebooks
Logbook
Notebook
Many simple
Few complicated
Entry speed
Rapid
Carefully crafted
Entry value
Short term
Long term
Entries
Topology Directed graph
Threads
Multiple
Linear
Single
Hall D Desiderata
•
•
•
•
•
•
•
Integrated – online, offline, detector, etc.
Best features of logbook and notebook
Multiple, parallel logbooks with cross-references
Multiple threads, locking, annotation
Problem tracking/resolution facility
Automatic entries
Images, other mime-types uploaded and stored
locally
Desiderata, con’t
•
•
•
•
•
•
Screen capture possible
Database driven, Perl/JDBC accessible
Extensive searching capability
Summary, detailed views
Web/servlet (vs application) based
(Re)Configurable via XML
Existing Projects
• Fermilab Control Room logbook
– Java app: http://www.hep.net/hepnrc/LogBook.html
• JLab Accelerator logbook
– Web/Tcl app based: http://devweb.acc.jlab.org/CSUEApps/elog02
• ORNL, PNNL, Midas notebooks (web,applet,web)
– E.g. ORNL used by CLAS: http://clasweb.jlab.org/ENOTE
• CODALOG at JLab
– Web based, see below
• There are others…
CODALOG Design
•
•
•
•
•
•
•
•
Entry data for all logbooks in one set of tables
All navigation info in separate tables
Use database functions to hide tricky bits
Configure via XML file
Built-in threads: type, topic, subtopic
Explicit named threads
Minor threads (head is unique)
Each entry associated with a “primary” logbook
CODALOG Status
•
•
•
•
•
•
•
•
Prototype stage
Database design completed (Postgres)
XML configuration working (via Perl)
Database programming mostly done
Initial Java database access class working
Velocity based (template rendering)
Needs web design and templates
Tested with CLAS online logbook data
CODALOG References
• CLAS XML config
– http://coda.jlab.org/codalog/test/hallb.cfg
• Database
– http://coda.jlab.org/codalog/admin/createdb.sql
• Java access class
– http://coda.jlab.org/codalog/admin/codalog.java
• Rendering class
– http://coda.jlab.org/codalog/test/vtest.java
• Example Velocity template
– http://coda.jlab.org/codalog/test/vtest.vm
• Example rendering
– http://coda.jlab.org/codalog/test/hallb.html
Summary and Conclusions
• CODALOG mostly meets Hall D criteria
• DB design fine, proof will be in the GUI
• Not ready yet, initial version perhaps soon
– Is anyone willing to help?
• Other products very good but do not meet H-D criteria
• Do we need something right now?
– If so, use ORNL notebook
– If not, wait for CODALOG