WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

Training Request Forms #18

@samozzy

Description

@samozzy

The Training Site currently records training given, not competence, even though these two are linked. Zoe has suggested an architectural revamp to honour this further.

1) Training Requests

Users are able to request training (/training/request/new) using a form not dissimilar to /training/new. This will then generate a list of requested sessions at /training/request which can then be actioned and organised.
Training requests will be able to be marked as completed via a button which transfers them into a training session.

The below is nonsense but kept for context.

## 2) Training Given Training sessions become the first step in a process. Once a training session has been given, trainees' records are then updated in amber (rather than the current green) to reflect this.

3) Competence Agreed (or a good name)

Users are then invited (via email?) to reflect on this training session and their confidence in performing these skills. If they feel confident they can complete the training item; otherwise, they can request further training/practice in this skill. This can be selected on an item-by-item basis.
Competence Agreed: Users then receive a green training item on their record, indicating their competence in this skill.
Competence not agreed: Users retain the amber item, and a new training request is created for those skills that want some more work.

Decision needed: Competence agreed can only be completed by the trainee, and not by the trainer.

Note: Competence can be revoked by adding a training session more recently than competence agreed.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions