Replace webapollo_user table

bradfordcondon commented 5 years ago

this table doesnt follow great database practices and is challenging so i'm removing it. In it's stead I will create:

An apollo user table , that links a drupal user to apollo login credentials,
A user_organism_instance table, that links an apollo user to an organism-instance.

That user_organism_instance table is a little verbose but.... It cant link to instance because we provide permissions only to a subset of the apollo instance. It cant link to organism because an organism might be theoretically hosted on multiple instances.

Whats the benefit?

UID is no longer incorrectly used
users actually get linked to a Drupal User!
Syncing login credentials across organisms is no longer a problem (see #7)

bradfordcondon commented 5 years ago

backwards compatibility is an issue because a Drupal user is not actually linked to web apollo user entries. We could write a migration that autoassigns identical emails. Otherwise I don't know a migration is possible.

bradfordcondon commented 5 years ago

Issue moved to NAL-i5K/tripal_apollo #9 via ZenHub

NAL-i5K / tripal_chado_datasets

Replace webapollo_user table #48

Whats the benefit?