4 results found
Extending the Bookmarking API to recognise Chapter Author.
Currently the Bookmarking API does not recognise Chapter Author, so that any author included in the API is considered to be the Book Author.
It would be useful if a Chapter author could be included which would appear in the Chapter part of the record and therefore also be displayed on the full list.7 votes
this idea remains under review as we are about to start investigating and prioritising API use cases
Two extensions to the ISBN look-up API would significantly extend its utility -
- For each matching list return the numeric value of the priority status of the item (1, 2, 3)
-- It would be very useful to be able to display importance alongside occurence
- Support 'OR' requests (allowing multiple ISBNs to be added to a single call)
-- With a JSON [or other] string for each ISBN match3 votes
As part of integration theme
We would like to be able to directly access reports and other authenticated data from scripts without the need to web-scrape through the login process protecting them.
It would be good if the existing APIs implemented an API-key style scheme, e.g. accepting a header "Authorization: api_key <customer-api-key>" with each request.2 votes
It would be nice to add two new columns to the CSV output for the linked data API. These two new columns would contain information about the section the item is in and the parent section. This information would be enough to construct the section information from the CSV call and help to surface content in other systems (the VLE for example).2 votes
Will be looked at as part of integration theme this year
- Don't see your idea?