Use context to recognize personal initials and lowercase names
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 67/100
Research direction
Find the validator and augmenter prompt guidance, then compare how each treats short or lowercase names and single-letter initials. Render both prompts and use the supplied synthetic examples to check that context distinguishes names from unrelated letters or words. Done means their guidance is consistent, permitted name labels are preserved without expanding initials, and the examples are documented.
Written by the indexing model from the issue text.
Description
Priority Level
Medium (Annoying but has workaround)
Describe the bug
The validator explicitly drops a single-letter first_name unless a surname follows. This rejects contextual personal initials, such as a first initial in a greeting or signature. The validator and augmenter also lack clear guidance that personal names can be lowercase or short, which is common in informal conversation.
Steps/Code to reproduce bug
Synthetic examples:
First initial: Q.with candidateQ/first_name: the existing surname-following rule directs the validator to drop it.hi sam, can you review this?: capitalization should not determine whethersamis recognized as a personal name.- Contrast with
Set Q = 3.,Grade: A,Length: 4 m,The cat is asleep., andty for helping, where the letters or words do not identify a person.
Expected behavior
Use context rather than capitalization or length alone to judge personal names and initials. Do not require a following surname for a supported personal initial. Keep validator and augmenter guidance consistent, preserve the supplied text without expanding initials, and use existing permitted name labels.
Verify the rendered prompts and document the contextual handling using synthetic examples.
- Dominant language
- Python
- Stars
- 129
- Forks
- 21
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 23
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NVIDIA-NeMo/Anonymizer
-
Clarify date validation for months, years, and partial datesPossibly taken @lipikaramaswamy claimed this 2 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NVIDIA-NeMo/Anonymizer#334 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
NVIDIA-NeMo/Anonymizer#327 ·
Maintainers usually reply within 1 day
-
Replacement-map generation can silently omit a requested entity, causing the rewrite to be marked unavailablePossibly taken @dundysm claimed this 35 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NVIDIA-NeMo/Anonymizer#278 · 2 comments ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
NVIDIA-NeMo/Anonymizer#6 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 54/100
NVIDIA-NeMo/Anonymizer#331 ·
Maintainers usually reply within 1 day
All issues in NVIDIA-NeMo/Anonymizer
Similar issues
-
test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
teramoby/speedle-plus#129 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
btclib-org/btclib-ecc#404 ·
-
verify: just verify runs tools/verify_agents_imports.py (the recipe line was only read, not run)Openneeds-verification
Difficulty 1/5 Under an hour Newbie friendliness 76/100
EchoTools/nevr-runtime#1322 ·
Maintainers usually reply within 1 day
-
changelog investigate
Difficulty 1/5 Under an hour Newbie friendliness 78/100
ramnes/notion-sdk-py#430 ·
-
bug good first issue
Difficulty 1/5 Under an hour Newbie friendliness 91/100
hyeonjoong/debussy#56 ·