BETTER / SEED Connection and BETTER data privacy - Githubissues

SEED-platform / seed

Standard Energy Efficiency Data (SEED) Platform™ is a web-based application that helps organizations easily manage data on the energy performance of large groups of buildings.

Other

107 stars 55 forks source link

BETTER / SEED Connection and BETTER data privacy #4023

Open RDmitchell opened 1 year ago

RDmitchell commented 1 year ago

In the LBL/DOE call today the issue came up about data privacy on the BETTER server.

It occurred to me that to SEED users, it isn't obvious that when they are doing a BETTER analysis, they are actually making a record on the BETTER server, and it stays there.

I think this might be an issue for some users, such as CERL. And potentially others.

Although some users may have accounts on both BETTER and SEED and want the runs that they do in SEED to be part of their BETTER world.

So we might need to do the following:

Add a checkbox in the BETTER API settings area to have the user say whether they want their data to stay stored on the BETTER server. Unchecked meaning they do not
Add funcitonality to SEED that once a BETTER analysis has been completed, the record on BETTER is deleted. This would mean that the report would have to be stored on the SEED side in some format (PDF, who knows) so that we could attach it to a record if

Not sure what the priority of this should be, but we might want to try to address it in the FY 23 Q3?

github-actions[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] commented 10 months ago

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] commented 8 months ago

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] commented 6 months ago

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] commented 4 months ago

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.