databrickslabs / databrickslabs/ontobricks

[FEATURE]: Add option to mass exclude unmapped entities

Open
#143 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Python
Stars
377
Forks
69
Avg merge
7h 42m
Merged PRs (30d)
5

Description

Is there an existing issue for this?
  • I have searched the existing issues
Problem Statement

Currently there is a way to exclude unmapped entities in the manual mapping pane in order to allow the knowledge graph to be built. Unfortunately, right now you have to go entity by entity and manually exclude each entity separately. If you are attempting to map a large preexisting ontology like BFO or CCO you will almost certainly have dozens if not hundreds of unmapped entities after an auto map run.

Proposed Solution

Add a button to mass exclude all unmapped entities from consideration for mapping, alternatively, allow the knowledge graph to be built regardless of how many entities from the ontology are unmapped (there was another ticket asking for this solution and it was supposed to be in 0.6 but it didn't make it into the release notes.

Area

Mapping (Manual / SparkSQL)

Additional Context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in the Mapping (Manual / SparkSQL) area, then review issue #40 and the referenced release notes in discussion #96 to understand the prior expected behavior. Determine whether the accepted outcome is a mass-exclude control or allowing graph construction with unmapped entities; done means one chosen behavior works for large sets of unmapped entities.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, spark, sql
Domain
data-engineering
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.