Account information consistency for Galaxy and PEGR

[AliNemat]

Analysis in Galaxy are done by account credentials of [email protected], but we send data to PEGR as [email protected] . So, although we login to Galaxy as [email protected], we tell PEGR the user who sends the information is [email protected] (through JSON dictionary and API key in Galaxy config file).
Suggestions: We may use same account for both tasks (login to Galaxy and communicating with PEGR) to avoid confusions.
Note: PEGR has [email protected] in its database but not [email protected].

[grettadarmstrong]

This seems like a minor point, but I'm glad it was noted and recorded. As we think through the workflow that would entail a user who is downloading and spinning up PEGR for themselves, it would be best if we clarified exactly what role that the pipeline has here. Are we going to tell the user to set up a service account for their labs' pipelines, or the galaxy instance? Is it a contact email address? What makes the most sense in a new deployment? what is the best solution for our deployment?