The objective of notice management is to reduce the number of interactions (‘clicks’ and other ‘interruptions’) users face in order to achieve their actual desired objectives, both on first use and on subsequent use of the same services in a similar workflow. As proposed in AARC-G083, Guidance for Notice Management by Proxies, notice presenters (proxies, communities, and service and data providers) should provide machine-readable identifiers and associated registry meta-data for the notices they can present to users.
This feature needs technical support in the collaboration platform, and in most cases the platform operator will provide this as part of the AAI platform service. Only for collaborations implementing their own AAI service, the feature should be added explicitly.
The collaboration platform is the consolidated entry point for all access to resources, usually across multiple infrastructures and services. Hence the collaboration layer is the most appropriate place to present this, and forestall interstitial notice screens for each infrastructure and service.
When a common notice can be constructed for all services and infrastructures that are supporting a collaboration, the collaboration can present that common notice once also without a technical notice presentation component.