INTRODUCTORY TOPICS

Tuesday, 1/18/05: Introduction, cont.

• Assign Homework 1, due Tuesday, 2/1/05.

Thursday, 1/20/05: Human Information Processing and Problem Solving

• Blair, D. (2002). Knowledge management: Hype, hope or help? Journal of the American Society for Information Science and Technology, 53(12), 1019-1028. [e-journal]
• Jacob, E. (2001). The everyday world of work: Two approaches to the investigation of classification in context. Journal of Documentation, 57(1), 76-99. [e-journal]

Tuesday, 1/25/05: Information

• Buckland, M. (1991). Information and Information Systems. New York: Praeger. Chapter 1, Information, 3-13. [e-reserve]
• Buckland, M. (1991). Information and Information Systems. New York: Praeger. Chapter 5, Information-as-Thing., 43-54. [e-reserve]
• Buckland, M. (1997). What is a document? Journal of the American Society for Information Science, 48(9), 804-809. [e-journal]
• Meadow, C. (1992). Text Information Retrieval Systems. San Diego: Academic Press, Inc. Chapter 2, Data, Information, Knowledge. [e-reserve]

Thursday, 1/27/05: Organization and Information System Structure

• Soergel, D. (1985). Organizing Information. San Diego: Academic Press. Chapter 5, The structure of information systems, 41-65. [e-reserve]

Tuesday, 2/1/05: Organization and Information System Structure, cont.

• In-class exercise
• Homework 1 due.

INFORMATION AND KNOWLEDGE MANAGEMENT

Thursday, 2/3/05: Knowledge Management Overview

• Wikipedia entries on knowledge management; also read the “see also” topics.
• Malone, T. (1983) How do people organize their desks? Implications for the design of office information systems. ACM Transactions on Office Information Systems 1(1), 99-112. [e-journal ACM DL, e-reserve]
• Wilson, T. D. (2002). The ‘nonsense’ of knowledge management. Information Research, 8(1).

Tuesday, 2/8/05: Personal Information Management

• Kwasnik, B. (1989). How a personal document’s intended use or purpose affects its classification in an office. Proceedings of the Twelfth Annual International ACMSIGIR Conference on Research and Development in Information Retrieval, 207-210. [e-journal, ACM DL]
• Barreau, D. & Nardi, B. (1995). Finding and reminding: File organization from the desktop. SIGCHI Bulletin, 27(3), 39-43. [e-journal, e-reserve]
• Nardi, B. & Barreau, D. (1997). “Finding and Reminding” revisited: Appropriate metaphors for file organization at the desktop. SIGCHI Bulletin, 26(1), 76-78. [e-journal, ACM DL,e-reserve]

Thursday, 2/10/05: Personal Information Management, cont.

• Dumais, S., E. Cutrell, E., J. J. Cadiz, G. Jancke, R. Sarin and D. C. Robbins (2003). Stuff I've Seen: A system for personal information retrieval and re-use. Proceedings of SIGIR, 72-79. [e-journal, ACM DL]
• Jones, W., Dumais, S. & Bruce, H. (2002). Once found, what then?: A study of “keeping” behaviors in the personal use of Web information. Proceedings of the 65th Annual Meeting of the American Society for Information Science and Technology, 391-402.

• Assign Case study or tool review, due Thursday, 2/24/05.

Tuesday, 2/15/05: Enterprise Knowledge Management

• Hahn, J. & Subramani, M. (2000). A framework of knowledge management systems: Issues and challenges for theory and practice. Proceedings of the 21st International Conference on Information Systems. 302-312. [e-journal, ACM DL]
• Schriever, A. (2004). The knowledge-model driven enterprise November 22, 2004.

REPRESENTATION

• Meadow, C. (1992). Text Information Retrieval Systems. Orlando: Academic Press. Chapter 3, Representation of information. 32-48. [e-reserves] Meadow, C. (1992). Text Information Retrieval Systems. Orlando: Academic Press. Chapter 4, Attribute content and values. 49-75. [e-reserves]
• Norman, D. (1993). Things that make us Smart. Addison Wesley. Chapter 3, Power of representation, 43-75. [e-reserves]

Tuesday, 2/22/05: Representation, cont.

• Durkin, J. (1994). Expert Systems: Design and Development. Englewood Cliffs, NJ: Prentice-Hall Knowledge representation 52-67. [e-reserves]

METADATA

• Weibel, S. (1995). Metadata: The foundations of resource description
• Greenberg, J. (2003). Metadata generation: Processes, people and tools. Bulletin of the American Society for Information Science and Technology, 29(3).
• Greenberg, J. (2004). Metadata Extraction and Harvesting: A Comparison of Two Automatic Metadata Generation Applications. Journal of Internet Cataloging, 6(4): 59-82. [e-journal]
• Starr, J. (2003). Metadata use in the commercial banking industry. Bulletin of the American Society for Information Science and Technology, 29(6).

• Case study or tool review due.
• Assign Reflection paper 1, due Thursday, 3/10/05.

Tuesday, 3/1/05: Metadata - FRBR, DC, OAI

• IFLA (1998, latest revision 2004). Functional Requirements for Bibliographic Records – Final Report..
• Hillman, D. (2003). Using Dublin Core
• Dublin Core Metadata Element Set, Version 1.1. Browse through this.
• Lagoze, C. & Van de Sompel, H. (2001). The Open Archives Initiative: Building a low-barrier interoperability framework. Proceedings of the Joint Conference on Digital Libraries. [e-journal ACM DL]
• Open Archives Initiative FAQ

• Browse through the Dublin Core Projects list. Choose one (from this list or another project that uses DC) and be prepared to discuss it in class on Tuesday, 3/8/05.

Thursday, 3/3/05: Metadata -- XML, RDF

• Bray, T. (2001). What is RDF?
• RDF Primer , W3C 2004, Sections 1 and 2. (and as much more as you’d like)
• XML Tutorials. – You can start with the basic. (optional --–as much as you need)
• Powell, A. (2003). Expressing Dublin Core in HTML/XHTML meta and link elements.
• Beckett, D. (2002). Expressing simple Dublin Core in RDF/XML

Tuesday, 3/8/05: Metadata --– Applications

• NSDL Metadata Primer, from the National Science Digital Library Metadata Management group.

• Be ready to discuss DC-related project

SEMANTIC WEB

• Berners-Lee, T., Hendler, J. & Lassila, O. (2001). The Semantic Web. Scientific American, 284(5), May. [e-journal]
• Greenberg, J. (ed.) (2003). ASIST Bulletin, 29(4), Special Section on the Semantic Web.

• Reflection paper 1 due.

Tuesday 3/15/05 & Thursday, 3/17/05: Spring Break, no class

CLASSIFICATION

• Hunter, E. (2002). Classification Made Simple. Ashgate. Pp. 1-24. [e-reserves]
• Langridge, D. (1992). Classification: Its Kinds, Elements, Systems and Applications. Pp. 2-23; 76-78. [e-reserves]
• Ranganathan, S. (1985). Facet Analysis: Fundamental categories. In Chan, Richmon & Svenonius (eds). Theory of Subject Analysis: A Sourcebook, Littleton, CO Libraries Unlimited. 88-96. [e-reserves]

Thursday, 3/24/05: Classification, cont.

• Parsons, J. & Wand, Y. (1997). Choosing classes in conceptual modeling. Communications of the ACM 40(6), 63-69. [e-journal, ACM DL]
• Priss, U. & Jacob, E. (1999). Utilizing faceted structures for information systems design. Proceedings of the 62nd Annual Meeting of the American Society for Information Science, 203-212. [e-reserves]

Tuesday, 3/29/05: Classification, cont.

• Efron, M., Elsas, J. Marchionini. G & Zhang, J. (2004). Machine learning for information architecture in a large governmental website. Proceedings of the 2004 Joint ACM/IEEE Conference on Digital Libraries (JCDL 2004). 151-159. [e-journal, ACM DL]

• NIST exercise
• Assign Homework 2, due Thursday, 4/7/05.

Thursday, 3/31/05: Classification -- Ontology

• Gruber, T. (n.d.) What is an Ontology?.
• Guarino, N. & Welty, C. (2002). Evaluating ontological decisions with Ontoclean. Communications of the ACM, 45(2), 61-65. [e-journal, ACM DL]
• McGuinness, D. & van Harmelen, F. (Eds.) (2004) OWL Web Ontology Language Overview
• OWL FAQ from W3C.

• CYC upper level ontology
• SUO upper level ontology
• Portion of GovStat statistical ontology
• WordNet

Tuesday, 4/5/05 & Thursday, 4/7/05: Classification -- Ontology, cont.

• Protégé.
• Getting Started with Protégé
• You may also want to look at some existing ontologies.
  • Ontolingua
  • DAML Ontology Library
  • CYC
  • MICROKOSMOS, for MT.
  • SENSUS (Hovy, 2002). MT
  • GALEN medical ontology.
  • Others?

• Homework 2 due.
• Assign Reflection paper 2, due Thursday, 4/21/05

LANGUAGE

• Soergel, D. (1985). Organizing Information. San Diego, Academic Press. Terminological Control, 213-224. [e-reserves]
• Soergel, D. (1985). Organizing Information. San Diego: Academic Press. Index Language Structure I: Conceptual, 251-287. [e-reserve]
• Bates, M. (1998). Indexing and access for Digital Libraries and the Internet. Journal of the American Society of Information Science, 49(13), 1185-1205. [e-journal]
• Batty, D. (1998). WWW -- Wealth, Weariness or Waste: Controlled vocabulary and thesauri in support of online information access. D-Lib Magazine, November.

• Homework 2 due.
• Assign Reflection paper 2, due Thursday, 4/21/05

Thursday, 4/14/05: Controlled Language and Vocabulary

• Fast, K., Leise, F & Steckel, M. (2002). All about facets & controlled vocabularies
• Fast, K., Leise, F & Steckel, M. (2002). What is a controlled vocabulary?
• Fast, K., Leise, F & Steckel, M. (2003). Creating a controlled vocabulary
• Fast, K., Leise, F & Steckel, M. (2003). Synonym rings and authority files
• Fast, K., Leise, F & Steckel, M. (2003). Controlled vocabularies: A Glosso-Thesaurus
• Johnson, E. (2000). Talking across frontiers. Paper presented at International Conference on European Cross Border Cooperation: Lessons for and from Ireland.

Tuesday, 4/19/05: Names

• Johnson, J. (2000). Textual bloopers. interactions, 7, 5, 28-48. [ejournal, ACM DL]
• Amitay, E. (2000). Anchors in context: a corpus analysis of authoring conventions for web pages. in L. Pemberton & S. Shurville. Words on the Web: Computer Mediated Communication. Portland, OR: intellect. 25-35. [PAM]
• Department of Amplification (1957). New Yorker column on the naming of the Edsel. [PAM]

INFORMATION ARCHITECTURE

• Rosenfeld, L. & Morville, P. (2002). The Anatomy of an Information Architecture. In Information Architecture for the World Wide Web, (aka "The Polar Bear Book"), O'Reilly, Ch. 4. [PAM]
• Defining the Damn Thing, especially section 3.5.
• Glossary of Terms. Consider this as an initial listing of concepts composing or otherwise relating to information architecture.
• Wodke, C. (2001). Defining information Architecture Deliverables. What you need to deliver to a client should help define what information and activities are needed.

• Reflection paper 2 due.

Tuesday, 4/26/05: Information Architecture, cont.

Thursday, 4/28/05: Wrap-up, course evaluation.

• Assign Take-home Final Exam, due Tuesday, 5/3/05, 12:00 noon.

Tuesday, 5/3/05:Take-home Final Exams due, 12:00 noon.