JISC-PoWR Workshop 1 - Recently Updated Pages

Breakout2Scenario2

Anonymous — Wed, 02 Jul 2008 11:21:44 CDT

The University of Poppleton provides prospective students with a printed copy of their prospectu, and only limited information on courses has been made available on the institutional Web site; this information is fairly general to avoid legal vulnerabilities and to minimise maintence issues. However the Web team would now like to move towards an online driven model but are unsure of how to proceed.

You are a member of the Online Prospectus steering group and have a particular interest in preservation of Web resources.

Exercise

What challenges will an online prospectus present? Consider both the technical and cultural challenges. Who has responsibility for such a project?

Which of the challenges have preservation implications? What are the implications?

What potential solutions are there for the preservation implications?

Breakout1B

Anonymous — Wed, 02 Jul 2008 11:21:04 CDT

Technical Barriers to Web Resource Preservation

The strategic importance of institutional Web sites is now widely recognised but their preservation often remains low priority. Why is this? What are the barriers that hinder those involved from embedding Web resource preservation strategies into their working practice?

What are the main technical challenges related to Web resource preservation?

data structure
External dependancies
Database driven content
Identify content to archive
Format decay
How long to maintain for?
Copyright
Maintenance
Interoperability of standards
numerous servers, sub domains
storage
recreation of user experience
dynamic content

Identify the top three challenges.

URIs - organisation of web site
Deep Web
External Services

Identify solutions to these challenges.

Redirects
Tools

-----------------------------------------------------------------------------------------------------------------------------------------------------------------
Further notes are given below (based on notes held Google docs).

ORGANISATION OF WEBSITE, URIs etc:

Subdomain setup for preservation; CMS unable to cope
Multiple sites (subdomains) on same server not cross linked
Mirroring/spidering tools can't find them all (HTTrack takes domain as starting point... without links can't find other subdoms)
Resource discovery
Preservation/persistence of URLs.
Managing redirects. Difficult with tools available
Versioning (not supported in URIs)
Do we need more formal policy about URI management allocation?
Website that doesn't reflect organisational structure is not good for management, navigation, customers etc. - but n.b. organisation structure may change.
"Architectural approach" to managing URI schemes etc. (but not bound to transient organisational structures - “logical” structure)

STORAGE SPACE:

Storage space issue with automated archiving where pages changed frequently.
(WE need to define/determine how CMS tools behave when archiving/versioning.)

DEEP/DYNAMIC WEBSITES:

Spidering not always appropriate for db-driven websites. How to do database snapshots meaningfully and practically?
How to recreate user experience?
PERSONALISATION of web sites/experiences: how to capture that.

OWNERSHIP:

"Temporary" websites. Don't know who or what school in university is responsible

WHAT TO KEEP:

HOW to decide when keeping the user experience is important; or when underlying information is enough?
HOW to preserve when external services used (e.g. Google Maps, Facebook)
HR and recruitment- if external services used. (Contract with external service should reflect institutional policy.)
Streaming media?
ReSTORE: web resources must be mature and complete (closed? finished?) before archiving
IPR issues around taking resources and putting them in a new domain.
ReSTORE is a bit like a "Home for orphaned websites" (cp. UKWAC?)
Quality control - appraisal
Distinction between archives and records. Organisation would have specific rules about location etc of archive

WHY KEEP?

What's the purpose of preservation? Will dictate different solutions. ReSTORE, UKWAC can archive "finished" things. Other needs may be dynamic.
Example: Scholarship application deadline contested. CMS history proved applicant was wrong.

PRESERVATION MANAGEMENT AND PLANNING

CURATION of resource needs to be actively managed and funded (WILL PoWR guidance include details of costs and implications?)
(Retention period: 5-10 years typically: keeping h/w and s/w to maintain resources over that period ought to be possible.)
Maybe we do have to preserve the equipment/browser/SW? Is it viable?
These things need to be built in from the beginning. "Funding for project website..." doesn't include preervation planning.
Recrords retention policy may make no reference to web.
How do we distinguish between retention periods for different web pages? (Automatically)
Archive.org useful - but beware of depending on it completely.

JISC-PoWR Workshop 1 Home

Anonymous — Wed, 02 Jul 2008 04:25:35 CDT

This workshop is part of the JISC Preservation of Web Resources project. For more information about the project, see the project blog.

About the Workshop:

Title: Preservation of Web Resources: Making a Start
Location: Dr Seng Tee Lee Room at Senate House Library, University of London
Date: Friday 27th June 2008
Time: 10.30 am - 4pm, lunch to be provided
Facilitators: Marieke Guy, Ed Pinsent, Richard Davis, Kevin Ashley

Programme:

10:00 - 10:30 Registration and coffee
10:30 - 12:45 Morning Sessions

Presentation: Preservation of Web Resources Part I
Breakout session: What are the Barriers to Web Resource Preservation?
Presentation: Challenges for Web Resource Preservation
Presentation: Bath University Case Study

13:00 - 14:00 Lunch
13:45 - 16:00 Afternoon Sessions

Presentation: Legal issues
Breakout session: Preservation Scenarios

15:00 - 15:15 Coffee

Presentation: Preservation of Web Resources Part II

16:00 End

This one day workshop is aimed at all those interested in issues relating to Institutional Web resource preservation. Through presentations and discussion group sessions it will introduce the concept of Web preservation, consider its importance and discuss the technological, institutional and legal challenges it presents. It will also look at ways you can begin to preserve your Web site, both in the short to medium term, and permanently. The workshop is intended to be interactive and will encourage open discussion. Lunch will be provided and participants will receive copies of the workshop handouts.

Breakout1A

Anonymous — Mon, 30 Jun 2008 05:26:55 CDT

Group B – Institutional and Organisational Challenges

The strategic importance of institutional Web sites is now widely recognised but their preservation often remains low priority. Why is this? What are the barriers that hinder those involved from embedding Web resource preservation strategies into their working practice?

What are the main institutional and organisational challenges related to Web resource preservation?

low priority
Confusion over responsibility
complexity of Web
No key driver
selection choices
IPR

Identify the top three challenges.

management buy in - costs
not sure of what you've got
What should we archive - conflict of interests

Identify solutions to these challenges.

Motivator for management

Breakout2Scenario5

Anonymous — Mon, 30 Jun 2008 03:13:51 CDT

There is no abstract available for this page revision.

Breakout2Scenario4

Anonymous — Mon, 30 Jun 2008 03:13:38 CDT

There is no abstract available for this page revision.

Breakout2Scenario3

Anonymous — Mon, 30 Jun 2008 03:13:19 CDT

There is no abstract available for this page revision.

Breakout2Scenario1

Anonymous — Mon, 30 Jun 2008 03:12:41 CDT

There is no abstract available for this page revision.