Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

People - Figure Out How to Handle Alumni #211

Open
fcjou opened this issue Apr 8, 2016 · 1 comment
Open

People - Figure Out How to Handle Alumni #211

fcjou opened this issue Apr 8, 2016 · 1 comment

Comments

@fcjou
Copy link
Contributor

fcjou commented Apr 8, 2016

In order to figure out how best to structure and organize the 'people' files, we first need to determine how we want to handle alumni.

Suppose this special case person exists:

  • Currently a professor in multiple departments
  • Previously a PhD student at UW
  • Previously a Master's student at UW

Some questions arise:

  • Do we want to keep alumni files in our system? (currently we do have an alumni folder)
  • Do we want to display alumni in their own section on our website? Is this important?
  • If someone has current and alumni roles (e.g. above), do we want to retain and/or display the alumni information? Together? Separately?
  • How will we maintain alumni status/info (people graduate, drop out)? Keep track of their graduation date? Manually update an alumni status flag and move them from one folder to another? Will we eventually want more organization beyond 'alumni' and 'current' such as graduation year?

If we don't care about displaying alumni info at all, that simplifies how we can think about organizing people by A LOT. Then we can follow something like what came out of the discussions for #63 :

role:
  - faculty
position:
  - title: Assistant Professor
    unit: Information School

role:
  - doctoral-student
position:
  - unit: Information School

role:
  - masters-student
position:
  - unit: Master of Science in Information Management

However, if a person has multiple roles (say... faculty AND doctoral-student-alumni) then there would be no way to tell which unit is associated with which role.

Currently my solution for designing around the 'special case person' is this:

role:
  - faculty:
    is-alumni: false
    position:
      - title: Associate Professor
        unit: Information School
      - title: Assistant Professor
        unit: Division of Design
  - doctoral-student:
    is-alumni: true
    position:
       - unit: Information School
  - masters-student:
    is-alumni: true
    position:
      - unit: Master of Design

Another variation is having alumni roles (e.g. faculty-alumni, doctoral-alumni) instead of having an is-alumni flag, or to have a field for graduation year for students. Either way, we need to have alumni information in the file itself, otherwise we'd have to resort to having multiple files for that 'special case' person, which is something undesirable.

Thoughts? Am I overthinking this?

@jayfo
Copy link
Member

jayfo commented Apr 8, 2016

This person exists!

http://directory.tacoma.uw.edu/employee/ejrose

But I do think you're currently overthinking this. Let's ignore alumni for now.

Get our current people live, then we'll figure out if and how to show alumni.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants