EDIT_THIS ADD_ARCHIVE ADD_ISSUE ADD_ARTICLE PUBLISH ?

Archive Infrastructure: Sandpoints

article⁄Archive Infrastructure: Sandpoints
abstract⁄Outline of the Sandpoints infrastructure.
keywords⁄archive about

1. Introduction

This project implements Sandpoints, an open source framework for open and collaborative publishing. It is developed by Marcell Mars since 2019, and built as a theme for the static website builder www⁄Hugo. Both Hugo and Sandpoints are free, open source, and cross platform, and are developed in the programming language Go.

The implementation of Sandpoints in academic research publishing was outlined by van Gerven Oei in the editorial of Dotawo Journal issue 7 (2020):

Starting with the present issue, Dotawo will design and publish its content via the www⁄Sandpoints platform. Dotawo contributions are formatted in www⁄Markdown syntax, thus moving away from proprietary software such as Microsoft Word and Adobe InDesign. For collaboration and version-control we employ www⁄Git rather than Google Drive or Dropbox. The online issue is created via www⁄Gitea and www⁄Hugo, which take the Markdown files from the Git repository and generate a static website from them. The result is a compact and fast website, which moreover can also be used offline. Also the typography of Dotawo is now based on open fonts. The journal is typeset in www⁄Gentium, which is released under an www⁄SIL Open Font License. The PDF output is generated by www⁄PagedJS […]. In short, all of the software used in the creation of Dotawo is now open source. Although this process demands a certain amount of flexibility of the editors, it also shows that transitioning an open access journal to open infrastructure is not only possible but also feasible.1

2. Key features of Sandpoints

3. Ontology

Sandpoints supports a triadic hierarchy. This follows that content is organized, or parented according to a tree structure with a depth of three (entities). This project follows the scheme archive>issue>article, as in:2

Archive
└── Issue
    └── Article
-Editor 
-Contributor
-Print

This ontology follows that:

Furthermore:

Lastly, print items are used to enable printing of any of the above elements (e.g. article, issue, or the whole archive ).

4. Content organization

Content in Sandpoints is formatted in Markdown files, which are organized in subdirectories within the directory /root/content/. Each subdirectory inside content/ is named after and corresponds to a specific content type.

This project features the following content types (and subdirectories):

5. Sitemap

Sandpoints projects feature a sitemap, that lists all published content (all content that is not marked as draft). The sitemap is at the root URL of any given project.

The concept of backlinks was described in early speculations that informed hypertext (i.e. by Vannevar Bush and later Ted Nelson), but were not implemented the WWW. According to these ideas, hyperlinks are bi-directional, which follows that a hyperlink is visible both in the document that features a link and also at the target document where the link is pointing to. The latter is a backlink. By this scheme, any document knows which other documents point to it. The same concept is used by search engine algorithms, such as ‘page rank’ by Google, that function by creating an index of how many webpages link to a specific target website – or how many backlinks a given webpage has.

Sandpoints allows backlinks for selected items.3 Here these are article, contributor, and editor.

![this is a link to an article](article:target-article)

This will create a link to the target-article but it will also create a backlink – a mention of this link inside the target-article.

A link from this article to some other one, at the latter article will generate a backlink that would appear at the top right of the page (mentioned in this-article).

Backlinks (as well as external and internal hyperlinks) are catalogued at urls.

7. Notes


  1. www⁄Preface by the Editor (Vincent W.J. van Gerven Oei, Dotawo issue 7, 2020)↩︎

  2. Other examples to visualize this content are book>chapter>section, and ship>deck>room↩︎

  3. These can be set in the config file, at the sandpointsMentionedIn array. ↩︎