Uniting Catalog and Genesys-PGR DBs
Currently we have 2 separate DB’s for our projects (Catalog and Genesys-PGR), which are in facts tightly connected between each other. The more we dig into implementation of Catalog’s structure, the more connections and dependencies we find.
Having interconnected data in two separate DBs will require us to duplicate code and to spend time supporting changes in both DBs
There’re the latest observations we’ve got after discussing the mockups of “Partners” and “Descriptors” for Catalog.
Search functionality should be common for two sites: https://projects.invisionapp.com/share/WED8CI5U5#/screens/250699613/comments/86546920
We should have connection between Partner and Accession: https://projects.invisionapp.com/share/WED8CI5U5#/screens/250699613/comments/86544342
We should have connection between Partner and Institute: https://projects.invisionapp.com/share/WED8CI5U5#/screens/250699613/comments/86544634
2 sites should have common administration section: https://projects.invisionapp.com/share/WED8CI5U5#/screens/250699613/comments/86543918
We should use the same crop list in both sites (which is generated dynamically each time) https://projects.invisionapp.com/share/WED8CI5U5#/screens/250699661/comments/86546654
Catalog is supposed to be a subsite of Genesys-PGR, in which case if user is logged in on Genesys-pgr and goes to the Catalog, he will find out that he’s not logged in, though it would seem like he hadn’t gone to a different environment.
Thus, on current level of understanding we think it would be reasonable to merge two DB's together in order to improve the effectiveness and speed of work.