1 / 21

Do as I Say, Not as I Did

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.

mizell
Download Presentation

Do as I Say, Not as I Did

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. Mudd’s first web page, c. 1997

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

  4. TODAY

  5. File Structure of the 1997 web page

  6. Outline of the 1998 web page

  7. Today’s web page

  8. Naming Conventions • Upper vs. lower case vs. mixed • .htm vs. .html • collection formula (1st 8 characters etc.)

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

  10. Databases/Photos • Naming/numbering conventions again! • Additions to… • 72 dpi on website • Pay close attention to student data entry

  11. Format • Tables • .HTML vs. .SHTML (footers with home page option) • Meta data tags

  12. Format II • No Frames! • Small files for modem users? • DIV tags instead of tables?

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

  14. Don’t Forget to… • BACKUP!

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

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

  17. PHP: The future?

  18. PHP: operational outline

  19. Finally... • Create a manual for all of this! • (Be prepared to revise it frequently)

  20. dlinke@princeton.edu

More Related