You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a parameter I can send that will leave out the "coci => " prefix in the response fields? It makes it trickier to parse the results and I don't trust that my regular expressions won't be fragile to some case I haven't anticipated.
The text was updated successfully, but these errors were encountered:
Actually, in the "index" API, the prefixes are crucial in order to understand where such a piece of information is actually coming from. For instance, it would be possible that a citation between two papers is actually included in two distinct indexes. In that case, you need to actually know from where they are coming from.
Currently, you can think of using a specific solution for at least ask the API to separate such prefixes, by means of the "json" parameter (it works only if JSON is the return format).
As you can see, the result in the fields "citing" and "cited" will be structured so as to make everything easily accessible via JSON.
I'm planning to extend the tool behind the API so as to make also more custom parameters, that in principle would allow one removing something from all the fields, though. Thus, thanks for the input!
Is there a parameter I can send that will leave out the "coci => " prefix in the response fields? It makes it trickier to parse the results and I don't trust that my regular expressions won't be fragile to some case I haven't anticipated.
The text was updated successfully, but these errors were encountered: