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
110 stars 55 forks source link

Portfolio Manager Defaults mapping preset -- needs some fine tuning #2120

Closed RDmitchell closed 3 years ago

RDmitchell commented 4 years ago

Expected Behavior

In the Data Mapping screen, when using the Portfolio Manager Defaults mapping present, I thought that the program would generate the same fields names as in previous versions.

Actual Behavior

It seems that some of the SEED Header fields are blank and some are set to variable names, not display names

And this is just a sample file -- I will test with a more complete ESPM file that has 250 fields.

Steps to Reproduce

Instance Information

Instance: dev1 SHA: c97042d2 Org: LBNL Test 200

RDmitchell commented 4 years ago

Instance: LBNL producion SHA: 035748e5 (2.6.1)

In comparison, here is the default mapping for an org (I deleted the mapping as Admin) that doesn't have a previous mapping history image

RDmitchell commented 4 years ago

Link to sample ESPM files https://drive.google.com/drive/folders/1fUjC8WAjckkGsSsSnXsRbAB1ZcdkAXH_?usp=sharing

RDmitchell commented 4 years ago

Importing another ESPM file that is more complete, the program doesn't have default fields for most of the fields in the program.

So I guess for users that already have their ESPM Mapping set up, they should make a new preset, and save it to whatever name they want. Can they save it to the default Portfolio Manager preset and have the program update that? Presumably the answer is yes.

image

axelstudios commented 4 years ago

One somewhat related issue is that if you apply a preset (or manually map the fields) and click Map Your Data without also clicking Save Mappings, and then come back to the mapping page your previous mappings are cleared out

github-actions[bot] commented 3 years 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 3 years ago

This issue has been closed automatically. If this still affects you please re-open this issue with a comment or contact us so we can look into resolving it.