Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integrate data from SimaPro into the User Interface #46

Closed
8 tasks done
MichaelScheiderer opened this issue May 18, 2021 · 9 comments
Closed
8 tasks done

Integrate data from SimaPro into the User Interface #46

MichaelScheiderer opened this issue May 18, 2021 · 9 comments
Assignees
Labels

Comments

@MichaelScheiderer
Copy link
Collaborator

MichaelScheiderer commented May 18, 2021

User story

  1. As a salesperson
  2. I need to have an overview of the projects that are available on SimaPro
  3. So that I can choose the one I want to present to my customer

Acceptance criteria

Definition of done

  • Documentation for the feature is done
  • Feature branch has been merged
  • Code has been reviewed by at least one other team member
  • Unit tests are written
@MichaelScheiderer MichaelScheiderer added the feature New feature or request label May 18, 2021
@MichaelScheiderer MichaelScheiderer changed the title Integrate Data from SimaPro into the User Interface Integrate data from SimaPro into the User Interface May 18, 2021
@Waldleufer
Copy link
Collaborator

The basic backend Scaffolding has been done

@Waldleufer
Copy link
Collaborator

The backend has a middleware that does the login to the SimaPro API

@Waldleufer
Copy link
Collaborator

The backend controller can proxy various incoming requests

Waldleufer added a commit that referenced this issue May 18, 2021
Implementation of #47, #48, #49 for Feature #46
SaiVarunVaranasi added a commit that referenced this issue May 24, 2021
regarding #46

Co-authored-by: Martin Wagner <martin.wagner@fau.de>
SaiVarunVaranasi added a commit that referenced this issue May 24, 2021
reagrding #46

Co-authored-by: Martin Wagner <martin.wagner@fau.de>
@Waldleufer
Copy link
Collaborator

If there is only one model available on SimaPro, no drop-down window is shown

@Waldleufer Waldleufer self-assigned this May 28, 2021
Waldleufer added a commit that referenced this issue May 29, 2021
Regarding #46

Co-authored-by: Martin Dürsch <martin.duersch@t-online.de>
@Waldleufer
Copy link
Collaborator

image

🎉

@Waldleufer
Copy link
Collaborator

@olyaee My question now:
Where should the scenarios go? Because they are now just within the same list of data, and we will have to do filtering stuff probably.

Waldleufer added a commit that referenced this issue May 30, 2021
@MichaelScheiderer
Copy link
Collaborator Author

From the glossary:
Scenario: The scenario created by changing default values of a model.

So, if you press on a product/model then it first shows the baseline scenario. Then, when you change a variable it shows a different scenario. So the scenarios should be shown on the details page after selecting a different variable. Was this understandable? 😊

@Waldleufer
Copy link
Collaborator

Yes that is clear to me. Thanks!

Then the next question is: where in the SimaPro data is the information about the variable? Or do we just say scenario 1 scenario 2 for now in the variable Dropdown on the details page? Because as you can see in the screenshot above, the only difference is the _Scenario1, _Scenario2 for now.

@MichaelScheiderer
Copy link
Collaborator Author

MichaelScheiderer commented May 30, 2021

Seems like those informations are still missing. I will clarify that together with the industry partner. They would need to provide this information via SimaPro.
We have the same problem with the categories: "Which Project belongs to which Category? e.g. Generation/Solutions". We talked to the SimaPro Experts, there is no way in SimaPro to tag or categorize the project. The only option will be to use the Project name or a comment field, which you also should be able to access via the API. The plan is to somehow encode this information in plain text in one of those field so its possible to automatically parse it.
For example something like: Categorie:Generation/Products#Name:"Gas Turbines"#Model:XYZ2#Location:Germany
So I guess the Information "which scenario changes which variable" will also be encoded in one of those fields in the future, but its not done yet. I try to find a solution as fast as possible but they didnt reply to my email yet.

For now I think there is no way to correctly connect the projects, except hardcoding them. So I think it would be best to leave it like this until we found the best solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants