Difference: Meeting071206 (2 vs. 3)

Revision 32007-12-11 - PhilippeCharpentier

Line: 1 to 1

Bookkeeping meeting, December 6th 2007

Line: 37 to 37
  One of the requests from users is to introduce flexibility in the queries compared to the current rigid web interface. One should be able to chain criteria in any order and get the choice of possible other criteria according to the already selected ones. There is a need to have a browser that can be integrated into ganga and also run in stand-alone mode for producing job options. The web browsing capabilities are not considered as a "must". The WG therefore recommends to implement in priority a stand-alone browser (in python and pyQT for the GUI). The web interface could be added if easy to maintain. The web interface should however be used for providing statistics (e.g. for management of productions).
After considering the prototype browser developed in Dublin within feicim, which presents search criteria as a file search tree, the WG was in favour of such a presentation to users. The default behaviour would however basically reproduce the current behaviour (with the caveat of replacing application versions by "processing pass" for non experts). It is also clear that the browsing criteria are different for real data and MC.

Current new developments (Elisa)

Elisa presented the status of hte work she had been doing (slides) in the past month.

She has developed a python class that allows querying the BKDB directly through the AMGA interface after having prompted the user for his search criteria (in any order). The interface discovers the allowed values for the next criterion, from the previous ones. Checking this method against the web interface+servlets is giving identical results. When asking for files replicated at a given sites, there is one more replica found which pointed to a bug in the web implementation (one file missing)...

There was a long discussion on how to evolve this prototype. One possibility would be to implement the interface as in the prototype directly in the client, while the alternative is to turn it into a DIRAC service that would be interrogated by a DIRAC API client within the framework.

 -- PhilippeCharpentier - 10 Dec 2007
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback