Should we have a User/Store association ?

[Abdullah Shaikh <ab...@gmail.com>]

We have 3 stores, and the requirement is when a customers registers on any
one of the 3 stores, and if the customer again registers on any one of the
other 2 stores, we want to have a check that if the customer is already
registered with any one of the other 2 stores so that on new customer
registration page we can display customer the message that if he has
registration on store1 then he can use the same userid/password for this
store too.

This way we will be able to minimise the no. of users because the same id
can be used across all the stores, and also it will solve the issue when
instead of having any user id, which the user creates, you are using email
id for user id, otherwise incase of using email id for user id field, the
user will need to create 3 email id's for 3 stores.

We can have a UserStoreAssoc table which will have userid & product store id
mapping, so that we can check if the user has already registered with any
other stores. During user registration we can create a record in this table.


- Abdullah

Re: Should we have a User/Store association ?

[Abdullah Shaikh <ab...@gmail.com>]

Thanks Rishi, this is what I wanted ..

- Abdullah

On Mon, Mar 15, 2010 at 5:17 PM, Rishi Solanki <ri...@gmail.com>wrote:

> While creating a user for your site for the first time create its record in
> ProductStoreRole entity with CUSTOMER role.
> Now if user wants to use same ID then he can just for that option that
> means
> register for other two stores, in that case just create ProductStoreRole
> two
> more record in CUSTOMER role.
>
> Rishi Solanki
> Enterprise Software Developer
> HotWax Media Pvt. Ltd.
>
>
> On Mon, Mar 15, 2010 at 4:53 PM, Abdullah Shaikh <
> abdullah.shaikh.1@gmail.com> wrote:
>
> > We have 3 stores, and the requirement is when a customers registers on
> any
> > one of the 3 stores, and if the customer again registers on any one of
> the
> > other 2 stores, we want to have a check that if the customer is already
> > registered with any one of the other 2 stores so that on new customer
> > registration page we can display customer the message that if he has
> > registration on store1 then he can use the same userid/password for this
> > store too.
> >
> > This way we will be able to minimise the no. of users because the same id
> > can be used across all the stores, and also it will solve the issue when
> > instead of having any user id, which the user creates, you are using
> email
> > id for user id, otherwise incase of using email id for user id field, the
> > user will need to create 3 email id's for 3 stores.
> >
> > We can have a UserStoreAssoc table which will have userid & product store
> > id
> > mapping, so that we can check if the user has already registered with any
> > other stores. During user registration we can create a record in this
> > table.
> >
> >
> > - Abdullah
> >
>

Re: Should we have a User/Store association ?

[Rishi Solanki <ri...@gmail.com>]

While creating a user for your site for the first time create its record in
ProductStoreRole entity with CUSTOMER role.
Now if user wants to use same ID then he can just for that option that means
register for other two stores, in that case just create ProductStoreRole two
more record in CUSTOMER role.

Rishi Solanki
Enterprise Software Developer
HotWax Media Pvt. Ltd.


On Mon, Mar 15, 2010 at 4:53 PM, Abdullah Shaikh <
abdullah.shaikh.1@gmail.com> wrote:

> We have 3 stores, and the requirement is when a customers registers on any
> one of the 3 stores, and if the customer again registers on any one of the
> other 2 stores, we want to have a check that if the customer is already
> registered with any one of the other 2 stores so that on new customer
> registration page we can display customer the message that if he has
> registration on store1 then he can use the same userid/password for this
> store too.
>
> This way we will be able to minimise the no. of users because the same id
> can be used across all the stores, and also it will solve the issue when
> instead of having any user id, which the user creates, you are using email
> id for user id, otherwise incase of using email id for user id field, the
> user will need to create 3 email id's for 3 stores.
>
> We can have a UserStoreAssoc table which will have userid & product store
> id
> mapping, so that we can check if the user has already registered with any
> other stores. During user registration we can create a record in this
> table.
>
>
> - Abdullah
>