Trouble migrating from Jurism 6 (back to native) Zotero 9

I switched from Zotero 6 to Jurism 6 in 2021 because I needed multiple citation languages. Now that feature is in Zotero 9 and Jurism (still on 6) is not well supported on Mac silicon, so I want to move back to Zotero.

However...

1. I cannot sync Jurism with my Zotero cloud account because it cannot log on. Iit says the credentials are invalid, but I can log on manually just fine; I presume Jurism is just not up to date with Zotero authentication protocols.

2. Jurism will not export the whole library as an RDF (or anything else); the error log says it has an unknown library type. I can export and import a few items, but I have over 11k items altogether.

3. If I just copy Jurism/jurism.sqlite to Zotero/zotero.sqlite Zotero tells me I need to upgrade because I need 6 but it is only on 9!

Did anyone manage such a migration?

Ideally I would like to copy the multilingual data into the CNE plugin as well, but could forego that if necessary - as long I as I am sure I have the whole library.

  • I am working on an extractor (python script) that will take data from a Jurism 6 database and write a format that can be imported into Zotero 9, including attachments and CNE tags. If anyone wants to help ....
  • Have you tried changing your Zotero password and syncing right afterwards -- as per Zotero devs that should be possible to get Zotero versions <9 to authenticate and would then get you going.

    If you do use an extractor, I'd recommend going from the Jurism database through the Zotero API rather than an import format. The beta should also have a local implementation of the write API.
  • @adamsmith thanks. Yes I tried the password change trick but it seems Zotero has closed that loophole now. The new Zotero logon uses a web page to authenticate.

    I am not sure what you mean by "going from the Jurism database through the Zotero API"?

    The current approach is to use a python script to write an RDF file, then import that into Zotero. Seems safest. It is however still work in progress. For details see https://github.com/AndySymons/Jurism-to-Zotero-migrator
  • dstillman Zotero Team
    I tried the password change trick but it seems Zotero has closed that loophole now
    We haven't for older Zotero clients, but we can't guarantee it works for Jurism, which likely identifies itself differently.

    Zotero API is referring to https://www.zotero.org/support/dev/web_api/v3/
  • edited 18 days ago
    @dstillman Thanks. I tried several times with Jurism over the last couple of years, but no luck.

    I can export a few items from Jurism 6 and import them into Zotero 9, but for some reason Jurism will not export the whole library. I am also trying to get the extractor to translate Jurism language fields into 'Extra' field tags for CNE, and do a few 'cleaning up' tasks:
    - normalise language field values to iso codes (e.g. 'Spanish' to 'es'), so CNE will recognise them (good practice anyway)
    - change (legacy) absolute linked attachment paths to relative
    - keep the original date added (as a tag in 'Extra' (because the Zotero import overwrites it with the import data)
  • edited 11 days ago
    I am happy to announce that I now have a solution that meets my needs: https://github.com/AndySymons/Jurism-to-Zotero-migrator
  • I'm glad you found something, but I'm not sure the need for it? If you were syncing up to the point that it stopped working, you should be able to just install Zotero 9 and sync up. The extra data is all stored in the extra field, I thought. I don't think any of the sqllite data uploaded in the sync. That said, for pure multi-lingual maybe it was different.
  • @AndySymons first and foremost, thank you so much for this! This is exactly what I've been looking for! That said, I ran into a few issues so I posted them on your GitHub issues page. Willing to help where I can!
  • @rish The problem was not synching with Zotero -- it was synching with Jurism. That has been broken for a couple of years now. I mentioned it only as one of several reasons to stop using Jurism! Once I migrate to Zotero I am sure synch will not be a problem any more.

    The solution I 'found' is actually to build a migration program myself that extracts the data from Jurism, and writes a Zotero RDF file, putting the language information into tags in 'Extra' that can be read by the Zotero CNE plugin. I am not quite there yet, but close. See my GitHub page for details.

    I am of course still interested in any shortcuts anyone can offer!
  • @nomadism Thanks very much for bringing this to my attention, and am I pleased to have found an audience.

    Issues I am working on (and hope to solve within a few days) are

    1. Some fields missing altogether (a slip up in regression testing)
    2. Collections and saved searches not migrated.
    3. Transliterations not migrated - these were originally out of scope, because I never used them; but I am going to bring them into scope.

    Please bear with me, all this requires a lot of testing and I do not want to rush it - but look out for release 1.3 soon.
Sign In or Register to comment.