NFDI4Energy / NFDI4Energy/SMECS
Systematic test of the extraction capabilities of SMECS
Open
Nobody has claimed this yet.
mid-term
testing
- Dominant language
- Python
- Stars
- 13
- Forks
- 1
- Avg merge
- 22h 24m
- Merged PRs (30d)
- 1
Description
We still need to test SMECS with a large amount of repositories to check where errors occur and which metadata can normally be extracted. Perhaps https://github.com/smutyala1at/automatic-metadata-extraction/tree/main/dataset can be used for that?
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reviewing the linked automatic-metadata-extraction dataset and how SMECS runs extraction across repositories. Run a systematic sample, record where errors occur and which metadata fields are extracted normally, and document the results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100