Home » Posts tagged 'pnx'
Tag Archives: pnx
OneSearch, E-Resources, and Dedup
Over the winter break, OLS applied a major improvement to OneSearch results: we “de-deduped” many e-resource records!
The Problem
As OneSearch was initially configured, it applied its dedup process to all records equally, whether they were print or electronic.
What is dedup? The dedup process allows OneSearch to present a single result when the identical resource is held by multiple schools. Multiple records are merged into one display record. This is useful in the case of print resources, allowing the system to offer all CUNY locations to the user in one result.
However, this proved a major problem for e-resource records as the merged data includes the MARC 856 fields (which often provide links to electronic resources). OneSearch uses these fields to create a “View Online” button which links to full-text whenever the underlying metadata indicates this is the purpose of the field (see Why Does OneSearch Say We Have the Electronic Book?).
Deduped e-resource records with multiple 856 fields included in the merged records made it difficult for OneSearch to determine the correct availability for many deduped records. This resulted in the dreaded Full text may be available, see “Details” for links availability message with its accompanying grey dot and lack of a “View Online” button:
The Solution
E-resource records whose links require proxying are being prevented from matching other records for the purpose of deduping. This allows each local view to accurately identify the availability status of its e-resource:
The solution was only applied to records which require proxying on the assumption that e-resources that do not require proxying are freely available to everyone and should be shared with everyone.
The Caveat
Please note that this solution works best in the local school views. A version of the problem still exists for many records in the CUNY view. Instead of a single, deduped record, the CUNY view now displays a group of records (as they are now FRBRized instead of deduped):
Clicking on the title will take the user to a list of individual e-resource records. Records which are only available via a local library will still show the Full text may be available message in the CUNY view.
If you run across any problems, please be sure to report them to OLS by opening a work order with the CUNY Service Desk.
Behind OneSearch: Part 2 – View PNX and Source Records
In part two of this 3-part series about basic tools for understanding and troubleshooting results in OneSearch (Primo), you’ll find out how to view the PNX and also the source records “behind” search results. In part one, you learned about the structure of internal Primo records (PNX). In part three, we’ll show you how to use bookmarklets to easily view PNX and source records in one click.
Now that you understand Primo’s internal record structure, aka PNX (Primo Normalized XML), the next step is to learn how to view PNX. A small change to a Primo URL will allow you to view that PNX record for any record in Primo search results. For local data sources, such as Aleph and CUNY Academic Works, you can use the information in the PNX record to create a URL that will display the source data used to create that PNX record.
Primo PNX Record
Search for something in OneSearch
Pick a record in the results and click on the “Details” tab. Then click on the “open this item in a new window” icon at the top right of the “Details” frame:
(This opens the record in a full screen view.)
Copy this text:
&showPnx=true
Click anywhere in the address box:
Push the End key on your keyboard to move to the end of the URL, paste the copied text at the end of the URL, and hit the Enter key. The result looks like this:
(Click on the above image to see the result of “&showPnx=true” being added to a full screen search result display URL.)
Source Record: Aleph MARC
Now that you’ve got the PNX for an Aleph record, you can view the source MARC record in Aleph.
Examine the PNX that you opened. Near the top, you see fields like this:
<sourcerecordid>007651609</sourcerecordid>
<sourceid>CUNY_ALEPH</sourceid>
<recordid>CUNY_ALEPH007651609</recordid>
First of all, you know it’s an Aleph record because it says so in the sourceid field (CUNY_ALEPH). The sourcerecordid is the Aleph record number or “system number” (007651609).
Create that Aleph MARC record URL by placing that record number at the end of this base URL:
https://libsearch.cuny.edu/F?func=direct&doc_library=CUN01&format=001&doc_number=
For example:
https://libsearch.cuny.edu/F?func=direct&doc_library=CUN01&format=001&doc_number=007651609
This will take you to the OPAC MARC record view:
Source Record: Academic Works Dublin Core
If we look back at the search that we ran at the beginning of this post, we see that there was another record in the search result image and clicking on the “Details” tab for that record shows that it is from CUNY Academic Works:
Click in the full screen view URL/address box and add “&showPnx=true,” just as you did earlier. This will take you to this record’s PNX record and there you will be able to see the sourceid and sourcerecordid, just as we did for the Aleph record.
<sourcerecordid>jj_pubs-1019</sourcerecordid>
<sourceid>CUNY_BEPRESS</sourceid>
<recordid>CUNY_BEPRESSjj_pubs-1019</recordid>
(bepress is the vendor of the CUNY Academic Works software.)
To view Academic Works source data, we need a different (and longer) base URL:
http://academicworks.cuny.edu/do/oai/?verb=GetRecord&metadataPrefix=oai_dc&identifier=oai:academicworks.cuny.edu:
Otherwise, the process is the same. Take the sourcerecordid from the PNX record and add it at the end of the base URL. For example:
That was a lot for one post. But we have tools to make it easier: bookmarklets!
Coming soon:
