Do as I Say, Not as I Did

Lessons Learned On Archival Web Page Management

Dan LinkeSeeley G. Mudd Manuscript LibraryPrinceton UniversityPoughkeepsie MARAC/NEA meeting, October 25, 2002

Mudd’s first web page, c. 1997

Mudd’s second web page, c. 1998-2001

TODAY

File Structure of the 1997 web page

Outline of the 1998 web page

Today’s web page

Naming Conventions

• Upper vs. lower case vs. mixed• .htm vs. .html• collection formula (1st 8

characters etc.)

Naming Conventions II

• Section Organization, i.e. Subdirectory structure (news, exhibits, etc.)

• News1, news2, etc.• Collection numbers for finding aid

file names• Multiple files for one finding aid

(a,b,c,d… or 1,2,3,4, …)

Databases/Photos

• Naming/numbering conventions again!

• Additions to…• 72 dpi on website• Pay close attention to student data

entry

Format

• Tables

• .HTML vs. .SHTML (footers with home page option)

• Meta data tags

Format II

• No Frames!

• Small files for modem users?

• DIV tags instead of tables?

Know when to stop….• They don’t call it the web for nothing.

• Set deadlines and down periods.

• Accept that anything you do will need to be updated tomorrow.

Don’t Forget to…

•BACKUP!

Staffing issues

• Who does what?• Professional vs. Support• Consider the training investment

If working with contractor...• Assume they know little about what

you do• Review their early outlines closely for

misconceptions• Get any files they custom create as

part of the deal (fonts esp.)

PHP: The future?

PHP: operational outline

Finally...

• Create a manual for all of this!

• (Be prepared to revise it frequently)

dlinke@princeton.edu