1

Topic: Redetermination not working

We're running the verification 5 report on our own Indicia installation.  The redetermination option is not pulling in the species list.  Is there any instruction anywhere relating to what to look at in terms of fixing it?  Are they any obvious things to check?

Thanks

Dave

2

Re: Redetermination not working

Look for network traffic with your favourite browser tool while you type the new species name. Ensure requests are being sent. See what responses are coming back. Compare with a working system like iRecord.

Jim Bacon

3

Re: Redetermination not working

Hi Jim

Thanks for the tip.  Here's what we're seeing:

URL request:

http://www.natappdata.co.uk/indicia/ind … 2416577943

Results in response:
jQuery1820981551069766283_1442409674762({"error":"general_errors.unauthorised","code":1})
This differs from iRecord, which rather than requesting '?callback=jQuery...' is requesting 'callback=jsonp.....'

Both, as far as I'm aware are using the Verification 5 form, so I'm not sure how to configure this to work or why it's different?  Does this make any sense to you?

4

Re: Redetermination not working

If I put the url in code tags (and url decode to get rid of the %20 etc.) that will make the posting more readable.

http://www.natappdata.co.uk/indicia/index.php/services/data/cache_taxon_searchterm?
callback=jQuery1820981551069766283_1442409674762 &
q=avo &
limit=21 &
timestamp=1442416577943 &
orderby=searchterm_length, original, preferred_taxon &
mode=json &
qfield=searchterm &
auth_token=96a132414e292e8ee3587a00333f630bf9daaa13 &
nonce=b8387f15094231634a7e3201ae19ad94da7369b1 &
taxon_list_id=2 &
query={"where":["(simplified='t' or simplified is null)"]} &
_=1442416577943

The callback name is not important but might indicate different versions of jQuery in use which we may want to keep in mind.

However, a response of unauthorised says to me that there is an authentication problem. Either this website does not have permissions to taxon_list_id = 2 or the auth_token and nonce have expired in some way is my guess.

Jim Bacon.

5

Re: Redetermination not working

The outcome of an off-forum discussion was that
1. When checked again, the web service response was not unauthorised but empty because there were no matches.
2. There were no matches because the cache_taxon_searchterms table was not populated.
3. A rebuild of the cache table was prompted by deleting the populated-taxon_searchterms entry in the variables table.
It is now working correctly.

Jim Bacon.