Use cases look at by the wallet sub-task
- eduID (AcademicID) credential
For reference a link to the use case list of GN5-1/WP5/T7
See EUDIW user research conducted by the EU Commission between 4 December 2024 and 6 January 2025 (page 17 "Students"), published in January 2026. The use cases were assessed by students, most use cases are not linked to R&E.
| Use cases (UC) & Use case Scenarios | Generic view (Description..) | User Journeys | UX, Usability & Accessibility |
UC1 |
Studying (life cycles) |
|
| |
UCScenario 1.1 | Study place application | |||
UCScenario 1.2 | Enrolment | |||
UCScenario 1.3 | PHD students (candidates) | |||
UCScenario 1.4 | Guest students | |||
UCScenario 1.5 | Diploma credentials | A secure, tamper-proof, long-living digital version of a university degree that preferably follows open standards and is widely recognised | ||
UCScenario 1.6 | Micro credentials | Smaller units than Diploma credentials, e.g. for individual courses, within or outside of a learning path leading to a diploma. Long-lived credential | ||
UCScenario 1.7 | Student ID | Proving student status at a specific moment, e.g. in the context of student discounts in on-line and off-line settings | ||
UCScenario 1.8 | Nano credentials | Smaller units than Micro credentials, e.g. for individual assignments, potentially short-lived | ||
UCScenario 1.9 | Alliance use case | Short-lived credentials to make alliance-specific decisions flow user-driven between alliance partners without back-end integration. Likely only relevant within one Alliance and governed by that Alliance. | ||
UCScenario 1.10 | Student mobility | engage in student/academic mobility, mobility support services, housing, guest universities, get courses taken elsewhere being recognised and accounted for | ||
UC2 |
Teaching
|
|
| |
UCScenario 2.1 | Use of learning management systems | |||
UCScenario 2.2 | Temporary accounts for employees from other institutions | |||
UCScenario 2.3 | Cross-university continuous education | |||
UCScenario 2.4 | Access to teaching training | |||
UC3 |
Research
| Wallet-based credentials can support research use cases by enabling portable and verifiable representation of user attributes such as institutional affiliation, collaboration membership, roles, and training. These credentials can be issued by trusted organisations (e.g. home institutions or research infrastructures) and reused across services and infrastructures, enabling more consistent access control. In this context, AAI components (e.g. AARC-compliant proxies such as Collaboration Management services - see AARC-G080) may act as verifiers of such credentials and translate them into authorisation decisions for downstream services. In some scenarios, services may also directly verify and consume such credentials |
|
|
UCScenario 3.1 | Access to publication servers | |||
UCScenario 3.2 | Research data management and linking of identities and publications | |||
UCScenario 3.3 | Connection to other identifiers / IDs | |||
UCScenario 3.4 | Collaborative creation of documents | |||
UCScenario 3.5 | Mobility of Researchers | |||
UCScenario 3.6 | Access to Services from national libraries / information centres | |||
UCScenario 3.7 | Access to central resources (i. e. cloud services) | Access decisions may rely on verifiable credentials representing institutional affiliation, as well as Virtual Organisation (VO) or research collaboration membership and role entitlements. Such credentials can be reused across research infrastructures and evaluated to enforce access control. | ||
UCScenario 3.8 | Management of virtual organisations | Membership and roles within Virtual Organisations (VOs) or research collaborations may be represented as verifiable credentials issued by Collaboration Management services. These credentials can be presented by users and reused across research infrastructures to support consistent authorisation decisions. | ||
UCScenario 3.9 | Apply for a research job | |||
UC4 |
Administration (managing studying cycles, research and teaching)
|
|
| |
UCScenario 4.1 | Recruitment | |||
UCScenario 4.2 | Organisational representation | present organisational representation powers to interested parties with sector-specific contents (e.g. entitlements towards EWP) |