eprintid: 1385
rev_number: 9
eprint_status: archive
userid: 24
dir: disk0/00/00/13/85
datestamp: 2016-06-08 20:44:06
lastmod: 2016-06-08 20:44:06
status_changed: 2016-06-08 20:44:06
type: conference_item
metadata_visibility: show
creators_name: Ammerman, Jack
creators_name: Ward, Michael
title: Scripted Primo Search Assessment Tool
ispublished: pub
subjects: meta
subjects: primo
divisions: eluna_conf
abstract: Have you been in any of these situations before... You've activated a large collection in PCI, yet don't know what impact it had on search results for end users? What is the breakdown of content in that collection? What about duplicate records across PCI or locally managed collections? Did that change to the search engine configuration or boosting rules have the intended effect?

To attempt to get a handle on these questions, we've been developing a Python script to query the Primo API, return and then compare the results to measure the impact of changes we've made. In this presentation we will go through some of our reasons for developing this, demo the script, present some possible conclusions, and invite discussion into expanding the utility of this tool.
date: 2016-05-06
date_type: published
full_text_status: restricted
pres_type: paper
event_title: ELUNA 2016 Annual Meeting
event_location: Oklahoma City, OK USA
event_dates: May 1-6, 2016
event_type: conference
refereed: FALSE
citation: Ammerman, Jack and Ward, Michael (2016) Scripted Primo Search Assessment Tool. In: ELUNA 2016 Annual Meeting, May 1-6, 2016, Oklahoma City, OK USA.
document_url: https://beta-documents.el-una.org/id/eprint/1385/1/Ward_Ammerman-ScriptedPrimoSearchAssessmentTool.pptx