EBMS Tickets

The difficulties here depend on whether we can make the NIH login name or NCI (eDir) user name the real user name inside drupal. If so, then full names like "Alan Meyer" would not appear anywhere in the EBMS reports or displays. Only "alan", my NIH login name, would ever appear.

I can't think of any other way to solve the problem because we can't change eDir or SSO login names.

Is that what we want?

If we need to preserve the customary names stored in the EBMS, that's significantly harder, requiring that we store an extra field and modify all of the reports and displays to use it.

Would it be possible to preserve the Board member names on some pages in the EBMS (e.g., "public-facing" pages) and not on others, or is it a lot of work to do this at any level? Thanks.

We'll do the story-pointing for this ticket after the requirements have been nailed down.

I have another question: Alan mentioned the SSO login names, but would this change affect the SSO users and how their names appear in the system? I wasn't thinking that it would since we are already doing some form of mapping between their NIH userid and their name in the system. Could you please clarify?

I think it would be worth getting a few different story point estimates for this issue to help us determine which avenue to take.

1. Scenario 1 - eDir username is used to log in and appears throughout the system anywhere the EBMS username used to appear.
2. Scenario 2 - eDir username is used to log in and appears on internal pages but public-facing pages (*listed below) display the EBMS username (first name and last name)
3. Scenario 3 - eDir username is used to log in but it is replaced by the EBMS username on all pages (internal & external)

*public-facing pages:
Literature>Assigned Packets>Reviewer Uploads
Literature>Completed Packets
Literature>FYI Packets
Manage Summaries>Documents Posted by NCI (if this applies to SSO users)
Manage Summaries>Documents Posted by Board Members
Calendar - names that appear on participant hover on an event page

It's also worth noting that this ticket could become obsolete if we find out that we are approved to implement OCEEBMS-330.

I would say scenario 1 is easy but, I agree, problematic for users. Who, after all, is "juther"?

Scenario 2 is harder. How much harder 3 would be depends on the number of additional pages that use the name. We'd have to do some research before we could figure out the levels of effort.

There are some other conceivable options, for example:

Maybe we could change the screen display for the user name. Instead of saying: "Robin Juthe", we could say "Robin Juthe (juther)" or maybe: "Robin Juthe (nci:juther)", or "Robin Juthe ("nih: juther)" or something similar. We could put the info on two lines if it fit better, using a smaller font for the special NCI/NIH name.

This would not eliminate the use of two names, but it would help the user to remember his NCI or NIH password change name and, maybe, reduce the confusion.

As for OCEEBMS-330, I think that would reduce confusion for frequent Open ID users, but might not solve everyone's problem.

We estimate 3-5 story points for scenario 1, 13 for scenario 2 and 20 for scenario 3.

The alternative posed above (displaying both names as the logged in user identifier in the banner part of each page) is in the 3-5 range.

Is this issue still applicable with the OpenID? I'm guessing that it has at least changed a bit. Maybe we can discuss this in today's CDR/EBMS meeting.

I think so. If nothing else, federated login wouldn't affect the SSO accounts (if I understand correctly). As you say, let's discuss it this afternoon.

I think we can close this issue.