Project COUNTER's Registry contains information about vendors/platforms/providers that are compliant with the Code of Practice Release 5 standard for online resource (ebooks, ejournals, etc.) usage.
The Registry includes information about the platform/provider including contact information, what COP5 (or COP4) reports they support, and all of the specifics regarding how they support COP5 SUSHI API requests for usage reports, basically everything except an institution's own required credentials (customer_id plus optionally requestor_id and api_key) and other constraints on using their SUSHI API server (eg if they also require the request to come from the customer's IP range, if they have volume or speed limits on server requests, etc.)
March 2022 Note: the Registry is still a work in progress, and only some vendors have finished populating their own entry with all of the needed data. If you have more direct and relatively recent SUSHI information already from a vendor, that may be more accurate than what you get from this.
This simply python program, which runs from the command line and has no user prompts, produces two output files in the same folder that the code is run from:
- a tab-delimited table of all of the known registry entries that have a COP5 "sushi service" registered called "registry-entries.tsv"
- a log file listing all of the registry entries that exist but don't have a COP5 sushi service registered yet called 'log-registry-entries.txt'
https://registry.projectcounter.org/
https://registry.projectcounter.org/api/v1/
API returns JSON.
https://registry.projectcounter.org/api/v1/platform/
https://registry.projectcounter.org/api/v1/platform/60d34416-9666-4b09-8d58-220ffc04901e/
https://www.projectcounter.org/counter-sushi/
See also my project providing a COUNTER harvesting tool (also python, with GtK) for a GUI interface to collect a library's usage data into an sqlite3 database, with friendly search tools. https://github.com/CS-4820-Library-Project/COUNTER-5-Report-Tool That project requires the vendor configuration info found in the Registry, along with the library's unique credentials (customer_id, requestor_id, api_key). The Registry provides for each vendor/platform/provider information about who to contact or where to look for those credentials.