Annotum Final Release

· Releases, Site Updates
Authors

I’m a little sad to write that today we are releasing the final update to Annotum, v2.1.1.1, five years to the day since the first production release of Annotum on November 22, 2011.

For all of you that downloaded Annotum (260k+!), or used it as a home on WordPress.com for your Google Knol content, I’d like to express my thanks for your enthusiasm, patience, and most of all for your willingness to provide open access content to the world.

I’d also like to thank the strong supporters of Annotum, including Automattic, Google, NCBI, Crowd Favorite, and Solvitor. And I’d like to send a special Thank You to the late Alex King, who believed in and supported this project from the very beginning.

As to the why, those of you who maintain Annotum sites have known for some time that it has become difficult to keep all of Annotum’s rich editor functionality working properly as WordPress has continued its relentless forward progress.  Therefore we will no longer be providing any new features or updates, including compatibility updates and bug fixes, for Annotum.

So, what now? As far as the Annotum source code goes, the Annotum repository on Github will continue to remain available to anyone.  The annotum.org blog (this site) will soon be moved (including all pages and posts) to a github-hosted site within the Annotum repository (but still under the annotum.org URL).

Please continue to use the Annotum Support site (for as long as Uservoice supports free sites, anyway).  If you find that you can’t reach me that way, please feel to reach out via Twitter to @annotum or @solvitor.

For those with existing Annotum sites, you have a few options:

  1. Keep your site running on WordPress v4.4.5.  I don’t really recommend doing this for too long; it’s generally not a good practice to keep using older WordPress versions.
  2. Export your content via JATS-XML.  If you started using Annotum for its JATS support, this is probably the most robust way to maintain your existing content. You will want to double check all images after export — particularly equations which currently rely on the Google chart APIs for rendering.
  3. Export your articles to WordPress posts using the “convert to post” button in the article editor.  This is the simplest if you don’t have any need for JATS or XML. If you go this route, you will definitely want to update to the latest version of Annotum; as a rough and ready workaround for those already using version 2.1.1, you can try replacing just the article-post-type.php file. As always, MAKE A COMPLETE BACKUP of all of your code and data BEFORE trying this on your production site.

    Unfortunately, for converting articles to posts, there’s no batch export — you’ll need to do this one article at a time.

Whatever you choose, please do feel free to reach out via the Support site or on Twitter.  I’m happy to provide support for your migration on an as-available basis, but if your migration needs are extensive, there are additional paid support / development options as well.  For that, please feel free to reach out using one of the methods mentioned above.

Thank you all again and happy WordPressing!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: