• Save
Quality Assurance and Cataloguing
Upcoming SlideShare
Loading in...5

Quality Assurance and Cataloguing






Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

Quality Assurance and Cataloguing Quality Assurance and Cataloguing Presentation Transcript

  • Quality Assurance and Cataloguing Dr. Essam Obaid
  • Quality Assurance Quality assurance is the essential component of any web archivingprogram. All collection methods involve some degree of automationto ensure that the selection policy and the collection list are actuallybeing implemented successfully. The greater the scale of collectionundertaken, the more basic the level of quality assurance that can be employed. These is a trade off between the number of resourcesthat can be collected and the quality control which can be applied to them, and a policy decision is required as to the minimum acceptable level of assurance.
  • PRE-COLLECTION TESTINGPre-collection testing is concerned with the identification ofpotential issues that may affect the quality of collected contentbefore its acquisition. It is clearly desirable to identify andremove all the potential problems before collection. Pre-collection testing will typically include two approaches:1- Resource Analysis and2- Test Collection
  • Resource AnalysisIt involves the manual or automated analysis of the target webresource, in order to identify the appropriate method and anyissues that are likely to arise during collection. In resourceanalysis it should be necessary to determine- Website is static or dynamic- Resource target is linked or available through database queries- Suitable Collection Method (remote harvesting or other technique)
  • Test Collection If a target web resource is only intended to be collected on a single occasion, and if the resource is going to be collected repeatedly, than it may be beneficial to undertake a testcollection. This will allow the selected collection method to be fully evaluated, and any necessary corrections made to the collection parameters.
  • Post Collection Testing This type of technique is followed after the collection has been made. The most feasible approach will be to test a representative sample of the collected material, the size of the sample being determined by the volume of the collection and available resources.To ensure the consistency the test should be based on a standard test script, which describes the precise test to be conducted andallows recording of the results. The test script should be followed using two browser windows, for both the live and archived versions of the web resource: this allows the valid comparison between the results.
  • Example of Testing Types- Availability of website snapshot- Functionality of the Navigation- Date and Time- Frames- Text- Images- Multimedia Content (audio/video/flash animations)- Downloadable Content- Search Facility
  • Issue TrackingTesting at the pre and post collection stages may identifies issues that need tobe addressed, and an efficient system for logging, tracking and resolving thoseissues lies at the heart of the quality assurance process. Every issue identifiedmust be recorded in a standard issue log, and include the followinginformation..- Nature of the issue- Severity of the issue- The date when it was identified- The name of the person who identify it- The individual/ the process or organization able to resolve the issue- The expected resolution date.Once the issue has been passed on for the resolution the log should bemonitored periodically for outstanding issues and any necessary action takento facilitate their resolution.
  • Issue TrackingOnce the issue has been resolved the following informationshould be saved in the appropriate log- The date on which the issue is resolved- The manner in which it is resolved- An indication of whether the issue is now closed, or if the resolution is unsatisfactory remains open.