| Item | Desired Outcome | Time | Who | Notes | Decisions | Actions |
|---|
| 1 | Check-in / Logistics / Any issues with testing? | Report any major changes in availability / circumstances Anything to report on the test load?
| 15 | Tom | | | |
| 2 | Progress on integrations work | Round-robin to see how everyone is doing on integrations work. For non-alma campuses, where are you at in the patron update (SIS loader) process? Progress or changes to your 3rd party integrations plans? (refer to your forms on Basecamp)
| 20 | Tom | Authentication: due April 30 UCLA: Done! (except for logout issue) Merced: Done! (need to make a change to the patron data in mapping and it will work) Berkeley LBL: Done for Alma and Primo! UCSD: Working fine. They are creating a system ID as a matching point for SSO. Wrinkle: A few hundred that are missing.
SIS loader: due April 30 UCB: some behavior with internal notes being overwritten. UCLA: need to confirm with Andy what the status of the work is. UCM: manual method works. Testing Mulesoft. Should know more next week. UCSD: still working on it. Coding XML file to do a fullscale test. UCSF: working on test loading XML files and making progress. Is anyone using the ExL ftps server or using their own? Everyone is using their own server.
Other day 1 integrations: UCB: label printing, paypal, invoice payment, aeon, dam test, EOD integration, letters, EDI, OCLC UCLA: waiting on decisions from various FGs. UCM: mostly under way UCSD: lesser integrations are mostly done. Bursar integrations, AP batch (most challenging; developing specs and get exports into the test environment so they can develop the middleware.) UCSF: acquisitions and EDI, GOBI API is scheduled, publishing holdings to OCLC. CDL: scaled back for day 1; Calisphere will be ingested into the NZ; will not have direct integration with financial system; Alma to VDX bridge is tested; NCIP work; importing records from OCLC.
| | |
| 3 | ILS Data cleanup / Patron Data groups / PPC | ILS Data Cleanup (Tom): co-chairs visit on 3rd Thursdays. TJ Kao and/or Catherine Busselen will join on TBD. Patron Data (Greg) PPC: Review final decisions (as needed) SILS Chairs/Coordinators meeting update & actions
| 5 | Tom | Patron Data: Nothing ILSDC: N PPC: decision on CDI - EasyActive Coordinators: met with EUOS to answer what cutover means for patrons. Ask of ICs: please invite your EUOS member to your local imp team meeting. SILS Chairs: Review the Cutover plan and ask what questions chairs have. (Note: Post questions on the Cutover plan BC post.)
| | 98 |
| 4 | Timeline review / PM update | Stay up to date on timeline / deadlines | 5 | Lena | Any questions on the timeline? What is your technical freeze date? Let us know by May 31. We’ll add it to Basecamp. Update on Alma slowness issue: Current testing for UCLA (5/10) had the following results:
01UCS_LAL ; all titles - keyword Reported updated testing results to Development. Campuses should still document any issues with slowness in SalesForce. The data ExL needs for development is posted on BC: SalesForce Cases for Reporting Alma Slowness Jeremy did some testing.
What happens when Cutover begins? Professional services do some work before handing it to Migration. Migration will begin to export SFX data, copy the NZ to a migration environment, and build the NZ starting then. Most deliverables (and pre-cutover activities) are due on dates prior to Migration's start work. The existing Alma campuses are doing their technical services freeze at EOD on July 9th - due to the fact the Migration team will begin copying their environment at that time.
Reminder: Post cutover questions on Basecamp in the UCS Cutover Planning To Do list in the relevant action item. If there’s not an action item, use the message board. Quick Q to already-Alma campuses: Did you get all the information you need about how to access your old environment post-go-live (during the 30-day grace period)? Have not received any details yet. Lakshmi is waiting. Laurie said she would put the details on the Cutover case. (Confirm that’s the case)
| | |
| 5 | Go-Live Discussions Cutover planning on basecamp Timeline on confluence | Getting prepared for go-live Let your website manager know that discovery links will need to reflect the change on July 27 (exact time TBD). Decide as a team what time we want to go live on July 27th. How can we coordinate this to ensure we are all "open for business" at the agreed upon time? This could require weekend work. Are we willing/able to do that? UCB is asking each FG to assess how much testing they need to do, so they can plan to be done by Monday for signoff. Talk to your group and see what you think is reasonable. Does signing off on data acceptance clear ExL of responsibility? What does it mean to signoff? (Lena will ask) Also involves lining up DNS changes, etc. What is the mechanism to immediately report issues? SalesForce cutover case. If it’s something you think might affect others, slack the ICs. What time works? noon and aim for 10am.
Coordinate this as part of our testing? No consensus on this. Sample searches to test Primo speed once we get our cutover instances: should we all use the same search terms? one search term that brings lots of results one search term with few results how many searches is enough? 5? 10? 100? Share a spreadsheet so we can see results at a glance? Possible next step: Create a draft sheet then consult with Discovery? Comments from ICs Ask ExL what they advise for testing. (Lynne will ask)
Please invite your EUOS member to your local imp team meeting to keep them informed. Do the already-Almas have a checklist/countdown for go-live? From Marci: The Go Live Readiness checklist is a version of what we sometimes refer to as generally as the Health Checklist. We’ll actually use the form formally two times during the full implementation portion of the project: once as you a readying for Go Live (so around the start of Cutover) and then a second time prior to the official Switch to Support. I have suggested to past projects for them to also use the form earlier on in the project themselves to track progress on what they have learned and completed implementing, and what areas may still need additional review. This helps both sides tremendously as we can work on focusing on earlier determined problematic areas. It’s also easier for your project team when it’s time to formally complete the checklist as it’s been already been “in progress” and could be kept up to date. Questions about Go Live Readiness Checklist and Certifications.
| 30 | Carlo, Tom | Do Health checklist by May 17 for discussion at May 20 ExL meeting and upload to the Completed health checklist folder. Do we need to accommodate for ExL to run each go-live job consecutively or can they be run simultaneously (10 campuses + NZ)? Laurie’s answer about if NZ has to delay go-live: QUESTION: What happens if we were to find a major problem with the NZ data and it couldn't be fixed in time. Could the IZs go live without the NZ? RESPONSE: The NZ is built first so if there are any issues, they will be addressed right away. If there is a major issue, it will be addressed with the highest priority. The IZs could go live even if the NZ isn’t available but they would of course not have access to full NZ functionality such as the AFN (automated fulfillment network). Also, the discovery network scope in Primo would not be available.
QUESTION: Related, what if there is a problem with one IZ's data. Could the NZ and the other IZs go live without them? RESPONSE: Yes
| Campuses will check with their teams on whether a noon go-live time works. | - Gem Stone-Logan to ask on basecamp if NZ has to go live first? Are there other dependencies such as the AFN?
- ICs to invite your EUOS member to your local imp team meeting to keep them informed.
- Campuses will check with their teams on whether a noon go-live time works.
- Lynne E. Grigsby to ask ExL what they advise for go-live testing for performance, particularly Primo. (Lynne)
- Lena Zentall (Unlicensed) to post on Basecamp: Does signing off on data acceptance clear ExL of responsibility? What does it mean to signoff?
|
| 6 | Questions from slack | | | | | | |
| 7 | Other / Homework | | 0 | Tom | | | |
| 8 | Q&A (recurring) | Q&A during the IC meeting as a first stop before asking a question on Basecamp. If it’s time-sensitive, post to slack (IC channel, SILS Chairs are good options) Any issues that we want to seek broader input from other consortia? | TBD | Carlo | | | |
| 9 | Questions for Ex Libris PM (recurring) Post questions in Basecamp as they come up. It’s open 24/7! | Note: We lose in efficiency and we may lose in translation when questions go through the PMs. When topics come up that should logically go to Basecamp to the Ex Libris consultants, invite an IC (or appropriate person) to take point on that issue. | 0 | Lena | | | |
| 10 | Parking lot | | 0 | | UCD Escalation (3/17) [from 5/6] Load and performance testing (If needed) Best practices/guidelines for APIs. Awareness that NA04-NA07 servers are being physically moved to a new location over Memorial Day weekend and there will be a scheduled downtime from May 29 6pm PT to May 30 6pm PT.
| | |
| 11 | | TOTAL | 90/90 | | Review decisions and actions. | | |