Add fields to user search

[BuddyEthridge]

Is it possible to add the LSU ID and Clicker ID fields to the user search function in the Help Desk block?

When we redesigned the LSU People block to basically replace the User Data Viewer, we did not take into account the administrative usage of the UDV. Admins and FTC personnel used the UDV to search for users by LSU ID and Clickers on occasion. It would be nice to have this search ability back.

Low priority.

[philcali]

Rather than replicating this behavior in two places, the UES Meta data viewer actually has a pretty interesting ability to limit the queryable fields for a specific (type of) user: https://github.com/lsuits/ues_meta_viewer/wiki

This was done with EARS in mind (those who need to filter on athletes and those who don't), but the Help desk could actually share this implementation. This would separate areas of concern too, as the Help desk currently works now without UES installed.

I like your idea, and I see the value in it. I'd like to pursue this course of action, but how do you feel about Help Desk users having to go to the Meta viewer to find this info?

Alternatively, the idnumber field is a standard Moodle user entry, so it would be painless to have that queryable. It brings up an interesting question: is it ok that these users could find other user's idnumber numbers?

[BuddyEthridge]

Actually, this inquiry came from the FTC personnel, who used the data
viewer to search for this information. I thought it might be easier to
combine it on you guys. I have no problem sending FTCers to the data
viewer.

That being said, adding the LSU ID as a field in the help desk block might
actually be beneficial to the HD personnel. Add those users all have a
right to search by LSU ID, so we are not granting any new permissions,
other than in Moodle.

On 6/6/12 7:42 AM, "Philip Cali"
<reply+i-4918134-e5dedc615604a3dd45a2753d1571c82621d651f0-969177@reply.gith
ub.com> wrote:

Rather than replicating this behavior in two places, the UES Meta data
viewer actually has a pretty interesting ability to limit the queryable
fields for a specific (type of) user:
https://github.com/lsuits/ues_meta_viewer/wiki

This was done with EARS in mind (those who need to filter on athletes and
those who don't), but the Help desk could actually share this
implementation. This would separate areas of concern too, as the Help
desk currently works now without UES installed.

I like your idea, and I see the value in it. I'd like to pursue this
course of action, but how do you feel about Help Desk users having to go
to the Meta viewer to find this info?

Alternatively, the idnumber field is a standard Moodle user entry, so it
would be painless to have that queryable. It brings up an interesting
question: is it ok that these users could find other user's idnumber
numbers?

---

Reply to this email directly or view it on GitHub:
#4 (comment)

[philcali]

Cool deal. It's much easier to make the idnumber queryable. Also UES will eventually add the Keypad ID field on the user profile, so the HD user will be able to quickly tell if it's been assigned (I think this is correct).