500 at dev server

[schloett]

when providing type information, the dev server responds with a 500 (see attached files). The error was initially reported in EEXCESS/eexcess#28

q1.txt
r1.txt

[hziak]

Actually according to http://jsonlint.com/ it looks like your json is not valid.
{
"contextKeywords": [{
"text": "women",
"type": "Misc", <--- that comma is the problem
}]
}

[schloett]

sry, my bad. But same problem without comma.

[hziak]

just seen that yes ... the problem is that we have no "misc" value for that parameter
so valid parameter are
WHO WHERE WHAT .... is there misc as valid parameter in the documentation?

(they are in uppercase ;)

[hziak]

ok ... just found it ... in the example is misc as valid value
The question is if we should change it in the documentation or change it in the code.
Who, where, and what are useful since they are part of the query of the partners supporting that.
But i doubt that misc will be a valid filter query parameter on any partner soon.

[schloett]

the question would be the other way round - were are WHO WHERE WHAT in the documentation? ;)
(https://github.com/EEXCESS/eexcess/wiki/Request-and-Response-format#query-format)
As far as I know, the possible types for the deployed version on the stable server are "Person","Location","Organization","Misc"

[hziak]

It might be that this is an feature that’s undocumented yet since we wanted to have the filter queries in place until the review. ;)
The stable server hasn't that feature yet. (Type was not of any use before)
I would suggest to leave the ticket open as reminder to update the documentation.

[hziak]

should be resolved
Types are again: "Person","Location","Organization","Misc"
open for testing