Rest of Eureka will be in single rfc rather than multiple
German consortium still working on standing up Eureka environment
Cooperative effort, Kirstin can liaison a bit, Craig will try and connect
Current projects
All
Wayne Schneider can generate a dependency graph from Okapi, possibly by area
Okapi raml allows generating some visualizations
Worked from Q CSP 1 list of modules
Can fake out okapi to generate graph of modules even if they aren't installed to get the graph
Q full graph is overwhelming!
built an install file of what okapi thinks you need to run UI and users module by telling okapi wanted to enable users module with simulate=true then okapi will respond with list of what it thinks that module needs based on module descriptors
pinned snapshots to the Q version to get list of requirements and added in stripes core and stripes smart components
okapi doesn't perfectly portray the NPM requirements, have to know
minimal system of stripes with users a bit less overwhelming
surprises: calendar, batch print, circulation, fees fine, etc
add in inventory and it gets a few more things, surprises: SRM, entities links
add in ERM, minor surprises as well
would want to look at minimum graph and start chopping out what shouldn't be there, and move on to other areas
only shows documented dependencies, bugs do get filed for those