Hi @ewjerome, I just looked into this. Our fetcher (the tool that we run every hour to get Directory updates) consistently runs into an error when it tries to update records for your network, which appears to be related to how your server’s SSL configuration. When I ran a SSL test on your network, I saw a 'This server’s certificate chain is incomplete.` warning: SSL Server Test: openbooks.library.umass.edu (Powered by Qualys SSL Labs). You may want to ask your sys admin to look into and fix this, at which point, I think our fetcher will be able to successfully update records for your network again.
In case it’s helpful, the fetcher call throws a “Runtime.UnhandledPromiseRejection” exception and the error message reads: “Error: unable to verify the first certificate”. This might be helpful for your colleague? node.js - Error: unable to verify the first certificate in nodejs - Stack Overflow
I’m also noticing that your API endpoints include http:// links rather than https:// links for all book URLs: https://openbooks.library.umass.edu/wp-json/pressbooks/v2/books
I suspect you’ll want to switch to force https for all traffic/URLs on your network.