Create New Project Type for Client Demos

appirio-tech / connect-app

Build your next project on Connect with the power of crowdsourcing

https://connect.topcoder.com

44 stars 139 forks source link

Create New Project Type for Client Demos #4325

Open acshields opened 3 years ago

acshields commented 3 years ago

In order to have demo projects with reporting available, we need to create a specific demo project type.

acshields commented 3 years ago

Carrying this over from our Slack conversation... what details do we need to align on for the creation of this demo project type? (reminder: the goal with this project type is to enable Looker reporting in the project... i.e. we can show our internal data, and not accidentally expose any client information).

vikasrohit commented 3 years ago

@acshields do you have mock reports ready in looker?

acshields commented 3 years ago

@vikasrohit - they would be the exact same as the client one today in terms of content. The only difference is that I need the Project ID mapped to one of our internal projects, so the dashboard can be populated with data (that isn't coming from another client's project).

So, how do we move forward for this? Duplicating the dashboard should be easy, but I want to understand how to handle to project ID thing (since this will be a demo project used by marketing, so there will be no real work occurring for it, but we need data to show the reporting).

vikasrohit commented 3 years ago

@acshields we have to duplicate the dashboard and hard code the project id in the looker dashboard itself. We can not and should not do that from the API or front end. So, please copy the dashboard and hard code the project id in it. I am not sure if we can set the projectId at the dashboard level, if we can not do that, we have to replicate each look with hard coded project id.

acshields commented 3 years ago

@vikasrohit - to be clear, here is my understanding:

I need to create a new dashboard specifically for the demo project.
I need to hardcode a Project ID from one of our internal projects (example) so that the dashboard will populate with real data, without exposing any client data.
Step needing clarifying: are we able to map the demo project ID and the project ID containing real data together, or is that the hardcoding to which you are referring?

The backup plan I am considering: We use the demo project as our "project" for the next shape-up round, so that the dashboard for that can be populated with internal data. Make sense?