Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 631 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
  814   Wed Nov 24 13:55:22 2004 Reply Stefan Rittstefan.ritt@psi.chRequestAll2.5.4-6Re: Attribute Negative Search
> Is there any way to search for all attributes _except_ a certain value?

If you mean "search all attrubutes except one specific attribute" then the
answer is no.

> Can "Display" links work with multiple options? 
>
> "ABC | DEF" is currently one link.
>
> Ideally, it would be two links, each formatted per the "Display" string.

I don't understand your qyestion. You have an attribute with MOptions, so you
get "ABC | DEF" displayed in the list view. All links in each line point to
the individual entry, so what is the benefit of having two links for ABC and DEF?

> Is there a way to disable wildcard matching in searches?
> A search for "1" returns "1" and "10" and "11".  
> Is there a way to perform an explict match?
> Could there be a numeric match if the attribute type is numeric?

That should all be possible with the build-in regular expression. Just type

\b1\b

where "\b" means "word boundary". I agree that a numerical comparison for
numerical attributes would be better, I will put that on the to-do list.

> Could there be a multi-value option for free text fields, e.g. comma-
> separated?  This would allow multi-parent relationships between log items. 
> 
> E.g. specifying 12, 15 as a value would create unique Display links 
> for "12" and "15", based on the Display specification for that attribute.
> 
> This would be like "multiple fixed options", for the purpose of formatting.

Again, this is not clear to me. What do you mean by "display specification"?
Is it the "List display = ..." option or the "Format attribute = ..." option?
What is a "multi-parent relationship"? Why do you need multiple options for a
free text field? Why can't you use the MOptions specification?
  816   Wed Nov 24 18:59:45 2004 Reply Rich Persauddev2id@yahoo.comRequestAll2.5.4-6Re: Attribute Negative Search
> > Can "Display" links work with multiple options? 
> >
> > "ABC | DEF" is currently one link.
> >
> > Ideally, it would be two links, each formatted per the "Display" string.
> 
> I don't understand your qyestion. You have an attribute with MOptions, so you
> get "ABC | DEF" displayed in the list view. All links in each line point to
> the individual entry, so what is the benefit of having two links for ABC and DEF?

Display Subsystem = <a href="/LogBook1/?Subsystem=$Subsystem" style="color:
saddlebrown">$Subsystem</a>

ABC and DEF links would perform filter searches of a _different_ logbook.   

Separate links would perform separate searches.

> > Is there a way to disable wildcard matching in searches?
> > A search for "1" returns "1" and "10" and "11".  
> > Is there a way to perform an explict match?
> > Could there be a numeric match if the attribute type is numeric?
> 
> That should all be possible with the build-in regular expression. Just type
> 
> \b1\b
> 
> where "\b" means "word boundary". I agree that a numerical comparison for
> numerical attributes would be better, I will put that on the to-do list.

Thanks, this is very helpful.

> > Could there be a multi-value option for free text fields, e.g. comma-
> > separated?  This would allow multi-parent relationships between log items. 
> > 
> > E.g. specifying 12, 15 as a value would create unique Display links 
> > for "12" and "15", based on the Display specification for that attribute.
> > 
> > This would be like "multiple fixed options", for the purpose of formatting.
> 
> Again, this is not clear to me. What do you mean by "display specification"?
> Is it the "List display = ..." option or the "Format attribute = ..." option?
> What is a "multi-parent relationship"? Why do you need multiple options for a
> free text field? Why can't you use the MOptions specification?

MOptions does not work because the options are not fixed.   The options can be any
numeric ID for items in a related logbook.

Consider the case of two logbooks, where we wish to associate items in the second
logbook with more than one item in the first logbook.  We could define separate
attributes for each "parent item", e.g. Parent1, Parent2, Parent3, then use a
"Display" spec to convert a numeric ID into a hyperlink to the first logbook's item.
  The exact relationship is not important, could be parent/peer/child - some generic
relationship.

The benefit here would be the same as having separate links for MOptions attribute
values.
  818   Thu Nov 25 08:42:07 2004 Reply Stefan Rittstefan.ritt@psi.chRequestAll2.5.4-6Re: Attribute Negative Search
> Display Subsystem = <a href="/LogBook1/?Subsystem=$Subsystem" style="color:
> saddlebrown">$Subsystem</a>
> 
> ABC and DEF links would perform filter searches of a _different_ logbook.   
> 
> MOptions does not work because the options are not fixed.   The options can be any
> numeric ID for items in a related logbook.
> 
> Consider the case of two logbooks, where we wish to associate items in the second
> logbook with more than one item in the first logbook.  We could define separate
> attributes for each "parent item", e.g. Parent1, Parent2, Parent3, then use a
> "Display" spec to convert a numeric ID into a hyperlink to the first logbook's item.
>   The exact relationship is not important, could be parent/peer/child - some generic
> relationship.
> 
> The benefit here would be the same as having separate links for MOptions attribute
> values.

Ah, now I'm getting your point. You want kind of relational database where a logbook
correspond to a table, using the entry ID as primary key. Well, elog was not designed
having that in mind, so its capabilities will always be very limited. A MySQL with
phpMyAdmin might be better for that.

But what you could do is to put manual links betweek logbooks. If you enter in an
attribute following text:

elog:Forum/816 elog:Forum/806

then you get two links to entries 806 and 816. Writing this is a bit more than just 
"816 | 806", but it's less than writing directly an HTML link.
  68275   Thu Mar 3 14:51:55 2016 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionWindows2.9.2Re: Attribute Field Size Limited to 255 Characters

No. At least there is no simple method.

You would need to edit the source code and recompile elogd. But the number 256 is used for about 300 times in the source code, you'll have a hard time finding the right one to increase.

Cheers, Andreas

Mike Bodine wrote:

I currently have an Attribute defined in my .cfg file as  "Format <Attribute> = 0, attribname, attribvalue, 120, 500". I've found if I exceed 255 characters elogd.exe fails. Is there a method that will allow me to exceed 255 characters?

 

  1559   Wed Dec 21 20:54:11 2005 Reply Stefan Rittstefan.ritt@psi.chBug reportLinuxV2.6.0-betRe: Attachments in duplicated entries

Bertram Metz wrote:
The duplicate command duplicates the entry text itself, but it does not duplicate attachments. If attachments in a duplicated entry are deleted, the original attachment files are deleted as well and cannot be accessed anymore within the original entry.

My suggestion is to copy the attached files too and to use file names of the copies in the duplicated entry.


I chaned it such that attachments are removed from the duplicated entry, which was easier to implement. I hope this is ok as well. The change is in SVN revision 1584.
  1623   Tue Jan 24 14:39:21 2006 Agree Bertram Metzbmetz@sbs.comBug reportLinuxV2.6.0-betRe: Attachments in duplicated entries

Stefan Ritt wrote:

Bertram Metz wrote:
The duplicate command duplicates the entry text itself, but it does not duplicate attachments. If attachments in a duplicated entry are deleted, the original attachment files are deleted as well and cannot be accessed anymore within the original entry.

My suggestion is to copy the attached files too and to use file names of the copies in the duplicated entry.


I chaned it such that attachments are removed from the duplicated entry, which was easier to implement. I hope this is ok as well. The change is in SVN revision 1584.


Yes, that's ok for me.
Thank you very much Stefan.

Best Regards,
Bertram
  66626   Mon Nov 23 12:32:14 2009 Reply David PilgramDavid.Pilgram@epost.org.ukQuestionLinux2.7.7-2266Re: Attachments and images of attachments
> Hi Stefan,
> 
> I attached a 12 page (22kB) pdf file - no images - to an entry, but elog only converted the first 8 pages to
> images (.png).  This is reproducable, i.e. a different small multipage pdf file produced the same number of images.
> 
> The size of the pdf file does not seem to be a problem, a single page pdf file with a lot of images in it
> attached as expected.
> 
> Is this correct, or a defined limitation?

This is a defined limitation. Sometimes people attach whole books in PDF form to an entry, and you don't want to end up 
with hundreds of images cluttering your browser. If you want to see the full document, just load it into your PDF viewer.
  66627   Mon Nov 23 13:17:53 2009 Agree David PilgramDavid.Pilgram@epost.org.ukQuestionLinux2.7.7-2266Re: Attachments and images of attachments
> > Hi Stefan,
> > 
> > I attached a 12 page (22kB) pdf file - no images - to an entry, but elog only converted the first 8 pages to
> > images (.png).  This is reproducable, i.e. a different small multipage pdf file produced the same number of images.
> > 
> > The size of the pdf file does not seem to be a problem, a single page pdf file with a lot of images in it
> > attached as expected.
> > 
> > Is this correct, or a defined limitation?
> 
> This is a defined limitation. Sometimes people attach whole books in PDF form to an entry, and you don't want to end up 
> with hundreds of images cluttering your browser. If you want to see the full document, just load it into your PDF viewer.

Thanks, Stefan (why is this answer down under my name!?)

I couldn't find reference to this in the documentation.  In the case I referred to, I'll have to play with the pdf so that
the six pages I actually want displayed are.
ELOG V3.1.5-3fb85fa6