With server migration complete and the desktop client and with plugins for browser and word processor released and confirmed to be stable, the role of these project news blurbs shifts from cataloging Frank's triumphs, musings and frustrations to, well, providing news.

The #Jurism v6.0.22m3 release went up today, and plugin connectors for Firefox and Chrome are available.

https://juris-m.github.io/release

#ReferenceManager #LawFedi #ResearchTool

Jurism 6.0.20 is now available.

https://juris-m.githib.io

#Jurism is a variant of the Zotero reference manager that adds support for legal and multilingual citations. The software suffered two years without updates, but that changes today. If you work in multiple languages or need to reference legal materials, it's worth a look.

#DigitalHumanitites #Productivity #ReferenceManagers #Writing #WritingTools

@BradRubenstein Oh noooos! ☝️
#Zotero #CSL #citationStyleLanguage #Jurism

Happy to report that a Linux build of #Jurism has uploaded without mishap via the deployment chain, and that a test download has succeeded from a dynamic "latest version" link under the Beta tab of a development copy of the Jurism project website.

Further, yesterday I accidentally ran the J6 client against my large personal database—and it upgraded without error.

And the Google Chrome plugin works.

All of which means we're just days away from a beta release.

This morning I extended the refactoring of the "rebuild" feature (which is quite heavy when the very large CSL style repository is being digested) to cover "refresh" (incremental update) as well.

It all looks peachy.

There's something to report on the client as well. Today was a twofer for #Jurism.

A significant feature of the update server is the ability (for me) to update styles and site translators from their GitHub repositories with a click. The code that I wrote for this in between teaching university classes was a tangled mess, and after throwing up my hands at ever understanding it, I did some refactoring & it is now swell.

We're getting close to #Jurism beta release. The next little mountain to climb will be the client download and update resolver.

Some of the code in my bespoke #Jurism update server was a terrible mess, so I put in some time to rewrite much of it yesterday and today.

So on to installation and testing ... to find that the HTTPS connection is now dead, that the site has two recognized IP addresses, one of which is entirely dead, and that the Digital Ocean verification email that I need to access the server doesn't arrive.

Have filed a support request.

Taking the rest of the day off.

The service for #Jurism style and translation updates plus bug reports is now online. Still needs to be populated with the source files, but we're looking good so far.

Now that the #Jurism client is built and tested, the focus returns to the server migration that I began posting about yonks ago. Deployment depends on that infrastructure.

I copied the tools down from the old university server a couple of months ago—and a good thing too, because the faculty have at last pulled the plug on it.

Yesterday I got the translator+style updater and bug report daemon working. It was not fun. It is now fun. Next up is the client updater.

The #Jurism client now clears all of its test fixtures.

I'm pretty well exhausted from the plunge, and there is still plenty of work to do before it can be called complete, but this was a major milestone and I'm *very* happy to have cleared it so quickly.

A solid round of applause is due to the #Zotero team for the work that's gone into the project's test suite. Jurism could not be sustained without it.

The menu overlap issue is apparentlu due to a bug in the version of Firefox that #Zotero 6 uses as its platform. It can be controlled for, so no worries.

Now that the path to final bugfixing is clear, I'll stop pestering feeds with these little messages for a time. When all tests clear, though, I'll be back!

Here's to the glittering prospect of #Jurism client update [15]. Until then, dear reader, take care of yourself, be kind, and don't take any wooden nickels.

The #Jurism client builds and runs. Yikes. I didn't expect it to come up with so little effort.

There is one obvious bug: the creator role menu is now being invoked by "onclick", so a right-click to pull up the multilingual menu calls both menus at once. Easily fixed.

The build process is throwing up some errors that make me nervous. When I have a chance to contact #Zotero developers, I'll try to explore that further.

Meanwhile, onward to the test suite!

With an update to the #Zotero tools for building #Jurism, the client builds, and successfully crashes with meaningful errors reported to the JavaScript console. We're now on familiar ground, and it's just a matter of time before this is stable enough to run the test suite and explore less catastrophic issues.

With the OS upgrade in place, and after muddling my way past some issues in the #Zotero build process that were (I think) less critical than I thought them to be, it appears that building the #Jurism core succeeds.

Yay.

Tomorrow we move on to the less white-knuckle drama of watching test fixtures fail. Forward!

Progress today! Sort of. It took some doing to get the latest stable OS on the laptop without losing data, but networking is back up, and we're back to running the #Zotero / #Jurism test suite. Or attempting to ...

Tests fail at the same point they did before the OS upgrade (darn), when attempting to load a fixture from the mocha test runner's own test suite. We now have the latest kit in place, however, and can call for upstream guidance with more confidence. Progress.

ActivityPub didn't like the ravings in #Jurism client update [9]: the threading of it seems well and truly broken. Apologies to all about all that.

We're not out of the woods yet. It looks like (ha! looks like!) bumping the OS from v16 to v18+ will fix networking. Without networking, it has to be done with a USB stick, and the v18 stick doesn't find the OS on the machine, so it can't upgrade. I've bought a 2tb disk to save my files to and I'm taking the evening off.

Another day at the #Jurism chalk face, and we have a last-meter issue. Not figuratively. Literally. After the Linux OS version upgrade, wireless on the laptop refused to connect. Everything checked out to the router IP, but onward connections were dead.

After thinking seriously about crawling under the house to string cable, I tried restarting the router. Everything works now.

I'm now qualified to work on the help desk.

Kind of a ho-hum notice today. Patching is done and I'm ready to run tests of the #Jurism client. After two years out of the loop, the Linux OS on my laptop is well out of date, so I'm doing an upgrade.

The first run of the test suite (after some silly missteps) failed miserably, but only because the final stage of the Linux install hadn't been run, and the OS itself was incomplete.

But EVERYTHING WILL BE FINE. It's all under control. Absolutely nothing to worry about.

Schema update is done. After much head-scratching and rummaging about, it emerged that git pull, removing three lines of code, and running the existing #Jurism version of schema-update was all that was needed. Once upon a time I did some good work on this, it seems. Yay.

A bundle of utilities, some touched by Jurism, has been moved to a submodule on #Zotero side. I don't expect serious difficulties, but patches there will need to be generated and applied manually.

There are some interesting issues in the new schema. Taking the rest of the day off, but for this note on the state of play.

On #Zotero side we have a couple of new item types that can just be copied across. Changes in item type mappings to CSL seem unproblematic. What will need closer inspection that I'm too thrashed work on further today is (possible) changes to item fields. #Jurism adds a bunch via a patching mechanism, and any adopted by Zotero needn't be hacked in.