160 likes | 295 Views
LANL’s Review and Approval System. Miriam Blake Los Alamos National Laboratory. Genesis . Automating the R&A process on the “to-do” list since 2008 Lean-Six Sigma recommendation “unfunded mandate” Obvious need Small team began investigating tools
E N D
LANL’s Review and Approval System Miriam Blake Los Alamos National Laboratory
Genesis • Automating the R&A process on the “to-do” list since 2008 • Lean-Six Sigma recommendation • “unfunded mandate” • Obvious need • Small team began investigating tools • In-house system used by Tech Transfer (Ideas) • Alfresco • Adobe workflow • Changes in priorities and staffing 2009-2010 • Late 2010 – one programmer and one “workflow designer” began development • Php / mysql • Harvest out to Library repository (aDORe / OPPIE)
Review and Approval System for STI (RASSTI) • Started with intent to roll-out first for DUSA (Designated Unclassified Subject Area) content • Environmental Programs? • TBD…. • Workflow: http://review.lanl.gov (Internal webpages) Must authenticate as a LANL employee
info:lanl-repo/lareport/LA-UR-11-10450 permanent ID assigned here
Once a final number is assigned • Item is harvested (with metadata) from RASSTI to Library repository • And the Electronic Public Reading Room for Environmental documents • Flagged for harvest by OSTI • PDF is removed from RASSTI (metadata is kept) • Customers are sent to “LA Authors” to retrieved submitted copies
Lessons learned from RASSTI v.1 (DUSA) • People really LIKE the automated system (almost too much!) • “Soft” rollout is a little dangerous – doesn’t get all the communication out easily • MUST have draft/replacement functionality • Policy/procedure must be addressed early and consulted often • Always difficult to interact with other systems (Employee system, cost codes database, Environmental programs – Sharepoint, Documentum, etc.) • now on to the hard part….?
RASSTI v.2 (in development) • What’s new and improved • Workflow for Derivative Classifier (DC) • Workflow for Classification Office • Ability to “revise” and add new versions (adds more complexity) • In tandem: • Clean up legacy “LA-” numbers (are over 20 different formats that have been used!) • Start discussions around ALL STI going through system (video, audio, data, etc.) • Re-write procedure