...
...
| Note |
|---|
The TPDM Work Group is now the Educator Preparation Work Group. Read more about the name change We're renaming TPDM, here's why |
Participation
| Members | Support |
|---|---|
Tricia Farris LaCole Foots Lori Ludwick Luis Machuca Cari Reddick Sarah Kolbe Tiffany Fernandez Jordan Mader | Steven Arnold Nancy Smith |
...
Jira Legacy server Ed-Fi Issue Tracker columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId e04b01cb-fd08-30cd-a7d6-c8f664ef7691 key TPDMX-60
- For Relay, this would be helpful to add a classification field to alleviate the issue of not being able to distinguish their type. In addition, the ticket #60, also asks for a way to distinguish who manages the staff member (e.g. manager). Our campus Deans and leaders usually want to know how different teams are doing, the performance of their faculty and how they are impacting the teachers in their classroom. Having such relationship type within the staff will allow for us to be able to do this. So this way, a dean can see all faculty managed by x person and then the teacher candidate associated with that x person.
- Staff to Staff. Deans want to know how they are impacting, who they are associated with
- What are the relationships?
- Would this be different relationships like 'university supervisor', 'advisor', etc.? There is value is finding a way to determine that. (university relationship)
- Staff to staff - we might be organized differently - more likely to associate that with a program; less likely around staff to staff
- could see the value of having data in the model and use for other reporting
- what is the data source for this?
- not sure how they are mapped together
- does have data in Unit 4
- Relay could use program associations, but there is variation of staff to staff within programs that this does not necessarily align
...