This consultation is open from 4 March 2021 15:00 CET to 5 April 2021 17:00 CET.
The REFEDS Schema Editorial Board's subcommittee, the eduPerson Analytics Code subcommittee, has proposed a new attribute to be added to the eduPerson schema that would provide a way for an institution to send through a set of reporting codes as part of the authentication transaction, which SP will then use to create segmented usage reports. The primary use case captures the need of a publisher/library scenario where data is needed to understand the use of a given resource and be able to classify that resource into buckets (such as internal billing codes). This happens outside the authentication/authorization transaction and so is not itself an entitlement.
This consultation is open from: 4 March 2021 15:00 CET to 5 April 2021 17:00 CET.
Participants are invited:
- to consider the proposed new attribute for the eduPerson schema; and
- to propose appropriate changes / challenges to the proposed document.
The specification is available as a Google doc in Comment mode or as a PDF. Background on the eduPerson Analytics Code Subcommittee is available in the REFEDS Schema Editorial Board wiki space. All comments should be made on: email@example.com or added to the change log below. Comments posted to other channels will not be included in the consultation review.
Following the consultation all comments will be taken back to the REFEDS Schema Editorial Board subcommittee for review and if appropriate the document will then be forwarded to the REFEDS Steering Committee for sign-off and publication on the REFEDS website as per the REFEDS participants agreement.
|comment #||Line/Reference #||Proposed Change or Query||Proposer / Affiliation||Action / Decision (please leave blank)|
|1||n/a||I don’t like the attribute name - eduPersonAnalyticsID - its the ID part that worries me, its not an ‘Identity’ per se. I can foresee confusion and people sending almost or real PII in that ID value…. eduPersonAnalyticsTag or eduPersonAnalyticsValue ?||Alan Buxey|
|2||"represents the use of a service by a subject"||The spec seems to allow for use as a targeted, privacy preserving identifier. I don't have a strong opinion regarding the name, but as worded I think this attribute could be used to represent an identity. If this is not the intent then use of the term 'subject' may need to be clarified.||Mark Jones / UTHealth|