In Primo VE, Zotero Connector not recognizing individual items, only lists
Zotero Connector is not recognizing when an individual item record is opened in Primo VE. When I open a list of results using Primo VE in Chrome, the Zotero Connector shows a folder icon. When I open the record for an individual item, there is still the folder icon. When I click the folder icon when the individual item is open, a popup shows the list of results with checkboxes, just as if I hadn't opened the individual item.
and that shows a book & imports individually.
Getting the book item for the pseudo-single view might be more fragile than is worth it.
Have you recently noticed that permalinks from PrimoVE are incorrectly imported from Zotero connector?
Only domain url of the catalogue is imported, not the link to the single item in the catalogue.
This could be fixed in a way or another ?
Best regards,
Anna Couthures-Idrizi
Please find an example here : https://catalogue-bibliotheque.sciencespo.fr/permalink/33USPC_SPO/1d4eftp/alma991005928709705808
Best regards,
Anna
The point is not to have the whole permalink in URL zotero field, but in the Library Catalogue field.
Hope you're fine. Just adding my support, also, on this. I have so make a bibliography on a primo portal and not one single item imported the URL (permalink) which is a problem to later retrieve the document. I know this is a weakness on the Primo side, not on Zotero, since Zotero imports beautifully from most databases. But is there something that can be done about this? Currently, I need to manually add the URLs to the items. Maybe I am also doing something wrong.
Thanks so much! Well, it is our own catalogue:
https://labordoc.ilo.org
And if we need to make fixes to make it work... we are happy to!
Thanks so much!
<lds03><a aria-label="Permanent link to item" href="https://id.lib.harvard.edu/alma/990022085630203941/catalog">https://id.lib.harvard.edu/alma/990022085630203941/catalog</a></lds03>
which isn't super clean, but the lds03 element is clean enough to handle this. It doesn't have to be in the same field or even format, but we do need the permalink in the metadata (i.e. the PNX) -- I don't want to try to construct it somehow from the URL.
Thank you so much.
Does this solution work?
Please see the PNX record here
https://ilo-psb.primo.exlibrisgroup.com/discovery/fulldisplay?docid=alma995074393502676&context=L&vid=41ILO_INST:41ILO_V2&lang=en&search_scope=ALL_ILO&adaptor=Local Search Engine&tab=ALL_ILO&query=any,contains,Towards effective and funcional social dialogue&offset=0&showPnx=true
You will find the URL under "lds24"
"lds24" : [ "https://ilo-psb.primo.exlibrisgroup.com/discovery/search?query=any,contains,995074393502676&tab=ALL_ILO&search_scope=ALL_ILO&vid=41ILO_INST:41ILO_V2" ]
This is in our sandbox. If this is the way to go, I will run it in production, but I want to make sure it gives what is needed in oder to show the field in Zotero.
Could you, please, let me know if it works?
And also, let me know if you need anything else from our side.
Best regards,
Indira
Hope all is well on your side. Please let me know anything that has to be done on our end.
Thanks so much for all your support.
Indira
We're interested in adding something similar for our institution (https://torontomu.primo.exlibrisgroup.com/discovery/search?vid=01OCUL_TMU:01OCUL_TMU&lang=en), but I realized that Harvard's code only works for monograph content from Alma (ex. books), but not for content from the Discovery Index (ex. articles, book chapters). I was able to push links to Zotero by adding this code snippet to Primo Normalized XML.js which adds a prefix and suffix to the record ID:
for (let recordid of ZU.xpath(doc, '//p:recordid', ns)) {
item.attachments.push({
url: "https://torontomu.primo.exlibrisgroup.com/discovery/fulldisplay?docid=" + recordid.textContent + "&context=L&vid=01OCUL_TMU:01OCUL_TMU&lang=en&search_scope=OCULDiscoveryNetwork&tab=OCULDiscoveryNetwork",
title: "TMU Permalink",
snapshot: false
});
}
This works perfectly for our institution. The problem is, it doesn't distinguish between PrimoVE instances, so it would also create invalid permalinks the same way for other PrimoVE institutions.
Do you see a way to modify the translator so that it recognizes our institution? I note that the web translator uses a regex pattern to recognize Primo URLs. Primo instances all have a unique institution codes (01OCUL_TMU in our case). Ideally, the import translator would recognize the URL as coming from our institution, and apply the correct prefix/suffix to the record ID, but I'm not really sure how to implement that in the import translator.
Paul