Skip to content

Commit

Permalink
Overhaul map process to use Excel and Sketch only
Browse files Browse the repository at this point in the history
  • Loading branch information
jessb0t committed Jan 14, 2025
1 parent 0d4b3c8 commit d64c4b7
Show file tree
Hide file tree
Showing 29 changed files with 248 additions and 33,114 deletions.
2 changes: 2 additions & 0 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
# OS specific files
.DS_Store
9 changes: 0 additions & 9 deletions Makefile

This file was deleted.

116 changes: 20 additions & 96 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,110 +1,34 @@
## Instructions
## Instructions for Updating

**Making updates**
#### What You Need

If you want to push changes directly to this repository, one of the [@linguistics](https://github.com/linguistics) organization administrators will need to grant you access.
You will need to be familiar with GitHub.

If you don't think you'll need to make changes very often, you can fork this repository and clone the fork to your local hard drive, or use GitHub to edit the file (in which case it will create a fork for you).
After you've committed your changes to your fork, you will need to submit a pull request to this repository, which the GitHub web interface makes quite easy.
This will notify the organization members, and one of them will be able to merge your changes.
You will need [Sketch](https://www.sketch.com/) for Mac. As an eductional user, you can get a free license by starting a free trial and then filling in their form to explain why you need Sketch for your work in academia.

**Design modifications**
Finally, you will also need Microsoft Excel, which UT [provides](https://microsoft365.utexas.edu/students-and-microsoft-365) to all students.

1. Open [`map.sketch`](map.sketch) in [Sketch](http://www.bohemiancoding.com/sketch/)
2. Make your changes
3. Save (optional)
4. Export to [`map.svg`](map.svg)
#### Fork and clone this repository

**Workstation modifications**
In order to have access to all files in this repository, fork it to your own GitHub account, then clone your fork onto your local computer.

1. Open [`people.tsv`](people.tsv) in a unicode-friendly editor. (Note from MHP: If possible, just use the github editor, to avoid encoding mixups.)
2. Make your changes, preserving the column headers and tab-separated format
3. Save with `utf-8` encoding. You can ensure that it was saved correctly by running `file people.tsv` at the command line, which should return:
#### Update the list of people

> people.tsv: UTF-8 Unicode text
Open people.xlsx in Microsoft Excel. Delete/add/update any rows as necessary. Only modify columns A, B, and C; column D will automatically generate. (If you add to the bottom of the list, just hover over the bottom-right corner of the last filled cell in column D and drag down to fill in the formula.) Click into cell A1, press cmd+A to select the whole island of data, and sort by last name. Save but do not close.

If it is returning ASCII instead, well, technically ASCII is a type of UTF-8, but the code won't accept that. The fix for this problem ([drawn from this StackOverflow](https://stackoverflow.com/a/28380315)) is:
#### Update the graphic file

> (printf "\357\273\277";cat INPUT.tsv) > OUTPUT.tsv
1. Open the .sketch file in Sketch.
2. Open a blank text file. Select just the filled cells in column D from the Excel file and copy to your clipboard. Paste into the blank text file. Use cmd+A to select all contents of this text file and then cmd+C to copy to your clipboard.
3. Inside Sketch, double click the first block of names/workstations so that it is editable. Use cmd+A to select everything, then cmd+V to overwrite with the new list. You will need to select subsets of the next text block and use these to overwrite the contents of the other two until you are satisfied with the presentation.
4. Save down your changes to the Sketch file by using "Save to your Mac." Replace the .sketch file in the repository folder on your local drive with this updated version.
5. Output the PDF version by going to File>Export>Artboards to PDF. Name as "map.pdf" and replace the .pdf in the repository folder on your local drive with this updated version.
6. As a precautionary measure, export the .sketch file to .svg. Select the artboard and Export to SVG in the bottom-right of the Sketch window. Click "Export Selected" and save as map.svg. Replace the .svg file in the repository folder on your local drive with this updated version.

**Rendering and Printing**
#### Push your changes to your GitHub

1. Open <https://linguistics.github.io/rlp/map.html> in [Chrome](https://www.google.com/chrome/).
2. Print to PDF or a physical destination.
* By default, Chrome should use a landscape layout and minimal margins.
Once all changes are complete, push to your forked GitHub repo.

#### PR to the ASOL repository

## Workstation Allotment Policy

1. Three or four weeks before the beginning of semester:
* Call the set of current workstation residents (whether fellowship or not) `incumbents`
* Ask administration for a list of all fellowship recipients, TAs, and AIs (and maybe GRAs); call this set `privileged`
* Let `itinerants = incumbents - privileged` (students who may need to move out)
* Let `residents = incumbents ∩ privileged` (these guys aren't going to move, and their workstations will not go up for grabs)
* Let `incoming = privileged - incumbents` (students who will for sure get a workstation but we don't yet know where)
* Let `homeless = privileged'` (the complement of `privileged`)
2. Send some emails:
* Ask all of the `homeless` to apply for a workstation, if they want one.
* There are currently 25 workstations total. Select the top `25 - |privileged|` applicants, and call these `winners`.
* Call the remainder of the applicants `rejections`, and inform them that they didn't make the cut.
* Add `winners ∩ itinerants` to the `residents`, and let `evictions = itinerants - winners` (which may overlap with the `rejections`)
* Ask the `incoming` which workstations they would like, from among the `evictions` (assuming that all workstations are currently occupied; if that's not the case, add the abandoned workstations to the `evictions` set)
* If there are any `winners - itinerants`, let them choose among the workstations `evictions - incoming`
3. If possible, go back in time a couple months and send some more emails:
* Inform `evictions` that they may need to vacate their workstations, especially if they are going to be gone for the summer.

See the examples in the [emails](emails/) directory for templates for these notifications.

### Prioritization

As available, workstations will be assigned to the following groups of students / physical objects:

1. Fellowship recipients
2. Assistant Instructors
3. Teaching Assistants
4. Graduate Research Assistants
5. Best applicants
6. Worst applicants
7. Lingerers-on
8. Groupies
9. Pets
10. Prized possessions


#### Applications

The only prioritization step that's hard (requires some actual decision-making) is #5.
Generally, preference will be given to students who:

1. Would use their workstation a lot
2. Are near the end of their degree program
3. Have good workstation prank ideas


E.g., **Fall 2013 workstation application** form had these fields:

* Full name
* Email address
- Drop-down list of emails, to aid identification of student
* Need: On a scale of 1 to 10, how much do you want a workstation?
- Radio buttons from 1 to 10
* Alternatives: Do you already have a desk or assigned workspace elsewhere?
- [ ] No
- [ ] CILLA
- [ ] Signed Languages Lab
- [ ] Language Acquisition Lab
- [ ] Phonetics Lab
- [ ] German department
- [ ] Spanish department
- [ ] Other: `______________`
* Time: How often do you think you would use your workstation?
- [ ] < 1 day a week
- [ ] 1 day a week
- [ ] 2 days a week
- [ ] 3 days a week
- [ ] 4 days a week
- [ ] 5+ days a week
* Cardinality: Which side would prefer?
- [ ] West
- [ ] East
* Rhetoric: Any parting remarks?
On the GitHub interface, initiate a pull request (PR) to merge your fork with this repository. Although the Digital Resources representative from ASOL should receive a notification of your pull request, it is a good idea to reach out personally to let them know so that they can immediate complete the PR. If you are not sure who is the Digital Resources representative is, check out the [ASOL website](https://asol.ling.utexas.edu/).
118 changes: 0 additions & 118 deletions admin.html

This file was deleted.

7 changes: 0 additions & 7 deletions emails/homeless.txt

This file was deleted.

15 changes: 0 additions & 15 deletions emails/incoming.txt

This file was deleted.

9 changes: 0 additions & 9 deletions emails/itinerants.txt

This file was deleted.

5 changes: 0 additions & 5 deletions emails/rejections.txt

This file was deleted.

7 changes: 0 additions & 7 deletions emails/winners.txt

This file was deleted.

32 changes: 0 additions & 32 deletions map.html

This file was deleted.

Binary file added map.pdf
Binary file not shown.
Binary file modified map.sketch
Binary file not shown.
Loading

0 comments on commit d64c4b7

Please sign in to comment.