do as i say, not as i did

21

Upload: mizell

Post on 08-Jan-2016

96 views

Category:

Documents


2 download

DESCRIPTION

Do as I Say, Not as I Did. Lessons Learned On Archival Web Page Management Dan Linke Seeley G. Mudd Manuscript Library Princeton University Poughkeepsie MARAC/NEA meeting, October 25, 2002. Mudd’s first web page, c. 1997. Mudd’s second web page, c. 1998-2001. TODAY. - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Do as I Say, Not as I Did
Page 2: Do as I Say, Not as I Did

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

Page 3: Do as I Say, Not as I Did

Mudd’s first web page, c. 1997

Page 4: Do as I Say, Not as I Did

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

Page 5: Do as I Say, Not as I Did

TODAY

Page 6: Do as I Say, Not as I Did

File Structure of the 1997 web page

Page 7: Do as I Say, Not as I Did

Outline of the 1998 web page

Page 8: Do as I Say, Not as I Did

Today’s web page

Page 9: Do as I Say, Not as I Did

Naming Conventions

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

characters etc.)

Page 10: Do as I Say, Not as I Did

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, …)

Page 11: Do as I Say, Not as I Did

Databases/Photos

• Naming/numbering conventions again!

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

entry

Page 12: Do as I Say, Not as I Did

Format

• Tables

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

• Meta data tags

Page 13: Do as I Say, Not as I Did

Format II

• No Frames!

• Small files for modem users?

• DIV tags instead of tables?

Page 14: Do as I Say, Not as I Did

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.

Page 15: Do as I Say, Not as I Did

Don’t Forget to…

•BACKUP!

Page 16: Do as I Say, Not as I Did

Staffing issues

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

Page 17: Do as I Say, Not as I Did

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.)

Page 18: Do as I Say, Not as I Did

PHP: The future?

Page 19: Do as I Say, Not as I Did

PHP: operational outline

Page 20: Do as I Say, Not as I Did

Finally...

• Create a manual for all of this!

• (Be prepared to revise it frequently)