Feature #2467
closedProfile search and member filters must reflect new profile fields
Added by Boone Gorges over 11 years ago. Updated almost 11 years ago.
0%
Description
New fields introduced in #404 must be accomodated by the search and filter functions on our members directory. Initial thoughts:
- This might be a good opportunity to abstract and polish the BP Better Directories plugin currently powering our members directory
- RSS should probably be excluded from search
- Filtering by structured Positions field will be tricky
Updated by Boone Gorges about 11 years ago
BP Better Directories (the AJAX filters on the left hand side of the directory) has been updated to reflect the new profiles: https://github.com/castiron/cac/commit/68223fbfe703efaa4af32c2f7d90677e261b5c3b
Chris, question for you. The Member Directory currently shows "College" and "Title" under each user. How should this be updated in the new system? Should we instead show a list of positions? Should we show "College" and "Title" for the first position in the list? What about users who haven't entered Positions yet - just continue to display as we currently do?
Updated by Boone Gorges about 11 years ago
Filtering by Positions fields is now in place.
Updated by Boone Gorges about 11 years ago
Because other profile fields already use xprofile as their storage mechanism, no further mods are needed for them to be included in search.
Leaving this ticket open for feedback from Chris on http://redmine.gc.cuny.edu/issues/2467#note-1
Updated by Boone Gorges about 11 years ago
- Assignee changed from Boone Gorges to Chris Stein
Reassigning to Chris for feedback.
Updated by Boone Gorges almost 11 years ago
- Target version changed from 1.5 to 1.5.1
The release of 1.5 is imminent, and the issue of member directories hasn't been resolved. For the time being, this is probably ok, because making no changes means that the current Title and College data will continue to appear on the directories. And, at first at least, this data will continue to be up to date.
However, we should really do something about it sooner rather than later, so I'm moving to 1.5.1. Chris, any thoughts on the matter would be most helpful. Thanks.
Updated by Chris Stein almost 11 years ago
Sorry I didn't get back to you on this earlier. What to show in the listing is a tricky one as we will be going through a transition period and I don't think there is any good programmatic way to make the switch. People will just have to create new positions. Here are my thoughts for now, perhaps too complex? We can also talk about it in the monthly meeting.
1. Check to see if there is at least one position
2a. If there is at least one position then list it. We could just concatenate the fields with of and at in between:
Position: Title of Department at College.
you can add a semicolon to string multiple ones.
Positions: Associate Professor of English at City Tech; Director of Awesome at CUNY Grad Center
there could also be a check for multiple positions so as to use Position or Positions as the heading.
2b. If there are not positions then show the old College and Title as is currently done.
Question:for new members are we removing the option to list College and Title so they have to use the Positions?
If we do something like this dual display solution we should probably think about notifying people who add a position that it will be what shows up in searches. We may also want to put a note by the College and title fields that they are not editable anymore and recommend using positions. Those concerns are worthy of a separate ticket.
Updated by Boone Gorges almost 11 years ago
Thanks, Chris. I think that the conditional strategy you suggest is pretty good. I have a feeling that the "of"/"at" trick is not going to be grammatical with some user-entered fields, so maybe we could opt for commas instead. It should be clear enough.
Question:for new members are we removing the option to list College and Title so they have to use the Positions?
Yes.
We may also want to put a note by the College and title fields that they are not editable anymore and recommend using positions
Already implemented.
Updated by Chris Stein almost 11 years ago
Great. Yes, agree that we should use commas instead of of/at. It will work better with those not in traditional academic departments and who enter non-standard text in those fields. so..
Title, Department, College
Positions: Associate Professor, English, City Tech; Director, Awesome, CUNY Grad Center
Updated by Boone Gorges almost 11 years ago
- Target version changed from 1.5.1 to 1.5.2
Updated by Chris Stein almost 11 years ago
- Assignee changed from Chris Stein to Boone Gorges
Updated by Boone Gorges almost 11 years ago
- Status changed from Assigned to Resolved
In https://github.com/castiron/cac/commit/862cec00bed03253c4ce0be027e21df5f56c13e5 I implement the following: In members loops, for each member, if the member has Positions data, show it; otherwise show College and Title like before.
I think that finishes out the ticket.