It is my understanding that if a customer has an email address in the database, but it is not associated with a web login (in T_CUST_LOGIN), then that customer will be unable to use that email address to register for a new web login (due to the preexisting address) and will also be unable to recover the account online (due to the lack of an actual login to recover).
Assuming that is true, would anyone recommend a good workaround for this situation? The best I can come up with is to create a procedure that runs periodically and creates web logins for email addresses that haven't already been associated with a login. This seems pretty clunky, though. Thoughts?
It is my understanding that if a customer has an email address in the database, but it is not associated with a web login (in T_CUST_LOGIN), then that customer will be unable to use that email address to register for a new web login (due to the preexisting address) and will also be unable to recover the account online (due to the lack of an actual login to recover). Assuming that is true, would anyone recommend a good workaround for this situation? The best I can come up with is to create a procedure that runs periodically and creates web logins for email addresses that haven't already been associated with a login. This seems pretty clunky, though. Thoughts? You were sent this email automatically because you subscribed to the Tessitura Web forum. You may reply to this message to post to the Web forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
If the person doesn't have a web login then if they go to use that email address to create a login, they'll create a duplicate account, with the same email address, one account having a login associated with the email, one without. We have patrons who do this all the time, and then it's just a matter of merging. It may be a useful/good idea to create temporary logins for all email addresses that don't have logins, especially if your users use their email address as the login. In the situation above, I believe you wouldn't be able to create a login for the original because of the dupe the patron created and its having a login already associated with the email address. But if the login had already been automatically created, then the patron might be prevented from creating the dupe because they would be able to recover the login (even if they didn't know it existed). Of course there's always people who'll just create a new account using a different email, but that's a separate matter...
If the person doesn't have a web login then if they go to use that email address to create a login, they'll create a duplicate account, with the same email address, one account having a login associated with the email, one without. We have patrons who do this all the time, and then it's just a matter of merging.
It may be a useful/good idea to create temporary logins for all email addresses that don't have logins, especially if your users use their email address as the login. In the situation above, I believe you wouldn't be able to create a login for the original because of the dupe the patron created and its having a login already associated with the email address. But if the login had already been automatically created, then the patron might be prevented from creating the dupe because they would be able to recover the login (even if they didn't know it existed). Of course there's always people who'll just create a new account using a different email, but that's a separate matter...
Thank you, Ms. Dean and Ms. Freeman. I'll proceed with building a nightly-run procedure to create logins for unassociated email addresses. If the same address exists multiple times, I suppose I'll just have to pick one arbitrarily and leave it to the merging process to reconcile.
Does such a procedure already exist, or is it up to us to code our own?
There is a procedure we shared a few years back that does just that. It’s called Assign Usernames or something of that sort.
From: Tessitura Web Forum [mailto:forums-tessitura-web@tessituranetwork.com] On Behalf Of Bryan DrennerSent: Monday, September 12, 2011 3:56 PMTo: Gloria OrmsbySubject: [Tessitura Web Forum] Email addresses without associated web logins
You were sent this email automatically because you subscribed to the Tessitura Web forum. You may reply to this message to post to the Web forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
We have done something similiar before. But there is always a chance that the id has not yet been created. Maybe you can do something with forgot password/login and call a custom proc to create the missing user id.
Jon
We are having a similar discussion about temp logins. I'm curious--when you are creating a login using their email address, are you flagging the login as temporary or flagging the password as temporary?
I would think that you would want the logins to be permanent, but the passwords temporary. The users can then just update their passwords over time.
Thanks,
Patrick
Technical Project Analyst The Pittsburgh Cultural Trust 803 Liberty Avenue Pittsburgh, PA 15222 fitzgerald@pgharts.org w 412-325-7061 c 646-434-8955
Patrick,
We make the login permanent and the password temporary. The patron can then use our Forgot Login link to reset their password to a permanent password of their choosing.
Teresa
Thanks Teresa.
One other question--do you communicate with customers to let them know that a login exists and that they should update it? Or do they just stumble across it when they are on your site?
Right now, because we are a consortium and don’t have a way to email with individual org information, patrons have to stumble on the accounts. I’m trying to find a way to format an email template that conveys to the patron that they now have an account on each website for the group instead of just one site. The other problem is figuring out who to have the email come from without upsetting a consortium member.
From: Tessitura Web Forum [mailto:forums-tessitura-web@tessituranetwork.com] On Behalf Of Patrick FitzGerald Sent: Tuesday, September 13, 2011 3:05 PM To: Teresa Dean Subject: RE: [Tessitura Web Forum] Email addresses without associated web logins
From: Teresa Dean <bounce-teresadean9276@tessituranetwork.com> Sent: 9/13/2011 2:51:29 PM
Hi there,
we're about 6 months old in TNew and need to get up to play with automating these logins! I'm not tech savvy however am very familiar with the web user guide and can't see how this is done. Any tips and procedures most welcome.
Cheers
Ina
We have 3 of 5 consortium members now running TNEW and are encountering the login issues mentioned in this thread. If anyone has current SQL (v12.1.2) for creating login accounts it would be appreciated.... thanks.
We had a similar issue. When we converted to Tessitura 12.1.2 and it created temporary TNEW logins for everyone that had an email address on their record. So when they tried to log in or use guest check out with that email address it would not let them proceed.
They had not created a log in but the system thought they had one. It caused a lot of confusion but we were able to help clarify once we understood the issue. When they entered that address, there was a forgot password option and if they clicked and reset the password then it would complete the login account set up and provide them with fill log in credentials and allow them to proceed. We had the TNEW team add some language to the error message on that page acknowledging that their email was in our system and asking them to set up a password using the reset password link.
Hope that helps!
Amanda
From: Tessitura Web Forum [mailto:forums-tessitura-web@tessituranetwork.com] On Behalf Of Barbara Pinney Sent: Friday, April 24, 2015 12:25 PM To: Amanda Nash Subject: Re: [Tessitura Web Forum] Email addresses without associated web logins
From: Bryan Drenner <bounce-bryandrenner9059@tessituranetwork.com> Sent: 9/12/2011 2:52:28 PM