• What XP can do, how to use more of it's features?
• Why XP is better than Win 2000?
• Easy Registration hacks,
• Possibly incorporating Office 2K & 2003 and the differences in Powerpoint, Outlook & Word,
• Microsoft backup,
• Remote Assistance, and,
• Windows SP2--the good & the bad, how to configure it

Designed for business, professional and academic research, Onfolio is a PC application for collecting, organizing and editing online content, reading RSS news feeds, publishing to email, blogs, web sites and creating RSS feeds for items and collections posted on websites and weblogs. With Onfolio you get all of these tools in a single application. Onfolio is an add-on to Microsoft Internet Explorer and Mozilla FireFox, is 100% integrated with Windows OS, Microsoft Office and EndNote.

Several projects created with Onfolio at WSU Law Library that will be shared with CALI attendees:

• the Fall 2004 Law Library orientation package that was produced as a single multi-part html (mht) file on 16 MB USB flash drives that were provided free to all first year law students; product is installed on the network, updated and made available for synchronization to all law students using the law library computer lab
• collection of all library resources and services that was created for the WSU Law School faculty and made available via the Law Library Twen web course
• guide to creating and bringing West IntraClip RSS feeds to Twen that was created and shared with the WSU faculty and the academic law library community via multi part html (mht) and html files (including RSS feeds)

Onfolio features that will be demoed at CALI: Collecting content

• collect bookmarks
• capture local copies of web pages, PDFs, Office Documents
• capture snippets of text and graphics and multi-page articles
• capture lists of links and complete or partial web pages
• capture e-mails directly from Outlook and shortcuts to documents on your PC

Organizing research

• browse captured content in Explorer style sidebar
• create individual research collections
• add comments, keywords and flags
• highlight sections of captured web pages
• search for documents and web pages by content
• create dynamic views of Search Folders
• add bibliographic reference data to items & share with EndNote

RSS (aggregation & syndication)

• read news feeds in your browser
• subscribe to feeds with one click
• organize feeds using Windows-style folders
• read feeds in newspaper view
• capture content from feeds
• read feeds in detail view
• e-mail, capture & blog (Movable Type, LiveJournal, Blogger, TypePad) items as you read
• add items to reading list for follow-up
• search your feeds
• create and monitor persistent web searches

Collaborating

• store Onfolio collections on a LAN (Read only)
• collaborate with Onfolio collections (Read/Write)
• subscribe to notifications for shared collections

Sharing research

• post individual items to a weblog
• e-mail items, folders and collections
• publish folders and collections to a weblog
• publish folders and collections to a web site
• publish reports with bibliographic references
• create multi part html (mht) reports with Onfolio Publisher
• share content with Microsoft Office applications
• export items and collections to XML
• exchange reference data with EndNote
• syndicate your items and collections (create RSS feeds)

Thomas Nelson Blogging Guidelines

At Thomas Nelson, we want to encourage you to blog about our company, our products, and your work. Our goal is three-fold:

* To raise the visibility of our company,

* To make a contribution to our industry, and

* To give the public a look at what goes on within a real live publishing company.

Therefore, we have established a “blog aggregator page” that is linked to the ThomasNelson.com Web site. “House Work,” the name of this page, contains links to employee blogs, along with the first few sentences from the most recent entry. The page is automatically updated whenever a blogger creates a new post. This way readers can quickly scan new entries, click on those that interest them, and then read the entry on the blogger’s site. This makes it convenient for people who are interested in reading employee blogs. It also helps publicize individual blogs and generates traffic for everyone.

In order to give some direction to employees who wish to blog, we have established a “Blog Oversight Committee” or “BOC.” This is a group of fellow-employee bloggers who are committed to promoting blogging within our company and making sure that the Company’s interests are served.

If you would like to have us link to your blog, you must submit it to the BOC. Before doing so, you should design your blog and write at least one entry. Once you have done this, send an e-mail to Gave Wicks with a link to your blog. The BOC will then review your blog and notify you whether or not it meets the criteria.

In order to participate in this program, you must abide by the following guidelines. (Please keep in mind that review by the BOC and participation in this program does not absolve you of responsibility for everything you post.)

1. Start with a blogging service. We do not host employee blogs. We think it adds more credibility if the Company does not officially sponsor them. Therefore, please use one of the many third-party blog hosting sites on the Internet. Some of these are free, such as Blogger.com, LiveJournal.com, Blog-City.com, Xanga.com, and MSN Spaces. Others charge a nominal fee. Examples include TypePad.com, SquareSpace.com, BlogIdentity.com, and Bubbler.com. If you use one of the latter, any expense is your responsibility.

2. Write as yourself. In other words, please use your real name. We don’t want people writing anonymously or under a pseudonym. Your name should be prominently displayed on your blog’s title or subtitle. This will add credibility with your readers and promote accountability within our company.

3. Own your content. Employee blog sites are not Company communications. Therefore, your blog entries legally belong to you. They represent your thoughts and opinions. We think it is important that you remind your readers of this fact by including the following disclaimer on your site: “The posts on this blog are provided ‘as is’ with no warranties and confer no rights. The opinions expressed on this site are my own and do not necessarily represent those of my employer.” You assume full responsibility and liability for all actions arising from your posts. We also encourage you to put a copyright notice on your site in your name (e.g., “© 2005, John Smith”).

4. Write relevant. Write often. Whether you know it or not, you are an expert. You have a unique perspective on our company based on your talents, skills, and current responsibilities. People what to hear about that perspective. Also, in order to develop a consistent readership, you should try to write on a regular basis. For some, this will be daily; for others, it may be weekly. The important thing is consistent posting. New content is what keeps readers coming back. You may also write on company time, provided it doesn’t become excessive and doesn’t interfere with your job assignments and responsibilities.

5. Advertise—if you wish. While there is no requirement to run ads on your blog, you are free to do this if you wish. Some of the free blog services run ads as a way to offset their costs. If you use such a service, you won’t have a choice. On the other hand, if you pay for your service, you can avoid advertising altogether or participate in a service like Google’s AdSense or Amazon’s Associate Program. These types of programs will pay you based on “page views,” “click-throughs,” or purchases made on participating Web sites. You might want to ask the BOC or fellow bloggers for suggestions. The only thing we ask is that, to the extent you have control, you run ads or recommend products that are congruent with our core values as a Company.

6. Be nice. Avoid attacking other individuals or companies. This includes fellow employees, authors, customers, vendors, competitors, or shareholders. You are welcome to disagree with the Company’s leaders, provided your tone is respectful. If in doubt, we suggest that you “sleep on it” and then submit your entry to the BOC before posting it on your blog.

7. Keep secrets. Do not disclose sensitive, proprietary, confidential, or financial informa-tion about the Company, other than what is publicly available in our SEC filings and corporate press releases. This includes revenues, profits, forecasts, and other financial information related to specific authors, brands, products, product lines, customers, operating units, etc. Again, if in doubt, check with the BOC before posting this type of information.

8. Respect copyrights. For your protection, do not post any material that is copyrighted unless (a) you are the copyright owner, (b) you have written permission of the copyright owner to post the copyrighted material on your blog, or (c) you are sure that the use of any copyrighted material is permitted by the legal doctrine of “fair use.” (Please note: this is your responsibility. The Company cannot provide you with legal advice regarding this.)

9. Obey the law. This goes without saying, but by way of reminder, do not post any material that is obscene, defamatory, profane, libelous, threatening, harassing, abusive, hateful, embarrassing to another person or entity, or violates the privacy rights of another. Also, do not post material that contains viruses, Trojan horses, worms, or any other computer code that is intended to damage, interfere with, or surreptitiously intercept or expropriate any system, data, or information.

10. Remember the Handbook. As a condition of your employment, you agreed to abide by the rules of the Thomas Nelson Company Handbook. This also applies to your blogging activities. We suggest you take time to review the section entitled, “Employee Responsibilities” (pp. 36–39).

If you do not abide by the above guidelines, we reserve the right to stop linking to your blog.

If you wait until a request for service arrives before you have considered how to provide it, you probably won’t provide good service.

This session will look at a number of ways you can get a jump on service requests – before they are even requested.

W. Ken Woo
Director of Law School Computing
Northwestern University School of Law
k-woo at law dot northwestern dot edu

Dan Manier
Director of IT
Notre Dame Law School
manier at nd dot edu

This session will offer a brief case study of the systems used for publishing the decisions of the US Supreme Court on the LII site, warts and all, with due attention to metadata and editorial content. Possible topics for technical discussion include the LII's use of LAMP, swish-e, Mason, Linux-based clustering, Amanda, perl, and python -- bring questions.

Thomas Bruce
Director, Legal Information Institute
Cornell Law School
trb2 at cornell dot edu

Sara Frug
Editor, Legal Information Institute
Cornell Law School
ssf6 at cornell dot edu

Brian Laurence Hughes
Web Developer, Legal Information Institute
Cornell Law School
blh at pobox dot com

Daniel Nagy
Sys Admin, Legal Information Institute
Cornell Law School
dn56 at cornell dot edu

Dave Shetland
XML Architect, Legal Information Institute
Cornell Law School
das85 at cornell dot edu

CiteStation presents a series of ALWD or Blluebook citation exercises in the context of legal documents, such as a memorandum, contract, or pleading. Each exercise contains embedded questions that examine the student's mastery of how, when, and why to cite legal authorities. Students and professors can view individual and class responses to each question.

Editing Essentials is a series of online exercises designed for law review and journal staff. Exercises cover subjects, such as ensuring that the cited source supports the proposition, detecting and avoiding plagiarism, determining the scope of cited sources, when to paraphrase, evaluating the quality of web resources, international citation, and citation rules for scholarly writing, broadcasts, interviews, unpublished materials, and web sites.

Carolyn Weaver
Senior Instructional Designer
Thomson-West
carolyn dot weaver at thomson dot com

At the University of Texas, we rolled out several new technologies in less than a year: Outlook/Exchange, Blackberry, Brightmail, computer-based voicemail and soon: Windows server, XP and Office 2003. We learned a lot about Change Management - both good and bad. Join us to learn what worked, what didn't and how to land in one piece.

June Liebert
Law Library Director and Asst. Professor
John Marshall Law School, Chicago
8liebert at jmls dot edu

John W Croslin
Senior Systems Analyst
University of Texas School of Law
jcroslin at law dot utexas dot edu

Michael Harvey
Director of Technology
University of Texas School of Law
mharvey at mail dot law dot utexas dot edu

Additional information: I will be going through the entire creative process of writing a master JSP/XSLT script for our site's redesign, from initial requirements to bug fixes. The JSP used can be easily implemented using ASP, PHP, or one of many other C based languages. The master script created also integrates with content management systems and other third party web administration tools. I hope to encourage quite a bit of audience participation, "writing" the script together and problem solving as a group.

Nathan Stryker
Web Services Manager
Pepperdine University School of Law
nathan dot stryker at pepperdine dot edu

One of the innovative featues of A2J-Author is the interface. It uses a cartoon-like avatar that leads the client along a road while filling out the form. Once forms are created, they can be shared or modified for new jurisdictions.

A2J-Author may be quite interesting to law clinics or even for teaching law students about certain types of law practice. This session will demonstrate A2J-Author and explain the underlying work that went into its development. Feedback is welcome.

Jay Carle
A2J Project Manager
Chicago-Kent College of Law
JCarle at KentLaw dot edu

Open Editing: Technique, Law, Trust, and Temperament

Over 200 students responded to the survey duing a one-month period in April of May. The student responses were variously laudatory, frank and informative. Some of the results may surprise you as well.

Ronald W. Eades
Professor of Law
Louis D. Brandeis School of Law at the University of Louisville
ron dot eades at louisville dot edu

Ronald Benton Brown
Professor of Law
Nova Southeastern University Shepard Broad Law Center
brownr at nsu dot law dot nova dot edu

Joseph M. Grohman
Professor of Law
Nova Southeastern University Shepard Broad Law Center
grohmanj at nsu dot law dot nova dot edu

Part I of this session will provide an overview of the digital conversion project currently underway at the Rutgers-Camden School of Law Library. Part I will also examine the following topics:

1. Selection of digital conversion equipment (both hardware & software)
2. Selection and preparation of materials for scanning
3. Assembling and training a digital conversion team
4. Implementing quality control

Part II will address the technical computing issues of implementation, including selection of metadata, archival and production formatting, and methods for automated processing.

John Joergensen
Librarian
Rutgers, The State University of NJ, Camden
jjoerg at camlaw dot rutgers dot edu

PURPOSE:

Though many law faculty members at Wayne State University Law School are adept at integrating technology into their teaching, others have been hesitant to do so for a variety of reasons. According to Professor Rogelio Lasso of Washburn University School of Law, a tentative view toward the use of technology in the classroom is not peculiar to WSU law faculty, but is relatively common among law faculty across the country. See Lasso, Rogelio, From the Paper Chase to the Digital Chase: Technology and the Challenge of Teaching 21st Century Law Students, 43 Santa Clara L. Rev. 1 (2002). One reason cited for the hesitation in the use of technology in teaching is the fear that technology is fallible. Another reason cited is professors’ lack of knowledge about using some of the tools available to them in law school classrooms.

At Wayne State, as a part of the Library System, there are two departments that are relevant to faculty’s use of technology in teaching. The Department of Faculty Support & Media Services has as a part of its mission, the:

"support [of] teaching and learning at Wayne State University by providing the highest quality technical assistance, advice, and customer service in the areas of faculty research-related support, multimedia/audiovisual equipment support, audio and video streaming services, teleconference scheduling, and digital support for instruction. Library Computing and Media Services provides essential audio visual services and support to nearly 300 general purpose classrooms on the Main and Oakland Center Campuses."

The Office of Teaching and Learning:

"promotes excellence in teaching in the University at all levels. It supports individual faculty members in the development of instructional skills. OTL staff conduct workshops and seminars, observe classes, and assist in the drafting of teaching portfolios and in the development of instructional technology."

The purpose of the survey underlying this presentation is three-fold:

1. To determine the technology used by law school faculty;
2. To determine faculty members’ willingness to participate in training for the use of technology; and
3. To use the information collected formulate a basis for the planning of activities by OTL and clarification of procedures by Media Services geared specifically for law school faculty.

PROCESS:

The survey was developed by the presenter, a law librarian, with assistance regarding the technology from Michael Samson, Public Service Librarian in the Arthur Neef Law Library, using Zoomerang. The Survey was reviewed by the director of OTL and manager of Media Services. Representatives of both Media Services and OTL expressed interest in greater participation in the process; thus, a Brown Bag was conceived at which both could inform law faculty about their services.

It was decided that the Brown Bag should present members of OTL and Media Services to law faculty and law professors who integrate technology in their teaching were also approached to speak with the hope being their participation would enhance buy-in into the project. The final step was to seek the endorsement and participation of the Law School Dean’s Office.

GOALS:

The survey results will be used by OTL and the law library to plan seminars, workshops and classes during the fall 2005 semester to meet the interests and goals of the faculty. Where one-on-one sessions are appropriate, those will also be planned. Media Services is planning a manual for law faculty to describe the equipment available in the law school and the channels to obtain use and assistance with that equipment. The results of the survey will be used to enhance that manual.

Information will be shared with vendors to help them determine the amount of faculty training appropriate for the use of their systems and course management tools. If faculty members seek one-on-one assistance, those requests will be shared with them.

The presentation will chronicle this progress and leave the door open for a possible follow up session at next year's conference.

Lauren Collins
Public Service Librarian/Instruction Services
Wayne State University Law School
lmcollins at wayne dot edu

'Despite the tons of examples and docs, mod_rewrite is voodoo. Damned cool voodoo, but still voodoo.'
-- Brian Moore

This module uses a rule-based rewriting engine (based on a regular-expression parser) to rewrite requested URLs on the fly. It supports an unlimited number of rules and an unlimited number of attached rule conditions for each rule to provide a really flexible and powerful URL manipulation mechanism. The URL manipulations can depend on various tests, for instance server variables, environment variables, HTTP headers, time stamps and even external database lookups in various formats can be used to achieve a really granular URL matching...

...But all this functionality and flexibility has its drawback: complexity. So don't expect to understand this entire module in just one day.

Deb Quentel will lead you through the basics of authoring with CALI Author. Every attendee will have his or her own computer to work on and CALI Staff will be available to help you out and answer questions.

In Part II, Deb will cover more advanced uses of CALI Author including branching, multimedia and instructional design.

Deb Quentel
Director of Curriculum Development & Gen. Counsel
CALI
dquentel at cali dot org

While there are many well established ways of teaching students to build these chains, the evaluation and assessment step typically takes place at the end of the process, when the professor reviews a written product. From this “after the fact” position, the professor must deduce from a problem in the writing where the student went wrong in the pre-writing analysis. What would be ideal would be to have a way to evaluate the “linking and thinking” process earlier. The question, then, is how to evaluate how a student is progressing in building the chain *while they are building it.*

Legal writing teachers have tried many ways of “peeking” into this process. Generally, the methods used all follow some sort of interim evaluation of a written product that focus on each link. But if it were possible to review the full linking process before the writing begins, problems and issues could be identified before they are further compounded by the student starting the writing step before the linking steps are complete. If there were some way to review the student’s mental “map” of the case before they started writing anything – that would help.

Starting in the Fall of 2004, at the University of Denver Sturm College of Law all students in the 1L Lawyering Process class used a software product called CaseMap to list facts of the case problem, collect their research, and develop an outline for their major writing projects. This software creates a data file that each professor can review before the writing step begins. A review of that file can quickly reveal missing facts, gaps in research, gaps in understanding statutory and common law, and difficulties in building the link from analysis to outlining the problem.

I propose to share our work with CaseMap in the LP program, demonstrate how it works, and explain how it can be used to evaluate and assess critical steps in many different law school courses, not just legal writing.

David Thomson
L.P. Professor
University of Denver Sturm College of Law
dthomson at law dot du dot edu

1. You can stop it at the user through education,
2. You can stop it at the mail client with filters, spam-filtering software, etc.,
3. You can stop it at the server with filters, firewalls, etc.,
4. You can stop it before it's sent by strategically hiding your email addresses and other activities involving your webmaster and your users.

What mechanisms can be used to foster this collaboration? Three schools present their thoughts and experiences.

Pepperdine University School of Law recently separated the IT budget and much of its operations from the Law Library, establishing it as an "almost" separate department from the law library. Is it possible to find synergy in working together and sharing resources? We think so. Through coordinated budgeting, intradepartmental teams, and friendships we have found a path to nirvana if not a taste of it.

Duke University Law School created its computing services department twelve years ago and added an educational technologies department in 2001. Both departments and the library report to the same senior associate dean, and together all three departments focus on a single overall service mission.

Rutgers Camden School of Law has a strong history of collaboration between the IT department and the law library. While these departments are separate, they coordinate on several high profile projects and services.

Kenneth J Hirsh
Director of the Law Library and Information Technology
University of Cincinnati College of Law
ken dot hirsh at uc dot edu

Kenneth J Hirsh
Director of the Law Library and Information Technology
Duke University School of Law
ken dot hirsh at uc dot edu

Phillip C. Bohl
Director, Info Svcs & Assoc Dir Law Library
Pepperdine University School of Law
phillip dot bohl at pepperdine dot edu

Katie Kerr
Associate Director, Library Services
Pepperdine University School of Law
katie dot kerr at pepperdine dot edu

John Joergensen
Librarian
Rutgers, The State University of NJ, Camden
jjoerg at camlaw dot rutgers dot edu

Tom Ryan
Director of IT
Rutgers, The State University of NJ, Camden
tomryan at camlaw dot rutgers dot edu

Outline

• Introduction to YLS IT Services
  
• Student and Public Computing
  • Public Computing Facilities
    • Library Patrons and Alums, Visiting Researchers
  • Student Computing Facilities
  • Computer Classroom for training
  • Computer Cluster used for research and writing
  • Distributed Printing Services
  • Contract with Central Campus vendor for Printing services to provide printing in computer clusters
  • Initiatives: Began a partnership with the University Client-Site printing and copying group for printing and copying services, so that our students can use the same printID for printing and copying at multiple library and computer cluster locations outside of the law school.
  • IT Help Desk
    • 9am-7pm, 7 days a week
    • 12 student and casual employees
    • provide software, networking and hardware troubleshooting
    • Help monitor and maintain student cluster, classroom, and printing services
    • Initiatives: Information gathering and proactive support.
  • Laptop Support and Laptop Purchasing Program
    • All students strongly encouraged to have a PC or Mac laptop
    • We support: software installation and troubleshooting, data recovery, hardware repair, network configuration and troubleshooting
    • Laptop purchasing agreements with Apple and Dell to provide competitive pricing and limit configurations for support purposes
  • Training and Orientation
    • New Student Orientation
    • Internet Security Sessions
    • Student Computing Manual
    • Computer Assistant Handbook
    • Initiatives: Develop a curriculum for a series of informal computer and Internet literacy courses.
  • Technology Evaluation and Testing
  • Software License Contracts
  • New software and update testing and deployment
  • Dell and Apple

-installation of classroom technology balanced with effective use of mobile equipment,
-Reducing the clutter of technology in the classroom,
-Reducing the distractions of classroom technology,
-Instilling confidence in end users through training, consistent support and emergency response, and,
-Building communication tools such as online request forms.

Deb Kinney
Video Conferencing Specialist/Media Coordinator
Duke University School of Law
kinney at law dot duke dot edu

Wade Mitchell
Multimedia and Educational Specialist
Indiana University - Indianapolis School of Law
wamitche at exchange dot iupui dot edu

This session will discuss methods of "battening down the network hatches" and monitoring for compromised computers with tools you already have or can get for free. Microsoft's IPSec implementation can be used to limit exposure of vulnerable services to only trusted computers, but its configuration is not user-friendly. We will discuss IPSec background information, limitations, simple and more complex implementations for both servers and desktops, pitfalls to beware of, and methods of deployment. Also, Windows firewall has been greatly improved in Windows XP SP2, can be configured through scripts and group policy, and is complementary to an IPSec implementation.

Monitoring a large number of Windows computers for system compromise can be daunting. We will discuss methods for remotely checking multiple Windows computers for suspicious network connections and event log entries.

Michael Sparks
Director of Computing Services
Louisiana State University Law Center
msparks at lsu dot edu

This presentation will give an introduction to web services, REST and SRU. To illustrate these protocols we will demonstrate and discuss our library federated search application that includes an SRU implementation. This implementation enables our users to search our library catalog, journal and database titles, web resources, and digital library collections from the same interface. Using Perl and PHP wrappers we integrate MARC records, full-text indexes, and MYSQL databases into a group of collections that can be searched simultaneously. Other examples of REST-ful and non REST-ful web services of interest to librarians and web developers will be discussed. These include the Open Archives Initiative (OAI), OpenURL, LibraryLookup, the Amazon API, and the Google Web Services API.

Kevin Reiss
Head of Digital Services
Rutgers School of Law-Newark
kreiss at andromeda dot rutgers dot edu