Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Item #

Severity Level

Escalated Y/N

Description/Risk

Owner

Mitigation Strategy

Next Step

Priority

JIRAs

Date

1.

MODERATE: Could affect any college.

Y

Seat Count & Hybrid Courses/Modality Changes: For the past 6 months, we’ve been experiencing issues with how the system is not working correctly when a section is no longer being offered online and how modality changes are not reflecting correctly in the UI.

Parchment has been working on these items along with the CVC’s input.

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLQ-855

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyPICE-398

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyPICE-399

Parchment

  • N/A - code fix has been pushed to production.

  • Testing in progress with CVC.

  • CVC will provide results ASAPnext week to Parchment.

Status
colourRed
titleHigh

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLQ-855

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyPICE-398

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyPICE-399

121/217/2324

2.

Severe: Affects Financial Aid Integration

N

Financial Aid Pilot:

  • Issues with Workflow

  • Peoplesoft college dropped out of pilot

  • Colleague and Banner pilot colleges both have stopped responding

Parchment

  • Workflow issue was resolved by Parchment, but CVC needs to test.

  • We can’t test to prove it’s working until we have a pilot college test with us and they have stopped responding.

  • CVC to reach out again after Jan 1 to all college, as well as determine a new Peoplesoft college to use. CVC brought this hinderance up in the 12/12/23 CVC leadership meeting and next steps are as follows:

    • Need to talk to Chris and Greg for support.

    • Have a conversation with CCCSFAAA leadership and tell them we need their help in piloting.

    • Start including this feature as a P2 implementation requirement.

Status
colourRed
titlehigh

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLQ-1015

121/157/2324

3.

Users Were Not Able to Authenticate to CVC via Proxy

Yes

On Friday, Dec 15th, all student attempts to authenticate to our platform via the proxy seem to be failing. No one was been able to sign in. We've seen 100% failure rate on all attempts from every user who has tried at every college since about 6 AM Friday morning.

CVC reached out to CCCTC support team but they didn’t seem to have any insight into what could be causing this as they have shared that no one else has reported any issues.

However, we kept receiving a 403 Forbidden error message when we try to connect to any college via the Proxy. This is impacting both production and pilot and began failing around the same time on Friday. Whenever a user selects any college where we would normally route them to the appropriate SSO page, we instead are getting this error.

https://search.cvc.edu/users/sign_in (select any college)

  • 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.”

  • The CCCTC rolled back their previous code to help eliminate this issue over the holidays.

  • Once we return in Jan 2024, Parchment will continue to work on this/investigate this further.

Status
colourRed
titlehigh

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLQ-1041

121/217/2324

...

Weekly Project/Product Summary

Item #

Topic

Item Details: Weekly Activity/Decisions

Next Steps

Priority

Important Links & Documentation

Last Update Date

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 1/

9
  • 23/24

Status
colourRed
titlehigh

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

1/12/

15/23Mike is researching

24

2.

Weekly Error Report

  • Attached is the weekly error report.

Status
colourRed
titlehigh

Below is the enrollment report for 1/8 - 1/14. 

https://docs.google.com/spreadsheets/d/18hbBR0JAJUu9Pk9dExovESEZiaXhlhhPf_QX3_EYgaI/edit?usp=sharing

1/14/24

3.

Increase In SBVC Errors

  • We're seeing a lot of failed calls to SBVC over the recent week (e.g., <html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> </body> </html>)I sent an email to the support channel last week but most everyone is currently OOO, I put in a maintenance window until we're able to get eyes on this and have N2N resolve the connection issue?21 failed attempts submitted since 12/18 (including duplicate attempts)

Canvas Solution for ILP Colleges

  • Database access to ILP team today

  • Test environment is not updated for Kern, so will work to get this updated.

  • Development will be done by 12/19/23.

  • Go live in production will happen on 12/19/23.

  • Kern will be configured and will go live.

  • Other colleges can utilize the code, but will need to be configured in the future. CVC to manage this on an ongoing basic.

  • Mike has another meeting to discuss testing and implementation on 12/18/23.

Status
colourRed
titlehigh

1/12/

26/23

24

4.

Financial Aid Integration

  • Chaffey

  • Mt. Sac

  • Long Beach

  • Chaffey - CVC testing with Parchment to see if issue resolved.

  • Mt. Sac - CVC testing with Parchment to see if issue resolved.

  • Long Beach - opted to not participate at this time.

  • CVC is looking to target another Peoplesoft college to participate in the pilot.

Status
colourRed
titlehigh

12/15/23

5.

Canvas Solution for ILP Colleges

  • Database access to ILP team today

  • Test environment is not updated for Kern, so will work to get this updated.

  • Development will be done by 12/19/23.

  • Go live in production will happen on 12/19/23.

  • Kern will be configured and will go live.

  • Other colleges can utilize the code, but will need to be configured in the future. CVC to manage this on an ongoing basic.

  • Mike has another meeting to discuss testing and implementation on 12/18/23.

Status
colourRed
titlehigh

12/15/23

6.

Parchment Weekly Sprint Jira Status Updates

Week of January 8th, 2024:

Lane 1: Major Functional and Implementation Blockers

  • Cuesta Reverse Import Course Units Counts Off BLQ-845 Additional research to be completed. 

  • Financial Aid Integration Workflow BLQ-1015 - On Hold while CVC determines which colleges will be included for next steps.    

  • Banner-Ethos - Course Availability Impacted by Inventory Nightly Import PICF-407 - As of Tuesday, January 9th, Donna (CVC) and Courtney (Parchment) have confirmed that the courses still being hidden for Shasta College are currently transmitting a term code of 2023S which is resulting in the courses being hidden for the Spring 2024 term. 

  • Is Parchment sourcing the Home College FAFSA school code? PICE-513 Creating a new field to store college FAFSA numbers. Additional work to be done to then display the FAFSA number instead of the current FICE number. 

Lane 2: Renewal Enhancements

  • CCPG Overview - BLQ-948 Parchment is adding a new field to store FAFSA code in addition to the ETrans FICE code. Once this field has been added, Parchment will populate the FAFSA code for schools based on the list provided by CVC (Donna). Parchment will also finalize changes to the CCPG when making the change to display FAFSA code instead of FICE code to the learner. 

  • Preferred Name Enhancement BLQ-713 & BLQ-1022  - This has been moved into Production.   

  • Document search result output sorting methods BLQ-979 & BLQ-1008 - Work to begin in 2024.  

Lane 3: Prioritized Enhancements and Research

  1. Drop/Withdrawal and Freeze Date Considerations for Financial Aid Integration Marker Courses | All SIS' and Show Withdrawn Status / First Drop Attempt in Student and Admin Dashboard -  BLQ-1010 and BLQ-988  - Parchment work is still in progress. 

  1. Payment Status, Errors, and Reconciliation BLQ-724  - Researching updates to batch application status to reflect when confirming payment processing to the teaching college may have had an error. 

  1. Session Management Changes BLQ-1026 and  UI Changes for Open Registration Dates and Inventory Imports BLQ-967 - Reviewing to determine next steps. 

  1. Enhanced Workflow for Late Enrollment into Courses with Prereqs & Canceling Applications Where a Prereq Check or Person Match Check is Pending and the Course Has Started BLQ-1018 and BLQ-1027 - No change. 

  1. Need Address Validation on the AER Form BLQ-1029 - Next steps to be determined.

  1. North Orange CCD - Multiple Payment Posts PICE-504 - Parchment research ongoing. 

  1. Available Seat Filter Logic Change: Home College Courses Should Always Display Regardless of the Open Registration Date BLQ-1033 - In the queue. 

Make Text Updates To Email "CVC Exchange: Request to use financial aid BLQ-1028- In the queue. 
  1. Add synch/asynch (format) field to downloadable sections reports BLQ-989 - Parchment team is working on getting the Delivery Method added to the CSV download for Sections Report. 

Add Language for DSPS Accommodations BLC-107- In Parchment queue. Fraud Score % Change And Start Sending New Reports BLQ-954- Parchment to provide additional information on the public API documentation to determine next steps. 

Parchment Deliverable Pending:

  • Enrollment Report Showing Error Messages BLQ-286  - Accessibility review is complete, report to be made available soon. 

  • Complete application/integration diagram - BLQ-673 Diagram to be shared with CVC when available.. 

Additional Notes: 

These CVC Q3 priorities are still being discussed by the Parchment team. Further details will be shared as they are determined. 

Status
colourRed
titlehigh

12/21/23

7.

eTranscript Implementations & Follow up with colleges

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

  • Barstow 10.25.23: Sean and college had a meeting to setup XAP for sending and they are currently finishing up with Parchment for testing the sending. I emailed the Parchment team so they can advise next steps.

  • Cabrillo CCD - 7.12.23: No cohort established yet. They are going to move to Saas....so it will be awhile before we can get them set up for sending. When their cohort is established, then Amanda to reach back out to them to start sending process. Only will do this though when they have successfully migrated to SaaS.

  • Compton CCD - 12.14.23 - Compton reached out and asked that we send over the XAP contract. Sean did so. They are ready to kickoff again. Amanda responded and said that I can schedule a call to go over sending and receing again when they are ready. Will wait to hear back and then will schedule.

  • Copper Mountain CCD (ECA) - 11.21.23 College responded with the following: Currently, we are still working on Colleague's exported file. Some fields were hard coded so we had to create data fields in Colleague to save information such as the Accreditation and FERPA information. This week we will work on including the student's courses and grades. We are making progress.

  • College of the Desert CCD (ECA) 12.18.23: Parchment delivered the sample transcripts to the college today. Parchment asked that the college let them know when they are done reviewing/testing so we can resume with next steps.

  • El Camino CCD (ECA) - 12.6.23 - Live in production for sending.

  • Feather River CCD (ECA) -11.2.23 - Mike advised that we need to reach out now because they are working on phase 1. AManda to reach out Monday Nov 6.

  • Grossmont-Cuyamaca CCD (ECA) - 11.2.23 - Amanda is waiting on Parchment to provide a list of what colleges are on robo. If they are on robo, then we need to hold off from starting.

  • Imperial Valley CCD (ECA) -10.25.23 - sent email to Melody and Don asking for a status update. They advised that they are now a live TC." I have circled back to Jeff about the final step needed. We have the configuration ready in both PROD and TEST to run the process and are successfully generating the XML files needed. We are at the point now where we need to move the files to a location for Don to access via SFTP, or move them to the Windows server on our end, so that Don can wrap up his piece in setting up the process to send to XAP when present. Jeff has requested that I look into a Banner baseline functionality in SHACTRL to map where XML transcripts are sent before we settle on a cron job or other external method. We are so close! Will flw up again Nov 15th if no response.

  • Long Beach CCD (ECA) 10.24.26 - sent email to Kyne to see where they are and to see if they are ready to go live. If no response by mid Nov, will flw up again.

  • Marin CCD - 5.25.23 - emailed Jon at the college and provided dates/times for us to meet to start going over the sending process for eTranscripts. Will schedule when he responds. But if he doesnt respond, no need to follow up for several months out since they have not established a cohort yet.

  • Merced CCD (ECA) 12.11.23: Parchment met with college and the college needs to review the new batch of samples after the PROD/INT refresh and share feedback when available. Parchment needs to notify the college when a new sample batch is ready for your review.

  • Napa Valley CCD - 12.14.23 - We now have the greenlight to reengage with the college to become a receiving college. AManda working with Alison to get contact names.

  • Palo Verde CCD - 11.2.23 - Mike said to go ahead and email them to advise them to get set up now bc they will benefit when they start because of the no fee module with Parchment.

  • Peralta CCD (ECA) 11.30.23: Sean and I met with Peralta and went over everything they need to do in order to build this in house. Amanda to touch base with then again on Jan 29 to see how things are progressing.

  • Riverside CCD (ECA) 12.11.23 - College reached out and asked Sean to send me transcripts for testing.Sean sent examples to the college."

  • San Diego CCD (ECA) 11.2.23 - Mike said to go ahead and email them to advise them to get set up now bc they will benefit when they start because of the no fee model with Parchment.

  • San Francisco CCD - 3.30.32 - live for receiving. Holding off on sending process until they are starting their implementation cohort.

  • San Joaquin Delta CCD (ECA) 12.18.23: Parchment sent out the following email to the college: Our team is working on samples, but has noted we've not received the directory path from Robo to your XAP directory. Once we have this info we can generate your samples. Can you share that info today perhaps if it is readily available now, or tell us when we might expect it with the holidays fast approaching?

  • San Mateo County CCD - 11.2.23 - Per Mike/Donna hold off on reaching out to them.

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

  • Shasta-Tehama-Trinity Joint CCD (ECA) -11.2.23: Met with Shasta and Mike and went over options. College is planning to go parchment for sending. They need to meet internally to get all items squared up and then will reach out to me and Mike for when they are ready. From there, I'll send an email and cal invite to Parchment to get a call scheduled.

  • Sierra Joint CCD - 11.2.23- no cohort established, hold off on sending until then.

  • Siskiyou Joint CCD (ECA) 11.2.23 - Per Mike, Amanda needs to reach out now.

  • 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 revist 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.

  • South Orange County CCD (ECA) 12.11.23: The XAP functionality is deployed in production. The college now needs to update the WS_Customs file on the "robo", Windows Server 2019 machine, and then stop and start the 2 services to be able to populate that new field.

  • Victor Valley CCD (ECA) 9.13.23 - Heard from Dr. Henry and he advised that: "We finalized our ethos UAT and Production testing with Logan Murray in mid-August and are set for the next steps in the transcript implementation phase 1. I hope to meet with you for a quick chat on 1st steps. In the meantime, I will conduct a meeting for the VVC team to outline steps preliminary including a scheduling visitation with Chaffey to to discuss best practices. Amanda scheduled meeting for 9.18.23.

  • West Hills - 11.20.23 - Parchment advised they are on the Feb kickoff timeframe. Mike advised that works fine. Amanda to follow with Parchment in Jan to ensure still on track.

  • West Kern CCD (ECA) 11.2.23 - Mike advised Amanda to reach out to them now to advise Parchment plan for 2025 - it might save them time and effort.

  • West Valley-Mission CCD (ECA) 7.12.23 - Sent flw up email to college to check in on how things are progressing. They dont have a cohort established yet, so if no response follow up in end of Aug.

  • Yosemite CCD (ECA) 12.11.23 - College reached out saying they;ve made amazing progress but have run into an error they need our help with. I sent them mine and Sean's schedule this week and will schedule the meeting when they respond.

  • Yuba CCD (ECA) 11.21.23 - College responded and advised they are wrapping up implementation of superglue for the application, and will be transitioning to this project soon. I’m going to review the documentation we received back in May, and discuss it with Sonya and our IT team. I’ll reach out when we have questions/are ready to discuss. Amanda will reach out again in Jan 2024 to check status if no response.

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

Status
colourRed
titlehigh

Status
colourPurple
titleIn Process

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

12/15/23

Active Production Issues

JIRA, Description, and Status

Priority

Created Date

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyPICE-399

Status
colourRed
titlehighest

3/11/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyPICE-398

Status
colourRed
titlehighest

3/11/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyPICF-338

Status
colourYellow
titleMEDIUM

4/26/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyPICE-451

Status
colourYellow
titlemedium

7/26/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyPICE-471

Status
colourYellow
titlemedium

9/14/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyPICE-487

Status
colourYellow
titlemedium

10/17/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyPICF-388

Status
colourYellow
titlemedium

10/17/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyPICE-494

Status
colourYellow
titlemedium

11/9/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyPICF-402

Status
colourYellow
titlemedium

11/13/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyPICF-401

Status
colourYellow
titlemedium

11/13/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyPICF-407

Status
colourRed
titlehighest

11/20/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyPICF-408

Status
colourYellow
titlemedium

11/20/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyPICE-504

Status
colourRed
titlehighest

11/30/23

Parchment Weekly Sprint Jira Status Updates

Lane 1: Major Functional and Implementation Blockers

  • Cuesta Reverse Import Course Units Counts Off BLQ-845 Additional research to be completed. 

  • Financial Aid Integration Workflow BLQ-1015 - On Hold while CVC determines which colleges will be included for next steps.    

  • Banner-Ethos - Course Availability Impacted by Inventory Nightly Import PICF-407 - As of Tuesday, January 9th, Donna (CVC) and Courtney (Parchment) have confirmed that the courses still being hidden for Shasta College are currently transmitting a term code of 2023S which is resulting in the courses being hidden for the Spring 2024 term. 

  • Is Parchment sourcing the Home College FAFSA school code? PICE-513 Creating a new field to store college FAFSA numbers. Additional work to be done to then display the FAFSA number instead of the current FICE number. 

Lane 2: Renewal Enhancements

  • Financial Aid implementations  - On Hold while CVC determines which colleges will be included for next steps.    

  • CCPG Overview - BLQ-948 Parchment is adding a new field to store FAFSA code in addition to the ETrans FICE code. Once this field has been added, Parchment will populate the FAFSA code for schools based on the list provided by CVC (Donna). Parchment will also finalize changes to the CCPG when making the change to display FAFSA code instead of FICE code to the learner. 

  • Preferred Name Enhancement BLQ-713 & BLQ-1022  - This has been moved into Production.   

  • Document search result output sorting methods BLQ-979 & BLQ-1008 - Work to begin in 2024.  

Lane 3: Prioritized Enhancements and Research

  1. Drop/Withdrawal and Freeze Date Considerations for Financial Aid Integration Marker Courses | All SIS' and Show Withdrawn Status / First Drop Attempt in Student and Admin Dashboard -  BLQ-1010 and BLQ-988  - Parchment work is still in progress. 

  2. Payment Status, Errors, and Reconciliation BLQ-724  - Researching updates to batch application status to reflect when confirming payment processing to the teaching college may have had an error. 

  3. Session Management Changes BLQ-1026 and  UI Changes for Open Registration Dates and Inventory Imports BLQ-967 - Reviewing to determine next steps. 

  4. Enhanced Workflow for Late Enrollment into Courses with Prereqs & Canceling Applications Where a Prereq Check or Person Match Check is Pending and the Course Has Started BLQ-1018 and BLQ-1027 - No change. 

  5. Need Address Validation on the AER Form BLQ-1029 - Next steps to be determined.

  6. North Orange CCD - Multiple Payment Posts PICE-504 - Parchment research ongoing. 

  7. Available Seat Filter Logic Change: Home College Courses Should Always Display Regardless of the Open Registration Date BLQ-1033 - In the queue. 

  8. Make Text Updates To Email "CVC Exchange: Request to use financial aid BLQ-1028- In the queue. 

  9. Add synch/asynch (format) field to downloadable sections reports BLQ-989 - Parchment team is working on getting the Delivery Method added to the CSV download for Sections Report. 

  10. Add Language for DSPS Accommodations BLC-107- In Parchment queue. 

  11. Fraud Score % Change And Start Sending New Reports BLQ-954- Parchment to provide additional information on the public API documentation to determine next steps. 

Parchment Deliverable Pending:

  • Enrollment Report Showing Error Messages BLQ-286  - Accessibility review is complete, report to be made available soon. 

  • Complete application/integration diagram - BLQ-673 Diagram to be shared with CVC when available.. 

Additional Notes: 

These CVC Q3 priorities are still being discussed by the Parchment team. Further details will be shared as they are determined. 

Status
colourRed
titlehigh

1/12/24

5.

eTranscript Implementations & Follow up with colleges

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

  • Barstow 1.9.24: Parchment advised, "I checked in with the PM for Barstow, and they have decided to add an SSO component to their set up alongside the work being done for XAP. I am being told that from a technical perspective, we are ready to move XAP to production for go live. That being said, the school is wanting to wait to make those changes to production until the SSO work is also ready to be migrated. The team is hopeful they will go live in the next few weeks.

  • Cabrillo CCD - 7.12.23: No cohort established yet. They are going to move to Saas....so it will be awhile before we can get them set up for sending. When their cohort is established, then Amanda to reach back out to them to start sending process. Only will do this though when they have successfully migrated to SaaS.

  • Compton CCD - 1.9.24: Met with Compton to go over receiving. They have to run everything past the board and so they will do so in Feb for an approval go live. Until then, we can go ahead and set up test accounts and get them in beta. Once they send questionnaires back, Sean will set up users and I'll reach back tou to schedule call. Amanda to talk to Mike about SaaS solution for eTranscripts and let them know.

  • Copper Mountain CCD (ECA) - 1.8.24: Sent email to college to check on status and where they are and ask that they provide an update. They advised, "We are making progress on the exported transcript file from Colleague. We have completed Row 08C - 'Term Identification Section' from the data dictionary. This week will start analyzing and adding Row 08E- Student's Course Detail Segment to the electronic transcript." Amanda advised she will touch base at beginning of Feb.

  • College of the Desert CCD (ECA) 1.11.24: Sent email to Parchment and college to get status and next steps.

  • Feather River CCD (ECA) -11.2.23 - Mike advised that we need to reach out now because they are working on phase 1. Amanda to reach out Monday Nov 6.

  • Grossmont-Cuyamaca CCD (ECA) - 1.8.24: Sent email to college to get a kickoff meeting started and scheduled.

  • Imperial Valley CCD (ECA) -1.8.24: Sent email to college and asked for a status. They are ready to go live they said. Amanda coordinating a final zoom call for go live date.

  • Long Beach CCD (ECA) 1.11.24: Emailed Kyne to see if he's ready for go live and asked if he wanted to jump on a call.

  • Marin CCD - 5.25.23 - emailed Jon at the college and provided dates/times for us to meet to start going over the sending process for eTranscripts. Will schedule when he responds. But if he doesnt respond, no need to follow up for several months out since they have not established a cohort yet.

  • Merced CCD (ECA) 1.11.24: Sent email to college and Parchment to check status.

  • Napa Valley CCD - 1.10.24: Emailed atorres@napavalley.edu, malopez@napavalley.edu, brodriguez@napavalley.edu, jcota@napavalley.edu, anrmail@napavalley.edu and asked for a kickoff call. Scheduled meeting for 1.23.24.

  • Palo Verde CCD - 1.11.24: Sent email to Shelley requesting a call to start set up for etranscripts receiving.

  • Peralta CCD (ECA) 11.30.23: Sean and I met with Peralta and went over everything they need to do in order to build this in house. Amanda to touch base with then again on Jan 29 to see how things are progressing.

  • Riverside CCD (ECA) 1.11.24: Nicholas responded that they are pretty much ready to go live. Sean checked on his end and they are all set there for when they go live. I advised to let me know when they are going live and I will schedule a meeting with A&R to train them.

  • San Diego CCD (ECA) 1.11.24: Reached out to the college to get a call scheduled to get this in place. They responded with some availability and I will schedule when others respond, as well.

  • San Francisco CCD - 3.30.32 - live for receiving. Holding off on sending process until they are starting their implementation cohort.

  • San Joaquin Delta CCD (ECA) 1.4.24: Parchment sent out the following email to the college: I am following up on your sample generation. Our team noted we've not yet received the directory path from Robo to your XAP directory. Once we have this info we can generate your samples.Can you share that info at your earliest convenience, or confirm when we may expect this information?

  • San Mateo County CCD - 11.2.23 - Per Mike/Donna hold off on reaching out to them.

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

  • Shasta-Tehama-Trinity Joint CCD (ECA) -1.11.24: Becky emailed me back and said they are ready to proceed. I asked her to make sure she and I are on the same page with me reaching out to Parchment and if she confirms yes, I'll get that process started.

  • Sierra Joint CCD - 11.2.23- no cohort established, hold off on sending until then.

  • Siskiyou Joint CCD (ECA) 11.2.23 - Per Mike, Amanda needs to reach out now.

  • 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 revist 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.

  • South Orange County CCD (ECA) 1.11.24: Sent email to Courtney at Parchment advising that we were advised that Irvine and Saddlebacl went live and no one told us. And, looks like Irvine is working fine but saddleback is having issues. Requested a meeting with Courtney.

  • Victor Valley CCD (ECA) 9.16.23: 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 Hills - 1.9.24: Melissa from Parchment said there is a kickoff call scheduled for Feb 21.She sent over invite to me and Sean for kickoff.

  • West Kern CCD (ECA) 1.16.24: Taft is ready to go live but wants to test first. I emailed them back advising that we should meet to discuss testing. Sent him mine and Sean's availability and will schedule when he responds.

  • West Valley-Mission CCD (ECA) 11.2.23 - Per Mike - hold off since they dont have a cohort established.

  • Yosemite CCD (ECA) -1.16.24: Received the following update from the college: "The setup of eTranscripts is going well. Here is what we have accomplished so far…. Successfully produced a flat file that is accepted by XAP Successfully transmitted an electronic transcript from MJC to Columbia Successfully transmitted several electronic transcripts from MJC to Chabot College Here is what we are currently working on…. Data remediation surrounding grade notations Continued Beta testing with MJC Enrollment Services and Columbia Admissions & Records It is our goal to have all data remediation and Beta testing completed by end of January. We will keep you updated on our progress.

  • Yuba CCD (ECA) 1.11.24: Sent email to Yuba to ask status of set up and how things are progressing.

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

Status
colourRed
titlehigh

Status
colourPurple
titleIn Process

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

1/12/24

Active Production Issues

JIRA, Description, and Status

Priority

Created Date

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyPICFPICE-406399

Status
colourYellowRed
titlemediumhighest

3/11/26/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyPICFPICE-416398

Status
colourYellowRed
titlemediumhighest

123/1011/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyPICF-420338

Status
colourYellow
titlemediumMEDIUM

124/1826/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyPICFPICE-418451

Status
colourYellow
titlemedium

127/1426/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyPICE-512471

Status
colourYellow
titlemedium

129/14/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyPICE-513487

Status
colourYellow
titlemedium

1210/1817/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyPICEPICF-510388

Status
colourRedYellow
titlehighmedium

1210/1217/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyPICE-514494

Status
colourRedYellow
titlehighmedium

1211/209/23

Q2 Sprint Priority Items

Legend

Status
titleBacklog
= Prioritized, Development Not Started

Status
colourBlue
titlein Progress
= In Development/Status

Status
colourBlue
titleIn Testing

...

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyPICF-402

Status
colour

...

Yellow
title

...

Status
colourBlue
titleLow

...

Status
colourRed
titleHigh
= High Priority

Jira, Description, and Status

Priority

Component

Date Started

Date Completed

medium

11/13/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyPICF-408

Status
colourYellow
titlemedium

...

11/20/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
key

BLC

PICE-

129

504

Status
colourRed
title

High

highest

idP/EPPN

4.27.

11/30/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
key

BLQ

PICF-

891

416

Status
colour

Red

Yellow
title

High

Product Maintenance

4.1.23

10.26.

medium

12/10/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
key

BLQ

PICE-

920

512

Status
colour

Red

Yellow
title

Highest

Financial Aid Integration

2.22.

medium

12/14/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
key

BLQ

PICE-

952

513

Status
colour

Red

Yellow
title

Highest

Financial Aid Integration

3.28.

medium

12/18/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
key

BLQ

PICE-

972

510

Status
colourRed
title

High

Financial Aid Integration

6.8.

high

12/12/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
key

BLQ

PICE-

8551.18.

514

Status
colourRed
title

High

Product Maintenance

high

12/20/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
key

BLQ

PICE-

77912/20/23

519

Status
colourRed
title

High

System Enhancement

8.4.23

high

1/12/24

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
key

BLQ

PICE-

845

518

Status
colour

Yellow

Red
title

medium

System Enhancement

7.26.22

12/21/23

high

1/5/24

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
key

BLN

PICE-

380

517

Status
colour

Yellow

Red
title

medium

SIS/Sandbox

3.21.23

12/19/23

high

1/4/24

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
key

BLN

PICE-

675

520

Status
colour

Yellow

Red
title

medium

Reverse Import

5.17.23

high

1/11/24

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
key

BLN

PICF-

670

423

Status
colour

Red

Yellow
title

high

Person Match

5.8.23

12/19/23

Jira LegacyserverSystem JIRAserverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997keyBLN-664

medium

1/11/24

Q2 Sprint Priority Items

Legend

Status
titleBacklog
= Prioritized, Development Not Started

Status
colourBlue
titlein Progress
= In Development/Status

Status
colour

...

Blue
title

...

eTranscripts

...

3.2.23

...

In Testing
= In Review or Testing

Status
colourGreen
titleDONE
= Finished/Closed

Status
colour

...

Blue
title

...

Error Handling

...

7.5.23

...

Low
= Low Priority

Status
colourYellow
titlemedium
= Medium Priority

Status
colourRed
title

...

ASSIST File

...

High
= High Priority

Jira, Description, and Status

Priority

Component

Date Started

Date Completed

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLNBLC-730129

6.8

Status
colourRed
titlehigh

Program Code

High

idP/EPPN

4.27.23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLNBLQ-280920

4

Status
colourRed
titlehighest

Student Eligibility Checker

Highest

Financial Aid Integration

2.22.23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLQ-673

Documentation

12.3.21

952

Status
colourRed
titleHighest

Financial Aid Integration

3.28.23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLQ-948972

Status
colourRed
titleHigh

Financial Aid Integration

36.8.2112/14/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLQ-976

Financial Aid Integration

6.12

855

Status
colourRed
titleHigh

Product Maintenance

1.18.23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLQ-977

Financial Aid Integration

6.12.

845

Status
colourYellow
titlemedium

System Enhancement

7.26.22

12/21/23

6.12

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLQ-978

Financial Aid Integration

-ca6b48c5c997
keyBLN-675

Status
colourYellow
titlemedium

Reverse Import

5.17.23

11/30/

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLQ-995

Emails

8/10/23

BLN-664

Status
colourYellow
titlemedium

eTranscripts

3.2.23

11/7/

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLQ-961

CSU/UC Student Management: Route Appropriately

10/24/23

BLN-727

Status
colourYellow
titlemedium

Error Handling

7.5.23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLQ-1010991

10/10/

Status
colourYellowRed
titlemedium

Financial Aid Integration

high

ASSIST File

7.24.23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLQBLN-713280

10/10/

Status
colourRed
titlehigh

Preferred Name

highest

Student Eligibility Checker

4.22.23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLQ-1009673

Status
colourYellow
titlemedium

Email Content

10/3/23

10/25/23

Documentation

12.3.21

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLQ-988977

Status
colourYellow
titlemedium

Admin Panel/Reporting

10/10/Financial Aid Integration

6.12.23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLQ-997978

Status
colourYellow
titlemedium

Prerequisites UI Messaging

10/10/23

12/11/Financial Aid Integration

6.12.23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLQ-9801010

Status
colourRedYellow
titlemediumhighest

Financial Aid Integration

10/1110/23

11/17/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLQ-286713

Status
colourBlueRed
titlelowesthigh

AccessibilityPreferred Name

10/1210/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLQ-724988

Status
colourRedYellow
titlehigh
Payment Processor
medium

Admin Panel/Reporting

10/10/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLQ-1015286

Status
colourYellowBlue
titlemediumlowest

Financial Aid IntegrationAccessibility

10/1612/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLQ-1016724

Status
colourRed
titlehigh

API Payment Processor

10/16/2312/1410/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLCBLQ-1331015

Status
colourYellow
titlemedium

API Financial Aid Integration

910/2816/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLC-134133

Status
colourYellow
titlemedium

API

9/28/23

10/12/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLN-686683

Status
colourRed
titlehigh

Preferred Name

10/10/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLN-685765

Status
colourRed
titlehigh

Preferred NameCensus Date Issue

10/1016/23

10/31/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLNBLQ-681520

Status
colourRedBlue
titlehighLOw

Preferred NameRedirect

10/10/2312/19/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLN-682752

Status
colourRed
titlehigh

Preferred NameWaitlist

10/1613/23

12/19/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLN-684771

Status
colourRed
titlehigh

Preferred NameSeat Counts

10/1016/23

12/11/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLN-683784

Status
colourRed
titlehighhighest

Preferred NameReverse Import

1011/1017/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLN-761789

Status
colourYellowRed
titlemediumhighest

DocumentationScript update LACCD

10/11/2312/1917/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLN-765730

Status
colourRed
titlehigh

Census Date Issue

10/16Program Code

7/6/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLQ-1011989

Status
colourYellow
titlemedium

Error Messages

10/11/23

11/2/23

Sync/Asynch

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLQ-5201036

Status
colourBlueYellow
titleLOwmedium

RedirectUI Language update

1011/2321/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLNBLQ-7521037

Status
colourRedYellow
titlehighmedium

WaitlistAdmin Panel

1011/1328/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLNBLQ-771979

Status
colourRed
titlehighhighest

Seat CountsSearch

1006/1612/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLNBLQ-7841022

Status
colourRedYellow
titlehighestmedium

Reverse ImportPreferred Name

1110/1724/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLNBLC-789129

Status
colourRed
titlehighesthigh

Script update LACCDEPPN

1104/1727/23

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLN-802803

Status
colourRedYellow
titlehighmedium

Sandbox

12/19/23

1/2/24

Jira Legacy
serverSystem JIRA
serverId3bc2d1ff-b4f9-313a-8d84-ca6b48c5c997
keyBLCBLN-136775

10/26/23

Status
colourRedYellow
titlehigh

Admin Panel Guide

medium

UI Language update

11/18/23

Quarterly Dates

CVC Quarterly Dates

Parchment Quarterly Dates

N2N Quarterly Dates

Q1: July 1-Sept 30

Q2: Oct 1-Dec 31

Q3: Jan 1-March 31

Q4: April 1-June 30

Q1: Jan 1-March 31

Q2: April 1-June 30

Q3: July 1-Sept 30

Q4: Oct 1-Dec 31

Q1: Jan 1-March 31

Q2: April 1-June 30

Q3: July 1-Sept 30

Q4: Oct 1-Dec 31