Can Boards handle interactive mapping against an existing dataset, or is an external UI better?

Server (Hub) / Explorer
1

I’m trying to work out whether EasyMorph Boards can handle a particular human-review scenario, or whether I should use Boards only for issue management and build a separate UI for the actual mapping step.

Scenario
I have incoming data from multiple sources where a key field is inconsistent — in my case drug names, but the question is really about master-data mapping in general.

Example raw values:

  • amox 500mg caps
  • AMOXICILLIN CAPS 500MG
  • Amoxicillin 500 mg capsules

I already have, or plan to maintain, an existing reference dataset of normalized values that I want users to map against.

What I want to do

  1. EasyMorph processes incoming data.
  2. Any unmatched or low-confidence values are surfaced for human review.
  3. The reviewer should be able to choose the correct value from an existing dataset of canonical values.
  4. That mapping should then be stored and used in later runs.

So the main question is not about raising issues in general — I understand Boards can do that — but about the actual mapping interaction.

Questions

  • Can Boards support a workflow where a user reviews an unmatched value and maps it to a value from an existing lookup/reference dataset?
  • If yes, can that be done in a practical way when the reference list is fairly large?
  • Is there any built-in searchable/selectable control for choosing a match from an existing dataset, or would this effectively mean editing a dataset manually?
  • Has anyone used Boards + Dataset Editor for this kind of “map source value to reference value” workflow?
  • If not, is the recommended pattern to let EasyMorph identify the exceptions, but use an external app/UI for the actual match selection and then write the approved mappings back to a dataset or database?

I’d be grateful for any examples, screenshots, or recommended patterns from people who have built something similar in EasyMorph.

2

Yes, you can handle it with Explorer (Boards). From the user perspective, it will work as follows:

  1. The user opens a list of not matched names from an issue.
  2. In the list, the user clicks a value and selects the "Pick standard name" command.
  3. The command opens a new asset with a list of standard names similar to the clicked one
  4. In that list, the user clicks a standard name and selects the "Add as new mapping" command.
  5. The user repeats steps 2-4 for each not matched item.

Here is how to configure it:

  1. Create an asset that simply displays the contents of the dset file provided via a parameter - it will have just 1 action - Import dataset.
  2. Before creating an issue, export the result into a .dset file (e.g. not-matched.dset).
  3. When you create an issue, attach to it the asset with non-matched.dset as a parameter. Setting the file name via a parameter allows multiple users to work with different lists of non-matched names simultaneously as each of them can work with a different file.
  4. In the asset, create a command "Pick standard name" that opens another asset "Suggested mappings" and passes the clicked value as a parameter.
  5. In the asset "Suggested mappings":
    • List all the canonical (standard) names from your mapping table, add a column with the clicked value (so you have pairs of suggested mappings).
    • Using the fuzzy matching in the "Match action", filter only standard names that are similar to the not matched value.
    • Create a command "Add as new mapping" that adds a row to the mapping table.
3

Thank you for the very helpful response. I shall be certain to give it a go. What if there is no fuzzy/suggested mapping in the database? Is there a way to add some sort of other match or would that have to be done in another way?

4

You can use the fuzzy matching mode in the "Match" action in EasyMorph.