Made detection and parsing less restrictive for Primo translator

zotero / zotero-bits

CSL-related community feedback for Zotero

56 stars 8 forks source link

Made detection and parsing less restrictive for Primo translator #33

Closed mehmetc closed 13 years ago

mehmetc commented 13 years ago

Detection and parsing was to restrictive. This resulted in Zotero not recognizing all records on a page.

Fixes:

Expecting classes in a specific order could break the translator if pages get updated.
Title does not have to contain a link I used the link on the details tab instead.

avram commented 13 years ago

Can you provide URLs for a catalog that requires this patch, for future reference?

mehmetc commented 13 years ago

It should work on all off them. Our Primo 3.0.3 is running at http://limo.libis.be. I noticed that older Primo installations like the one at Boston College have a problem saving Primo Central records.

avram commented 13 years ago

I also noticed that the Boston College installation had problems with some records, which is why I added a fallback to RIS in revision 90d2722 -- hopefully this will make it somewhat better.

Is there a good place I can send people to help library staff configure Primo to be more Zotero-friendly?

mehmetc commented 13 years ago

We have been doing all sorts of hacks to Primo mostly jQuery in order to help Librarians accept it more but hacks come at a price. So, the only once who can make Primo more Zotero-friendly is the software provider. But we will do what we can to fill the gap until they fix it.