Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 538 of 808  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subject
  2229   Thu May 17 02:12:52 2007 Question Dennis Seitzdseitz@berkeley.eduQuestionAll Summary view: View only most recent entry for all values of a given attribute?
We are using Elog to track status of hardware assemblies. One attribute we've created is the serial number of an assembly. Other attributes are items like "location" and "status". We have set up these latter attributes with presets to make entry easy and keep entries consistent.

I would like to filter the summary view so it only shows me the most recent entry for every value in the serial number attribute. This would be very useful for quickly viewing the present status and location of every assembly, for example.

I can't find a way to do this in the documentation. Is it possible? If not, may I submit a request for this feature?

I am very impressed with the Elog and it has become an essential part of our record keeping. Thank you for a very useful and well implemented application!
  2228   Thu May 10 13:03:51 2007 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows | AlllastRe: Import log

bob wrote:
thank you,
but the last method (simplest for me) does not import the comment.
it's a pity...


Ok, I implemented the XML import which also includes the text body. However there are currently two limitations:

  • If you want to import entries which contain replies, it only works if import them into an empty logbook, where the imported entries can obtain the same entry IDs as in the original logbook.
  • The names of possible attachments are correctly imported, but not the files themselves. These you have to copy by hand.
  2227   Tue May 1 16:54:12 2007 Reply Stefan Rittstefan.ritt@psi.chQuestionLinuxELOG V2.6.Re: Change default for suppressing email notification and/or targeting entries manually

Alan Stone wrote:
I would also like the option to add additional email addresses on the fly.


There is a simple way to accomplish this. Define a new attribute, let's call it "cc". Then add to your config file following statement:
Email all = $cc

In you entry form, you can now enter comma-separated email addresses in the CC filed, to which a notification will be sent.
  2226   Mon Apr 30 21:01:49 2007 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.5-1857Re: Upgraded from 2.6.1 to 2.6.5, but cannot login now & top.html is not displayed

Alan Stone wrote:
We followed the simple download instructions. Our existing logbook entries
are still visible. Nothing was lost or touched in our /usr/local/elog directory.
Is there some step we missed?
Alan


Have you tried to delete your cookies in the browser and try again?

The location of top.html has been changed from the ELOG root down into the loogbook directory. If you want to keep it in the original location, you have to specify the full path. See the documentation for where to put the file for "Top text".
  2225   Mon Apr 30 20:52:51 2007 Entry Alan Stonealstone@fnal.govQuestionLinux2.6.5-1857Upgraded from 2.6.1 to 2.6.5, but cannot login now & top.html is not displayed
We followed the simple download instructions. Our existing logbook entries
are still visible. Nothing was lost or touched in our /usr/local/elog directory.
Is there some step we missed?
Alan
  2224   Fri Apr 27 14:06:34 2007 Idea Stefan Rittstefan.ritt@psi.chInfoAllSVN 1857+How to make a table of contents
For those people who have not fully understood the discussion of elog:2218, here is an example table of contents.





First Chapter

The table of contents consists of a set of [url] tags like this:

[url=#first]First chapter[/url]
[url=#second]Second chapter[/url]
[url=#thirs]Third chapter[/url]


Then the chapter header contains a tag like this:

[ANCHOR]first[/ANCHOR]

to which the browser ups if you click the corresponding entry in the table of contents.

... empty lines to full up some space ...
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.



Second chapter

You should jump here if you click on Second chapter at the table of contents.

Third chapter

You should jump here if you click on Third chapter at the table of contents.
  2223   Fri Apr 27 13:06:59 2007 Reply Stefan Rittstefan.ritt@psi.chRequestLinux2.6.3-1764Re: Is there (planned) support for <A NAME> and <HR /> in ELCODE?

Kevin McCarty wrote:
I am wondering if there is any support (or if not, if it is planned) for inserting HTML <a name> and <hr /> tags via ELCODE. This would be useful for long log messages in order to provide a table of contents and divide them into clear sections. If this support already exists, I'm afraid it is not obvious to me how to access it in ELCODE. If it does not yet exist, would you consider a patch for it?

As a related issue, to support <a name> usefully, it will also be necessary for ELCODE to support things like [url=#tag], which it currently converts to <a href = "http:///#tag"> instead the expected result of <a href = "#tag">.


I implemented anchor tags. You can write something like

[ANCHOR]top[/ANCHOR]

and you can then reference it either by directly entering

http://midas.psi.ch/elogs/Forum/2223#top

or by entering simply

elog:2223#top

To make your table of contents, you can put a complete URL tag like

[URL=http://midas.psi.ch/elogs/Forum/2223#top]Goto top[/URL]

or inside the same entry simply

[URL=#top]Goto top[/URL]

which will be shown as

Goto top

I have added these link again at the bottom of this entry so you can try it with this entry directly.

... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...

elog:2223#top
  2222   Fri Apr 27 08:56:10 2007 Reply Kevin McCartykmccarty@princeton.eduRequestLinux2.6.3-1764Re: Is there (planned) support for <A NAME> and <HR /> in ELCODE?

Stefan Ritt wrote:

Kevin McCarty wrote:
I am wondering if there is any support (or if not, if it is planned) for inserting HTML <a name> and <hr /> tags via ELCODE.


Very good idea. The horizontal line
is already implemented via [LINE] and the anchor tag will soon follow.


Wonderful, thanks!

-- Kevin McCarty
ELOG V3.1.5-3fb85fa6