Sashimi2 - Fake SUSHI Provider

This is a fake COUNTER API/SUSHI provider and COUNTER 5.0 / 5.1 report generator. This server generates random usage data for testing purposes. All usage numbers are randomly generated and should not be used for any real analysis or decision-making.

Table of Contents

• About This Server
• Platform Name Usage Types
• Query Parameters
• Available Reports
  • COUNTER Release 5.1
    • Item Reports (IR)
    • Title Reports (TR)
    • Database Reports (DR)
    • Platform Reports (PR)
  • COUNTER Release 5.0
    • Item Reports (IR)
    • Title Reports (TR)
    • Database Reports (DR)
    • Platform Reports (PR)
• Non-Data Endpoints
  • Server Status
  • Member List
  • Report List

About This Server

This is a test server that generates fake COUNTER reports. The data is:

• Randomly generated - All usage numbers are synthetic
• Deterministic - Same input parameters always produce the same output
• For testing only - Do not use for production or real analysis

Platform Name Usage Types

The platform name controls which types of usage data are generated:

• 'm' in platform name → include multimedia usage
• 'd' in platform name → include database usage
• 't' in platform name → include title-based usage (journals, books, articles)

You can combine letters (e.g., platform=mdt for all types). If no letters are specified, it defaults to title-based usage.

Query Parameters

Data Report Endpoints

All data report endpoints require:

• customer_id - Customer identifier
• begin_date - Start date (YYYY-MM or YYYY-MM-DD)
• end_date - End date (YYYY-MM or YYYY-MM-DD)

Optional parameters:

• platform - Platform name (controls usage types via m/d/t letters)
• requestor_id - Requestor identifier
• api_key - May be used to configure the data generation. Currently supported keys are: platform:PlatformName;scale:100 which override the platform name and control how much data is generated, respectively

Non-Data Endpoints

Non-data endpoints have different parameter requirements:

• Status (/status) - No required parameters. Optional: platform
• Members (/members) - Required: customer_id. Optional: requestor_id, api_key, platform
• Reports (/reports) - Required: customer_id. Optional: requestor_id, api_key, platform

Available Reports

COUNTER Release 5.1

Item Reports (IR)

Item Report (IR)

• Full item-level usage report
• Example: /r51/reports/ir?customer_id=test123&begin_date=2025-01&end_date=2025-01&platform=mdt

Journal Article Requests (IR_A1)

• Journal article requests only

• Example: /r51/reports/ir_a1?customer_id=test123&begin_date=2025-01&end_date=2025-01&platform=mdt

Multimedia Item Requests (IR_M1)

• Multimedia item requests
• Example: /r51/reports/ir_m1?customer_id=test123&begin_date=2025-01&end_date=2025-01&platform=mdt

Title Reports (TR)

Title Report (TR)

• Full title-level usage report
• Example: /r51/reports/tr?customer_id=test123&begin_date=2025-01&end_date=2025-01&platform=mdt

Book Requests - Controlled (TR_B1)

• Controlled book requests
• Example: /r51/reports/tr_b1?customer_id=test123&begin_date=2025-01&end_date=2025-01&platform=mdt

Book Access Denied (TR_B2)

• Book access denied events
• Example: /r51/reports/tr_b2?customer_id=test123&begin_date=2025-01&end_date=2025-01&platform=mdt

Book Usage by Access Type (TR_B3)

• Book usage broken down by access type
• Example: /r51/reports/tr_b3?customer_id=test123&begin_date=2025-01&end_date=2025-01&platform=mdt

Journal Requests - Controlled (TR_J1)

• Controlled journal requests
• Example: /r51/reports/tr_j1?customer_id=test123&begin_date=2025-01&end_date=2025-01&platform=mdt

Journal Access Denied (TR_J2)

• Journal access denied events
• Example: /r51/reports/tr_j2?customer_id=test123&begin_date=2025-01&end_date=2025-01&platform=mdt

Journal Usage by Access Type (TR_J3)

• Journal usage broken down by access type
• Example: /r51/reports/tr_j3?customer_id=test123&begin_date=2025-01&end_date=2025-01&platform=mdt

Journal Requests by YOP (TR_J4)

• Journal requests by year of publication
• Example: /r51/reports/tr_j4?customer_id=test123&begin_date=2025-01&end_date=2025-01&platform=mdt

Database Reports (DR)

Database Master Report (DR)

• Full database usage report
• Example: /r51/reports/dr?customer_id=test123&begin_date=2025-01&end_date=2025-01&platform=mdt

Database Search and Item Usage (DR_D1)

• Database searches and item-level usage
• Example: /r51/reports/dr_d1?customer_id=test123&begin_date=2025-01&end_date=2025-01&platform=mdt

Database Access Denied (DR_D2)

• Database access denied events
• Example: /r51/reports/dr_d2?customer_id=test123&begin_date=2025-01&end_date=2025-01&platform=mdt

Platform Reports (PR)

Platform Report (PR)

• Full platform usage report
• Example: /r51/reports/pr?customer_id=test123&begin_date=2025-01&end_date=2025-01&platform=mdt

Platform Usage (PR_P1)

• Platform usage standard view

• Example: /r51/reports/pr_p1?customer_id=test123&begin_date=2025-01&end_date=2025-01&platform=mdt

COUNTER Release 5.0

Item Reports (IR)

Item Master Report (IR)

• Full item-level usage report
• Example: /r50/reports/ir?customer_id=test123&begin_date=2025-01&end_date=2025-01&platform=mdt

Journal Article Requests (IR_A1)

• Journal article requests only
• Example: /r50/reports/ir_a1?customer_id=test123&begin_date=2025-01&end_date=2025-01&platform=mdt

Multimedia Item Requests (IR_M1)

• Multimedia item requests
• Example: /r50/reports/ir_m1?customer_id=test123&begin_date=2025-01&end_date=2025-01&platform=mdt

Title Reports (TR)

Title Master Report (TR)

• Full title-level usage report
• Example: /r50/reports/tr?customer_id=test123&begin_date=2025-01&end_date=2025-01&platform=mdt

Book Requests - Controlled (TR_B1)

• Controlled book requests
• Example: /r50/reports/tr_b1?customer_id=test123&begin_date=2025-01&end_date=2025-01&platform=mdt

Book Access Denied (TR_B2)

• Book access denied events
• Example: /r50/reports/tr_b2?customer_id=test123&begin_date=2025-01&end_date=2025-01&platform=mdt

Book Usage by Access Type (TR_B3)

• Book usage broken down by access type
• Example: /r50/reports/tr_b3?customer_id=test123&begin_date=2025-01&end_date=2025-01&platform=mdt

Journal Requests - Controlled (TR_J1)

• Controlled journal requests
• Example: /r50/reports/tr_j1?customer_id=test123&begin_date=2025-01&end_date=2025-01&platform=mdt

Journal Access Denied (TR_J2)

• Journal access denied events
• Example: /r50/reports/tr_j2?customer_id=test123&begin_date=2025-01&end_date=2025-01&platform=mdt

Journal Usage by Access Type (TR_J3)

• Journal usage broken down by access type
• Example: /r50/reports/tr_j3?customer_id=test123&begin_date=2025-01&end_date=2025-01&platform=mdt

Journal Requests by YOP (TR_J4)

• Journal requests by year of publication
• Example: /r50/reports/tr_j4?customer_id=test123&begin_date=2025-01&end_date=2025-01&platform=mdt

Database Reports (DR)

Database Master Report (DR)

• Full database usage report
• Example: /r50/reports/dr?customer_id=test123&begin_date=2025-01&end_date=2025-01&platform=mdt

Database Search and Item Usage (DR_D1)

• Database searches and item-level usage
• Example: /r50/reports/dr_d1?customer_id=test123&begin_date=2025-01&end_date=2025-01&platform=mdt

Database Access Denied (DR_D2)

• Database access denied events
• Example: /r50/reports/dr_d2?customer_id=test123&begin_date=2025-01&end_date=2025-01&platform=mdt

Platform Reports (PR)

Platform Report (PR)

• Full platform usage report
• Example: /r50/reports/pr?customer_id=test123&begin_date=2025-01&end_date=2025-01&platform=mdt

Platform Usage (PR_P1)

• Platform usage standard view
• Example: /r50/reports/pr_p1?customer_id=test123&begin_date=2025-01&end_date=2025-01&platform=mdt

Non-Data Endpoints

These endpoints provide service information and do not require date parameters.

Server Status

Returns the current status of the reporting service. This endpoint is public and does not require authentication.

• R5.1: /r51/status
• R5.0: /r50/status or /status

Example: /r51/status

Member List

Returns the institutions associated with the customer ID. For this implementation, returns a single member derived from the customer_id.

Required parameters:

• customer_id - Customer identifier

Optional parameters:

• requestor_id - Requestor identifier
• api_key - API key for configuration

• platform - Platform name

• R5.1: /r51/members?customer_id=test123

• R5.0: /r50/members?customer_id=test123 or /members?customer_id=test123

Example: /r51/members?customer_id=test123

Note: R5.0 uses Name field instead of Institution_Name in the response.

Report List

Returns the list of reports supported by the COUNTER API server for the customer. The available reports are dynamically determined based on the platform name letters (m, d, t):

• 'm' in platform name → include multimedia reports (IR, IR_M1)
• 'd' in platform name → include database reports (DR, DR_D1, DR_D2)
• 't' in platform name → include title/item reports (IR, IR_A1, TR, TR_B1, TR_B2, TR_B3, TR_J1, TR_J2, TR_J3, TR_J4)
• PR reports (PR, PR_P1) are always included

If no letters are specified, it defaults to title-based usage.

Required parameters:

• customer_id - Customer identifier

Optional parameters:

• requestor_id - Requestor identifier
• api_key - API key for configuration

• platform - Platform name (controls which reports are listed via m/d/t letters)

• R5.1: /r51/reports?customer_id=test123&platform=mdt

• R5.0: /r50/reports?customer_id=test123&platform=mdt or /reports?customer_id=test123&platform=mdt

Examples:

• All reports: /r51/reports?customer_id=test123&platform=mdt
• Multimedia only: /r51/reports?customer_id=test123&platform=m
• Database only: /r51/reports?customer_id=test123&platform=d
• Title/item only: /r51/reports?customer_id=test123&platform=t

Note: R5.0 reports use "Master Report" suffix in names (e.g., "Platform Master Report" instead of "Platform Report") and do not include First_Month_Available and Last_Month_Available fields.