Individual Search export failed

In which Wildbook did the issue occur? Flukebook

What operating system were you using? (eg. MacOS 10.15.3) Windows 11

What web browser were you using? (eg. Chrome 79) Microsoft Edge 97.0.1072.55

What is your role on the site? (admin, researcher, etc) Researcher

What happened? I wanted to export Individual Search Results, but it gives me an error.

What did you expect to happen? I expected to be able to download the files

What are some steps we could take to reproduce the issue? Search for the individuals starting with PPBD- and try to download the SOCPROG or the CAPTURE file. They both failed for me and gave me an error message (see pictures). @sue_mason


links to the errors:
SOCPROG -
Wildbook (flukebook.org)
CAPTURE - https://www.flukebook.org/IndividualSearchExportCapture?noDate=noDate&approved=acceptedEncounters&unapproved=allEncounters&unidentifiable=allEncounters&male=male&female=female&unknown=unknown&alive=alive&dead=dead&patterningCodeField=None&measurementWaterTemperature%28operator%29=gteq&measurementSalinity%28operator%29=gteq&satelliteTagName=None&biomeasurement13C%28operator%29=gteq&biomeasurement13C%28value%29=&biomeasurement15N%28operator%29=gteq&biomeasurement15N%28value%29=&biomeasurement34S%28operator%29=gteq&biomeasurement34S%28value%29=&464465_alleleValue0=&464465_alleleValue1=&EV1_alleleValue0=&EV1_alleleValue1=&EV14_alleleValue0=&EV14_alleleValue1=&EV37_alleleValue0=&EV37_alleleValue1=&EV5_alleleValue0=&EV5_alleleValue1=&EV94_alleleValue0=&EV94_alleleValue1=&Ev1_alleleValue0=&Ev1_alleleValue1=&Ev104_alleleValue0=&Ev104_alleleValue1=&Ev14_alleleValue0=&Ev14_alleleValue1=&Ev21_alleleValue0=&Ev21_alleleValue1=&Ev37_alleleValue0=&Ev37_alleleValue1=&Ev94_alleleValue0=&Ev94_alleleValue1=&Ev96_alleleValue0=&Ev96_alleleValue1=&FCB1_alleleValue0=&FCB1_alleleValue1=&GATA28_alleleValue0=&GATA28_alleleValue1=&GATA417_alleleValue0=&GATA417_alleleValue1=&GT211_alleleValue0=&GT211_alleleValue1=&GT23_alleleValue0=&GT23_alleleValue1=&GT575_alleleValue0=&GT575_alleleValue1=&SW13_alleleValue0=&SW13_alleleValue1=&SW19_alleleValue0=&SW19_alleleValue1=&rw4-10_alleleValue0=&rw4-10_alleleValue1=&rw410_alleleValue0=&rw410_alleleValue1=&rw48_alleleValue0=&rw48_alleleValue1=&alleleRelaxValue=0&individualID=PPBD-&resightGapOperator=greater&resightGap=&firstYearField=&organizationId=None&projectId=None&submitSearch=Search&noDate=noDate&approved=acceptedEncounters&unapproved=allEncounters&unidentifiable=allEncounters&male=male&female=female&unknown=unknown&alive=alive&dead=dead&patterningCodeField=None&measurementWaterTemperature(operator)=gteq&measurementSalinity(operator)=gteq&satelliteTagName=None&biomeasurement13C(operator)=gteq&biomeasurement13C(value)=&biomeasurement15N(operator)=gteq&biomeasurement15N(value)=&biomeasurement34S(…&GATA417_alleleValue0=&GATA417_alleleValue1=&GT211_alleleValue0=&GT211_alleleValue1=&GT23_alleleValue0=&GT23_alleleValue1=&GT575_alleleValue0=&GT575_alleleValue1=&SW13_alleleValue0=&SW13_alleleValue1=&SW19_alleleValue0=&SW19_alleleValue1=&rw4-10_alleleValue0=&rw4-10_alleleValue1=&rw410_alleleValue0=&rw410_alleleValue1=&rw48_alleleValue0=&rw48_alleleValue1=&alleleRelaxValue=0&individualID=PPBD-&resightGapOperator=greater&resightGap=&firstYearField=&organizationId=None&projectId=None&submitSearch=Search&noDate=noDate&approved=acceptedEncounters&unapproved=allEncounters&unidentifiable=allEncounters&male=male&female=female&unknown=unknown&alive=alive&dead=dead&patterningCodeField=None&measurementWaterTemperature(operator)=gteq&measurementSalinity(operator)=gteq&satelliteTagName=None&biomeasurement13C(operator)=gteq&biomeasurement13C(value)=&biomeasurement15N(operator)=gteq&biomeasurement15N(value)=&biomeasurement34S(operator)=gteq&biomeasurement34S(value)=&464465_alleleValue0=&464465_alleleValue1=&EV1_alleleValue0=&EV1_alleleValue1=&EV14_alleleValue0=&EV14_alleleValue1=&EV37_alleleValue0=&EV37_alleleValue1=&EV5_alleleValue0=&EV5_alleleValue1=&EV94_alleleValue0=&EV94_alleleValue1=&Ev1_alleleValue0=&Ev1_alleleValue1=&Ev104_alleleValue0=&Ev104_alleleValue1=&Ev14_alleleValue0=&Ev14_alleleValue1=&Ev21_alleleValue0=&Ev21_alleleValue1=&Ev37_alleleValue0=&Ev37_alleleValue1=&Ev94_alleleValue0=&Ev94_alleleValue1=&Ev96_alleleValue0=&Ev96_alleleValue1=&FCB1_alleleValue0=&FCB1_alleleValue1=&GATA28_alleleValue0=&GATA28_alleleValue1=&GATA417_alleleValue0=&GATA417_alleleValue1=&GT211_alleleValue0=&GT211_alleleValue1=&GT23_alleleValue0=&GT23_alleleValue1=&GT575_alleleValue0=&GT575_alleleValue1=&SW13_alleleValue0=&SW13_alleleValue1=&SW19_alleleValue0=&SW19_alleleValue1=&rw4-10_alleleValue0=&rw4-10_alleleValue1=&rw410_alleleValue0=&rw410_alleleValue1=&rw48_alleleValue0=&rw48_alleleValue1=&alleleRelaxValue=0&individualID=PPBD-&resightGapOperator=greater&resightGap=&firstYearField=&organizationId=None&projectId=None&submitSearch=Search

If this is a bulk import report, send the spreadsheet to services@wildme.org with the email subject line matching your bug report

Hi @PaolaLacetera

This is a pair of bugs we will fix.

The CAPTURE bug is occurring because no start date and end date were set on the search. I can adjust the error message to be more informative, but using a Start Date and End Date on your Individual Search should avoid this individual error and is required. Please note this output format is only for the CAPTURE model, and there are other export formats on Individual Search that can be used for more models in Program Mark.

The SOCPROG bug is an individual naming bug I will look to fix.

I have filed ticket WB-1909 and will follow up here.

Thanks,
Jason

Hi @PaolaLacetera

These should be fixed. Please let me know if you see them fixed on your side.

Thanks,
Jason

Hi @jason

They are fixed, thank you. However, I still can’t download the CAPTURE file. I used 2012-01-01 and 2021-12-31 as start and end date respectively and it didn’t work. I also thought it might too long as time period, so I tried with a shorter one (from 2018-01-01 to 208-12-31). I tired both the date filter “At least one sighting within these dates” and “Encounter submission dates”. Even though I think it should work with the first one. Do you have any idea what is going on there? Did I do something wrong?

Regards,
Paola

Can you please send a link to this CAPTURE output?

Also, do you intend to run CAPTURE directly or via another system like Program MARK or RMark?

Thanks,
Jason

Hi @PaolaLacetera

Can I further help here? With a link to the new CAPTURE output I can further look at the issue.

Thanks,
Jason

Hi @jason,

sorry to bother again. I had to change and add some data and now I have to re-download the SOCPROG export file, but I encounter an issue again. Here’s the link Wildbook (flukebook.org) . It says:
" Error encountered with file writing. Check the relevant log.

Please let the webmaster know you encountered an error at: SOCPROGExport servlet".
Is there anything that can be done?

Kind regards,
Paola.

Hi @PaolaLacetera

Please give it a try again. I merged the ongoing fix for WB-1909, and I can now download the export again.

Thanks,
Jason

Hi @jason

It worked. Thank you very much!

Regards,
Paola.

1 Like