I'd like to be able to create multiple profiles of the same type and assign them to users, any way that can be done?

I'll also lay out my use case to see what I'm trying for, and maybe someone can either explain where I'm going wrong or offer alternatives.

This site is for an arts and crafts festival, and I'm creating a vendor registration function where vendors can also maintain data in their profile to be displayed publicly (eg. a "list of vendors" and whatnot). The festival is yearly, so the same vendors will often return many times, so I wanted to give them multiple Vendor profiles, one for each year they register.

I have a taxonomy vocabulary listing the festivals (years), with a term reference in both the Vendor profile and the Registration. The Registration also has various fields to populate their profile (website, description of their wares, etc.). I planned to create a Rule that fired upon saving a Registration that would create a Vendor profile entity with the same festival (term reference) set and copy some fields to it. Then the vendors could edit/maintain each year's profile with different information as needed.

As best I can tell, when I created the Vendor profile, there's a one-to-one reference of the vendor profile for each user, and the profile owner (user) under each profile. I want to either have the profile reference allow multiple entries (ie. so it can be a "list" in Rules), or eliminate it altogether (ie. not have a forward and backward reference, just the profile itself knows what the owner is). Or am I simply off base as a relative newbie?

Thanks...
Jesse

Comments

stephen verdant’s picture

Jesse -- Restricting each user to 1 profile node (or 1 node of each type) seems to be a main purpose of a profile module. Since you don't need that, could you just create a regular Content Type? What does Profile2 give you that a straightforward Content Type doesn't?

pwaterz’s picture

I second you stephen Verdant

jnorell’s picture

Status: Active » Closed (works as designed)

I'm probably just going about things the wrong way. I might do the data copy/display the other way, ie. have a single Vendor profile that can have a vendor's standard info in it, then copy that to the fields in a specific festival's Registration (and make a view based on the Registration info rather than the Profile to display on the site). Thanks for confirming I'm not just missing something obvious.