ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
69625
|
Mon Jan 23 22:24:23 2023 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | All | - | Re: Wikipedia Article deleted | I added some more references, that's about all I can do. Not sure if that is enough.
Stefan
Edmund Blomley wrote: |
It was now moved to the Draft space (which I did not even now existed so far): https://en.wikipedia.org/wiki/Draft:ELOG
Sebastian Schenk wrote: |
I have requested an undeletion of the article. The article was deleted "PROD", which means that someone tagged it. And if noone removes the tag, it could be deleted.
I could revive the article. So in the future, One should have an eye on it and maybe update the current version of the software.
If there iy an paper on the elog, maybe it could be cited for more creditability.
Andreas Luedeke wrote: |
It looks to me like only an author of an article can contradict a deletion. I did not find a single method to even comment on the deletion.
I am not an Wikipedia expert, can anyone suggest on how to push for the article to be restored? Or do we just write it again, until people stop deleting it?
Stefan Ritt wrote: |
I agree. I ahead ;-) I think it is not a good idea if the ELOG author pushes on that, but better someone else.
Best,
Stefan
Sebastian Schenk wrote: |
Hello,
I noticed the wikipedia article of the ELOG got deleted in November 2021.
With the reason: "Poorly sourced article, and I was not able to find good sources myself."
I could access the old article through web.archive.org, but for the project it would be good, if the article got revived.
|
|
|
|
|
|
69638
|
Wed Feb 1 11:31:10 2023 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 3.1.4 | Re: CKeditor Settings Cant Be Changed | elogd checks for the "scripts/ckeditor/ckeditor.js" file to detect the presence of CKeditor.
James Smallcombe wrote: |
I wanted to change some CKeditor settings so tried modifying elog/scripts/ckeditor to no avail.
I wiped elog/scripts/ and dropped a fresh download of CKeditor4, with only the basic extensions. But when I open the elog it still shows the full toolbar, with elog default style and with all extensions operational.
If I leave elog/scripts empty, I get "CKeditor NOT detected" when starting elogd and the HTML option is empty and shows nothing, all as expected.
Does anyone understand this? Is there some CKeditor configuration file elog is defering to that I've overlooked? I have tried system wide seaches just in case.
|
|
69678
|
Wed Jul 26 14:43:48 2023 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | Linux | Windows | Mac OSX | All | Other | 3.1.4 | Re: export the entries from ELOG to ECSS Word document (Manifacturing Report) | You can export logbook entries into a CSV file, then load it into Excel.
Stefan
Manuela Rigano wrote: |
Thanks a lot Stefan,
I asked if it is possible, in general, to create a connection and automatically fill in the tables of a report, or export the data into excell tables to then be connected to the report, having in our case about 24 process tables to be filled in with data or validation, for each report. If the compilation is not automatic, after having compiled the elog in each phase of the processing, the manifacturing report will then have to be compiled manually.
We use elog, having already used it in MEG We must then compulsorily also make manufacturing and test reports. The expected space-type documentation format for these documents is in word.
Below is a small example of a test table, with just a few steps.
Thanks again
Manuela
POWER INTERFACE VERIFICATION TEST
|
STEP
|
Description
|
Expected Value
|
Measured value
|
Remarks
|
-
|
Power-On Ixxxx
|
|
|
|
-
|
Test communications with ...
|
|
|
|
-
|
Command xxxx to switch-on the value ….V DC/DC
|
|
|
|
-
|
Configure a multimeter to measure voltage
|
|
|
|
-
|
Use the multimeter to check ..V interface. Connect multimeter positive prove to pin x, and negative prove to pin y of yyyy connector
|
Volts: x.xV ≤ ___ ≤ y.yV
|
|
|
-
|
Repeat operation between pins z and q of …
|
Volts: 5. 097V ≤ ______ ≤ 5.252V
|
|
|
-
|
Command xxxx to switch-on the ..V DC/DC
|
|
|
|
-
|
Use the multimeter to check ..V interface. Connect multimeter positive prove to pin xx, and negative prove to pin yy of yyyy connector
|
Volts: x.x V ≤ ______ ≤ y.y V
|
|
|
-
|
Power-Off xxx
|
|
|
|
-
|
Re-connect harness to zzzz through yyyy connector
|
|
|
|
-
|
Power-On xxx
|
|
|
|
-
|
Verify ..V input voltage. Check final voltage
|
Final Volts @ ..V: x.x V ≤ __ ≤ 5y.yV
|
|
|
-
|
Verify ..V power consumption
|
Consumption @ ..V: x.x< _ < y.y W
|
|
|
-
|
|
|
|
|
Stefan Ritt wrote: |
You can just copy-and-paste an elog entry into Word. I tested it here wiht a simple table:
Did a copy-and-paste to Word, and got the thing below.
Best,
Stefan
Manuela Rigano wrote: |
HI,
Is there a way to export the ELOG entries to a file like Microsoft Word?
For ECSS-type documents for space missions, I have to report the data that we enter in the ELOG in a Manufacturing Report, foreseen for ECSS, in word format. It's possible to do it?
The data has to go into tables, inserted in the world file, called "as run procedure".
Is it possible to connect the elog to a report template so that it automatically generates the manufacturing report? Or link the tables placed in it so that they are automatically filled in?
Thank you so much
Manuela
|
|
|
|
69687
|
Thu Aug 24 16:43:41 2023 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 3.1.5-1 | Re: File/App associations for attachments | Below are the MIME types hard-coded into elogd. As you can see there is neither .ods nor .eml. If you give me the MIME type, I can add that easily. I wonder however why both work differently for you. I believe this is a browser setting.
Stefan
struct FILETYPE {
char ext[32];
char type[80];
} filetype[] = {
{".AI", "application/postscript"},
{".ASC", "text/plain"},
{".BZ2", "application/x-bzip2"},
{".CFG", "text/plain"},
{".CHRT", "application/x-kchart"},
{".CONF", "text/plain"},
{".CSH", "application/x-csh"},
{".CSS", "text/css"},
{".DOC", "application/msword"},
{".DVI", "application/x-dvi"},
{".EPS", "application/postscript"},
{".GIF", "image/gif"},
{".GZ", "application/x-gzip"},
{".HTM", "text/html"},
{".HTML", "text/html"},
{".ICO", "image/x-icon"},
{".JPEG", "image/jpeg"},
{".JPG", "image/jpeg"},
{".JS", "application/x-javascript"},
{".KPR", "application/x-kpresenter"},
{".KSP", "application/x-kspread"},
{".KWD", "application/x-kword"},
{".MP3", "audio/mpeg"},
{".OGG", "application/x-ogg"},
{".PDF", "application/pdf"},
{".PNG", "image/png"},
{".PS", "application/postscript"},
{".RAM", "audio/x-pn-realaudio"},
{".RM", "audio/x-pn-realaudio"},
{".RM", "audio/x-pn-realaudio"},
{".RM", "audio/x-pn-realaudio"},
{".RPM", "application/x-rpm"},
{".RTF", "application/rtf"},
{".SH", "application/x-sh"},
{".SVG", "image/svg+xml"},
{".TAR", "application/x-tar"},
{".TCL", "application/x-tcl"},
{".TEX", "application/x-tex"},
{".TGZ", "application/x-gzip"},
{".TIF", "image/tiff"},
{".TIFF", "image/tiff"},
{".TXT", "text/plain"},
{".WAV", "audio/x-wav"},
{".XLS", "application/x-msexcel"},
{".XML", "text/xml"},
{".XSL", "text/xml"},
{".ZIP", "application/x-zip-compressed"},
/* Open XML file types */
{".DOCM", "application/vnd.ms-word.document.macroEnabled.12"},
{".DOCX", "application/vnd.openxmlformats-officedocument.wordprocessingml.document"},
{".DOTM", "application/vnd.ms-word.template.macroEnabled.12"},
{".DOTX", "application/vnd.openxmlformats-officedocument.wordprocessingml.template"},
{".PPSM", "application/vnd.ms-powerpoint.slideshow.macroEnabled.12"},
{".PPSX", "application/vnd.openxmlformats-officedocument.presentationml.slideshow"},
{".PPTM", "application/vnd.ms-powerpoint.presentation.macroEnabled.12"},
{".PPTX", "application/vnd.openxmlformats-officedocument.presentationml.presentation"},
{".XLSB", "application/vnd.ms-excel.sheet.binary.macroEnabled.12"},
{".XLSM", "application/vnd.ms-excel.sheet.macroEnabled.12"},
{".XLSX", "application/vnd.openxmlformats-officedocument.spreadsheetml.sheet"},
{".XPS", "application/vnd.ms-xpsdocument"},
{"", ""},
};
|
69696
|
Mon Sep 18 14:38:30 2023 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Other | latest | Re: update elog downloads page | Thanks for the reminder, I updated the download instructions. |
69706
|
Tue Oct 24 08:12:38 2023 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | latest | Re: Cannot send Emails | ELOG has not change in the last years in that respect, but I know that mailer get more and more picky about encryption etc. So you probably have to convince your mailer to accept the pw as it comes from ELOG, or do not require a pw for that specific client.
Stefan
John wrote: |
Hello, my sending of emails was working a while back but I have not checked on it in a few months and found out I am getting authentication errors sending to my MTA (mailer). I was using a base64 to encode the pw but now my mailer (gandi.net) rejects it. Has anything changed over the last couple of years with Elogs code that would be affecting this? I just upgraded (Linux) and changed my testing grounds to non-production and the same problem exists. Thing is I CAN send using other programs, but not with Elog. It is impertive I figure this out or have a work around.. but a 'work around' does not seem like a possible task since all the work (forums and such) will be via my Elog server.
Thanx, John
|
|
69710
|
Thu Nov 30 14:28:12 2023 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 3.1.3 | Re: Restricting entries view by user | Keeping the global and individual logbooks in sync is not possible. So indded my proposal is a cumbersome solution in your case. We do have "restrict edit" which lets users only edit their own entries, but we do not have "restrict view". Maye some thought for a future version of elog.
Stefan
Matteo Mannini wrote: |
Dear Stefan,
thanks to the answer you gave to my colleague.
Now, attempting to follow your suggestion... If we will create several logbooks, one for each user,
1) there is a way to automatically duplicate all the entries in anoter "global" elog without loosing them and keeping them updated between the global and the individual logbooks?
2) alternatively how I could activate a search in all these user logbooks (and only in this set of logbooks without searching in the others logbook present in the same file conf)? shall I gnereate a separated elog instance only for this set of logbooks? how to let this search to all option available only to a reduced number of "superusers" that are not "administrators?
thanks
Matteo
Stefan Ritt wrote: |
No, this is not possible with the current version of Elog, so indeed everybody needs their own logbook.
Stefan
Leonardo Tacconi wrote: |
Good morning,
I would like to ask you whether it is feasible to establish a logbook that limits access to entries, enabling each user to view only their own.
Although creating a logbook per user is an apparent solution, it does not meet my requirements.
Thank you in advance.
Leonardo
|
|
|
|
69717
|
Mon Jan 8 16:25:05 2024 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | ELOG V3.1.3-a38 | Re: Maximum number of attributes | Why don't you simply create a single attribute "identifier", which then gets a value D_001, ..., D_xxx. You can still use the D_xxx in full text search.
Stefan
Dr Marta Divall wrote: |
To explain the problem, we have silicon chip designs, which we log with an indentifyier, which is the attribute for easy search, as we want to follow their progress from design thorugh fabrication to testing, involving many people. They are called D_001; D_099...you get it. We have reached the 100, but maybe it is the est just to create an archive after each 100 design and make a new tab/logbook. Any other suggestions are of course welcome.
David Pilgram wrote: |
In my case, I had a number of attributes which had a varied prefix. For example, "progressed" , which could have no prefix, or prefix "I", "To be", "Strongly", "Seriously"... and that was true (the same prefixes, or at least many of them) for a number of attributes. Splitting them into two groups, the prefixes and the action, allowed me to gain more actual attributes without having to recompile. Suitable change in the elog config file will also make this easy to follow in how the entries are shown in threaded or full display modes. In your case suffixes may be better, but I hope you get the point.
Although I have done a (linux) recompile in the past, v2.9 something, 120 attributes seemed not to affect things.
Dr Marta Divall wrote: |
Dear Stefan,
Thansk for the super fast response! To keep the stability of the system we will look for a different solution then.
Best,
Marta
Stefan Ritt wrote: |
You would have to change the elogd.c code and recompile. At some point you wlll however get crash of elogd with a stack overflow. If you need more than 100 attributes, it becomes anyhow hard to manage, so I would suggest other ways, like adding iformation to the text body etc.
Best,
Stefan
Dr Marta Divall wrote: |
The maximum number or attributes is 100.
Is it possible to increase this?
Thanks!
|
|
|
|
|
|
|