Is Juris-M still active?
I will soon have much more of a need for "true" legal citations. I've until recently been primarily relying on the close-but-not-perfect citations generated by Zotero.
I can't tell if the Juris-M project is still active and if so, how far behind the true release it is.
As an aside, and I suspect this is an FAQ, why can't the codebase be merged eventually? Why does it need to be a fork?
I can't tell if the Juris-M project is still active and if so, how far behind the true release it is.
As an aside, and I suspect this is an FAQ, why can't the codebase be merged eventually? Why does it need to be a fork?
Upgrade Storage
As we've said, this functionality should be turned into a plugin (like the new multilingual plugin), not attempted as a fork of Zotero, an approach that stopped making sense many years ago.
[deleted — D.S.]
E.g., Jurism does not "sometimes lag behind" Zotero. It hasn't been updated in years. Until there is a new release, it should be considered abandoned. It's not helpful to tell people otherwise. (In a few days, Jurism will stop even being able to sync down items from official releases.)
And no, Frank hasn't posted here in 5 years (to the day).
And btw - I've never understood this Zotero-'schism'. And why the main Zotero devs didn't try to keep Frank's (IMO quite valid) additions 'on board', because his use case (both the legal part AND the multilinguial part!!) IS so important the the global epistemic endeavor!!! I personally think Frank will clearly prove to be on the 'right' side of history on the need for better multilingual treatment in bibbliographic management. It is UNCONSCIONABLE how 'Western' scholars have ignored Chinese, Japanese. etc. etc. and yes - even -Russian scholarship. And Zotero COULD have bene on the forefront of this. As it HAS been on so many other issues. But it decided not to...
But so I AM looking into the CNE repo, and I'll probaly use it; BUT from what I see, the 'interceptor' is quite fragile - I'm suprised you're ok with 'monkey patching' core Zotero functions like Zotero.Utilities.Item.itemToCSLJSON, as opposed to trying to implement this functionality more organically); not using caching may alos not be the best solution, etc, etc.
But ok, I guess I'll abandon the Zotero forum on this then and will just move to Discord...
In any case, yes, we are much happier with people using a plugin than a fork, let alone an unmaintained fork. Monkey-patching isn't ideal, but that's why we've been adding more and more APIs for common integration points. (I would assume CNE is using the custom-field API we added specifically for developers to customize the item pane.) Plugin developers can request additional APIs to meet their needs.
Even if we did try to build the functionality for either of these things ourselves, we would almost certainly implement it as a plugin rather than trying to add this incredibly complex functionality into the core product.