1 / 9

Logbooks/Notebooks for Hall D

Explore the best features of logbooks vs notebooks, like multiple threads, problem tracking, automatic entries, and more. Check out existing projects and the CODALOG design for a database-driven, searchable solution. Get a summary and conclusions on CODALOG's progress and potential, and find references for further information.

orrell
Download Presentation

Logbooks/Notebooks for Hall D

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Logbooks/Notebooks for Hall D E.Wolin Indiana University 14-Dec-2002

  2. Logbooks vs Notebooks

  3. 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

  4. 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

  5. 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…

  6. 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

  7. 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

  8. 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

  9. 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

More Related