A5. Faceted Classification

Assigned: 
October 5, 2011
Due: 
October 12, 2011 - 09:00
Create a new Assignment Submission Page titled: "A5 - Your Name".  Make sure to tag it with the A5 assignment tag.

Assignment 5: Faceted Classification
Assignment Overview

In this assignment you will:

1. Familiarize yourself with an online tool for facet creation.
2. Design a faceted classification for a provided set of instances.
3. Adjust your classification given additional instances.
4. Build and upload your faceted classification through the online tool.
5. Reflect on your experience designing and iterating your classification.

Deadline

You must submit your work by creating a new assignment submission page before 9 a.m. on Wednesday, October 12, 2011. Late assignments will not be accepted unless you have an exceptionally good excuse.

Submission Requirements

You will upload a .zip file named YourNameA5.zip that contains a copy of your Facetmap file (named ischool2011_yourlogin.xml or .txt, e.g. the professor's facet map would be ischool2011_glushko.xml) and the XML report (YourNameA5Report.xml, which should contain a link to your Facetmap) that conforms to the Report.dtd, same as previous assignments.

1. Getting Acquainted with Facetmap

Get acquainted with the Facetmap web site at http://facetmap.com. In particular, look at the wine demo to see how the three facets of Varietals, Region, and Price combine to organize hundreds of wine instances. The demo will start up in the "Commentary Track" that explains what is going on as you specify facet values to select wines in the collection. Notice that there are three different user interface styles for the display of the facets and the items that are selected by different facet values. Think about the pros and cons of each style of display.

2. Design A Faceted Classification

Once you have familiarized yourself with Facetmap, it’s time to start working on your classification. Review pages 12–16 of the Hemerly reading in the course syllabus for October 3rd, noting Ranganathan’s dimensions, the set of general criteria for facet design, and the principles guiding facet ordering. You will use these to design your own faceted classification to organize the set of instances provided here: http://www.polyvore.com/cgi/set?id=37832382.

You’ll notice that every instance is an animal. Remember that you are classifying the animal instance shown in the picture, NOT the type or class to which the animal belongs. In other words, we are not looking for taxonomic classes (reptiles, insects, etc.). You can see picture titles by holding your mouse over the picture. The titles provide important clues regarding how to classify your instance. You can have as many facets as you want, but you should have at least four. You will need to be creative but make sure that anybody else could use them without your help. They can be abstract or practical or a mix of both so long as they classify the instances in a way that other people could understand. Also make sure that your facets are flexible enough to handle additions to the list of instances.

3. Testing Your Facets with New Instances

A good set of facets should be able to accommodate new instances without adjustment. Please do not look at these sets until you’ve built the classification for the original 10 instances. Choose one of these five groups of new instances (5 new instances in each one):

Group 1: http://www.polyvore.com/cgi/set?id=37832674
Group 2: http://www.polyvore.com/cgi/set?id=37832954
Group 3: http://www.polyvore.com/cgi/set?id=37833084
Group 4: http://www.polyvore.com/cgi/set?id=37833454
Group 5: http://www.polyvore.com/cgi/set?id=37833699     

Revise your facets if necessary so that your system can classify all 15 instances.

4. Encoding Your Work for Facetmap

Once you have a system that handles all your instances, encode it and all your instances using either the XML or the text file format shown on Facetmap. (http://facetmap.com/demosetup/)

* Facetmap's Limitations

Previous students ran into several quirks, bugs and limitations while using Facetmap. Several of these bugs have been resolved but we can make no guarantees that you won't stumble upon some brand new ones. Have patience, make note of any compromises or design changes you had to make because of limitations of Facetmap or facets in general and send email to the class list if you are having difficulties that other students might encounter.

Facetmap enforces a strict "occurrence exclusivity" principle in assigning values in a facet. This means if a library facet map has a "subject" facet that includes both a "War" and a "Peace" heading, your copy of Tolstoy's renowned work about both war and peace cannot be listed under both. Keep this in mind when designing your facets and facet values. This principle is what distinguishes faceted classification from "tagging" in the flickr or del.icio.us sense, where any tag can be assigned to any information resource or object regardless of other tags already associated with it.

After you've uploaded your Facetmap, it will be available for 7 days, but after that it may expire, so be sure to keep a copy of what you submitted.

5. Submitting Your Work

Upload your Facetmap file to facetmap.com, using this file naming convention: ischool2011_yourlogin.xml or .txt (For example, the professor's facet map would be: ischool2011_glushko.xml).

Create a new assignment submission page and upload a zip file (named YourNameA5.zip) of your Facetmap file (named ischool2011_yourlogin.xml or .txt) and a short report (named YourNameA5Report.xml, which should include a link to the Facetmap). This report should specify which secondary group you chose, and answer the following bullet points in about 250 words total:

  • Were there sequence effects? That is, did you find that you had to work through them in a particular order to get to a classification you felt comfortable with?
  • How did you use Ranganathan’s PMEST in conceiving your facets? Was it useful?
  • What were your biggest challenges in designing the classification?
  • How well did your initial facet design handle the additional instances? What changes did you need to make to accommodate the new instances?

Class Meetings: