Giters
PatentsView
/
PatentsView-API
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
13
Watchers:
21
Issues:
44
Forks:
4
PatentsView/PatentsView-API Issues
Internal server errors
Updated
4 years ago
Comments count
4
Patents Endpoint - text_all comparison operation is getting a "Query internal" error
Updated
4 years ago
API hangs when trying to return many fields
Updated
4 years ago
Comments count
4
wipo bulk file and wipo_field_id search
Updated
4 years ago
POSTing results in error
Closed
4 years ago
Comments count
2
Some redirects result in 404s
Updated
4 years ago
Comments count
4
500s thrown on some cpc_group_id's
Closed
4 years ago
Comments count
8
patent_id is missing from field list tables
Closed
5 years ago
Comments count
1
Corrupt patent.tsv.zip
Closed
5 years ago
Comments count
1
Odd query results
Closed
5 years ago
Comments count
2
Strange behavior when locations endpoint is asked for fields across several groups
Updated
5 years ago
Comments count
3
Patent citation data is missing
Closed
6 years ago
Comments count
13
API server down?
Closed
6 years ago
Comments count
9
Locations endpoint throwing 500 errors
Closed
6 years ago
Comments count
9
Queries on non-patent endpoints with 'match_subentities_only' = 'false' returning error
Updated
6 years ago
500 error on invalid field requests
Closed
6 years ago
Comments count
3
Swagger UI compatibility
Updated
6 years ago
API can't handle large field lists anymore?
Closed
6 years ago
Comments count
1
Locations endpoint is timing out
Closed
7 years ago
Comments count
1
Inventors endpoint not returning expected data
Closed
7 years ago
Comments count
1
Locations endpoint throws 400 error when cpc_sequence field is asked for
Closed
7 years ago
Comments count
1
patents endpoint not behaving as expected
Closed
7 years ago
Comments count
4
ensure consistency across the the different APIs (or categories)
Closed
7 years ago
keep use (non-use) of version number consistent
Closed
7 years ago
ensure there's useful response codes for POST queries
Closed
7 years ago
Consider deprecating XML and focus on JSON
Closed
7 years ago
Strongly consider interactive documentation
Closed
7 years ago
Comments count
1
lead off with a better welcome
Closed
7 years ago
Note that lack of scrolling for left sidebar might be a problem for smaller screens
Closed
7 years ago
ensure all example URLs are linked
Closed
7 years ago
it's better to have the full url (so that it can be copied and pasted) instead of only part
Closed
7 years ago
Comments count
1
clarify that API keys aren't required
Closed
7 years ago
Enable HTTPS
Closed
7 years ago
Build a client (or several)
Closed
7 years ago
Comments count
1
Provide some story-telling about why this data is useful
Closed
7 years ago
Consider more user-friendly, simple English language
Closed
7 years ago
Consider a more useful, usable alternative to the database schema
Closed
7 years ago
Comments count
1
Is the copyright notice necessary?
Closed
7 years ago
The json editor link is unnessesary
Closed
7 years ago
Comments count
1
Try to focus on popular use cases
Closed
7 years ago
Comments count
1
Continue to work on ways to grapple with so much content
Closed
7 years ago
pct_data fields not served in format consistent with other fields
Closed
7 years ago
Comments count
1
Raw assignee and location date
Closed
7 years ago
Comments count
1
Problem with include_subentity_total_counts option
Closed
7 years ago
Comments count
8