---
title: "Features Requests / Issues 🦚 "
date: "2023-07-11T17:48:22+03:00"
author: "anybody"
contributors: ["constantinos-miltiadis.md"] 
draft: false 
keywords:
  - internal 
  - journal management 
  - feature requests
abstract: |
  (Internal) List of feature requests. 
---

# Introduction 

Here we can list feature requests and issues for *Sandpoints*, or for this project in general. 
After being discussed, issues and requests should be communicated to and discussed with the *Sandpoints* developers, ideally by filing an issue on the [Sandpoints repository](https://git.sandpoints.org/). 

To contribute an issue or request make a new subheading within [feature requests](#requests), and add date and contributor. Resolved issues should be moved to the [resolved](#resolved) section. 

# Feature requests {#requests}

## Expose item publication date (urgent)

Expose publication date of published material so that citation/reference scrapers can see when was something published. 
My experimental [Dotawo Zotero Translator](https://github.com/cmiltiadis/Dotawo-Journal-Zotero-Translator) cannot find any mention of a date. 

- Issue posted on *Sandpoints* repository -- CM 06.2023. 
- Perhaps this can be done with the `.PublishDate` [page variable](https://gohugo.io/variables/page/) associated with the header field `publishdate`  -- CM 13.07.2023. 

## Add option to sort orphan entries in Sitemap by type
Currently, entries without parent (Print, Authors, Editors, etc.) appear in the [sitemap](/) sorted by creation date. It would be useful to have an option for sorting such orphan entries by type. For example, to have all Authors together, as well as Print entries and Editors appearing as grouped together.

- Issue posted on *Sandpoints* repository -- CM 06.2023. 
## Associate print with target item 

Currently, to print something, one has to go to the [sitemap](/) and look if there is a `print` entity for the item they are interested in. 
It would be useful, as in backlinks, to be able to have a button such as 'print this item'. 

- Issue posted on *Sandpoints* repository -- CM 06.2023. 

## Fix Accorder (Zotero to Calibre) Metadata loss

Accorder seems to be optimized for book, and less for papers or chapters. 
Necessary metadata fields seem to get lost in the transfer, like: 
- ISBN of book chapter (ids)
- DOI of paper (ids)
- Conference and proceedings names
- URL of paper 
- Book editors are 
- For papers keep Conference and Proceedings name. 
- Here is a Zotero item exported (file/annotation fields remove): 
	```
	@incollection{graziano2019,
	  title = {Learning from \#{{Syllabus}}},
	  booktitle = {State Machines: Reflections and Actions at the Edge of Digital Citizenship, Finance, and Art},
	  author = {Graziano, Valeria and Mars, Marcell and Tomislav, Medak},
	  editor = {Colakides, Yiannis and Garrrett, Marc and Gloerich, Inte},
	  date = {2019},
	  publisher = {{Institute of Network Cultures}},
	  location = {{Amsterdam}},
	  url = {http://www.statemachines.eu/books/state-machines-reflections-and-actions-at-the-edge-of-digital-citizenship-finance-and-art/},
	  abstract = {some abstract},
	  isbn = {978-94-92302-33-5},
	  langid = {english},
	  keywords = {calibre,shadow libraries,syllabus}
	}
	```
- This in `catalog.json` becomes (cover,formats, librarian, and id removed): 
	- editors become authors 
	```
	"xxxxxxxxxxxxxxxxxx": {
	        "title": "Learning from Syllabus",
	        "title_sort": "Learning from Syllabus",
	        "pubdate": "2019-07-15 00:00:00+00:00",
	        "last_modified": "2023-07-12 15:10:30.186344+00:00",
	        "tags": ["shadow libraries", "calibre", "syllabus"],
	        "abstract": "abstract",
	        "publisher": "Institute of Network Cultures",
	        "authors": ["Valeria Graziano", "Marcell Mars", "Medak Tomislav", "Yiannis Colakides", "Marc Garrrett", "Inte Gloerich"],
	        "identifiers": [{
	                "scheme": "bibhash",
	                "code": "nBlXgFSgppCE"
	            }
	        ],
	        "languages": ["eng"]
	    }
	```

# Resolved {#resolved}

## Add background to code blocks 

Code blocks are useful not only for code but also for Markdown formatting instructions, or terminal commands having to do with site maintenance. I would be useful to be able to more easily distinguish code blocks like blockquotes. At the moment, it's not easy to tell code blocks apart, or to distinguish them from text.  

---

Edited CSS file (`site.min.css`) to: 
- introduce a background color for `code` (inline code blocks), and `pre` (multiline code blocks), which is only slightly darker than the blockquote background, 
	- > this is a blockquote 
	- `this is a codeblock (<code> css style)`
- reduce the font size and add a border for multiline code blocks. The border color is the same(red) as the blockquote left-side border. The font size is scaled to 75%
   ```
   this is a multiline blockquote (<pre> css style)
   ```

Nevertheless: 
- The actual background color, and padding should probably be reworked to fit better with the rest of the typesetting. 
- Perhaps a 75% (or other) font size should be shared between `code` and `pre`

Current changes are in commit `f405856fbd`  -- CM 11.07.2023. 

## Fix Zotero (.bib import) to Calibre 

Accorder (see ![Library management](article:int-library)), has a feature that allows reference collections exported from Zotero in `.bib` to be imported into the (Calibre) library. This doesn't seem to work properly  -- CM 07.2023.  
- We made it work via WSL terminal in Windows, using an older Calibre installation. In the meantime Marcell is working a new version of accorder in Go, which should arrive soon. For now library items can be forwarded via compressed `.bib` to the librarian  -- CM 13.07.2023. 

## Remove date from keywords perspective 

If you click on any keyword, the new page shows all entries with that keyword. It ALSO shows the date these were created (in my case file creation date is part of the MD header). It would be great if these dates could be omitted.

- [Issue posted on Sandpoints repository](https://git.sandpoints.org/Drawwell/SandpointsTheme/issues/6) -- CM 10.2022. 

Resolved by editing out line 15 in `..theme/layouts/taxonomy/list.html`

- Issue closed on 13.07.2022 -- CM.  