Annotation

The complete description of the annotation workflow can be found here, and an updated version here. Steps below only explain the process of selection of a text for annotation.

1. Open the priority list. It is organized chronologically and is searcheable (the field with a magnifying glass, saying Search this file).
2. Texts with priority are the ones that should be annotated. Work in chronological order. Texts up to 1000 AH are of top priority.
3. While the priority list will be updated regularly, you should check if a text is not being annotated. To do so, go to issues and, in the Field FILTER, search for the URI of the book that you want to annotate (use either complete URI, like 0597IbnJawzi.Muntazam, or Author's URI 0597IbnJawzi, or the title of the book like Muntazam; note: if you search for IbnJawzi nothing will be found).
4. Check results in both open and closed issues. If nothing found, you can start working on the selected text. (git fork > git clone > annotate).
5. Before you proceed, open an issue (issues > New Issue), using IN PROGRESS template.
6. After you finish annotating, send a pull request, close your IN PROGRESS ISSUE, and open another issue using Submission report (for Pull Requests) template.

A note for the project curators

You can create an URGENT issue to assignn specific text to a specific person. Go to ISSUES > New Issue > select URGENT template > Follow the instructions in the template.

Used IDs

IDs for Collections

IDs for Individual Contributions