Document file name normalization process
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- documentation
Research direction
No files, tests, or entry points are named. First trace how file names are normalized in the repository and identify the dataset-facing behavior; document the steps clearly and determine whether the optional cross-language helper functions belong in this issue.
Written by the indexing model from the issue text.
Description
Tool developers may wish to leverage the datasets from a variety of programming languages -- they will need to know what the steps are to normalize names in order to find matching entries in the dataset. (Another option: for file names that get normalized have both normalized and un-normalized file name entries).
It may be useful to provide pre-written helper functions for various popular programming languages to reduce the burden on users.
- Dominant language
- Python
- Stars
- 20
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Getting set up
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 llnl/dapper
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
-
Update the list of hosted datasets to include v2 versions and correct tags for non-Debian datasetsMay be free again @swest50 claimed this 361 days ago, and no pull request is open. Open
-
Compare files changed in Linux packagesMay be free again @monwen claimed this 394 days ago, and no pull request is open. Open
Similar issues
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
openvinotoolkit/openvino_notebooks#3665 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
docs
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
benchmark-gap
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day