Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Date

2-3:30 pm

Attendees

Guests:

  • Andy Kohler, UCLA (if needed)

Discussion items

Item

Time

Who

Notes

Decisions

Actions

1

Q&A (recurring) - urgent questions

Do you have a question to discuss at the meeting? Add it below with your name.

  1. (From Discovery) Purpose of sheet: to let EUOS, Discovery, ICs, Comms, and PMs primarily get a clearer picture of what is the same/not across our campuses. Is this accurate info?

  2. GK: UC-shared ebooks in NZ & Course Reserves Reading list update; more information, possible workarounds

30

All

2

Go-Live coordination

https://docs.google.com/spreadsheets/d/1olDkcAsvX3pp1W-GY4MJvpu0C2I5Krkts_0wIN96fGI/edit#gid=1252460463

Alison’s draft go-live (day-of) countdown with hour by hour CDL work

  1. Do you have a backup plan in the event key staff are not available during go-live?

    1. Is it for a couple of days or the whole week?

    2. What if your IZ is delivered early? Will staff be prepared?

  2. On early delivery of IZ/NZ from Marci:

    • ExL Prof Services does not get notified in advance about early delivery - we just get the environments when we do. And then we review them before agreeing for Migration to copy them to production (which needs to happen before we release the environment to the campus for review).

    • We have provided a date for when we expect to deliver them (on or by Friday July 23rd). If the campuses want to be proactive and prepare for a just-in-case early delivery, I would suggest them being available a few days in advance of that.

    • NOTE: The non-Alma campuses' Fulfillment Cutover is a separate delivery and usually is next day after data is provided to us (and will differ for your campuses) - Sun/Mon - Mon/Tues.

    • Advice: block off a couple of days in advance to review your testing plans with your local team.

10

Carlo, Tom

Backup plan:

  • Yes: UCR, UCM, UCI, UCB

  • Not yet/in progress: UCSF, UCSD

3

Timeline review / PM update

Stay up to date on timeline / deadlines

time-permitting

Lena

Any questions on the timeline?

Followup Qs on Salesforce post-go-live:

  • Will campuses see all of their ExL SF cases in one place, including for products that are not Alma/Primo, e.g., RefWorks, ProQuest, etc.?

  • Is it possible to choose whether to see all products or only Alma/Primo?

Response:

  • A SF user at a campus should be able to see all of their campus' cases for all of their products.

  • Based on the doc (added below) they may even be able to see cases from other campuses in the consortia. Marci never heard this before - but in your situation you will be able to do it with the PM super user account or anyone directly under the UCS parent account (like the special account Gem created).

  • I did not see anything about limiting the view of the lists of cases to a product - however you could ask one of the live campuses with multiple products and they can let you know if they can do that.

  • I do however see in the doc that you can limit a user to only being able to open cases for specific products.

  • Please see the https://knowledge.exlibrisgroup.com/Cross-Product/Support/030_Salesforce/Support_Portal_User_Guide for more information.

  • REMINDER for PMs: We will need to do SF clean up work post Go Live to move the existing live Alma campuses and CDL under the UCS parent umbrella (this still does not prevent anyone from opening cases at this time!). And there may be a month delay for doing the clean up work due to the 30 day extension for the current live Alma campuses.

Special meetings

4

Parking lot

0

  • [Hold for after 6/25] Clarification on Alma/Primo known issues page on Confluence: We have a suggestion to use it for product issues (Alma/Primo) that are controlled by Ex Libris; not for known issues as a result of CDL’s data clean-up and campus-level e-resources management (or non-migration related access issues that also may surface/be tracked).

    • Does everyone agree with this approach? Yes.

    • Do we need another list for internal known issues? Who manages it? Set it up decision page style so each group has one and it feeds into a consolidated view? (may be too much overhead?) - Return to this Q

  • [Hold for after 6/25] Risk assessment for Go-Live

    • ICs to do local risk assessment and share select risks before Jul 1

    • Go Live Risks sheet (feel free to make a copy for your local imp team risk assessment)

    • Brainstorm mitigations together with ICs at Jul 1 or Jul 8 (Jeremy reported in chat that fiscal close makes Jul 1 a busy time.) Preference?

  • Post go-live: Decide which IZ(s) to use for the analytics workshop (in addition to the NZ). Nothing will be edited during the demo. One suggestion from the trainer is to use a different IZ each day.

    • Would you like your IZ demo’ed in the analytics workshop? (Polled on slack)

      • Yes: UCB, UCSF

      • No: UCR, UCSB

  • In preparation for the eventual switch from implementation to support (and to Salesforce exclusively), new-to-Alma ICs should consider who should have Salesforce accounts (have it in place before go-live). Understand best practices in opening cases. Ex Libris has a template. See Basecamp post.

5

TOTAL

90/90

Review decisions and actions.

20

  • No labels