Project

General

Profile

Actions

Feature #3768

open

Institutions/Past positions on public portfolios

Added by Matt Gold about 9 years ago. Updated almost 6 years ago.

Status:
Assigned
Priority name:
Normal
Assignee:
Category name:
Public Portfolio
Target version:
Start date:
2015-01-28
Due date:
% Done:

0%

Estimated time:
Deployment actions:

Description

When we switched over to the new public portfolio system, I think that we tied institutional affiliation to the Position field. However, I don't think that there is a way to end one's affiliation with an institution -- so, if one leaves an institution and no longer wants it to show up on one's profile, one needs to remove the position entirely from one's profile. I guess that's okay, but a CV typically shows both present and past positions.

I would suggest that we add new logic that allows us either to set an end date for a position or just to indicate whether it is current and past -- and then, only institutions associated with current positions should show up on one's profile.

I think that this is ultimately one for Boone, but I am assigning to the UX team for now for feedback, and then will assign to Ray until Boone is back.


Files

Add New Section Mockup (120 KB) Add New Section Mockup Samantha Raddatz, 2015-01-29 04:35 PM
LinkedIn Positions.png (31.9 KB) LinkedIn Positions.png Samantha Raddatz, 2015-01-29 04:35 PM
Actions #1

Updated by Matt Gold about 9 years ago

  • Tracker changed from Bug to Feature
Actions #2

Updated by Samantha Raddatz about 9 years ago

As it is now, if you add a position to your profile, you're actually forced at that point to choose a college association (and there's no 'other' option, though there is "*non-CUNY" -- see my profile). I think an initial step would be to make that field optional during the adding positions process.

I agree that it would be nice to remove past positions/affiliations, or at least list them as such. Maybe we should take a page out of the LinkedIn book and allow for the existence of both (see 'LinkedIn Positions' attached), and give the user the decision of which they want to include. This would mean adding another option in the "Add New Section" area for 'Past Positions' and changing the current 'Positions' option to say 'Current Positions'. I've attached a quick mock-up for reference, 'Add New Section MockUp'.

Actions #3

Updated by Samantha Raddatz about 9 years ago

  • Status changed from Assigned to Reporter Feedback
  • Assignee changed from Samantha Raddatz to Matt Gold
Actions #4

Updated by Matt Gold about 9 years ago

  • Status changed from Reporter Feedback to Assigned
  • Assignee changed from Matt Gold to Boone Gorges

Thanks, Sam! Assigning to Boone for his feedback and thoughts

Actions #5

Updated by Boone Gorges about 9 years ago

Having separate entry types for Current and Past positions will require users to manually migrate current positions to past when they're no longer current - retyping everything, etc. Maybe not onerous, but annoying.

I kinda like the idea of putting optional start/end date fields on each position.

Actions #6

Updated by Matt Gold about 9 years ago

Thanks, Boone. Do you think it would be difficult to write logic such that if the end date for a position had passed, it wouldn't show up as a current institutional affiliation?

Actions #7

Updated by Boone Gorges about 9 years ago

Yes, that's possible, but is it really desired? If you auto-hide expired positions, then how would one show a previous position, assuming they wanted to?

In contrast, if you don't hide anything automatically, then users can choose to remove expired positions manually as they'd wish.

Actions #8

Updated by Matt Gold about 9 years ago

Good point. I guess this only matters for the Members page, and it's not a big deal to leave things there as is.

I do still think that start/end dates would be good if possible

Actions #9

Updated by Boone Gorges about 9 years ago

Oh, it's only for the members page? I could just change that logic so that only the first position is shown there.

Actions #10

Updated by Matt Gold about 9 years ago

As I look more at it, I don't think that affiliations show up in any other place, but I could be wrong about that.

I don't think that showing only the last entry in the member directory would work, as many people are legitimately at multiple institutions. If we had such logic, we'd just want it to exclude any positions whose endpoint has passed.

Actions #11

Updated by Boone Gorges about 9 years ago

As I look more at it, I don't think that affiliations show up in any other place, but I could be wrong about that.

What about the Positions widget on portfolio pages?

Actions #12

Updated by Matt Gold about 9 years ago

Yes, I guess it shows up there, but it's fine to show there if an end date is listed.

Actions #13

Updated by Boone Gorges about 9 years ago

  • Target version set to 1.8

OK, so:

1. Add start/end dates to Positions
2. On user profiles, show all entered Positions, regardless of end dates. Users will be responsible for sorting them.
3. In directories, when displaying the positions summary under each user, exclude positions with an end date in the past. Positions with no end date will be displayed. Positions will otherwise remain in the order specified by the user in their portfolio.

Is that right?

Actions #14

Updated by Matt Gold about 9 years ago

Is that right?

Perfect. Thank you!

Actions #15

Updated by Boone Gorges almost 9 years ago

  • Target version changed from 1.8 to 1.9

I started work on this but I've run out of time for 1.8.

Actions #16

Updated by Matt Gold almost 9 years ago

No worries

Actions #17

Updated by Boone Gorges over 8 years ago

  • Target version changed from 1.9 to 1.10
Actions #18

Updated by Boone Gorges over 7 years ago

  • Target version changed from 1.10 to 1.11
Actions #19

Updated by Boone Gorges almost 7 years ago

  • Target version changed from 1.11 to 1.12
Actions #20

Updated by Boone Gorges over 6 years ago

  • Target version changed from 1.12 to 1.13
Actions #21

Updated by Boone Gorges almost 6 years ago

  • Target version changed from 1.13 to Future release
Actions

Also available in: Atom PDF