Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Quality assurance, psyc info presentation


Published on

  • Be the first to comment

Quality assurance, psyc info presentation

  1. 1. Quality Assurance, PsycINFO<br />
  2. 2. What exactly is “quality”?<br /><ul><li>Accuracy</li></ul>Is the information correct?<br /><ul><li>Consistency</li></ul>Is all of the information present?<br /><ul><li>Usability</li></ul>Can users find the information they need in the database?<br />We are striving to keep the database as clean as possible on a continual basis!<br />
  3. 3. What makes our users happy? <br />Quick responses to their inquiries<br />Thorough attention to their needs<br />Professional responses<br />
  4. 4. Major QA Tasks<br />Correct errors in the database reported by internal staff and external clients. <br />Produce a weekly serial corrections report in conjunction with the Content Development team. <br />Track corrections weekly (via weekly corrections log), monthly (via monthly QA reports) and annually (via annual report).<br />Provide feedback and training, as needed, to staff in order to improve quality practices. <br />Perform large scale cleanup projects as needed, typically in conjunction with the Systems team. <br />Other duties as assigned <br />
  5. 5. Who Reports Errors? <br />External Customers<br />Customers (authors, researchers, publishing staff, etc.) report errors to, also referred to as the Email App. The customer relations team fields those emails and routes those that need QA attention to the QA Specialist. The QAS will research and correct the error, respond to the customer, and log the correction in the corrections log.<br />External customers typically report errors in author name and article title, as well as missing journal content. <br />Additionally, Alvin will provide a monthly report of EBSCO–reported errors, also to be researched and reported by the QAS. <br />
  6. 6. Who Reports Errors? <br />Internal Staff<br />Journals Department – Elizabeth Bruce and other members of the Journals Staff will periodically report errors in APA Journals content, most often title or author typographical errors. <br />Bibliographic Production Staff – Bib Prod staff will periodically report errors they have found during their QC process. These will typically be errors in Journal Publication Month/Year or Vol/Issue. <br />Bib Production is also instructed to report any changes they have made to erratum statements at the QC level, so that the QAS can make equivalent changes to the original record. <br />
  7. 7. Who Reports Errors? <br />Internal Staff<br />PI Managers – Managers will often encounter errors in the course of their various functions and report those to the QAS. <br />Full Text Staff – The Full Text team (Led by Kathleen) will perform a pdf-full text matchup that will often uncover errors in the database. Svetla will typically report these to the QAS for correction. <br />Systems Team – Sabina and her team will work jointly with the QAS to correct errors in the database. Systems is responsible for larger-scale corrections and will often enlist the QAS for assistance if necessary corrections can be done via the corrections module. <br />
  8. 8. Common types of post-release errors(and the good people who report them)<br /><ul><li>Author name misspellings</li></ul>usually reported by authors<br /><ul><li>Typographical errors in titles</li></ul>often reported by researchers<br /><ul><li>ISSN and DOI errors</li></ul>often reported by librarians and vendors<br /><ul><li>Journal title and publisher errors</li></ul>often reported by PsycINFO staff during production<br /><ul><li>Publication month or season errors</li></ul>often reported by APA technical staff<br />
  9. 9. The Correction Process<br />Replicate the error.<br />Verify that the error originated within PsycINFO <br />Identify the specific cause of the error.<br />Determine the scope of the error.<br />Implement corrections.<br />continued…<br />
  10. 10. The Correction Processcontinued<br />Take preventive measures.<br /><ul><li>Offer feedback.
  11. 11. Make recommendations to staff and managers in the interest of prevention.
  12. 12. Suggest changes and enhancements to internal production systems.</li></li></ul><li>The Corrections Module <br />The QAS makes corrections via the Corrections Module interface in Hermes. <br />The fields that should be corrected via the corrections module are : <br />Author (name, role, and email)<br />Institutional Author (except state/province)<br />Correspondence Address (except State/Province)<br />Title<br />Abstract (except source)<br />ToC (except when needing to add or delete ToC entries)<br />Volume/Issue numbers <br />Season/Month <br />Corrections in all other fields should be referred to the Systems team. <br />
  13. 13. Weekly Serial Corrections <br />Every week, typically by Wednesday, the QAS produces a report that lists any serial-level corrections that have been reported by the Journals Content team. This report will include the Journal name and code, the type of correction, a description of the correction, the number of affected released records, and the number of related records still in workflow. <br />This report is sent to staff in Product Development, Content Development, and Systems. Systems then marks the records for correction at the end of the week. <br />
  14. 14. Corrections Log<br />The weekly corrections log is housed here: <br />S:Customer RelationsQuality AssuranceCorrectionsPost-Release CorrectionsPost-Release Error Logs<br />This log contains every correction that has been made via the corrections module, as well as corrections made by systems as noted on the weekly serial corrections list and the systems-generated weekly corrections log. <br />
  15. 15. Weekly External Error Report <br />The weekly external error report tracks the number of errors that have been reported via the email app. <br />The report can be found here: S:Customer RelationsQuality AssuranceWeekly External Error Reports<br />Michael Miyazaki accesses this report to track email app activity. <br />
  16. 16. Monthly and Annual QA Reports <br />Each month, the QAS produces a monthly report, synopsizing the quality assurance activity. An annual report is also produced, examining trends for the year. <br />Previous reports can be found here: S:Customer RelationsQuality AssuranceQA Reports<br />These reports have taken various forms over the years, and it may be prudent to rethink how they should be used going forward and what format would be most beneficial. <br />
  17. 17. Large Scale Projects<br />Occasionally, particularly around the time of reload, Systems may enlist the help of the QAS in completing large scale clean-up projects. <br />Last year, this included correcting erroneous characters in author name and title data in over 4,000 records. Projects of this magnitude are infrequent, but they do occur. Systems will alert you to any large scale projects for which they need assistance. <br />
  18. 18. Keys to Success<br />Ask Questions<br />Stay as Organized as Possible<br />Be Patient…there’s a Learning Curve<br />Remember Your Colleagues are Your Greatest Asset<br />Have Fun! <br />