Closed labradford closed 1 year ago
<institution_name???>
Mandatory
<resource_type>
only if Called for
Regular
or TDM
<resource_type>
<institution_name???>
Mandatory
<resource_type>
<resource_type>
Sample JSON for platform report is located here: https://countermetrics.stoplight.io/docs/counter-sushi-api/e98e9f5cab5ed-pr-platform-report
Sample JSON for the platform usage report is located here: https://countermetrics.stoplight.io/docs/counter-sushi-api/82bd896d1dd60-pr-p1-platform-usage
Platform => not sure what this would be, maybe tenant?
I would lean toward interpreting the Platform as the Hyku tenant.
Another viable interpretation would see the Platform report available at the consortial level, and the Platform is H4C itself. Compare, for example, EBSCO as a platform hosting multiple databases, journals, etc. I think this interpretation breaks down for H4C in that tenants would presumably want their usage metric aggregated to the tenancy, as opposed to the consortia at large.
What host type would you be / which counter reports do you need?
Investigation vs. Request: If the PDF is viewable on the page, should any time the page loads it count as an Investigation or a Request?
Will you have any access restrictions? (do we need to record no_license or limit_exceeded? )
For searches, will you only have one database? (ie, will we need to support searches on shared search, and in different tenants differently for the counts?)
How would the Data_type attribute be determined on a work? (resource_type?)
How would sections be determined? Would it be based off of a metadata field? Off of relationships? What would this look like?
What access types will you have? How would we determine what was what?
questions: how often/when would reports be generated?
Next step is to investigate the JSON structure #622
Story
Create a list of all items that should be included in the Platform report and understand how the items align with Hyku
Acceptance Criteria
Testing Instructions
Not end user testable
Notes
There are two Platform Reports: the Platform Report and the Platform Usage Report