@PaulW - Yes @jrp62 = Jerry Palardy = Coach Palardy. I appreciate your support of the video series. Glad to hear that they are useful.
Interesting blabber...
A few years ago, when I first attempted to get my VEX teams to use CAD, I brought in a CAD expert to show the kids how itâs done. (Truth be told, although I like working in CAD, I have no professional experience). This guy had done VEX in high school and now used CAD on the job daily. He really knew his stuff and spent an hour showing the kids all about SolidWorks. The only thing he didnât show them was a VEX robot. When asked if he could show us a VEX model, he said something like, âWell, I need to make some updates to my VEX parts library, they are on my other computer, but I can have it ready in a few days.â Wait, whatâŚ?
Seems like you have the same impression of the current parts libraries. And I thought we had made progress. 
As far as I know (and I could be wrong), Onshape is the only CAD app with an official VEX parts library maintained by the company. For all others, the users create and maintain the parts libs. Protobot does have a built-in parts lib, but the app itself is maintained by a user/users; there is no company.
This works when those users are enthusiastic about keeping the libraries updated. However, what frequently happens is that those users move on and no longer support it. Iâm guessing that companies donât maintain the parts lib because they canât make money from it, plus the users are already taking care of it.
Anyway, it would be nice if the parts libs were complete and updated promptly. If there were a way of monetizing that task, it would happen more quickly. Having libraries for a particular competition year is a good idea. In Onshape, it may be possible to do this with the versioning features. The Onshape parts lib is already versioned, but you would need to be able to search by a version name. Something I havenât tried myself.
VEX does release new parts in the middle of the competition year, so minor versions would be needed. I am not sure how often VEX makes discontinued parts illegal, but that would have to be taken into account too. Removing parts from the lib brings challenges to existing models, should be manageable, albeit confusing.
There might be a misunderstanding about what the current Onshape parts lib actually is. Using searching and labeling allows you to find and insert VEX parts quickly. But Onshape is doing more than just providing a label or global handle. Each document returned in a search for âOfficial VEX V5 Libraryâ is a section of the parts library that Onshape created. And someone worked to create each of those. You can open and view any of them, your label has the URLs to them. For instance here is the URL for Sprockets and Chains. I believe that the parts lib is divided into multiple documents to improve performance. It might also have to do with providing more flexibility with versioning and releasing updates. As previously mentioned there is a new âVEX V5 Parts Libraryâ application. That is not trivial; a lot of work went into it. However, if users do not see the value in that, then Onshape will not continue to support it.
Back to the original problems you identified⌠The V5 parts lib is incomplete and is missing some new parts and this yearâs field elements. You are also looking for an IQ parts lib, as well as EXP.
For the V5 parts lib, the thing to do is create a supplemental library (or libraries) and show users how to add it to their VEX V5 Parts Label. As those parts get added to the official lib, they are removed from the supplement.
No quick answer for IQ and EXP, but there may be some good longer-term options. I may be wrong, but I donât think many IQ teams are using CAD. The kids doing CAD with IQ are taking a robotics or STEM class, and CAD is a lesson. So coaches with CAD experience will not see the need for a parts lib, whereas educators would. The good news is that educational institutions have budgets to pay for materials to support their curriculum. If an IQ parts lib were part of an educational package, it could be monetized.
Your idea of âparts assembliesâ is interesting too. Similar concept for the drivetrains lib that is out there; feel free to include it. Word of caution; I have noticed that students who start robotics using pre-existing CAD models sometimes think all robot designs or features are pre-existing. Like, just go into Onshape and find what you want to build. Of course, creating something from CAD is what we really want to see. So keep the parts assemblies generic and just use them to teach concepts.