CUNY Academic Commons

Thanks for sharing, Matt.

I've had a quick look at the documents. Most of them require minor technical fixes. It's likely that the majority of our time will be spent addressing the small subset of items that are more substantial.

Let's go ahead and get a meeting on the calendar to talk about the ARC software. If we're going to be using that software to communicate with TPGi, including letting them know that a specific item has been addressed, then I think we should wait until we've had this meeting and been onboarded before we begin the work of addressing any issues.

After that, we'll need to decide how to divvy up the work. The vast majority of the items have straightforward fixes and are siloed from one another, so we could cleanly divide them up between members of our dev team. But some of them will be larger or will have more interconnection with each other. Ray and Jeremy, I'll be unavailable to catalog these for the next week-and-a-half or so, but perhaps you could spend a half an hour each looking through to identify those items that will (a) require some meaningful technical decisions about how to remediate and/or (b) are related to other items on the list and so should be handled together to ensure a consistent approach. This will help us to decide how the work gets divided between us.