CGWP

I now have a fully-operational system that uses ORCID to log a user in (so no passwords are stored in the DB) and restricts them to sections of the site that their role demands. For example, if a user logs in and the role they have is 'editor' they will… Read More

Following up on this post, I now have the ORCID login/log out working reliably, but there's a caveat (below). The javascript solution is to set mode to no-cors, accept json, and include credentials.… Read More

I'm at the point where I need to start thinking about how the nightly update/refresh is going to work. Each night the DB needs to update the data tables with any vetted rows from the edit schema and refresh the materialized views. A good SO post… Read More

I've spent a while working on a user-management strategy. Here's what I've come up with. CGWP will not in any way manage or store passwords for accounts. We will retain only publically-accessible information and rely on ORCID to provide authentication.… Read More