I am looking for a little advice with the use of the Dyn User Directory module.  It works great but I am curious to see if anyone will suggest how to handle this data.

I am using the module to display detailed user profile information.  1500 members - 500 active, 500 inactive, 500 deceased.  It is a fraternity website so I maintain all members - alive or not - I need for all to be part of my directory.

I need to maintain data related to Offices, Honors, Awards ... as well as the year for each of these.  There are 20 or so Offices/Awards and 100 possible years for each.  If I hold this info in the user profile, I would have 2 fields for each - 40 or more fields - All list boxes or check boxes.  I could see this to be problematic when searching.

Should I consider another method to store this data?  I do need to include it in the Dyn User Directory search results.  Is there a way to include data from outside the profile in a Dyn User Directory search?

Thanks in advance for any suggestions.

Dan

Dan,

Hi. Are you also using a module such as Dynamic Registration? This might make splitting up the users data into multiple areas better, or does the directory even get updated this way? I have seen some users use Dynamic Registration with other modules such as a TABS module that gives you multiple tabs of data to manage. From there you could maybe setup multiple user directory modules and maybe a starting page such as....

'Search Directory by Offices'
or
'Search Directory by Honors'

etc...

You can technically have as many search fields as you want though, so maybe just one large search page?

-Chad

I am using Dynamic Registration. And I will be splitting up the data. For now I am using the core profile to get things working. I will migrate into Dyn Registration. The reason I am using the core profile is that my Dyn Registration is not getting back Listbox info from the core (it updates blank data back to the core since it did not get the data that is in the core field) that's another story.

Back to the original question. I am not sure that Dynamic registration is the right choice for my data. I am migrating users from a non DNN site to a DNN site. The data I need to use is currently like this:
UserID (one user from 1500 users - the one who was an officer)
YearID (one school year from a list of 100 years - example 1922-1923 - Year ID is linked to a year/term table)
OfficeID (one of 15 or so offices that are stored - again linked to a table)

Typical data: Joe User, President, Term: 1922-1923

FYI ... The data is maintained by the admin not the user. We don't want someone claiming to be president 

I can see why it was done this way. Moving it to DNN and using Dyn User Directory is what I am attempting to do. I don not see a way to include data that does not reside in the core profile.

I don't want to attempt to do something the module is not designed to do but I do still need to accomplish the goals of the project.

Thanks, Dan