« Older Home
Loading Newer »

The job wiki gears up for a second year

24Aug10

We’re preparing Phylo’s philosophy job wiki for a second year.

Most immediately, this means that we’ve archived old listings.

We’re also planning some changes to the layout and the function of the job wiki. These changes should make the wiki a little easier to use. One big change is that we’re going to try including AOCs this year. We’ll write a separate post about those changes a little later on.

For those who are new to the job wiki, the idea of an academic job wiki is to share information about the status of particular jobs. In particular, the wiki allows job seekers to share information about when (whether) a particular school has acknowledged applications; when it has scheduled first-round interviews, which usually happen at the APA; when it has scheduled final interviews, which usually happen on campus; when it has made an offer; and when the position has been filled. It also allows job seekers to share information about when job searches have been suspended or canceled. The primary goal of the wiki is not to help you decide which jobs to apply for or tell you how to apply. For that, you’ll need to go to the original job ad.

Remember, of course, that this information is provided by anonymous fellow job seekers. The information may not always be accurate and it will certainly not be complete. If you know that something is inaccurate or incomplete, please update it.

For those who are new to the job market, we suggest keeping an eye on the APA’s Jobs for Philosophers, the Chronicle of Higher Education’s job listings, jobsinphilosophy.org for job listings. In addition, you might find The Philosophy Smoker an entertaining and useful place to exchange information, commiserate about the job market, and be anonymously snarky.

We wish everyone the best of luck on the job market!

New features on the job wiki: status histories, comments, and personalized subscriptions

03Dec09

We’ve added a number of new features to our philosophy job wiki.

1. Status histories

You can now see how the status of each job listing has changed over time. You can look back to see when users reported that applications had been acknowledged, when they reported that interviews had been scheduled, etc.

To see the status history for a job listing, find the job listing on the main wiki page. Hold your mouse over the “View status history” link in that listing and wait for the popup. You’ll see a table showing every time someone reported on the status of the job, including: the status that was reported (e.g., “first-round interviews scheduled”), the date and time that the report was made, and the IP address of the user who reported it. (Clicking on the IP address will take you to InfoSniper, a free web service that provides detailed information about IP addresses, including geographical location, the institution that owns the address, etc. We have no affiliation with InfoSniper.)

You can also see the status histories on the standalone page for each job listing. (You can reach the standalone pages through the RSS feed or by clicking comment links on each job listing.) Check out the page for the listing for Georgetown’s opening in applied ethics for an example.

The “ditto” effect

When the job wiki was hosted on wikihost.org, users would often “second” a report by adding ‘ditto’. For instance, you might have seen something like this under a job listing: “Called to arrange APA interview (12/4); ditto (12/5).” Among other things, this helps confirm the validity of reports.

The status history allows us to simulate this ditto effect. If you would like to “second” the current status of a job, mouse over the pencil icon and click the current status again. For instance, suppose you go to the wiki and find that your favorite school’s status has changed to ‘First-round interviews scheduled’. While you’re drowning your sorrows, the school calls you to schedule an interview! After celebrating, go to the wiki and do exactly what you would if you were the first person to report that the school had scheduled first-round interviews: mouse over the pencil icon, wait for the popup, and click on ‘First-Round Interviews Scheduled’. When other users look at the status history, they’ll see that two people (with different IP addresses) both reported that interviews have been scheduled. In other words: “Ditto.”

2. Comments

You can now post comments about job listings. If you report on a job listing, the rest of us would appreciate it if you post a comment specifying how you heard (e.g., email, phone, carrier pigeon) and any other information you received (e.g., “the department will make a decision by mid-December about APA interviews”). If you want to spread, confirm, or dispel rumors about a job, you can do that in comments, too. But please don’t spread rumors. It’s not nice.

To read and post comments on a job listing, find that listing in the wiki and hold your mouse over the ‘comments’ link for that listing. You’ll see a list of comment titles, along with links to read the comments or post one of your own. If there are no comments for a post yet, you’ll just see a link to ‘Post comments’.

Comment titles and dates are now also included in the RSS feeds.

3. Personalized RSS feeds

You’ve been able to get an RSS feed of updates to the job wiki since we first launched the wiki. Now, you can create a personalized feed containing just the schools that interest you. To do this, you’ll need to create an account with us. Accounts are free. It takes less than a minute to create one. We’re never going to sell your information or spam you or do anything like that. (You can read our privacy policy if you’re concerned about that sort of thing.)

Once you’ve created and logged into your account, you can subscribe or unsubscribe to individual job listings by clicking on the RSS icons in each listing. The icons are semitransparent for listings to which you’re already subscribed. If you hold your mouse over an RSS icon, you’ll get a popup telling you explicitly whether you’re subscribed, giving you the option to (un)subscribe, and providing links to relevant information, including the personalized feed itself.

You can read more about RSS and our personalized feeds here.


We hope users find these new features helpful. Please let us know what other features you’d like to see and what problems you encounter with these features (or with the rest of the wiki).

Good luck to everyone in a very difficult market!

Interfolio and electronic recommendations

13Nov09

Users of our job wiki might be interested to know that Interfolio has broadened its capacity to handle electronic letters of recommendation. They’ve been able to email documents for some time now. Now they can apparently upload recommendations to online application sites. I can’t comment on how well it works, since I have yet to run into an online application that asked me to upload letters to the site (or have my recommenders do it). The online applications that I’ve seen asked for the letters to be mailed or emailed separately.

But for those who do run into this request, Interfolio can now handle it for you.

Teaching the job wiki to sort jobs by “last updated”

24Oct09

After some gentle prodding from one of the philosophy job wiki’s users, I revisited a task that I’d set aside some time ago: getting the job wiki to sort job listings according to the date and time of their last update. I’d tried this before without success, but today I figured it out.

The job wiki now sorts by “last updated” by default. You can, of course, sort jobs in other ways by clicking the ’sorted by’ controls at the top of the listings.

The stumbling block had been the spottiness of SIMILE Exhibit’s documentation. Since I couldn’t figure out how Exhibit handled dates for sorting purposes, the best I’d been able to do was to get Exhibit to sort from oldest to most recently updated. That was a bit better than nothing, but not good enough. Today I found the key in the Exhibit source code. I’m posting it here for the benefit of other SIMILE Exhibit developers:

To get Exhibit to sort items by date, you need to format the dates according to the ISO 8601 date formatting standards. For instance, October 24, 2009 14:01 CDT should be formatted as 2009-10-24T14:01:00-05:00. If you’re using PHP 5+ to format your dates, you can use the string c in your date() function. (If you’re using PHP <5, use Y-m-d\TH:i:s. It doesn’t include the timezone offset, but that won’t matter for sorting purposes. Include a separate timestamp for display in your Exhibit if you’re concerned about the timezone offset.) Exhibit will correctly sort items with dates in ISO 8601 format, both ascending and descending.

There’s still one problem, though. By default, Exhibit sorts dates from earliest to latest. If you’re sorting by the timestamp of the last update for each item, you’ll probably want to default to a descending sort order. Fortunately, Exhibit lets you do that.

To control the default sort order for the items in your exhibit, set the <code>ex:directions</code> and <code>ex:possibleDirections</code> properties of your view to ‘ascending’ or ‘descending’. You can even set different defaults for different (possible) orderings. (Exhibit always defaults to ‘ascending’ if it can’t find a sort order for something.)

For instance, our job wiki has the following declaration:

<div ex:role="view"
  ex:orders=".changed_1"
  ex:directions="descending"
  ex:possibleOrders=".changed_1, .field_name_value, .field_rank_value, .field_job_status_value, .province, .tid_2, .tid_1, .tid"
  ex:possibleDirections="descending"
  ex:grouped="false"
  ex:showAll="true">
</div>

This tells Exhibit to sort the items by property “.changed_1″ in “descending” order by default. It also tells Exhibit to allow users to sort by properties .changed_1, .field_name_value, etc. Finally, the ex:possibleDirections property tells Exhibit to sort items in descending order by default whenever it’s sorting by .changed_1; because I wanted all other properties to default to sorting in ascending order, I left them all blank.

One more example: Suppose you’re working with the Nobel prize winner data from Exhibit’s Getting Started Tutorial. You want to configure your Exhibit so that when it first boots up, the Nobelists are sorted by year from most recent to least recent. You also want your users to be able to sort by name, discipline, and year. You want the default order when sorting by name to be A-Z, the default order when sorting by discipline to be Z-A (you like physics best), and year to be most recent to least recent. You would need the following code:

<div ex:role="view"
  ex:orders=".nobel-year"
  ex:directions="descending"
  ex:possibleOrders=".last-name, .discipline, .nobel-year"
  ex:possibleDirections="ascending, descending, descending">
</div>

Happy sorting!

RSS feeds from Phylo’s philosophy job wiki

12Oct09

We recently launched our own philosophy job wiki to help the philosophical community keep track of academic job in philosophy. The community had maintained a wiki on a free wiki host, wikihost.org, for the past few years, which I found myself checking compulsively during my job search last year — not that it ever gave me anything but bad news. I don’t know who started the original philosophy job wiki, but kudos to them. It was a wonderful idea.

Wikhost.org has the wonderful advantage of being free and easy to use, but Chris and I realized that we could do something that no wiki on wikhost could do: we could provide RSS feeds that feed information about each job directly to you. (You can access our RSS feed at http://phylo.info/jobs/rss.) As with thought more about creating a wiki here on Phylo, we realized that our wiki could have other advantages, like filtering capabilities and connections with our database of institutional information.

If you’ve never used RSS, you’re missing out. RSS stands for “really simple syndication,” and it’s a wonderful invention that web sites use to syndicate information to end users and even other web sites. Subscribing to an RSS feed is a bit like subscribing to a web site’s updates via email, except that it doesn’t clutter your inbox and you don’t have to give out your email address. Personally, I find email updates extremely annoying. I usually banish them, unread, to my trash folder. But I find RSS really useful. For instance, I use a free RSS reader called Vienna. I subscribe to specific sections of various newspapers, about half a dozen philosophy-related blogs, about two dozen philosophy journals (which send updates of news issues or papers), a handful of tech-related blogs, and various feeds on the Phylo site itself. There’s no way I would keep track of all of these things on my own, but my RSS reader helps me pretend that I can keep track of them.

To get started using RSS, I’d suggest downloading Vienna or checking out Google Reader. Then go to your favorite newspaper’s RSS page (e.g., the feed list for the New York Times) and subscribe to whatever sections interest you. Then go to some of your favorite philosopher blogs or philosophy journals and subscribe to their RSS feeds.

And of course, if you’re on the job market, subscribe to the philosophy job wiki feed at http://phylo.info/jobs/rss. You’ll get a new item in your feed every time a new job listing is added to the wiki and every time someone updates the status of the wiki (e.g., when someone reports that the school that you’re dying to work for has scheduled APA interviews).

In other words, the job wiki can now crush your hopes and dreams from afar. I told you RSS was wonderful.

(One note for people already subscribed to the RSS feed: We tweaked the feed earlier today because some RSS readers weren’t displaying things correctly. This may result in your reader telling you that everything is new. I’m very sorry to tell you that there are not 143 new job listings today. The feed should behave normally from this point on.)

The technology behind Phylo: Drupal and SIMILE

12Oct09

Phylo is built on top of two major open-source platforms: the Drupal content management system and the SIMILE family of JavaScript data management tools. At the moment, Phylo uses SIMILE’s Timeline on the main site and Exhibit on the new philosophy job wiki.

At its core, Phylo is a database of professional information about academic philosophers, from which we can infer professional connections and relationships among those philosophers. Drupal gives us the ability to keep track of that information in a relational database, and it lets users view and manipulate that data in various ways. We’re using a lot of off-the-shelf modules that have been contributed by Drupal’s users, but we’ve also added a lot of modifications of our own, including a custom interface written in jQuery.

The SIMILE Project, started at MIT, provides a suite of software that lets you do all kinds of great things with data on the “client side” (i.e., on the end user’s computer). For instance, Timeline lets us plot a person’s academic career on a timeline or display a timeline of the faculty and students in a given department. Exhibit enables users to filter and sort the data in all kinds of ways.

Both Drupal and SIMILE have fairly steep learning curves, and it’s often frustrating to get them to play nicely together, but we think the products that you can create with the two of them are worth the effort. Besides, they’re both open source, and we’re big fans of the open source software movement.

Free the facts

21Jan09

Dave Gray has a nice Flickr slideshow up about research and open access.

Using reCAPTCHA to help digitize books

10Jan09

We’ve reactivated reCAPTCHA on our new domain. CAPTCHAs are the distorted images found on registration forms that help determine whether a user is a human or a computer program, such as a spam bot. Carnegie Mellon’s reCAPTCHA takes this function to a new level by using human-generated inputs to help digitize old books.

As recaptcha.net explains, Optical Character Recognition (OCR) cannot successfully digitize all words from book images. 

reCAPTCHA takes these unreadable words and uses them to generate CAPTCHA images. When human users solve the CAPTCHA, their responses help decipher the unreadable words. (In case you’re wondering how it works, users are given two images, one successfully OCRed and another that is not. When a user gets the OCRed word right, the system assumes he/she is correct about the other word. Responses are aggregated together to improve the confidence of digitization.)

reCAPTCHA currently helps digitize books from the Internet Archive and old editions of the New York Times.

We use reCAPTCHA on two areas of the site: user registration and Phylo Forum (where visitors can post messages without registering.

New .info domain

08Jan09

On Monday, we acquired phylo.info and moved the site over to our new domain. We still own phylosophy.net and all requests to our old domain will be redirected to our new one (seamlessly, as far as I can tell).

.info is one of the more popular generic top-level domains released in 2000. It is intended for “informative websites” and had roughly 5.2 million name registrations by April 2008.

One benefit of our new domain is the simplicity of browsing to

phylo.info/john_rawls

phylo.info/willard_van_orman_quine

phylo.info/donald_davidson

Benjamin Rand’s Bibliography of Philosophy

05Jan09

I just got my hands on Benjamin Rand’s 1905 Bibliography of Philosophy, Psychology, and Cognate Subjects. Rand lists roughly 60,000 books, articles, and reviews that were available in his time, and provides nearly exhaustive coverage of the nineteenth-century literature.

Rand’s Bibliography will be crucial for us as we expand our dataset backwards. How we’ll parse the vagaries of the citations is anyone’s guess at the moment. There will be more to come on that once we finish up 20C dissertations and appointments.

For the moment, I wanted to share  few paragraphs from his Preface that express the same spirit as Phylo over a century earlier:

Information concerning philosophical literature has heretofore been scattered among such a great variety of sources that much expenditure of time and effort has been required before it became available. A comprehensive bibliography of philosophy has therefore long seemed a necessity. To form a single serviceable bibliography[,] the literature in various philosophical publications of recent years and the vast array of dispersed data of earlier periods needed to be brought together. To accomplish this task has been the aim of the present work.

. . . Notwithstanding the many years thus devoted to the work, more time might doubtless have been spent on it in point of completeness and thoroughness; but there is a limit to what can be fairly expected of single-handed and self-supported endeavour. The constant desire, however, has been to afford judicious and ready access to philosophical literature alike to student, librarian, and teacher. Whether this end has been satisfactorily accomplished can best be determined by the measure in which the work shall prove helpful in revealing the valuable sources of information in the realm of Philosophy, and by the extent to which it shall serve as a vantage ground from which to carry forward independent philosophical research.

. . .

If it happens in the coming years that students of philosophy in different lands shall first turn here for the sources of information, and, without retracing the steps already laboriously trod, shall proceed more readily with their own original researches, then this work will indeed have served a useful end. That it shall give readiness of access to the works of the ‘great ones’ in philosophy, and shall render available to all, the literature on those systematic subjects with which philosophical writers have dealt; that it shall furnish the means through which libraries of philosophy may more readily be founded or enlarged; shall prepare the way whereby new philosophers may more freely advance and new systems be created; that it shall testify to the intellectual brotherhood of man by true service toward all—are hopes which have stimulated to constant effort and lightened toilsome hours in the preparation of this work. If in spite of the work’s limitations any of these purposes shall hereafter be fulfilled, the end sought by the author will have been reached and his true reward have been attained.

It took Rand over a decade to finish his Bibliography. Let’s hope Phylo goes a little quicker!