The Rogue Scholar science blog archive is built with Open Source software, starting with Javascript in June 2023 and adding an API written in Python in October 2023. This week I am releasing the first version of commonmeta written in Go to simplify the Rogue Scholar backend.
Library for conversions to/from the Commonmeta scholarly metadata format.
The Rogue Scholar science blog archive has launched a dedicated API today, publicly available at https://api.rogue-scholar.org and complementing the website. Rogue Scholar had an API before but with two important limitations. <strong> Serverless </strong> . The API at https://rogue-scholar.org/api uses serverless technology, which isn't a good fit for long-running resource-intense processes.
This week the references included in currently 1,123 Rogue Scholar blog posts have become much more powerful, as they now include the full set of scholarly metadata. These metadata are displayed in the Rogue Scholar web pages and can be fetched via an open API. One of my favorite personal blog posts – about the 10th anniversary of PLOS ONE, reference lists, and the X-Files TV series written in 2016 – nicely demonstrates this new functionality.
Last week the Rogue Scholar science blog archive added export of blog post content in various formats (Markdown, ePub, PDF, JATS XML). This week Rogue Scholar is improving the existing metadata export, and adding metadata export in Schema.org JSON-LD format.
From the start last year one important goal for the Rogue Scholar science blog archive was to make it easy to use for blog authors and readers. Today I want to focus on another aspect: keep it simple to run Rogue Scholar infrastructure. To address that goal I started development work last week to further simplify one important aspect of Rogue Scholar infrastructure: metadata conversion.
While it is a best practice for DOIs (expressed as URL) to send the user to the landing page for that resource (Starr et al., 2015), sometimes we want something else: <strong> metadata </strong> , e.g. to generate a citation, or to go to the <strong> content </strong> itself. The easiest way to do that is to use DOI content negotiation.
<strong> <strong> The Barcelona Declaration: a call for openness… but also for diversity and inclusion </strong> </strong> The launch of the Barcelona Declaration last week aims to mobilise the global research community towards making research information open and accessible.