This would have benefits to both Support and customers.

It would allow customers to do more self service troubleshooting for Primo publishing jobs.

status: open
priority: high
subject area: pnx records; pipes

Use Cases:

• PNX content. Users would like to be able to check specific fields which are being indexed to be able to resolve a mismatch between source records and Primo
• Where multiple SCOPE/VIEWs are used there is no way of checking what is being published or not published under each scope
• Users would like to be able to generate list(s) and count(s) of unique ORCiD IDs for linking; unique ORCiD IDs for linking and associated PNX records where number of PNX records containing this ORCiD ID is > 1
• Users would like to be able to list PNX records with specific local link field (lln44) and show/count how many occurrences of that local link there is in one PNX record

From the IGeLU-ELUNA Analytics Working Group, Analytics Evidence Document

Please send questions or comments to the Analytics Working Group Listserv