Inconsistency in JSON response
Posted: Wed Dec 07, 2016 12:20 pm
Dear OPS team,
while working the API in JSON response format, I encountered a problem, and maybe you could fix it somehow in a future API version:
I access the published-data/search/biblio endpoint and query publications related to certain applicant names.
If a publication has one ipcr class assigned, the response is like following:
The "classification_ipcr" attribute has a JSON object as value.
If a publication has more than one ipcr class assigned, the response is like following:
You see, the type for "classification_ipcr" is now an array of objects.
This is a problem for automated parsing with schemas in my code. I think this is very inconsistent, and that the first response should be an array with length 1.
Is this something you would be able to address in future versions?
Thanks,
Nisse
while working the API in JSON response format, I encountered a problem, and maybe you could fix it somehow in a future API version:
I access the published-data/search/biblio endpoint and query publications related to certain applicant names.
If a publication has one ipcr class assigned, the response is like following:
Code: Select all
"classifications_ipcr": {
"classification_ipcr": {
"x_sequence": "1",
"text": {
"$": "G05B C I"
}
}
}
If a publication has more than one ipcr class assigned, the response is like following:
Code: Select all
"classifications_ipcr": {
"classification_ipcr": [
{
"x_sequence": "1",
"text": {
"$": "F16D 13/ 64 A I"
}
},
{
"x_sequence": "2",
"text": {
"$": "F16D 13/ 72 A I"
}
}
]
}
This is a problem for automated parsing with schemas in my code. I think this is very inconsistent, and that the first response should be an array with length 1.
Is this something you would be able to address in future versions?
Thanks,
Nisse