Next Steps For Consolidated FacultyMember Data

[ajkiessl]

We have a script that can iterate through committee members, find a record for that faculty member in ldap, create a FacultyMember record in the etda database, store their department, and link matching committee members. This is all tested thoroughly.

How would we like to proceed from here?

Some things to consider:

• We find many committee members in LDAP that don't have departments. Should these be ignored? Many are EMERITUS, but some are STUDENT or FACULTY.
• How do we want to keep this up-to-date? We could run the import regularly, or add some functionality that does this creation/linking when committee members are created.

[ajkiessl]

Of course, we also need to figure out who/or what is going to use this data? Will someone interface with our db, API, CSV output, or do we want a UI dashboard?

[ajkiessl]

Let's start with a CSV export of this data.

After this, we want a high level view of how diverse committee interactions are between departments. Some kind of visualization of this would be great.