| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
69634
|
Sat Jan 28 08:11:05 2023 |
 | John Kelly | john@secondcomingtechnologies.com | Request | All | - | Re: Wikipedia Article deleted | Wikipedia has been an unreliable source for a very long time, just for the reasons that we are seeing here now with psi and Elog. Those that 'run' Wikipedia are political and authoratative. I have not only had these negative experiences with 'them' but know of many others that have as well. I see no reason why an organization as ours with such great ideas, programs and people need to be on their site. I think it would 'say more' if we left this as is and let others see how unreliable Wikipedia really is.
John
| Andreas Luedeke wrote: |
|
It appears to me that this is a really stupid problem: the article provides many links to sources, but they are just links, not "references". That does not count, since links could be something else than references.
I'll try to edit it and transform the list of external links into references to verify the text. Lets hope that this will suffice.
Okay: found three articles about applications of ELOG and put them under references. I took the liberty to submit the draft: it shows that they expect some month delay for a review. I have no idea if that was what they want, but it is worth a try.
| Edmund Blomley wrote: |
|
If I understand it correctly I think it has to be submitted for review with the blue button on that page, just not sure if that should come from your side or someone else
| Stefan Ritt wrote: |
|
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.
|
|
|
|
|
|
|
|
|
|
69635
|
Sat Jan 28 14:26:07 2023 |
| David Pilgram | David.Pilgram@epost.org.uk | Request | All | - | Re: Wikipedia Article deleted | I am rather with John on this.
I deliberately stopped contributing to Wikipedia years ago after I added an observation to an entry. That is, a piece of what could be called original research. It was shot down in flames for being precisely that: original research. From what I read in the Draft:Elog and the Talk section, I think that the same issue in some guise or other will come up. All of us use and love Elog - I think I use it for all of the listed purposes - but apart from being in the Debian distro (which I did not know about) there is very little published primary sources. Mind you, the quality of publications as primary sources can be questioned, I can bore on with several examples.
Has anyone ever published a paper citing their filing cabinet organisation? Elog's obviously different, but has the same problem when it comes to citations. It is a utility, a very useful one, but the sort of utility that might just make an aside in a paper these days. If we were in the 1980s and (hypothetically) Elog was available and as functional, that would probably make it the subject in computer research papers and magazines.
David.
| John Kelly wrote: |
|
Wikipedia has been an unreliable source for a very long time, just for the reasons that we are seeing here now with psi and Elog. Those that 'run' Wikipedia are political and authoratative. I have not only had these negative experiences with 'them' but know of many others that have as well. I see no reason why an organization as ours with such great ideas, programs and people need to be on their site. I think it would 'say more' if we left this as is and let others see how unreliable Wikipedia really is.
John
| Andreas Luedeke wrote: |
|
It appears to me that this is a really stupid problem: the article provides many links to sources, but they are just links, not "references". That does not count, since links could be something else than references.
I'll try to edit it and transform the list of external links into references to verify the text. Lets hope that this will suffice.
Okay: found three articles about applications of ELOG and put them under references. I took the liberty to submit the draft: it shows that they expect some month delay for a review. I have no idea if that was what they want, but it is worth a try.
| Edmund Blomley wrote: |
|
If I understand it correctly I think it has to be submitted for review with the blue button on that page, just not sure if that should come from your side or someone else
| Stefan Ritt wrote: |
|
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.
|
|
|
|
|
|
|
|
|
|
|
69674
|
Sat Jun 17 22:13:01 2023 |
 | Andreas Luedeke | andreas.luedeke@psi.ch | Question | All | 3.1.3 | Re: Nested commands in logbook | Atrributes can only be defined once in a logbook.
But you can select which attributes are shown with the commands:
Show Attributes = <list>
Attributes present in this list are shown in the single entry page. Omitting attributes can make sense for attributes which are automatically derived from other attributes via the Change <attribute> command.Show Attributes Edit = <list>
The same as Show Attributes, but for the entry form.
Those can be redifined in conditional attribute clauses.
(See https://elog.psi.ch/elog/config.html)
| Leonardo Tacconi wrote: |
|
Hi everybody,
I am trying to setup my personal ELog, defining attributes and stuff like that. I just tried to make some nested commands but I really could not achieve that.
The idea is something like this:
Attributes = Author
Options Author = Tizio{1}, Caio{2}, Sempronio{3}
{1} Attributes = Author, Project
{1} Options Project = Proj1{a}, Proj2{b}, Proj3{c}
{a} Attributes = Author, Project, Year
{a} Options Year = 2017, 2019
Anyway, when I select Proj1 nothing really happens. So, is there any way to set up nested commands like in the reported example?
Many thanks in advance!
P.S. Is there any documentation in which are reported all the possible commands that can be used?
|
|
|
69720
|
Thu Jan 18 13:56:59 2024 |
 | Sarah Kuckuk | sarah.kuckuk@uni-tuebingen.de | Question | All | V3.1.3-7933898 | Let the user decide which columns should be displayed | Hello
I was wondering if there is any possibility to let the user decide which columns to show/download in the search results? We have quite a lot of fields and it would help the usefulness of our elog a lot.
(If there is an obvious possibility that I missed I'm sorry).
Thanks a lot! |
|
69723
|
Mon Jan 22 12:15:26 2024 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | V3.1.3-7933898 | Re: Let the user decide which columns should be displayed | There is a general display option "List display", but that applies for all users. For the download, you can load the CSV file into a spreadsheet program and then delete some columns.
Stefan
| Sarah Kuckuk wrote: |
|
Hello
I was wondering if there is any possibility to let the user decide which columns to show/download in the search results? We have quite a lot of fields and it would help the usefulness of our elog a lot.
(If there is an obvious possibility that I missed I'm sorry).
Thanks a lot!
|
|
|
69807
|
Mon Jul 22 16:17:55 2024 |
 | André | andre.althaus@tu-dortmund.de | Bug report | All | 3.1.5 | HTTP headers should be parsed case insensitive | I'm trying to run elog behind haproxy, but get the error "Invalid Content-Length in header" on posting.
As stated in the manual, haproxy rewrites all headers to lower case.
elogd parses the content-length header case sensitive which is against the HTTP RFC. This might also apply to other headers that get parsed.
For now I'm using the workaround from the manual:
global
h1-case-adjust content-length Content-Length
h1-case-adjust content-type Content-Type
backend elog
option h1-case-adjust-bogus-server
server elog 127.0.0.1:8080
But as the manual states, this should not be used as a permanent solution. |
|
69817
|
Wed Jul 31 14:21:21 2024 |
| Stefan Ritt | I cstefan.ritt@psi.ch | Bug report | All | 3.1.5 | Re: HTTP headers should be parsed case insensitive | I changed elog to interprete the content-length header case in-sensitive and committed the change. Can you try again?
Stefan
| André wrote: |
|
I'm trying to run elog behind haproxy, but get the error "Invalid Content-Length in header" on posting.
As stated in the manual, haproxy rewrites all headers to lower case.
elogd parses the content-length header case sensitive which is against the HTTP RFC. This might also apply to other headers that get parsed.
For now I'm using the workaround from the manual:
global
h1-case-adjust content-length Content-Length
h1-case-adjust content-type Content-Type
backend elog
option h1-case-adjust-bogus-server
server elog 127.0.0.1:8080
But as the manual states, this should not be used as a permanent solution.
|
|
|
69821
|
Wed Aug 7 22:54:03 2024 |
| Walter Reviol | reviol@anl.gov | Question | All | 2 | Can Elog make a table? | Hi!
I like to format an Elog "directory" such that all entries make/occur as a table. Say: 5 columns and a large number of rows. In a sense, make an excel spreadsheet in Elog. Is this possible? How can this be done? Is there perhaps a template?
Thanks in advance.
Walter Reviol
reviol@anl.gov |
|