Web-at-Risk Meeting, 8.2.2006

NDIIP (National Digital Information Infrastructure and Preservation Program)

Meeting Participants

Kathleen Murray

Inga Hsieh

Valerie Glenn

Starr Hoffman

can add further comments or questions to the Web-at-Risk wiki

Guidelines p.26

Template p.13

• perhaps change order of appendices, so that Web Archiving, the most common aspect, will appear first
• will change some of the language here to read more clearly about required/optional aspects

Guidelines p.12

• take out term "default"
• also explain more about the "pre-set... three link-hops"
  • add "link-hop" to the glossary
  • explain the difference between scope settings (either internal or external) and link-hops (doesn't discriminate between interior/exterior)
• will probably use trial & error to determine the correct # of link-hops
• link-checker will probably not be built into WAS; curators will be responsible for running a separate link-checking program

Guidelines p.5

• diagram with arrows; adding explanatory sentence about not all stages being linear
• website "name" differs from the title tag; more like the name of the organization, host
  • there will also be a user manual for issues of this type

Guidelines p.15

• there may not be much in the document about presentation (customizing)
• unsure of answer; will be under development in 2007, so they won't be involved
• may at some point give notification that user is in an archive (like CC)
• this page talks specifically about preserving the code for email links
  • curator specifies in collection plan if this is necessary to include for your user group (RFP, required/desirable)
• don't know about standard descriptive metadata
  • some standard will be captured (date, time, title, etc.)
  • depends on search functionality, how you'll use the metadata
  • images, docs could have object-level metadata; may not be offered
  • main concern: what does your user group need?
• write regular review dates for the collection plan for regular maintenance (see "Maintenance" section of document)
• METS = frame for presentation metadata
• we'll probably use the UNT schema

Guidelines p.20

• restriction/authentication needs to be determined by each institution (not WAS)

Guidelines p.21

• "archive service provider" = CDL (will put in parenthesis)

Guidelines p.22

• "collection membership" = the sites that are "members" of the collection
  • ask: does this still belong in the collection?
• higher level than the seed list (also more abstract than technical)
• if a website's organization changes, it may no longer apply to your collection
• will come up with a better phrase for this

Template p.5

• this is for specific sites that need explanation
• not for URLs in the seed list (collection level, not individual site level)
• can create as many appendices as needed (examples, standard reports, maintenance records)

Template p.8

• if you can't fill it in yet, just make a note about that

Template p.10

• "them" = user groups

Back to the Projects & Digital Initiatives Page

Back to the Front Page