Add 4, update 1, delete 3 former CS members of University of Stuttgart. #8010
Task list completed / task-list-completed
succeeded
Nov 23, 2024 in 0s
18 / 18 tasks completed
All tasks have been completed
Details
Required Tasks
| Task | Status |
|---|---|
| All pull requests and issues must come from non-anonymous accounts. Make sure your GitHub profile contains your full name. | Completed |
| Use a reasonable title that explains what the PR corresponds to (as in, not "Update csrankings-x.csv"). | Completed |
| Combine multiple updates to a single institution into a single PR. | Completed |
| Only submit one pull request per institution. | Completed |
Do not modify any files except csrankings-[a-z].csv or (if needed) country-info.csv and old/industry.csv (see below). |
Completed |
| Do not use Excel to edit any .csv files; Excel incorrectly tries to | |
| convert some Google Scholar entries to formulas, corrupting the | |
| database. Use the GitHub user interface or a text editor like emacs or NotePad instead. | Completed |
Insert new faculty in alphabetical order (not at the end) in the appropriate csrankings-[a-z].csv files. Do not modify csrankings.csv, which is auto-generated. |
Completed |
| Check to make sure that you have no spaces after commas, or any missing fields. | Completed |
| Check to make sure the home page is correct. | Completed |
Make sure the Google Scholar IDs are just the alphanumeric identifier (not a URL or with &hl=en). |
Completed |
| Check to make sure the name corresponds to the DBLP entry (look it up at http://dblp.org). | Completed |
| If a faculty member is not in a CS department or similar, include a comment explaining how they meet the inclusion criteria (see below). | Completed |
| Make sure that any faculty you add meet the inclusion | |
| criteria. Eligible faculty include only full-time, tenure-track research | |
| faculty members on a given campus who can solely advise PhD students in | |
| Computer Science. Faculty not in a CS department or similar who can | |
| advise PhD students in CS can be included regardless of their home | |
| department. **Provide justification, pointing to specific home pages | |
| showing how faculty not in a CS department meet the inclusion criteria, | |
| e.g. showing a courtesy appointment in CS.** Faculty must also have a 75%+ time appointment (check | |
old/industry.csv for faculty who are now more than 25% in industry). |
Completed |
Update affiliations, home pages, and Google Scholar entries by modifying csrankings-[a-z].csv. For the Google Scholar entry, just use the alphanumeric identifier in the middle of the URL. If none is there, put NOSCHOLARPAGE. |
Completed |
| If the department is not yet listed in CSrankings, the entire CS faculty needs to be added (not just one faculty member). | Completed |
Enter each faculty member's DBLP name, home page, and Google Scholar entry (just the alphanumeric identifier, not the whole URL) by modifying csrankings-[a-z].csv (the letters correspond to the first letter of the faculty members' names); include disambiguation suffixes like 0001 as needed. If the faculty entry is currently ambiguous, please do not include them. Send mail to the DBLP maintainers ([email protected]) with a few publications by a particular faculty member; also, open an issue so that when the DBLP database is updated, that faculty member's information can be added. |
Completed |
If DBLP has multiple entries for this person, all of them need to be listed. Do not update dblp-aliases.csv. |
Completed |
| If the institution you are adding is not in the US, | |
update country-info.csv and add all of the faculty in the CS department. |
Completed |
| Fork the CSrankings repo. If you have an existing fork, but it is not up to date with the main repository, this technique may not work. If necessary, delete and re-create your fork to get it up to date. (Do not delete your existing fork if it has unmerged changes you want to preserve!) | Incomplete |
Do a shallow clone of your fork: git clone --depth 1 https://github.com/yourusername/CSrankings. This will only download the most recent commit, not the full git history. |
Incomplete |
| Make your changes on a branch, push them to your clone, and create a pull request on GitHub as usual. | Incomplete |
Loading