PubSweet 1.0 “Science Blogger” alpha, INK 1.0 alpha RELEASES!!!
Today we are very happy to announce that the 1.0 alpha of both our products -PubSweet and INK are available.
This is big news for us as it represents many months of hard work taking our initial vision of producing a suite of flexible tools for publishing and knowledge creation from idea, to design, to reality. It has been a huge team effort and we have several people to thank. First, some information about each product…
PubSweet 1.0 alpha “Science Blogger”
PubSweet is a framework, not a platform. Which means we can use it to create all kinds of solutions from monograph production, article QA systems, authoring platforms, and Journals (all of which are currently being worked on) amongst many. However for PubSweet 1.0 alpha we have bundled it with some default components so you can use it for science blogging, hence the title PubSweet 1.0 – “Science Blogger”.
If you install this software (see the README) you will see a lovely login screen, dashboard, editor, and publish page. Everything that you need to blog about science. It has features particular to science, for example images are treated as Figures and have titles and captions PLUS they can be dynamically referenced from within the post. The editor also leverages the CrossRef API for searching and placing references dynamically in the post…try it out, it’s a lot of fun! You can also place other media such as video etc and cite those in the text as well. The editing component is built on top of the Substance.io libraries and implements the Substance ScienceWriter and ScienceReader. The other components – login, dash, are Coko custom components. So you can see the power of PubSweet is to combine components to meet different use cases, when we started this was a promise, and ScienceBlogger now brings this to reality.
Science Blogger also has a simple theme system so you can make the published articles (and other interfaces) look exactly as you want it. All in all its a good platform for researchers to use to blog about what they do, or others to comment on the wonderful world of scientific research.
As mentioned, this is an Alpha release which means we will keep on testing it over the next weeks and then release the full 1.0 when we are happy that it all works as expected. Please feel free to try it and issue bug reports here:
INK 1.0 Alpha
A step does one thing, converting docx to HTML, for example, or validating HTML. The idea is that you can chain several of these steps together to manage complex conversion pipelines. We designed it like this so that you could also modify one single step in a recipe and improve it without having to change an entire hard-coded pipeline (which is usually the way these things are built). INK will progress over the next months and the vision is bigger than ‘mere’ file conversions. We intend this framework to be used for managing any type of heavy lifting needed in scholarly knowledge production. You could, for example, use it to automatically link terms in a research article to their persistent identifiers, or to validate an articles structure, or check and enhance embedded author information. The future is very interesting for INK and while it is a little more complex to install than PubSweet we would very much appreciate your bug testing, comments, and contributions.
We hope that you enjoy these Alpha releases. We are very proud of them and they set the stage for us moving forward and implementing solutions for publishers, researchers, and innovative new knowledge production and sharing models. We hope you enjoy them!
Thanks also for the whole host of people that gave us insight and inspiration for each of the products. None of these have been developed in a vacuum and we have learned a great deal from many many conversations with many many friends and allies. Thanks very much to you!
Finally thanks to our friends at the Shuttleworth Foundation who have been with us from the beginning, before the beginning infact, and our recent new friends at the Moore Foundation. Without you both we couldn’t do this at all!
Post by Adam Hyde