Fork me on GitHub

A publication and a publication framework

topazWhen PLoS One was first announced, one of the first things that caught my eye was the fact that it was built on an open source publishing framework, Topaz. As much as anything else, that was one of the reasons that PLoS One was so appealing; a journal that put the web first. Today, Topaz took a big step in becoming a general scientific publishing framework

Some of the cool new features found in the new release candidate (bold emphasis mine)

  • Enable multiple journals using a single repository
  • Skins for multiple journals.
  • Filter search results by journal using OTM
  • TrackBack linkbacks for articles
  • Citation download of the article
  • Migration to the Struts 2 web application framework

Personally, it is very exciting to see trackbacks implemented in a scientific publishing platform. Trackbacks are a powerful vehicle for communication (I prefer them to commenting), and allows people to discuss papers at length on their blogs in the appropriate context. It was one of the first feature requests that I submitted to the PLoS folks, as I am sure did many others, so one can feel good about it.

The next step for Topaz is to get to version 1.0 when it will become available with source. Many publications, struggling with funding and very poor internet presence could do much worse than adopt the Topaz platform. I wonder what uses people could make for Topaz outside the formal publishing field – Open Notebook Science perhaps?

Technorati Tags: , , , , ,

This entry was posted in Open Science, Publishing. Bookmark the permalink. Post a comment or leave a trackback: Trackback URL.

Post a Comment

Your email is never published nor shared. Required fields are marked *

*
*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

blog comments powered by Disqus
  • Archives

  • Disclaimer

    All opinions on this blog are my own and do not reflect those of my employers, past or present