Pelican Project - Mini Update

Good Morning Everyone,

 We have been 100% focused on validating member data and subscription rules for the past 10 days. We have one more night/day left until we are 100% confident that locate request notifications will be identical to the current system for all members.

The Cancel/Correction issue will receive all of our attention (and Pelican’s) starting tomorrow, and I have no doubt we will get to the root of the issue. The problem we are having on our side is that we are unable to replicate the issue as reported by a handful of members. When we create test corrections/cancels, we are seeing the correct notifications (new ticket and the cancel) being sent out (and received in our test members for ftp and email). The current feeling is that it could be something unique to the members that are reporting the inconsistency in cancels. That will be our investigative approach over the next few days when the Pelican team has more people to devote to a thorough look. UPDATE: testing started yesterday - we'll keep you posted

No Response testing was halted due to issues related to the database not being fully loaded and validated. (subscription values). That will resume tomorrow. We do not consider this a potential showstopper, as we have manual ways of contacting members to notify them of No Responses in the system until this module is ready for rollout.

Pre-Registration: The Pelican team identified an issue this morning, where they have no way to prevent pre-registered users from creating tickets once they are in the system. We cannot have Users creating tickets in the 'clean' pre-production environment as it could affect our current validation work and member subscriptions.
We are working on a solution, and will have another update on this issue tomorrow.
UPDATE: solution found. Links to pre-register will go out Friday at the latest.

 As the system itself seems to be operating correctly, and we have found no showstoppers in the data validation (BC and MB are 100% ready and AB is about 97% validated), we are proceeding as a “GO” for cutover on January 31. I am confident that the ticket edit issues and missing pieces will be resolved once we can give it our full attention and work with the individual members who are affected.

Thank you again to everyone for working through the last issues with us, and for your patience with the process.