Create Manage Personnel Page for the Department Portal
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 35/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Tranquilla
- Stack tecnologico
- python
- Ambito
- databases, full-stack
Direzione di ricerca
Start by reviewing the existing database models and the requirements in this issue, then check Issue #606 for the personnel-search dependency. Determine how personnel, supervisor eligibility, bans, inactive status, coordinator designation, and removal rules are represented before implementing the Manage Personnel page. Done means the page supports the listed table, search, status, designation, pagination, and removal behaviors with an appropriate data model.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Description:
Departments need a centralized page for managing personnel within their department. The page should allow Labor Coordinators, Labor Office administrators and Supervisors to manage department personnel, review supervisor information, designate coordinators, and review supervisor status.
As part of this implementation, the underlying database models should be reviewed and updated to properly support supervisor eligibility, inactive supervisors, Labor Coordinators, and supervisor bans. The current data model should be evaluated before implementation to determine whether additional tables or fields are required.
Requirements:
Create a Manage Personnel page.
Display a table containing department personnel.
Include:
-Supervisor name (email icon attached and if they are banned a ban status for supervisors.) ( This could have arrows to do ascend and descend arrangement)
-Total Primary supervisees
-Total Secondary supervisees
-Labor Coordinator designation (checkmark to allow multiple designation or none)
-Supervisor status (status should be active on top)
Removing Members - Inactive vs deleted
-Members that have been added and have not supervised students can be removed from a department permanently by Labor Coordinator, or marked as inactive by Labor
-Members that have supervised students cannot be deleted, but can be marked as Inactive by Labor Coordinator or Labor Admin
-Marking someone inactive should require a justification
A limit for the table (5 entries per page).
Allow searching personnel as a way to add Supervisor ( functionality implemented by Issue #606 )
Support Labor Coordinator designation (anyone access can do it as assigning a labor coordinator can be done by internal department discussion on by labor admin)
Review existing database models before implementation.
Determine an appropriate database design for supervisor bans and inactive supervisors.
Notes:
This issue intentionally includes database investigation before implementation.
Supervisor ban functionality is dependent upon this issue.
- Lingua principale
- Python
- Stelle
- 1
- Fork
- 1
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
Non abbiamo ancora controllato i file di configurazione di questo progetto. Parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di BCStudentSoftwareDevTeam/lsf
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
BCStudentSoftwareDevTeam/lsf#659 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
BCStudentSoftwareDevTeam/lsf#572 ·
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
BCStudentSoftwareDevTeam/lsf#675 ·
-
draft on hold
Difficoltà 3/5 1-2 giorni Idoneità per principianti 55/100
BCStudentSoftwareDevTeam/lsf#674 ·
-
Position Description should be reviewed by LaborForse già presa @nahom70 l’ha presa 14 giorni fa. Aperta
Difficoltà 4/5 3-5 giorni Idoneità per principianti 50/100
BCStudentSoftwareDevTeam/lsf#673 · 1 assegnatario ·
Tutte le issue di BCStudentSoftwareDevTeam/lsf
Issue simili
-
[Bug] @deck.gl/arcgis dist import resolves to unpublished @deck.gl/core source path (9.3.11, 9.4.0)Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno
-
workflow: a tick's dispatch counts as 'only this step', and no review self-grants a round unattendedApertaworkflow
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
kristofdegrave/homeassistant-smart-charging#1505 ·
I maintainer di solito rispondono entro 1 giorno
-
New Submission: TropWATERApertametadata submission
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
canonical/content-cache-operator#163 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
[submission]Apertasubmission
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 65/100
leanprover/lean-eval-submissions#1852 ·
I maintainer di solito rispondono entro 1 giorno