Esri / Esri/solutions-data-dictionary-viewer

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

Open
#57 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
14
Forks
11
PR merge metrics
No merged PRs in 30d

Description

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](https://user-images.githubusercontent.com/50338557/76253037-25ff4180-6207-11ea-8067-2a964aaddd3a.png)
2. Click the field being re-used across multiple asset types (e.g. diameter)
![image](https://user-images.githubusercontent.com/50338557/76253091-3dd6c580-6207-11ea-84c5-8723b0def7c4.png)
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.

Contributor guide

Open the contributing guide

Research direction

Start with the field card reached from a Feature Class's Fields and trace how field aliases are extracted from metadata and the asset package by the mapx script. Clarify whether the completed behavior should show an alias-to-asset-type table or open the corresponding asset-type card; done means the reuse mapping can be understood without searching across asset types.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.