May 24, 2011 at 3:45 pm #167388
I have a Pod that lists Attorney Profiles. The site also has a Services area with a number of WordPress child pages under it, referencing the different service types of the company. These service pages are a multi-select pick column in the Attorney Profiles Pod to allow the client to specify which employee specializes in which service(s). Simple enough.
However, the client wants to be able to sort the order of the multi-select picks on a per-attorney basis.
In other words, if Employee John excels at Service F, and he is ok at Service C, and he knows a little about Service H, the client wants to list those next to John’s name in the order of his expertise: 1) Service F, 2) Service C, 3) Service H
Any ideas?May 24, 2011 at 5:34 pm #167389
You’re probably going to have to remove some of that simplicity to get the functionality your client needs.
If your main pod is "Attorneys", I’d approach it by removing the multi-pick from there and creating another pod called "Attorney_Skills." Attorney_Skills would have 3 fields: Attorney (pick Attorneys), Skill (pick wp_pages Skills), and Skill_Level (int 0-100). That way you can associate any number of skills with an attorney, and give the firm flexibility in grading that attorney’s skill level in each specialty.
To make this manageable for the client, you’ll need to delve into PodsUI to create a custom page where they can see each attorney and their associated skill from each page.
You could also take this back to the skills pages and show a list of say all attorneys who are experts (say Skill_Level > 70) in that field.May 27, 2011 at 11:31 pm #167390
Mike Van WinkleParticipant
Hmm, it seems like there’d have to be a way to do this. It might be a hack but it should be doable. For instance (thinking out load), you could create a code field called "specialty_order" and then an input helper that uses jquery-ui-sortable to create a drag and drop list out of the selected options and then deposits a serialized array of specialty ids in the sorted order into the code field. Then on the front end you could iterate over the array and pull the respective specialty info. It’s a bit of a hack but it should work. How comfortable are you with jQuery?
That said, I think Chris’ approach would be more robust if you could make the UI work in a way the client wants it.February 16, 2012 at 7:22 pm #167391
I am actually looking for exactly the same functionality for the same situation. Did you ever get anything working on this jcross (or anyone else)?
I am trying to work with Chris’ approach but struggling a bit on getting an input helper sorted out that will work for the client.February 17, 2012 at 4:08 pm #167392
Maybe the least kludgy way to do this is limit the client to some arbitrary number of key skills per atty. Let’s say 10. Then create 10 pick fields in your pod for the skills and 10 additional fields for skill level. For attys with more than 10 skills, then have a multi-pick for "other skills". To make it idiot-proof, filter the display of these other skills to make sure you don’t have key skill repeated here.
The forum ‘General Questions – Pods 1.x’ is closed to new topics and replies.