Name change (etc) in the LMS and grade passback
Los mantenedores suelen responder en 4 días
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 12/100
- Tipo de issue
- Error
- Claridad
- Necesita aclaración
- Estado de actividad
- Estancado
- Stack tecnológico
- perl
- Área
- authentication, backend
Línea de trabajo
The issue concerns the lms_source_did field on WeBWorK users and how grade passback at the mass update treats two users sharing one value. Start by finding where lms_source_did is set during LTI login and where grades are sent back to the LMS. The issue does not say what the fix should be: it asks whether a better solution exists, and the thread has had no answer for about 660 days. Done would require a maintainer decision on merging or deduplicating users first.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Suppose a student user in the LMS had email [email protected] and email prefix is being used for WeBWorK user IDs via LTI. It's halfway through the term and the student has completed some work in WeBWorK. User foo has lms_source_did set to whatever the LMS's ID is for that user.
Then the student has a name change or something that leads to their email now being [email protected]. Now the WW course has two users, foo and bar, each with the same lms_source_did. The student enters WW as bar now and cannot see their progress from when they were foo. In the past we've discussed merging two users but it's hard to work out how some of the details would be handled, and I am not asking about merging two users for now.
Instead, the immediate issue is that foo and bar have the same lms_source_did. So when grade passback happens at the mass update, maybe bar's scores are sent to the LMS, but then foo's scores are also sent and they overwrite whatever recent scores bar has earned. Or it could be the other way around. To the student in the LMS, they end up seeing either scores from foo or from bar, and zeros (or non-initialized scores) for half the assignments.
Manually, I think what I need to do (since this is happening with a student right now) is to copy foo's scores over to bar within WeBWorK. Then remove foo's lms_source_did directly using sql. And if the student has some reason they should access user foo to see their old work, give them password access. Is there a better solution to this?
- Lenguaje dominante
- Perl
- Estrellas
- 164
- Forks
- 167
- Merge medio
- 6 d 7 h
- PR fusionados (30 d)
- 27
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Sin plantilla de pull request
- Sin guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de openwebwork/webwork2
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
openwebwork/webwork2#3295 ·
Los mantenedores suelen responder en 4 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
openwebwork/webwork2#3290 ·
Los mantenedores suelen responder en 4 días
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 62/100
openwebwork/webwork2#2997 ·
Los mantenedores suelen responder en 4 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 56/100
openwebwork/webwork2#3276 ·
Los mantenedores suelen responder en 4 días
-
Dificultad 4/5 3-5 días Aptitud para principiantes 52/100
openwebwork/webwork2#3272 · 6 comentarios ·
Los mantenedores suelen responder en 4 días
Todos los issues de openwebwork/webwork2
Issues similares
-
nftables: "Display comment in rules list?" option has no effect, comments not shown in rules listAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
Type: Bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
inverse-inc/packetfence#9707 ·
Los mantenedores suelen responder en 1 día
-
Mailaddress phrase quotingAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
RotherOSS/otobo#6457 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
The reply-to for the pro user signup emails should be the email of the user instrad of the contact@ emailPosiblemente ocupada @sisodiaumang la tomó hoy. Abierto🏭 producer platform - spam
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
openfoodfacts/openfoodfacts-server#15447 ·
Los mantenedores suelen responder en 1 día
-
Harden argument handling in deploy-contract.shPosiblemente ocupada @Asta-wizard la tomó hace 1 día. AbiertoStellar Wave
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Feyisara2108/stellargive#1377 · 3 comentarios · 1 asignado ·
Los mantenedores suelen responder en 1 día