Networks API call requires attributes in lower case
In my attempts to get the /networks API call to work, I have finally figured it out: I must switch my entity names to lower case before sending them. This took me off guard because the /connections and /analogies API call works regardless of case.
I suggest consistency across the various API calls. Either be case insensitive or case sensitive. (Or when deviating, please document it.)
I also observed that /networks API does not tolerate the "_" as a replacement for the space character. If a space character is in the attribute name, it must be present when calling /networks.
Support Staff 2 Posted by Jim Fleming on 05 Nov, 2010 11:13 PM
Thanks Anthony for your feedback. I will open a ticket to take case of this.
/Jim
3 Posted by Jared Peterson on 20 Jan, 2011 04:42 PM
Ok, after looking into this I don't think we want to change this. Forcing lowercase of values is dangerous. The reason it works on the /connections call is because it passes through AQL which allows "looser" matching. On this call you're more explicitly targeting a memory.
We should just document this difference.
Jared Peterson closed this discussion on 20 Jan, 2011 04:42 PM.
Anthony Edwards re-opened this discussion on 20 Jan, 2011 06:00 PM
4 Posted by Anthony Edwards on 20 Jan, 2011 06:00 PM
The documentation for /networks says it takes a "q" parameter. Is that correct? If it does, then what can the value of "q" be if it is not AQL?
5 Posted by Jared Peterson on 20 Jan, 2011 06:20 PM
Anthony,
It does take a "q" parameter, which is AQL. That AQL will be handled exactly the same as /connections (I believe). I think where you're getting into case sensitivity issues is on the "da" and "sa" parameters.
Jared