Re: Importing XML/CSV, posted by Andreas Luedeke on Wed Oct 9 09:19:54 2013
|
| Barend wrote: |
|
Hi Stefan,
I'm experiencing problems importing XML (.csv is not working at all for me).
My logbook contains 3 date-attributes besides the system DATE (entry time), date-format is defined as %d %b %y.
The XML file hold the date format "DD.MM.YYYY"
- During "preview" I see that all entries are listed.
- During the import I get the "wrong date format" error.
- When I review the Summary, I see that only the first XML entry (all 3 date-attributes hold a date) was imported.
- When I try to re-import the XML from the second entry (after removing the 1st entry from XML - this second entry hold NO date-value on one of the date-attributes) the elogd.exe crashes and I get the "Service Temporarily Unavailable" error page.
- When I try to re-import the XML from the modified second entry (after removing the 1st entry from XML - this second entry holds date-value on all of the date-attributes) the elogd.exe crashes and I get the "Service Temporarily Unavailable" error page.
Any suggestion what could be wrong? Is it the missing date-value?
|
Can you post your elog configuration file (elog.cfg)?
⇄
Detect language » English
|
Re: Importing XML/CSV, posted by Barend on Sun Oct 13 16:32:05 2013 
|
| Andreas Luedeke wrote: |
|
| Barend wrote: |
|
Hi Stefan,
I'm experiencing problems importing XML (.csv is not working at all for me).
My logbook contains 3 date-attributes besides the system DATE (entry time), date-format is defined as %d %b %y.
The XML file hold the date format "DD.MM.YYYY"
- During "preview" I see that all entries are listed.
- During the import I get the "wrong date format" error.
- When I review the Summary, I see that only the first XML entry (all 3 date-attributes hold a date) was imported.
- When I try to re-import the XML from the second entry (after removing the 1st entry from XML - this second entry hold NO date-value on one of the date-attributes) the elogd.exe crashes and I get the "Service Temporarily Unavailable" error page.
- When I try to re-import the XML from the modified second entry (after removing the 1st entry from XML - this second entry holds date-value on all of the date-attributes) the elogd.exe crashes and I get the "Service Temporarily Unavailable" error page.
Any suggestion what could be wrong? Is it the missing date-value?
|
Can you post your elog configuration file (elog.cfg)?
⇄
Detect language » English
|
Hi Andreas,
I had to filter-out some other logbook. Please find attached the configuration section for the affected logbook "UMOWY".
Looking forward to your review.
Regards, Barend |
Error: Attribute <date> not supplied., posted by Barend on Mon Oct 14 12:08:16 2013
|
Stefan/Andreas,
When I reply to an existing Logbook entry, I get the error page "Error: Attribute Audit Date not supplied. Please go back and enter the Audit Date field."
The configuration file uses:
Required Attributes = Audit No, Audit Date, Audit Type, Finding No, Finding Level, Section, MOE Procedure, Finding Details, Auditor, Deadline, Responsibility
Fixed Attributes Reply = Audit No, Audit Date, Audit Type, Finding No, Finding Level, Section, MOE Procedure, Finding Details, Auditor, Deadline, Responsibility
Type Audit Date = date
Type Deadline = date
The combination "Required Attributes" and "Fixed Attributes Reply" does not work for date-fields.
As soon as I disclose the date fields from either "Required Attributes" or "Fixed Attributes Reply" the error is no longer evident.
But I want the "Audit Date" and "Deadline" to entered during a new Record and they shall not be changed during a reply.
Is this a bug -or- do I have to change the configuration?
Thanks & regards, Barend |
|
Re: Error: Attribute <date> not supplied., posted by David Pilgram on Tue Oct 15 14:14:07 2013
|
| Barend wrote: |
|
Stefan/Andreas,
When I reply to an existing Logbook entry, I get the error page "Error: Attribute Audit Date not supplied. Please go back and enter the Audit Date field."
The configuration file uses:
Required Attributes = Audit No, Audit Date, Audit Type, Finding No, Finding Level, Section, MOE Procedure, Finding Details, Auditor, Deadline, Responsibility
Fixed Attributes Reply = Audit No, Audit Date, Audit Type, Finding No, Finding Level, Section, MOE Procedure, Finding Details, Auditor, Deadline, Responsibility
Type Audit Date = date
Type Deadline = date
The combination "Required Attributes" and "Fixed Attributes Reply" does not work for date-fields.
As soon as I disclose the date fields from either "Required Attributes" or "Fixed Attributes Reply" the error is no longer evident.
But I want the "Audit Date" and "Deadline" to entered during a new Record and they shall not be changed during a reply.
Is this a bug -or- do I have to change the configuration?
Thanks & regards, Barend
|
Hi Barend,
I can reproduce your point.
I've found various work-arounds, but possibly the best one is to remove "Audit Date" and "Deadline" from the Required Attributes line. True you won't get a warning saying that they were not entered for the first entry (if you didn't enter them, that is), but all subsequent replies run as you would want.
Another way is if you *preview* your entry, you can then submit it and that works. This seems to work by bring up a different page where you can edit all those Fixed Attributes. (I'm not sure that Preview is meant to do that, but it does and it's a work-around).
Or, if you remove "Audit date" and "Deadline" from the Fixed Attributes Reply (as you did) seems to work in the same way. But I see that you don't want the opportunity for these to be changed.
I note that if you get this error message and go back, the message that you may have written is erased (this is unusual, it doesn't do this if you have not supplied an attribute on the first entry, say).
So I suspect this is a bug, possibly not detected before; perhaps no-one had tried this combination. |
Re: Importing XML/CSV, posted by Andreas Luedeke on Wed Oct 16 16:53:55 2013
|
| Barend wrote: |
|
| Andreas Luedeke wrote: |
|
| Barend wrote: |
|
Hi Stefan,
I'm experiencing problems importing XML (.csv is not working at all for me).
My logbook contains 3 date-attributes besides the system DATE (entry time), date-format is defined as %d %b %y.
The XML file hold the date format "DD.MM.YYYY"
- During "preview" I see that all entries are listed.
- During the import I get the "wrong date format" error.
- When I review the Summary, I see that only the first XML entry (all 3 date-attributes hold a date) was imported.
- When I try to re-import the XML from the second entry (after removing the 1st entry from XML - this second entry hold NO date-value on one of the date-attributes) the elogd.exe crashes and I get the "Service Temporarily Unavailable" error page.
- When I try to re-import the XML from the modified second entry (after removing the 1st entry from XML - this second entry holds date-value on all of the date-attributes) the elogd.exe crashes and I get the "Service Temporarily Unavailable" error page.
Any suggestion what could be wrong? Is it the missing date-value?
|
Can you post your elog configuration file (elog.cfg)?
⇄
Detect language » English
|
Hi Andreas,
I had to filter-out some other logbook. Please find attached the configuration section for the affected logbook "UMOWY".
Looking forward to your review.
Regards, Barend
|
Hi Barend,
I can confirm that this is a bug of the ELOG import function: if you have a field that is defined as type "date" or "datetime", then elogd requires the value of the field to be of a matching format.
It is not even allowed to omit the time in "datetime" format. If the field is not required in an entry, then it is therefore possible to create an entry that cannot be imported.
I've attached a minimal example elogd.cfg and XML import file to reproduce the problem.
I'm afraid you'll either need to wait for a patch, or you can add dummy dates for all your empty date fields in the XML import file. Just do a "replace all" with your favourite editor; in my example you would e.g. replace all "<D></D>" strings with "<D>01-01-1970</D>" before the import.
⇄
Detect language » English
Cheers, Andreas
⇄
Detect language » English
⇄
Detect language » English
|
|
Re: Error: Attribute <date> not supplied., posted by Barend on Tue Oct 22 10:54:51 2013
|
| David Pilgram wrote: |
| Barend wrote: |
|
Stefan/Andreas,
When I reply to an existing Logbook entry, I get the error page "Error: Attribute Audit Date not supplied. Please go back and enter the Audit Date field."
The configuration file uses:
Required Attributes = Audit No, Audit Date, Audit Type, Finding No, Finding Level, Section, MOE Procedure, Finding Details, Auditor, Deadline, Responsibility
Fixed Attributes Reply = Audit No, Audit Date, Audit Type, Finding No, Finding Level, Section, MOE Procedure, Finding Details, Auditor, Deadline, Responsibility
Type Audit Date = date
Type Deadline = date
The combination "Required Attributes" and "Fixed Attributes Reply" does not work for date-fields.
As soon as I disclose the date fields from either "Required Attributes" or "Fixed Attributes Reply" the error is no longer evident.
But I want the "Audit Date" and "Deadline" to entered during a new Record and they shall not be changed during a reply.
Is this a bug -or- do I have to change the configuration?
Thanks & regards, Barend
|
Hi Barend,
I can reproduce your point.
I've found various work-arounds, but possibly the best one is to remove "Audit Date" and "Deadline" from the Required Attributes line. True you won't get a warning saying that they were not entered for the first entry (if you didn't enter them, that is), but all subsequent replies run as you would want.
Another way is if you *preview* your entry, you can then submit it and that works. This seems to work by bring up a different page where you can edit all those Fixed Attributes. (I'm not sure that Preview is meant to do that, but it does and it's a work-around).
Or, if you remove "Audit date" and "Deadline" from the Fixed Attributes Reply (as you did) seems to work in the same way. But I see that you don't want the opportunity for these to be changed.
I note that if you get this error message and go back, the message that you may have written is erased (this is unusual, it doesn't do this if you have not supplied an attribute on the first entry, say).
So I suspect this is a bug, possibly not detected before; perhaps no-one had tried this combination. |
Hi David,
Thanks for the reply. I'll review the options and decide what is the best option to move forward.
Regards, Barend |
|
Re: Importing XML/CSV, posted by Barend on Tue Oct 22 10:56:13 2013
|
| Andreas Luedeke wrote: |
| Barend wrote: |
|
| Andreas Luedeke wrote: |
|
| Barend wrote: |
|
Hi Stefan,
I'm experiencing problems importing XML (.csv is not working at all for me).
My logbook contains 3 date-attributes besides the system DATE (entry time), date-format is defined as %d %b %y.
The XML file hold the date format "DD.MM.YYYY"
- During "preview" I see that all entries are listed.
- During the import I get the "wrong date format" error.
- When I review the Summary, I see that only the first XML entry (all 3 date-attributes hold a date) was imported.
- When I try to re-import the XML from the second entry (after removing the 1st entry from XML - this second entry hold NO date-value on one of the date-attributes) the elogd.exe crashes and I get the "Service Temporarily Unavailable" error page.
- When I try to re-import the XML from the modified second entry (after removing the 1st entry from XML - this second entry holds date-value on all of the date-attributes) the elogd.exe crashes and I get the "Service Temporarily Unavailable" error page.
Any suggestion what could be wrong? Is it the missing date-value?
|
Can you post your elog configuration file (elog.cfg)?
⇄
Detect language » English
|
Hi Andreas,
I had to filter-out some other logbook. Please find attached the configuration section for the affected logbook "UMOWY".
Looking forward to your review.
Regards, Barend
|
Hi Barend,
I can confirm that this is a bug of the ELOG import function: if you have a field that is defined as type "date" or "datetime", then elogd requires the value of the field to be of a matching format.
It is not even allowed to omit the time in "datetime" format. If the field is not required in an entry, then it is therefore possible to create an entry that cannot be imported.
I've attached a minimal example elogd.cfg and XML import file to reproduce the problem.
I'm afraid you'll either need to wait for a patch, or you can add dummy dates for all your empty date fields in the XML import file. Just do a "replace all" with your favourite editor; in my example you would e.g. replace all "<D></D>" strings with "<D>01-01-1970</D>" before the import.
⇄
Detect language » English
Cheers, Andreas
⇄
Detect language » English
⇄
Detect language » English
|
Hi Andreas,
Thanks for the reply. The suggested approach is workable, so I'll use that one.
Regards, Barend |
|
Import of entries from DOOCS eLogBook to ELOG, posted by Andreas Luedeke on Thu Oct 24 12:09:29 2013
|
Hi everyone,
we have formerly used the DOOCS eLogBook from DESY for a couple of years for some application at our large
research facilities. Now we have standardized on ELOG and I've got a request to import the old DOOCS eLogBook
data into the new logbooks.
I've looked into it and the import appears to be fairly straight forward. I have two questions to the community,
before I start to program an import script:
1) Has anyone created such an import function already, and if the answer is yes, can I have it?
2) Would anyone else be interested in such a "cross logbook import", and if yes, what are your requirements?
Thanks
Andreas |
|