Improve dataset card: Add paper link, metadata, and description for MULocBench

#1
by nielsr HF Staff - opened
Files changed (1) hide show
  1. README.md +17 -3
README.md CHANGED
@@ -1,3 +1,19 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
  ## 1. Downloads
2
 
3
  Please download the benchmark from https://huggingface.co/datasets/somethingone/MULocBench/blob/main/all_issues_with_pr_commit_comment_all_project_0922.pkl
@@ -17,8 +33,6 @@ with open(filepath, 'rb') as file:
17
  print(f"{featurename}: {e_iss[featurename]}") # print feature_name: value for each issue
18
  ```
19
 
20
-
21
-
22
  ### 3. Data Instances
23
  An example of an issue is as follows:
24
 
@@ -37,4 +51,4 @@ ass_file_loc: (list) - Runtime-file location information.
37
  other_rep_loc: (list) - Third-Party-file location information.
38
  analysis: (dict) - Issue type, reason, location scope and type.
39
  base_commit: (str) - The commit hash of the repository representing the HEAD of the repository before the issue.
40
- ```
 
1
+ ---
2
+ task_categories:
3
+ - text-retrieval
4
+ tags:
5
+ - code
6
+ - software-development
7
+ - issue-localization
8
+ - bug-fixing
9
+ language:
10
+ - en
11
+ ---
12
+
13
+ This repository hosts **MULocBench**, a comprehensive dataset presented in the paper [A Benchmark for Localizing Code and Non-Code Issues in Software Projects](https://huggingface.co/papers/2509.25242).
14
+
15
+ MULocBench addresses limitations in existing benchmarks by focusing on accurate project localization (e.g., files and functions) for issue resolution, which is a critical first step in software maintenance. It comprises 1,100 issues from 46 popular GitHub Python projects, offering greater diversity in issue types, root causes, location scopes, and file types compared to prior datasets. This dataset provides a more realistic testbed for evaluating and advancing methods for multi-faceted issue resolution.
16
+
17
  ## 1. Downloads
18
 
19
  Please download the benchmark from https://huggingface.co/datasets/somethingone/MULocBench/blob/main/all_issues_with_pr_commit_comment_all_project_0922.pkl
 
33
  print(f"{featurename}: {e_iss[featurename]}") # print feature_name: value for each issue
34
  ```
35
 
 
 
36
  ### 3. Data Instances
37
  An example of an issue is as follows:
38
 
 
51
  other_rep_loc: (list) - Third-Party-file location information.
52
  analysis: (dict) - Issue type, reason, location scope and type.
53
  base_commit: (str) - The commit hash of the repository representing the HEAD of the repository before the issue.
54
+ ```