Zotero Pains… The “pre-print”

The massive pre-print industry has influenced Zotero to make their a specific category for pre-print. This is a cognitive fallacy which only exacerbates the citation and reference chaos.

Pre-prints are manuscripts.... There are hand-written manuscripts, there are typescript manuscripts and there are computer generated manuscripts... Zotero already has manuscripts as a category... no need to add a new category.

To make matters worse, Zotero imports PDFs when it can find open access versions of them. The problem is that it imports them to the article/publication type when they are pre-prints rather than to the pre-print item type. This make authority version management in Zotero nightmare. Classic case (try importing) : https://doi.org/10.1177/0964663914565848

I am still hopeful that Zotero staff will find a clean and easy way to automatically link pre-prints to their authority version records within Zotero.

Annotated Bibliography Options

I'm a big Zotero fan. I have two gripes with Zotero.

  1. Annotated Bibliographies are hard to create because one can't use notes. There are some other options. Here are two guides.
  2. Filtering resources so as to edit them or edit in bulk.

I started looking at biblatex options. Jabref is the leading software I have found. It does not have an easy sync for PDF files in a team. Here are some latex templates. It would be good if I could find a flexible template in latex.

Zotero Research

While in France I started looking at the literature on Zotero and looking at multi-lingual publications and citation and references.

Zotero: A bibliographic assistant to researcher
Tutorial: multilingual publications and bibliographies — Juris-M documentation
Roy Rosenzweig Center for History and New Media - Wikipedia
How many science journals? | Science Intelligence and InfoPros
How many science journals?
Citation Style Language - Citation Style Language

Software Needs for a Language Documentation Project

In this post I take a look at some of the software needs of a language documentation team. One of my ongoing concerns of linguistic software development teams (like SIL International's Palaso or LSDev, or MPI's archive software group, or a host of other niche software products adapted from main stream open-source projects) is the approach they take in communicating how to use the various elements of their software together to create useful workflows for linguists participating in field research on minority languages. Many of these software development teams do not take the approach that potential software users coming to their website want to be oriented to how these software solutions work together to solve specific problems in the language documentation problem space. Now, it is true that every language documentation program is different and will have different goals and outputs, but many of these goals are the same across projects. New users to software want to know top level organizational assumptions made by software developers. That is, they want to evaluate how software will work in a given scenario (problem space) and to understand and make informed decisions based on the eco-system that the software will lead them into. This is not too unlike users asking which is better Android or iPhone, and then deciding what works not just with a given device but where they will buy their music, their digital books, and how they will get those digital assets to a new device, when the phone they are about to buy no-longer serves them. These digital consequences are not in the mind of every consumer... but they are nonetheless real consequences.
Continue reading