Page Comparison

1.

Severe: Affects Financial Aid Integration

N

Financial Aid Pilot:

• Issues with Workflow

• Peoplesoft college dropped out of pilot

• At CISOA, colleges expresses concerns about marker courses and how it will negatively affect the A&R process.

Parchment

• We may need to deviate away from the original architecture that has been because of the pushback from colleges.

• No new updates this week.

• In process with Allan Hancock for the P2 Teaching College Implementations

• CVC leadership Leadership is investigating a possible new path.

5/31/24/24

2.

Moderate: Users Were Not Able to Authenticate to CVC via Proxy

• CVC and CCCTC

• We escalated this to Mike Caruso at the CCCTC and he advised they were able to log in with no issues.

• After further research, it looks like the CCCTC had some additional IP restrictions and our IP was possibly whitelisted.

• This issue was resolved same day, but we are working with the CCCTC and Parchment to ensure this does not happen in the future.

• CVC and Jason from Parchment are working to investigate to ensure this doesn't happen again in the future.

  Jason has provided the following update about next steps and continuing research with the CCCTC: “I've gotten some additional information on this, the net of which is that this part of our application isn't capable of being configured on a guaranteed static IP. There's work we can do to make it semi-static, meaning it still may change with some, but even so change of the outbound IP can happen for reasons outside our control. 

  A "more static IP" change is not something we can implement immediately, given the holidays and that such a change may impact other users.

  I can't speak to if this was also a risk in the Heroku infrastructure days or not, but I'm slightly concerned as in our current state, as this could happen again based on factors we can't really control.

  So, I have these questions for the Tech Center:

  • Is this a new practice? If so, can it be rescinded until we have time to ensure there's a lesser risk configuration on our side?

  • Can the Tech Center whitelist by fqdn, rather than by IP? On our end, this is the best solution because we can implement what we have in the rest of the platform, which ensures traffic will always be sourced from 

  egress.parchment.com even though the IP addresses assigned to that may change in a way we can't control.

  As an aside, we don't have great logging of this on our side, so normally we'd put a monitor in place that fires the moment we start seeing it. We're not in a position to do that yet.”

1. No new updates this week.

2. The CCCTC 'pushed pause' on this particular element of that security update, but they are unblocked in terms of continuing to make improvements via consistent security-focused deployments. It is something they need to resolve, but that work has just started, and there isn't a firm ETA yet.

3. Donna will either show Parchment how she gets around this in person at the on-site meeting this week OR on the 5/21 CRM.

5/24/24

1.

Weekly Combined Requirements Meeting Notes & Recordings

• We meet every Tuesday to discuss items that need attention, analysis, escalated, or enhanced. All recordings, notes, and next steps can be found on the running combined requirements meeting agenda.

• Next meeting is 6.4.24

https://docs.google.com/document/d/1S3zLxqu6CLDmIO6Eq1YmOlo-gPG_Hwn6-lyaEiTpkQE/edit

5/31/24

2.

Parchment Weekly Sprint Jira Status Updates

Product:

Lane 1: Major Functional and Implementation Blockers

• System time zone for CVC Test and Prod sites PICE-537/Date mismatch on drop date in UI PICE-546  - Verifying with Parchment team that this should be working as expected. 

• Restrict Error Messages on Enrollment Report PICE-542 - Deployment to production pending. 

• Registration Email Errors PICE-544 - Parchment team to document all instances when emails are sent, and which emails are sent in which cases. 

• Discrepancy in UI and Export of Student Enrollment Report PICE-471- identified discrepancy. Further discussion with CVC team needed to determine next steps.

Lane 2: Renewal Enhancements

• Financial Aid implementations  - Next steps to be determined following discussions on marker courses.  

  • BLQ-1064

• Parchment Search Functionality Changes BLQ-1034Parchment will continue to work on the changes required for the new search functionality. The Parchment team continues to update subject mappings as needed.  

• Student Eligibility Checker - Parchment testing in the Banner sandbox. 

  • BLN-729 N2N To Create API Specs, Place on Conf, And Send To Parchment

  • BLN-745 Parchment To Develop Feature Flag To Enable College Rollout Enablement

  • BLN-746 Parchment To Develop Progress Bar

  • BLN-748 Parchment To Develop Ability To Consume eligibilityStatus = and eligibilityStatusReason =

  • BLN-837 Parchment to Add/Display CVC Provided URL To Student Ineligible Page

Lane 3: Prioritized Enhancements and Research

1. Session Management Changes BLQ-1026- Parchment team in planning stages for this work. 

2. Parchment to Provide Technical Requirements for SaaS eTranscripts Compatibility BLQ-1061- Ellucian has advised it will be up to several more weeks before we have information on next steps. 

3. Determine Method to Identify Students Who Exist in the Teaching College Canvas Instance BLQ-572 - Further discussion at CRM and CVC feedback needed. Need to confirm who should have access to the reconciliation report.   

4. Payment Status, Errors, and Reconciliation BLQ-724  - CVC has provided updated language, Parchment work pending.

5. Course Audit Needs to Still Run if the Student Dropped BLQ-1056 - Parchment team working on a way to run course audit for a specific group of students, as well as provide a way for admins to run a check as needed.  

6. Cuesta Variation in Unit Count Across Different Terms- Course Units & Seat Counts

7. BLQ-845 - Additional information from CVC regarding prerequisites is linked to this issue. Parchment team to review and determine next steps. 

8. Add Additional Text To The Drop Email Notification BLQ-1031 - In the work queue. CVC has also provided some additional language edits to be made with this work. 

Show Message in UI for Users When We Get CCCID Invalid Errors | contactInfo API Only

BLQ-1091-Parchment reviewing CVC feedback. Next steps TBD.

5/31/24

3.

eTranscript Implementations & Follow up with colleges

Below is the latest updates on where we are with each college:

• Barstow 5.23.24: Parchment responded and stated they had sent an email early-mid April asking the following. We are ready to enable in production to go live whenever they are ready and advise on the below. We just didn't get a response yet...They need this question answered,""Are they wanting this enabled for all eligible receiver of eTranCA, or only doing this for CVC?"" Amanda responded to email and asked Barstow to respond/advised we can jump on a call if needed. Will flw up net week if no response today."

• Cabrillo CCD - 3.5.24: Emailed Parchment back advising that we are blocked on moving forward with Cabrillo until we have a SaaS solution in place. I will keep them informed with updates.

• Compton CCD - 4.18.24 Blocked for sending based on them being SaaS.

• Feather River CCD (ECA) 4.8.24: Sent cal invite to meet for eTranscripts sending for 4.15. 24.

• Grossmont-Cuyamaca CCD (ECA) - 5.30.24: Sean met with The Grossmont Cuyamaca team this morning to configure XAP Communicator to testing transcript uploads. Currently, only Grossmont College is set for Uploads. He is waiting for the XAP team to enable uploads for Cuyamaca College. Sean provided the paths for Grossmont College’s upload directories in the test environment.

• Marin CCD - 3.21.24: emailed Jon at the college and asked to set up a kickoff meeting to get this process started. No cohort established yet.

• Merced CCD (ECA) 5.24.24: Todd reached out to Merded to flw up. No response. Amanda followed up on 5/28 via email.

• Napa Valley CCD - 4.4.24: Met with Napa and they want to test this week. They plan to be ready for go live by 4.11.24. If I have not heard from them by then, I'll email them to get a status.

• Porterville - Kern CCD: 4.4.24: Met with Maria Braidi, new director, and they are having a meeting in 2 weeks to talk internally to see if they want to break contract with Certree or start picking back up with Parchment again. She will let us know what they decide. If I dont hear from them by May 1, I will folow up.

• Palo Verde CCD - 3.25.24: College emailed me back stating, " I currently use parchment for sending electronically, will this satisfy those requirements perhaps?" Amanda responded back that no, it wont meet the reqs. She asked that I send her some dates of availability. Amanda sent email with date and will schedule when she responds.

• Peralta CCD (ECA) 5.21.24: College and Sean met - they are building this in house. The call was an initial meeting to discuss XAP Communicator Integration with PeopleSoft at Peralta. I outlined, in basic terms, the process of extracting student data from PeopleSoft, creating an ASCII or XML report in the correct eTranscriptCA format, and uploading it via XAP Communicator. I explained that the “lift” to develop a process was on the College(s) as XAP’s IT team doesn’t have expertise in PeopleSoft to assist. They asked about their previous set-up for sending transcripts and I explained that this was managed through integration with Credentials/Parchment.Following the call, Sean sent the Peralta Team all the required implementation resources required including a very detailed sample implementation provided by Los Rios Community College District. The Peralta team will go over the materials and will plan a foll-up meeting.

• San Diego CCD (ECA) 6.3.24: Parchment emailed the college and advised, "Thank you, George! We are working on mapping these directories on the Parchment side. So that our team can complete the parser for the district, we need to have some test students to pull data for review. Who is the best person to work with to obtain the examples below?

• San Francisco CCD 4.22.24: Monika at the college told me she needs a timeframe on how long it takes to set up bc their plan is to explore a timeline in next spring to start this process. I told her the timelines and asked if she wanted to schedule a meeting to discuss details.

• San Joaquin Delta CCD (ECA) 5.28.24: Todd sent the following email to the college: Wanted to follow up with you all about your progress in running the XAP process in Beta and reviewing the resulting samples. Sean, I am hoping you may be able to provide their team assistance if they are not sure how to run the XAP connector, ensure its configuration is completed in Beta, and most importantly that they can process and see these samples. Once that process is complete, Parchment needs the Delta College Team to review the samples produced by the XAP and give us feedback on their formatting and content accuracy. If everything looks good, we're ready for your go live. Please let me know how we can better set a timeline on this XAP sample review in the Test Environment and what the status of running the XAP connector is today to create the samples at Delta College for review.

• San Mateo County CCD - 3.21.24 - Sent email to demellon@smccd.edu to schedule meeting to do a kickoff call. No cohort established yet and they are not a home college.

• Santa Monica CCD - 11.2.23 - Per Mike- hold off on reaching out.

• Shasta-Tehama-Trinity Joint CCD (ECA) - 4.22.24: Courtney from Parchment checked in with the college asking if they had questions regarding the test transcripts that Parchment sent over for your review.

• Sierra Joint CCD - 4.3.24 - College reached out to XAP and asked to start the process for the sending set up. Sean sent out dates/times. Hoever, they responded saying they arent interested in having this conversation based on being a CVC TC bc they are not starting that yet...they advised the following: Our interest is to understand what's possible with eTranscriptsCA beyond accepting electronic transcripts. We'd like to understand more about sending electronic transcripts as well as accepting (and sending?) electronic requests. We are not considering becoming a CVC-Teaching College at the moment, but we are collaborating with Sacramento State on the Placer Center project and sharing transcripts electronically will be important to that effort. Amanda sent email to Sean and Sean suggested dates for them to meet. Sean will schedule once he hears back.

• Siskiyou Joint CCD (ECA) 5.14.24: Met with Siskiyous team and they will have to build the sendinf process in house. Amanda sent them over the eTranscript samples Coast built. They advised they will probably not have this ready to go by the time they go live as a P2 TC, but should not be a problem to be live at the end of the first term. Advised Mickinzie will check in with them every 2-3 weeks to see how things are progressing and monintor for go live readiness from there.

• Solano CCD - 11.14.23 - Parchment sent email to Solano advising they need a status update. The college emailed us back stating: "Yes – our SaaS go-live date is April 8th, 2024. As noted by Amanda, I believe we have Parchment sending on pause until we have our integrations set up for SaaS. Our new timeline to become a “Teaching” College is to be part of the Fall 2024 Cohort. Once SaaS has been implemented with the given timeline, we can revisit our setup for Parchment sending. I apologize if any of these plans have changed, as I am going off my previous meeting notes documented at the time. Parchment responded that they have canceled this project and will pick it back up when they are ready.

• Victor Valley CCD (ECA) 9.16.23: BLOCKED Victor Valley is going to switch to SaaS in April 2024, so we will be placing this one on hold until after that migration.

• West Kern CCD (ECA) 2.19.24: Sent email to Kyle and asked how testing is going/see if they will be ready to go live this week or next.

• West Valley-Mission CCD (ECA) 5.30.24: The college has the XAP communicator installed BUT their servers live at Ellucian so they can't make the updates needed and get us the paths on the TEST and Prod Env until Ellucian does their piece. They are submitting a ticket to Ellucian today. I will escalate with my contact at Ellucian and hopefully we can get all this updated ASAP so we can get you all the paths.

• Yuba CCD (ECA) 4.18.24: They received what State Center did and they showed us what they plan to do to build this in house based on what state center did. They did a demo what what they accomplished so far and the started with edi format, so Sean said only csv or askii. They will go back and re-format. They will email us for another meeting when they have next steps figured out.

• Amanda and Sean to continue reaching out to colleges next week to continue getting them set up on sending and receiving.

Tracking HC and TC transcripts here: https://docs.google.com/spreadsheets/d/1e3Nq1Kt3qACJLqN4nWfmP-mWjdgK8_fSLiQb_ufBjdE/edit#gid=48089342

/wiki/spaces/CVCOEI/pages/1749647361

/wiki/spaces/CVCOEI/pages/1731002371

Weekly Meeting Notes and Action Items will be here each week: https://drive.google.com/drive/folders/12_-PObf7ii0hgvV3g4S-EfWzUamAi8zd

Weekly Status Call Recordings Here: https://drive.google.com/drive/folders/1LF4RbCkYhAdKjPwhoEw2SdArlvo4-u9i

5/24/24

9/14/23

11/9/23

11/13/23

12/10/23

11/20/24

3/5/24

93/1412/2324

113/913/2324

113/1329/2324

124/1016/2324

114/2022/24

35/56/24

35/126/24

35/137/24

35/298/24

45/1631/24

46/223/24

56/63/24

56/63/24

5/724/24

5/828/24

5/1331/24