Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error 200 on DDI batch refresh #6

Closed
Alhrath opened this issue Apr 23, 2019 · 5 comments
Closed

Error 200 on DDI batch refresh #6

Alhrath opened this issue Apr 23, 2019 · 5 comments

Comments

@Alhrath
Copy link

Alhrath commented Apr 23, 2019

Hi again :)
During the DDI batch refresh, I get a huge amount of "Error: 200 - Ignore errors and continue?" messages. Only 41/903 entries receive the {"success":"UPDATED: XXX"} messages, other ajax responses are empty. I have no errors in apache or php server side.
When I go to the studies, I have no "data description" tab in these failed update entries. Do you have a clue on what's happening ?
Thanks.

@mah0001
Copy link
Contributor

mah0001 commented Apr 23, 2019

Can you share one of the DDI files that are returning the errors?

@Alhrath
Copy link
Author

Alhrath commented Apr 25, 2019

Here you are :

ch.sidos.ddi.316.6634.xml.zip

@mah0001
Copy link
Contributor

mah0001 commented Apr 25, 2019

NADA uses the @id attribute on the fileDesc which is missing in your DDI. I see you have the ID at the fileName level, I can add a fix to check both places. Just curious, what did you use for generating the DDI?

ddi-error

mah0001 added a commit that referenced this issue Apr 27, 2019
…cr and fileDscr/fileTxt/fileName elements
@mah0001 mah0001 closed this as completed Apr 27, 2019
@Alhrath
Copy link
Author

Alhrath commented Apr 29, 2019

Thanks

We are coming from another data publish software : Nesstar. Someone else did the migration from Nesstar to Nada 4.4 so I'm not aware of all details on this part. I'm doing the migration from 4.4 to 5 and evaluating the best solution for us.

@Alhrath
Copy link
Author

Alhrath commented May 2, 2019

I confirm that this is fixed on current develop branch, thanks!

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants