70 likes | 146 Vues
Quality Assurance. Incoming and ongoing using the DCS Linkchecking protocol. DLESE Catalog System. Contribute Distributed, web-based cataloging Creates XML records in DLESE-IMS format, unique ID-URL mapping
E N D
Quality Assurance Incoming and ongoing using the DCS Linkchecking protocol
DLESE Catalog System • Contribute Distributed, web-based cataloging • Creates XML records in DLESE-IMS format, unique ID-URL mapping • Manage Distributed workflow, restricted access, record editing and status management • Directory structure reflects status of record
DCS QA Pre-accessioning • Manage module used for pre-accessioning QA of DCC and DWEL collections • Review of each record in Submitted for • URL functional, content within scope • Description (spelling, grammar etc) • No special characters • Required metadata present and correct • Coverage data correct (prefix syntax)
DCS QA – Post accessioning • Manage module used to locate records flagged by Idmapper (by ID number) or as requested by contributer • Password protected editing, URL change enabled here • Status change enabled • Move back to submitted for community edit • Move to holding if de-accessioned temporarily or permanently
Linkchecking process • Uses idmapper output on • error type, vitality over time, primary/mirror disconnects and duplicate URLs • Goal of < 5% inaccessible URLs • External collections- reports forwarded to collection builder for followup • Internal collections (records held at DPC) • Contracted QA collections (DCC, DWEL, EvalToolKit, JESSE) DPC QA staff initiate corrective action • Collection level records, overarching collections (Katy initiates corrective action)
Corrective action ….. • Check validity of Idmapper error report • Update URL on basis of report data if valid • (DCS or XML Spy depending on collection) • If URL down for > 3 days • Search for new URL and replace if found • Contact resource creator via email regarding status of site, make changes as indicated by response • If no response, move to holding directory (DCS or Windows Explorer if EvalTkt) • New status and updated are propogated forward to DDS in next update of collection (1-3 weeks)
Workflow challenges • Distributed, multiple workers need central record keeping with more detail noted • Temporary plan, Excel sheet attached to swiki • Need a human to track tasks • what, why and when action taken • follow up emails to creators – reply? • periodically check items placed in holding for subsequent re-activation • Updates/corrections not immediately indexed • External collections follow different protocol • Not scalable as number of collections/items grows