From 2bb1b8e7e5c0584bad84a1d4d2176436c5decdd7 Mon Sep 17 00:00:00 2001
From: julientaq <julien@coko.foundation>
Date: Fri, 7 Jan 2022 02:09:35 +0100
Subject: [PATCH] add articles ssp
---
src/articles/ssp-kotahi.md | 26 +++++++++++++-------------
src/articles/ssp2.md | 8 ++++----
src/articles/ssp3.md | 8 ++++----
src/articles/ssp4.md | 8 ++++----
src/articles/ssp5.md | 4 ++--
5 files changed, 27 insertions(+), 27 deletions(-)
diff --git a/src/articles/ssp-kotahi.md b/src/articles/ssp-kotahi.md
index 4ff4109..99e0d7e 100644
--- a/src/articles/ssp-kotahi.md
+++ b/src/articles/ssp-kotahi.md
@@ -22,7 +22,7 @@ overview, for in depth detail please contact Coko (email included below) for a f
<p class="paragraph">For the purposes of this document we will look at the following configuration which is being
used by the Aperture Neuro journal (Organization of Human Brain Mapping).</p>
<p class="paragraph"></p>
-<figure><img src="/images/uploads/sspKotahi-01.png">
+<figure><img src="/images/uploads/uploads/sspKotahi-01.png">
<figcaption class="decoration">Aperture Workflow in Kotahi</figcaption>
</figure>
<p class="paragraph">The Aperture workflow in sequential notation looks something like this:</p>
@@ -107,7 +107,7 @@ interface (see later in this document).</p>
</p>
<p class="paragraph"></p>
<figure><img
-src="/images/uploads/sspKotahi-02.png">
+src="/images/uploads/uploads/sspKotahi-02.png">
<figcaption class="decoration">Example Submission Form</figcaption>
</figure>
<h4>Submission</h4>
@@ -138,7 +138,7 @@ manuscripts on the Manuscripts Page (permissions permitting).</p>
<p class="paragraph">The Managing Editor can view new submissions via the Manuscripts Page (click to enlarge).</p>
<p class="paragraph"></p>
<figure><img
-src="/images/uploads/sspKotahi-03.png">
+src="/images/uploads/uploads/sspKotahi-03.png">
<figcaption class="decoration">Kotahi Manuscripts Page (with example data)</figcaption>
</figure>
<p class="paragraph">Columns can be sorted by Creation Dates, State etc.</p>
@@ -150,7 +150,7 @@ submission data, and the submission’s associated workflow controls.</p>
selected manuscript as per below (click to enlarge).</p>
<p class="paragraph"></p>
<figure><img
-src="/images/uploads/sspKotahi-04.png">
+src="/images/uploads/uploads/sspKotahi-04.png">
<figcaption class="decoration">Kotahi Control Panel</figcaption>
</figure>
<p class="paragraph">Please note, the above screenshot is soon to be replaced with three separate tabs for 1)
@@ -165,14 +165,14 @@ They can then review the manuscript and submission data. The next step is for th
Invite Reviewers page is accessible via the Control Panel.</p>
<p class="paragraph"></p>
<figure><img
-src="/images/uploads/sspKotahi-05.png">
+src="/images/uploads/uploads/sspKotahi-05.png">
<figcaption class="decoration">Kotahi Reviewer Management</figcaption>
</figure>
<p class="paragraph">At this stage of invitation, the editor can also decide if the reviewer is doing their own
review or a shared review.</p>
<p class="paragraph"></p>
<figure><img
-src="/images/uploads/sspKotahi-06.png">
+src="/images/uploads/uploads/sspKotahi-06.png">
<figcaption class="decoration">Reviewer Management showing shared review option</figcaption>
</figure>
<p class="paragraph"><em>Screenshot taken from CB (t.b.a) Instance</em></p>
@@ -183,7 +183,7 @@ email). The Reviewer can then access the manuscript, filtered submission data, a
Dashboard. The Review Page has a section for writing the review and attaching files:</p>
<p class="paragraph"></p>
<figure><img
-src="/images/uploads/sspKotahi-07.png">
+src="/images/uploads/uploads/sspKotahi-07.png">
<figcaption class="decoration">Kotahi Reviewer Form</figcaption>
</figure>
<h3>Editor Decision</h3>
@@ -203,14 +203,14 @@ Manuscripts Page). Live chat is also available per submission for communication
staff, as well as private chats for the editorial staff to discuss the submission.</p>
<p class="paragraph"></p>
<figure><img
-src="/images/uploads/sspKotahi-08.png">
+src="/images/uploads/uploads/sspKotahi-08.png">
<figcaption class="decoration">Kotahi Chat (Author view)</figcaption>
</figure>
<p class="paragraph"><em>Author—Editor chat embedded in the author submission pane (click to enlarge).</em>
</p>
<p class="paragraph"></p>
<figure><img
-src="/images/uploads/sspKotahi-09.png">
+src="/images/uploads/uploads/sspKotahi-09.png">
<figcaption class="decoration">Kotahi Chat (Editorial view)</figcaption>
</figure>
<p class="paragraph"><em>Editorial chat for staff only (per manuscript).</em></p>
@@ -219,7 +219,7 @@ configure as many templates as they like. Emails can be sent to existing users o
of all emails sent is kept as a retrievable log within the editorial staff chat.</p>
<p class="paragraph"></p>
<figure><img
-src="/images/uploads/sspKotahi-10.png">
+src="/images/uploads/uploads/sspKotahi-10.png">
<figcaption class="decoration">Email Management</figcaption>
</figure>
<p class="paragraph"><em>Screenshot taken from the CB instance of Kotahi.</em></p>
@@ -238,7 +238,7 @@ support automated PDF output via <a href="https://pagedjs.org/" rel target="blan
HTML for pushing to publish interfaces.</p>
<p class="paragraph"></p>
<figure><img
-src="/images/uploads/sspKotahi-11.png">
+src="/images/uploads/uploads/sspKotahi-11.png">
<figcaption class="decoration">JATS Export</figcaption>
</figure>
<h3>Publishing</h3>
@@ -264,13 +264,13 @@ we have a UI config manager design. While we will use the above workflow, the fo
for the Novel Coronavirus Research Consortium and CBinstances:</p>
<p class="paragraph"></p>
<figure><img
-src="/images/uploads/sspKotahi-12.png">
+src="/images/uploads/uploads/sspKotahi-12.png">
<figcaption class="decoration"><em>NCRC Kotahi Workflow</em></figcaption>
</figure>
<p class="paragraph"></p>
<p class="paragraph"></p>
<figure><img
-src="/images/uploads/sspKotahi-13.png">
+src="/images/uploads/uploads/sspKotahi-13.png">
<figcaption class="decoration">CB Kotahi Workflow</figcaption>
</figure>
<p class="paragraph"></p>
diff --git a/src/articles/ssp2.md b/src/articles/ssp2.md
index 1afaa0b..33e3a87 100644
--- a/src/articles/ssp2.md
+++ b/src/articles/ssp2.md
@@ -22,7 +22,7 @@ date: "2021"
and at publish time, that content is transformed into the target output – in this case a blog post shared
on the web.</p>
<figure><img
- src="/images/uploads/SSP/A2-Img1.jpg">
+ src="/images/uploads/uploads/SSP/A2-Img1.jpg">
<figcaption class="decoration"></figcaption>
</figure>
<p class="paragraph">Let’s add a little complexity as it is hard to really understand the value of single
@@ -43,7 +43,7 @@ date: "2021"
<p class="paragraph">As if by magic, we have effectively solved the problem of displaying the same content for two
different types of outputs – desktop and mobile displays.</p>
<figure><img
- src="/images/uploads/SSP/A2-Img2.jpg">
+ src="/images/uploads/uploads/SSP/A2-Img2.jpg">
<figcaption class="decoration"></figcaption>
</figure>
<h3>So what’s the problem?</h3>
@@ -52,7 +52,7 @@ date: "2021"
<p class="paragraph">No prizes for choosing HTML. To transform from HTML to HTML & HTML is cheap because there
is (in simple terms) no transformation needed. This is exactly what the smart folks at WordPress have done.</p>
<figure><img
- src="/images/uploads/SSP/A2-Img3.jpg">
+ src="/images/uploads/uploads/SSP/A2-Img3.jpg">
<figcaption class="decoration"></figcaption>
</figure>
<p class="paragraph">The content you are editing in WP is stored as HTML. Exactly that same source is directly
@@ -62,7 +62,7 @@ date: "2021"
multiple output types, which is most publishing scenarios, you must choose a source file format that can undergo
significant transformation into all of the output formats you require.</p>
<figure><img
- src="/images/uploads/SSP/A2-Img4.jpg">
+ src="/images/uploads/uploads/SSP/A2-Img4.jpg">
<figcaption class="decoration"></figcaption>
</figure>
<p class="paragraph">When designing a publishing system you face two basic questions, in this order:</p>
diff --git a/src/articles/ssp3.md b/src/articles/ssp3.md
index d3fc329..ed6a9d6 100644
--- a/src/articles/ssp3.md
+++ b/src/articles/ssp3.md
@@ -10,7 +10,7 @@ date: "2021"
all the outputs would roll out automagically – fully formed, perfect and beautiful.</p>
<p class="paragraph"></p>
<figure><img
- src="/images/uploads/SSP/A3-Img1.jpg">
+ src="/images/uploads/uploads/SSP/A3-Img1.jpg">
<figcaption class="decoration"></figcaption>
</figure>
<p class="paragraph">Is such automation possible? Let’s have a closer look at the types of conversion
@@ -23,7 +23,7 @@ date: "2021"
means removing information (structure).</p>
<p class="paragraph"></p>
<figure><img
- src="/images/uploads/SSP/A3-Img2.jpg">
+ src="/images/uploads/uploads/SSP/A3-Img2.jpg">
<figcaption class="decoration"></figcaption>
</figure>
<p class="paragraph">Removing structure is easy (usually), we just throw stuff away.</p>
@@ -32,14 +32,14 @@ date: "2021"
(structure).</p>
<p class="paragraph"></p>
<figure><img
- src="/images/uploads/SSP/A3-Img3.jpg">
+ src="/images/uploads/uploads/SSP/A3-Img3.jpg">
<figcaption class="decoration"></figcaption>
</figure>
<p class="paragraph">Adding structure is doable but not as easy.</p>
<p class="paragraph">A simple diagram to help us understand up and down conversion would be as follows:</p>
<p class="paragraph"></p>
<figure><img
- src="/images/uploads/SSP/A3-Img4.jpg">
+ src="/images/uploads/uploads/SSP/A3-Img4.jpg">
<figcaption class="decoration"></figcaption>
</figure>
<p class="paragraph">Down-conversion is generally an easier target for automation. Up-conversion is more likely to
diff --git a/src/articles/ssp4.md b/src/articles/ssp4.md
index c8e1922..fc021ed 100644
--- a/src/articles/ssp4.md
+++ b/src/articles/ssp4.md
@@ -24,7 +24,7 @@ date: "2021"
stakeholders work efficiently while they share the same canonical source.</p>
<p class="paragraph"> </p>
<figure><img
- src="/images/uploads/SSP/A4-Img1.jpg">
+ src="/images/uploads/uploads/SSP/A4-Img1.jpg">
<figcaption class="decoration"></figcaption>
</figure>
<p class="paragraph"> </p>
@@ -33,7 +33,7 @@ date: "2021"
thinking’ has looked like this:</p>
<p class="paragraph"></p>
<figure><img
- src="/images/uploads/SSP/A4-Img2.jpg">
+ src="/images/uploads/uploads/SSP/A4-Img2.jpg">
<figcaption class="decoration"></figcaption>
</figure>
<p class="paragraph">This thinking has lead us to where we are today, and today we have broken, disjointed
@@ -41,7 +41,7 @@ date: "2021"
<p class="paragraph">To bring about the efficiencies we are after, we need to think in this direction:</p>
<p class="paragraph"></p>
<figure><img
- src="/images/uploads/SSP/A4-Img3.jpg">
+ src="/images/uploads/uploads/SSP/A4-Img3.jpg">
<figcaption class="decoration"></figcaption>
</figure>
<p class="paragraph">What if the file format was the last decision you made when constructing ecosystems of
@@ -52,7 +52,7 @@ date: "2021"
largely why the sector has been driven away from single source publishing systems and is mired in the kind of
broken, slow, expensive processes we discussed in earlier and we illustrated as follows:</p>
<figure><img
- src="/images/uploads/SSP/A1-Img1-and-A4-img4.jpg">
+ src="/images/uploads/uploads/SSP/A1-Img1-and-A4-img4.jpg">
<figcaption class="decoration"></figcaption>
</figure>
<p class="paragraph">When we started our discussion of single source publishing systems in this article, we talked a
diff --git a/src/articles/ssp5.md b/src/articles/ssp5.md
index 761f33c..9b5ee68 100644
--- a/src/articles/ssp5.md
+++ b/src/articles/ssp5.md
@@ -23,7 +23,7 @@ date: "2021"
then downconvert to specific formats for consumption by tools such as InDesign.</p>
<p class="paragraph"></p>
<figure><img
- src="/images/uploads/SSP/A5-Img1.jpg">
+ src="/images/uploads/uploads/SSP/A5-Img1.jpg">
<figcaption class="decoration"></figcaption>
</figure>
<p class="paragraph">But it is possible for a single format to contain enough information to feed into each of these
@@ -127,7 +127,7 @@ date: "2021"
</li>
</ol>
<figure><img
- src="/images/uploads/SSP/A5-Img2.jpg">
+ src="/images/uploads/uploads/SSP/A5-Img2.jpg">
<figcaption class="decoration"></figcaption>
</figure>
<p class="paragraph">Where does that leave us? As it happens, it leaves us with the ecology of tools that surround
--
GitLab