life-itself / life-itself/web3

[epic] Migrate "library" to Zotero (?)

Open
#44 8 comments 0 reactions 1 assignee View on GitHub

@rufuspollock is already working on this.

Since Feb 23, 2022.

Dominant language
HTML
Stars
1.9k
Forks
213
PR merge metrics
No merged PRs in 30d

Description

What we have is essentially a bibliography. The proposal here is to adopt the [Zotero reference manager](https://zotero.org) as our backend storage for the bibliographic items.

### Why do this change?

The main plus point of managing as README in git(hub) is:

* Making it easy to have moderated contribution via pull requests etc
* Quick publishing (it is just the github readme)
* Stars ⭐ (so some sense of interest / attention)

However, this is not necessarily optimal, especially as the bibliography grows. For example:

* Manual additions of new items including the key metadata
* No standard format for items (a change in standard format requires
* Painful to show the same item under multiple topics (manually copy and paste and if we correct anything needs correcting in multiple locations)
* Re-organizing of topics requires manual work
* No ability to sort by date or similar

Zotero + a renderer (static site) would seem to address a lot of this. At a minimum using zotero and very simple rendering should be able to reproduce what we have already and allow for easier addition of new material.

## Acceptance

* [x] We have made choice about using (trialling?) Zotero
* [x] We have a working Zotero library and have migrated some items there
* [x] We have instructions for others on how to contribute
* [ ] We have a PoC for how we get items back out and into a "README"

## Tasks

* [x] Set out the reasons for doing this **DONE. See Why below**
* [x] Migrate content to Zotero (trial)
* [x] Boot Zotero group library **DONE: https://www.zotero.org/groups/4600269/web3**
* [x] Migrate a test set of items (e.g. the general section) from the awesome repo to the awesome/general Zotero folder
* [x] create an awesome subcollection
* [x] create a general subcollection of awesome collection (or do we use tags??)
* [x] Migrate items following the migration process set out below in analysis (and update as needed)
* [x] Write up notes for others
* [ ] #52
* [ ] Script converting this back into markdown
* [ ] Research if any libraries / tools already exist in zotero ecosystem
* [ ] Use one or or decide to roll our own
* [ ] ...

### Misc

* [x] @EilidhRoss1 take @catherinet1 through Zotero and record notes from this briefing into section below about using Zotero so that we can write it up for others

## Analysis

### How to Contribute to the Zotero Library

* Install Zotero app
* Install Zotero extension
* Join the group library TODO

#### How to add Items / Migrate items

Aim: have "good" items where good means:

* Has snapshot or PDF etc (auto-generated usually if you add from the extension)
* Has proper metadata (full author name, date of piece, publication etc)

When migrating items:

* Notes in notes section (paste without formatting)
* [ ] Check if there is markdown support in Zotero notes field ...

### How to contribute to Zotero

* Create an account at zotero.org if you haven't already
* Install the browser extension
* (Recommend) Download the desktop app
* Visit the group and click the join button https://www.zotero.org/groups/4600269/web3
* Be approved by an admin (ping me @rufuspollock !)
* Start adding materials (e.g. using the browser extension)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.