Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 347 of 808  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  286   Tue Apr 15 13:00:40 2003 Reply Stefan Rittstefan.ritt@psi.chInfo  Re: Question
> I tried that but on the summary screen it displays a list of all the 
logbook 
> regardless of group, also im not using public groups im using a seperate 
> password file.

Ah, you mean by "summary screen" the initial logbook selection screen where 
each logbook is displayed in one line. For that case, I just added a 
flag "Hide from selection". If set to "1", this logbook is not dispalyed 
among the list of logbooks. Is this what you want? New version under CVS.
  287   Wed Apr 16 13:28:38 2003 Reply nickc1nick@nick.comInfo  Re: Question
> > I tried that but on the summary screen it displays a list of all the 
> logbook 
> > regardless of group, also im not using public groups im using a seperate 
> > password file.
> 
> Ah, you mean by "summary screen" the initial logbook selection screen where 
> each logbook is displayed in one line. For that case, I just added a 
> flag "Hide from selection". If set to "1", this logbook is not dispalyed 
> among the list of logbooks. Is this what you want? New version under CVS.

Yes thats wicked perfect, now im prob being thick but is there a way to hide 
logbook tabs in the same way, as i dont really want to use groups as the 
people that use the system arent really techie and the titles will confuse 
them :)

Im trying to make it idiot proof for them 

Cheers
  288   Thu Apr 17 09:29:14 2003 Reply Stefan Rittstefan.ritt@psi.chInfo  Re: Question
> Yes thats wicked perfect, now im prob being thick but is there a way to 
hide 
> logbook tabs in the same way, as i dont really want to use groups as the 
> people that use the system arent really techie and the titles will confuse 
> them :)

Well, I changed the flag from "hide from selection = 1" to "hidden = 1", 
which hides it now also from the logbook selection tabs on the top row. But 
this means that the only way to access the hidden logbooks is by entering 
their URL directly (or from a bookmark). I'm not sure how useful this is...

New version under CVS.
  290   Sat Apr 19 11:09:33 2003 Reply nickc1nick@nick.comInfo  Re: Question
> > Yes thats wicked perfect, now im prob being thick but is there a way to 
> hide 
> > logbook tabs in the same way, as i dont really want to use groups as the 
> > people that use the system arent really techie and the titles will 
confuse 
> > them :)
> 
> Well, I changed the flag from "hide from selection = 1" to "hidden = 1", 
> which hides it now also from the logbook selection tabs on the top row. But 
> this means that the only way to access the hidden logbooks is by entering 
> their URL directly (or from a bookmark). I'm not sure how useful this is...
> 
> New version under CVS.

Thats perfect, administrator such as myself can access those books directly 
from the URL, and can be used as an archive logbook running in sync with the 
live one, so hold records such as completed tickets in a request system once 
completed can be moved to the archive logbook.

Cheers fella  that is gonna help me a great deal.
  330   Thu May 8 15:28:10 2003 Reply Stefan Rittstefan.ritt@psi.chInfo  Re: Question
> Can you tell me what the following change in CVS offers
> 
> Added lock icon for protected logbooks
> 
> Does this relate to the request in article 309

No, unfortunately not (yet). I'm still working on the problem described in 
elog:309. This "lock" icon only shows you in the logbook selection page which 
logbooks are public and which are protected by passwords (was another 
request).
  69222   Mon Sep 21 20:03:49 2020 Idea Andreas Luedekeandreas.luedeke@psi.chQuestionLinux3.1.3Re: Query to get values for Attributes

That would be a nice feature...

If you are good in parsing HTML you can achieve this feature: when you create a new entry "<elog-URL>?cmd=new", you'll get HTML source code that provides you with all possible attribute choices.

Disclaimer: this only works if you don't use Conditional attributes.

Florian Feldbauer wrote:

Hey,

I'm trying to integrate the Elog into our SlowControl System (Phoebus/EPICS). As a first step I translated the python library to Java. So writing new Entries and viewing them works.
But for Phoebus, you need a list of the possible values for the attributes. Currently this is done via the config file from Phoebus.

Is there a way to get the values also via a query directly from the Elog?

Cheers,
Florian

 

  69223   Tue Sep 22 09:27:45 2020 Reply Florian Feldbauerflorian@ep1.ruhr-uni-bochum.deQuestionLinux3.1.3Re: Query to get values for Attributes

Thanks for the tipp. I managed to use XPATH to get the values for my Type and Category attributes!

The API, I'm developing for Phoebus is quiet simple. It currently just supports Author, Subject, Type and Category as attributes and the latter two are just lists of values.

Andreas Luedeke wrote:

That would be a nice feature...

If you are good in parsing HTML you can achieve this feature: when you create a new entry "<elog-URL>?cmd=new", you'll get HTML source code that provides you with all possible attribute choices.

Disclaimer: this only works if you don't use Conditional attributes.

Florian Feldbauer wrote:

Hey,

I'm trying to integrate the Elog into our SlowControl System (Phoebus/EPICS). As a first step I translated the python library to Java. So writing new Entries and viewing them works.
But for Phoebus, you need a list of the possible values for the attributes. Currently this is done via the config file from Phoebus.

Is there a way to get the values also via a query directly from the Elog?

Cheers,
Florian

 

 

  663   Thu Aug 12 21:10:29 2004 Reply Stefan Rittstefan.ritt@psi.chQuestionAll2.5.4Re: Q: on 'FIND MENU commands =' <menu list>
> The help text on the website says the following:
> 
> "The command Select can be used to select multiple messages for deletion of
> moving to other logbooks."
> 
> This is not clear but was the intent to indicate that SELECT can be used to
> either select multiple log entries for deletion OR for moving to another
> logbook?  If the latter, then this does not work if one adds the MOVE TO
> menu item to the list.  If the former then the helptext is a little misleading.

SELECT can be used for deletion OR moving OR copying. To enable the copy and move
commands, they have to be present in the "Menu commands" list, like

Menu commands = Back, New, Edit, Delete, Reply, Find, Config, Logout, Move to, Copy
to, Help

I added an appropriate note to the documentation, sorry for the misleading descriptoin.
ELOG V3.1.5-3fb85fa6