MSI agenda - 18 March 2024
Feedback or more info needed on other tasks: (please provide feedback where we have questions)
- No existing user account matches the SAML ID provided. This authentication service is not configured to create new accounts."" error on login". This is expected behaviour; let us know if we should add additional users for testing purposes. No need to add additional users at this point, I think. Perhaps it is indicative of a wider question though: the current Login button logs someone into the site using their UMN account, as if they were going to edit the website. On the live site, will this simply allow anyone to log in? In the long run, this will likely be a link to the new Coldfront portal to access their user groups, but in the meantime, @Jim Ferguson is there a reason we need a site login for all users?
- Jim's response I believe that moving the Login button from the top of the home page to the footer, and renaming it "Admin Login" (prob. in smaller font, it does not need to be a large button/link) is probably the best option."
- Admin login vs PI login - what should we do? My thought is maybe we create a landing page on the archive site with instructions for logging in on the archive site to manage their group. Perhaps then we could rename the "Login" button in the top right of the new site to something like "Manage MSI Group" that navigates to the instruction page on the archive site." Noting the other request and email from Jim "I believe that moving the Login button from the top of the home page to the footer, and renaming it "Admin Login" (prob. in smaller font, it does not need to be a large button/link) is probably the best option
More requests that were not mentioned on the email/ came through later
Discuss: Need clarity
1. Please clarify what this means " other: probably related to "dropdowns," most links don't highlight upon hover, but they probably should."
https://docs.google.com/spreadsheets/d/1udbj48hhY14B8xYln4hlk1tgbyJcLRKVIaepygyH_rc/edit#gid=951525501
2. Images are draggable - I think we should suggest to leave this as is. We can find a way to make it impossible for images to be dragged, but I don't think it's an important issue to fix. we can just confirm with Sarah and Jim.
3. Experts pixelated Looks good to me. One thing I noticed is that the "our experts" photo is stretched and pixelated.
Not sure - this one? doesnt look stretched to us
Discuss: Out of scope
1. It would be nice to have the 'Quickly Find What You're Looking For' "Search >" button on top of the page along side the "System Status, Helpdesk, and Login buttons. It is somewhat strange to have this feature at the bottom of the page.
2. on the Helpdesk, I think it would be useful for a user to see ribhelp@msi.umn.edu as the direct-to-bioinformatics ticket link. Related, it would be useful for a user to be able to select bioinformatics as a category. Are the other categories relevant for the majority of Helpdesk tickets? I would redefine the categories to reflect usage.
3. Getting Started: This whole section, in my view, would better serve new users by being open-on demand-centric. There should be almost a roadmap for new users that is less focused on access and more on usage. E.g. 1) get access, 2) navigate your group's files with ondemand, 3) access the terminal with ondemand, 4) start interactive jobs in the terminal, 5) load modules and run them at the terminal, 6) repeating step 5 but with a batch job submission. This is loosely written under "knowledge base," but that is not where I would immediately think to go when trying to run stuff for the first time. I imagine that a very useful approach would be to have a few common use-case vignettes, sort of like what is in the CHURP manual.
- red is questions / discussions for MSI
Thanks peeps!
Apart from new feedback, the only open question for me is regarding PI / admin links.
And then it's just about picking a launch date :)
I left everything else I believe is still relevant on the list *and most I consider out of scope so with you on the PI/ Admin link being the only real request that needs solving
lastly, I wanted to do a sanity check on my thinking (which may or may not work for them)
- Can we commit to getting all of the reverts done by Friday or shall we commit to the 29th, giving the team the following week to check and we plan our role out the second week of April with DSI? (so both would roll out that week - is that practical?)