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

[ENH] Show field re-use mapping on field card #57

Open
avezina opened this issue Mar 9, 2020 · 3 comments
Open

[ENH] Show field re-use mapping on field card #57

avezina opened this issue Mar 9, 2020 · 3 comments

Comments

@avezina
Copy link
Collaborator

avezina commented Mar 9, 2020

Show which field alias is assigned to which asset type to better represent field reuse. (Feedback provided by user of the Data Loading Tools for Water - it was challenging to go back and forth to find which alias is being used for which specific asset type when trying to map a customer's data.)

Workflow could be:

  1. Go to a Feature Classe's Fields.
    image
  2. Click the field being re-used across multiple asset types (e.g. diameter)
    image
    3.a. Show a 2 columns table associating alias and asset type.
    OR
    3.b. Clicking on one of the aliases opens the card for the given asset type using this alias.

It may be challenging to do this since the field alias information is being extracted from the metadata and this information was extracted from the asset package using a script on the mapx. We'd need to discuss how we could potentially do this.

@avezina
Copy link
Collaborator Author

avezina commented Mar 10, 2020

Potentially could be added here - extend the script when generating the metadata files. Specify subtype aliases.
image

@avezina
Copy link
Collaborator Author

avezina commented Mar 10, 2020

@previnWong

@previnWong
Copy link
Collaborator

@avezina I can do the join and lookup on my end since from the breadcrumb I know here you are at when you got to the field card. Unless Ted wants to add it to the CSV directly. Let me know the decision.

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

No branches or pull requests

2 participants