Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -4,8 +4,8 @@

.. _reserved-elements:

Reserved Elements and Values Available for Extending Reports
------------------------------------------------------------
Reserved Elements Available for Extending Reports
-------------------------------------------------

COUNTER recognizes that there are some common extensions that report providers might want to include in COUNTER Reports or when creating custom reports; therefore the following element names and values have been reserved for this common use:

Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,64 @@
.. The COUNTER Code of Practice © 2017-2024 by COUNTER Metrics
is licensed under CC BY 4.0. To view a copy of this license,
visit https://creativecommons.org/licenses/by/4.0/

.. _reserved-values:

Reserved Values Available for Extending Reports
-------------------------------------------------

COUNTER's `Best Practice on Generative and Agentic AI Usage <https://www.countermetrics.org/code-of-practice/best-practice/bp-ai/>`_ created a new Access_Method and new Metric_Types specifically for reporting AI usage. These values are OPTIONAL extensions for inclusion in COUNTER Reports only when called for.


.. only:: latex

.. tabularcolumns:: |>{\raggedright\arraybackslash}\Y{0.17}|>{\raggedright\arraybackslash}\Y{0.26}|>{\parskip=\tparskip}\Y{0.46}|>{\raggedright\arraybackslash}\Y{0.11}|

.. list-table::
:class: longtable
:widths: 15 22 51 12
:header-rows: 1

* - Element Name
- Value
- Description
- Reports

* - Access_Method
- Agent
- Content and metadata accessed by an AI system.
- PR, DR, TR, IR

* - Metric_Type
- AI_Responses_Generated
Comment thread
berndoberknapp marked this conversation as resolved.
- A response delivered by an AI system in response to a user prompt. The response is likely to be text, but may include images or other multimedia. Each response MUST only be counted once regardless of the number of queries initiated by the AI system. Subsequent prompts within the same user session MUST be counted as a new AI_Responses_Generated.
- PR

* - Metric_Type
- Total_AI_Investigations
- Total number of times within a user session that a chunk from an Item or information related to an Item was included by an AI system in generating a response to a user prompt.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I still find the "with a user session" for the Total metrics and the Search metric confusing, since the session is only relevant for Unique metrics. The double click filtering does apply, but that information is missing.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changing this will require going back to the AI working group. Since they are working on phase two of the project now, my recommendation is to hold this PR for a subsequent R5.1.2.

- PR, DR, TR, IR


* - Metric_Type
- Unique_AI_Investigations
- Unique count of times within a user session that a chunk from an Item or information related to an Item was included by an AI system in generating a response to a user prompt.
- PR, DR, TR, IR


* - Metric_Type
- Total_AI_Requests
- Total number of times within a user session that a chunk from an Item was requested (i.e. the full text or content was accessible to the AI system) in generating a response to a user prompt, during a user session.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"accessible to" or "accessed by"? Same question for Unique_AI_Requests.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changing this will require going back to the AI working group. Since they are working on phase two of the project now, my recommendation is to hold this PR for a subsequent R5.1.2.

- PR, DR, TR, IR


* - Metric_Type
- Unique_AI_Requests
- Unique count of times within a user session that a chunk from an Item was requested (i.e. the full text or content was accessible to the AI system) in generating a response to a user prompt.
- PR, DR, TR, IR



Access_Method Agent is an OPTIONAL extension. Where report providers make Access_Method Agent available, it MUST only be included in COUNTER Reports. Where report providers make Access_Method Agent available, it MUST only be included in COUNTER Reports when called for by report consumers. Where Access_Method Agent is included in COUNTER Reports, it MUST be reported against AI Metric_Types.

The new AI Metric_Types are all OPTIONAL extensions. Where report providers make these AI Metric_Types available, they MUST only be included in COUNTER Reports. Where report providers make these AI Metric_Types available, they MUST only be included in COUNTER Reports when called for by report consumers. Where AI Metric_Types are included in COUNTER Reports, they MUST be reported against Access_Method Agent.
5 changes: 3 additions & 2 deletions source/11-extending/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -16,5 +16,6 @@ COUNTER recognises that some report providers may want to provide customized ver
02-creating-customized-counter-reports
03-creating-new-elements-columns-headings
04-creating-new-values-for-enumerated-elements-and-attributes
05-reserved-values-available-for-extending-reports
06-restrictions-in-using-customized-elements-and-values
05-reserved-elements-available-for-extending-reports
06-reserved-values-available-for-extending-reports
07-restrictions-in-using-customized-elements-and-values