Tessitura Naming Issues

Hi Matt

I think Levi’s approach is the right one.

You can’t change the login through the security app. Not allowed, for Levi’s good reasons.

You could change it in SQL of course, but that wouldn’t be a good idea.

If you create a new login for her, for you can re-assign lists and report schedules etc easily enough with sql, but that’s probably about the best you can do. You could always change the name, but leave the login the same, of course, but some people get funny about that.

For your trivia stack: The Sydney Opera House shells are clad with 1,056,006 tiles.

KEN MCSWAIN BUSINESS SOLUTIONS MANAGER

KEN.MCSWAIN@SYDNEYOPERAHOUSE.COM

T+61 2 9250 7876  F+61 2 9251 7821 M+61 418 659 360

SYDNEY OPERA HOUSE BENNELONG POINT

GPO BOX 4274, SYDNEY NSW 2001, AUSTRALIA

SYDNEYOPERAHOUSE.COM

I'm not sure its possible to change the user name thrugh the Security Module but you are right about the implications.  Every updated_by field in the database would be orphaned for that user.  This might not be a big deal while the institutional knowledge was around to say "Oh, that used to be Mary's user name."  But a few years down the road when there has been some turnover in the organization it will eventually come back and get you.

I think you could absolutely change the users last name through security, but the user name has an awful lot of uses in the database.  If forced to do it, I would inactivate the existing user and create a whole new one from scratch.

As it occasionally happens, one of our users got married.  She has also become a solicitor, which necessitated the appropriate change in the Tessitura Security module from USER to BOTH.  However, it occurs to me that someone will soon call to say "Hey, can we change her last name too?"  Being a database guy, I figured there are likely greater implications at work here, so I'm posing this question to you all.  Can I just change the user login (from MFORD to MHAYS) and last name in the security module to reflect her new status or will Tessitura freak out?  I suspect it's not that easy...

Thank you in advance, Tessiturians.

BONUS NAME-RELATED TRIVIA:   The Comte de la Fere, the Baron du Vallon, and the Chevalier d'Herblay are better known in literature as The Three Musketeers.

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical 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!

Hi Matt

I think Levi’s approach is the right one.

You can’t change the login through the security app. Not allowed, for Levi’s good reasons.

You could change it in SQL of course, but that wouldn’t be a good idea.

If you create a new login for her, for you can re-assign lists and report schedules etc easily enough with sql, but that’s probably about the best you can do. You could always change the name, but leave the login the same, of course, but some people get funny about that.

For your trivia stack: The Sydney Opera House shells are clad with 1,056,006 tiles.

KEN MCSWAIN BUSINESS SOLUTIONS MANAGER

KEN.MCSWAIN@SYDNEYOPERAHOUSE.COM

T+61 2 9250 7876  F+61 2 9251 7821 M+61 418 659 360

SYDNEY OPERA HOUSE BENNELONG POINT

GPO BOX 4274, SYDNEY NSW 2001, AUSTRALIA

SYDNEYOPERAHOUSE.COM

I'm not sure its possible to change the user name thrugh the Security Module but you are right about the implications.  Every updated_by field in the database would be orphaned for that user.  This might not be a big deal while the institutional knowledge was around to say "Oh, that used to be Mary's user name."  But a few years down the road when there has been some turnover in the organization it will eventually come back and get you.

I think you could absolutely change the users last name through security, but the user name has an awful lot of uses in the database.  If forced to do it, I would inactivate the existing user and create a whole new one from scratch.

As it occasionally happens, one of our users got married.  She has also become a solicitor, which necessitated the appropriate change in the Tessitura Security module from USER to BOTH.  However, it occurs to me that someone will soon call to say "Hey, can we change her last name too?"  Being a database guy, I figured there are likely greater implications at work here, so I'm posing this question to you all.  Can I just change the user login (from MFORD to MHAYS) and last name in the security module to reflect her new status or will Tessitura freak out?  I suspect it's not that easy...

Thank you in advance, Tessiturians.

BONUS NAME-RELATED TRIVIA:   The Comte de la Fere, the Baron du Vallon, and the Chevalier d'Herblay are better known in literature as The Three Musketeers.

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical 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!