sslabdata 3.1.0__tar.gz → 5.0.0__tar.gz

{sslabdata-3.1.0/sslabdata.egg-info → sslabdata-5.0.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: sslabdata
-Version: 3.1.0
+Version: 5.0.0
 Summary: Renderer-agnostic academic lab data assembler: BibTeX + YAML → structured data
 Author: Siddhartha Srinivasa
 License-Expression: MIT
@@ -37,6 +37,11 @@ Dynamic: license-file
 
 # sslabdata
 
+[![PyPI](https://img.shields.io/pypi/v/sslabdata.svg)](https://pypi.org/project/sslabdata/)
+[![Python](https://img.shields.io/pypi/pyversions/sslabdata.svg)](https://pypi.org/project/sslabdata/)
+[![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](https://github.com/siddhss5/sslabdata/blob/main/LICENSE)
+[![Tests](https://github.com/siddhss5/sslabdata/actions/workflows/test.yml/badge.svg?branch=main)](https://github.com/siddhss5/sslabdata/actions/workflows/test.yml)
+
 sslabdata compiles BibTeX and a little YAML into one schema-specified document —
 works, people, projects and the links between them — that any website, CV or
 script can read.
@@ -56,10 +61,11 @@ sslabdata --config lab.yaml --output lab.yml
   order the lists are in, which fields are derived, when the version changes.
 - [`CHANGELOG.md`](https://github.com/siddhss5/sslabdata/blob/main/CHANGELOG.md) — what changed at each release, and what it
   replaced.
-- [`schema/v5/output.schema.json`](https://github.com/siddhss5/sslabdata/blob/main/schema/v5/output.schema.json) — the
+- [`schema/v6/output.schema.json`](https://github.com/siddhss5/sslabdata/blob/main/schema/v6/output.schema.json) — the
   document's JSON Schema. Published versions are immutable and live at their
-  own paths; [`schema/v3/`](https://github.com/siddhss5/sslabdata/blob/main/schema/v3/output.schema.json) and
-  [`schema/v4/`](https://github.com/siddhss5/sslabdata/blob/main/schema/v4/output.schema.json) are still there.
+  own paths; [`schema/v3/`](https://github.com/siddhss5/sslabdata/blob/main/schema/v3/output.schema.json),
+  [`schema/v4/`](https://github.com/siddhss5/sslabdata/blob/main/schema/v4/output.schema.json) and
+  [`schema/v5/`](https://github.com/siddhss5/sslabdata/blob/main/schema/v5/output.schema.json) are still there.
 - [`tests/COVERAGE.md`](https://github.com/siddhss5/sslabdata/blob/main/tests/COVERAGE.md) — every input case sslabdata
   supports, and every case it does not, with the fixture and test for each.
 
@@ -182,6 +188,7 @@ nothing else:
 | `doi`, `isbn`, `issn`, `eprint` + `archivePrefix` (or `eprinttype`) | `identifiers`, an open map from scheme to a list of identifiers, plus the links built from them. An `eprint`'s scheme is the repository `archivePrefix` or `eprinttype` named, lower-cased, so that field needs no property of its own — and an `eprint` in a repository other than arXiv gets no arXiv link |
 | `abstract` | `abstract` |
 | `note` | `note` |
+| `award` | `awards`, a list of `{name, year}` (see below). `note` is never read for awards |
 | `url` | A link of kind `video` when its host is YouTube or Vimeo (or a subdomain of either), otherwise of kind `url` |
 | `video` | A link of kind `video`, whatever its host, so `url` can hold the work's website |
 | `pdf` | The work's one link of kind `pdf`. An entry without it gets `pdf_base_url` plus its citation key, when `pdf_base_url` is set |
@@ -192,6 +199,26 @@ The entry is also re-serialized into a `bibtex` field, so fields sslabdata does
 not interpret are still carried. It is a re-serialization, not a copy
 ([`SPEC.md` §5](https://github.com/siddhss5/sslabdata/blob/main/SPEC.md#5-input-versus-derived)).
 
+### Awards
+
+A paper's awards go in its `award` field. Several are separated by `and`, as
+the names in `author` are, and braces keep an `and` inside one name. An award
+may start with the year it was given, as `YYYY:` and a space, when that is not
+the paper's year:
+
+```bibtex
+award = {2026: Test of Time Award and {Best Systems and Software Paper Award}}
+```
+
+Each award becomes `{name, year}` in the work's `awards`, in the order
+written, with its name converted from LaTeX as `title` is. An award without a
+year takes the work's `year`, or `null` when the work has none. `awards` is
+`[]` for a work with no `award` field. An empty award, or a prefix that looks
+like a year and is not four digits, a colon and a space, is reported
+(`BIB-AWARD-EMPTY`, `BIB-AWARD-YEAR-MALFORMED`); a malformed prefix stays in
+the name. Awards a person holds, such as fellowships, are not part of the
+document.
+
 ### The `project` tag
 
 sslabdata adds one custom BibTeX field, `project`, to link a paper to a research
@@ -205,6 +232,7 @@ project:
   year      = {2024},
   eprint    = {2406.99812},
   archivePrefix = {arXiv},
+  award     = {Best Paper Award},
   project   = {homebot}
 }
 ```
@@ -227,6 +255,9 @@ author names to people:
   website: "https://example.org/people/bbrown"
   co_advisor: "Peggy Park"
   start_year: 2021
+  bio: |
+    Bob Brown is a PhD student advised by Alice Adams and Peggy Park.
+    He works on shared control for assistive robot arms.
 
 - id: "iingram"
   name: "Ivan Ingram"
@@ -243,6 +274,16 @@ author names to people:
 `id` and `name` are required. `role` is any non-empty string, so any lab's
 roles fit; `status` is `current` (the default) or `alumni`.
 
+`bio` is a short biography in plain text, not Markdown or HTML: it is
+emitted as written and a renderer escapes it. Line breaks are kept as YAML
+reads them, so a block scalar (`|`) keeps each line, and a renderer may treat
+a blank line as a paragraph break. A person without one gets `bio: null`; an
+empty string is emitted as written, as any other person field is. Keep the
+structured facts in their own fields: nothing reads `degree`, years or
+`current_position` out of a bio, so an alumni line such as "PhD 2022, now
+Research Scientist at Example Robotics" is for the renderer to build from
+those fields.
+
 ### External co-authors (optional, `data/collaborators.yaml`)
 
 A list of co-authors outside the lab whose spellings you want grouped
@@ -278,24 +319,26 @@ deciding which URLs are safe to render is the renderer's job.
 ### Checking inputs in an editor
 
 Each input file has a JSON Schema in
-[`schema/input/v1/`](https://github.com/siddhss5/sslabdata/tree/main/schema/input/v1):
+[`schema/input/v2/`](https://github.com/siddhss5/sslabdata/tree/main/schema/input/v2):
 `lab.schema.json`, `people.schema.json`, `projects.schema.json` and
 `collaborators.schema.json`. The wheel installs them under
-`sslabdata/schema/input/v1/`. An editor can use them to check and complete
+`sslabdata/schema/input/v2/`. An editor can use them to check and complete
 the files as you write; `--validate` stays the check, and also reports what
 a schema cannot see, such as a repeated id or a missing file. With the YAML
 language server (the VS Code YAML extension, among others), name the schema
 in a comment at the top of the file:
 
 ```yaml
-# yaml-language-server: $schema=https://raw.githubusercontent.com/siddhss5/sslabdata/input-schema-v1/schema/input/v1/people.schema.json
+# yaml-language-server: $schema=https://raw.githubusercontent.com/siddhss5/sslabdata/input-schema-v2/schema/input/v2/people.schema.json
 - id: "aadams"
   name: "Alice Adams"
   role: "professor"
 ```
 
-The URL is the schema's `$id`, served from the `input-schema-v1` tag, which is
+The URL is the schema's `$id`, served from the `input-schema-v2` tag, which is
 never moved ([`SPEC.md` §6](https://github.com/siddhss5/sslabdata/blob/main/SPEC.md#6-version-policy)).
+A file that names v1 still validates, because v1 allows keys it does not
+list, but only v2 checks and completes `bio`.
 Use `lab.schema.json`, `projects.schema.json` or `collaborators.schema.json`
 in the same way for the other files.
 
@@ -349,7 +392,7 @@ pip install jsonschema
 python -c "
 import json, yaml, jsonschema
 from importlib.resources import files
-schema = json.loads(files('sslabdata.schema').joinpath('v5/output.schema.json').read_text())
+schema = json.loads(files('sslabdata.schema').joinpath('v6/output.schema.json').read_text())
 jsonschema.Draft202012Validator(schema).validate(yaml.safe_load(open('lab.yml')))
 print('valid')
 "

{sslabdata-3.1.0 → sslabdata-5.0.0}/README.md

@@ -1,5 +1,10 @@
 # sslabdata
 
+[![PyPI](https://img.shields.io/pypi/v/sslabdata.svg)](https://pypi.org/project/sslabdata/)
+[![Python](https://img.shields.io/pypi/pyversions/sslabdata.svg)](https://pypi.org/project/sslabdata/)
+[![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](https://github.com/siddhss5/sslabdata/blob/main/LICENSE)
+[![Tests](https://github.com/siddhss5/sslabdata/actions/workflows/test.yml/badge.svg?branch=main)](https://github.com/siddhss5/sslabdata/actions/workflows/test.yml)
+
 sslabdata compiles BibTeX and a little YAML into one schema-specified document —
 works, people, projects and the links between them — that any website, CV or
 script can read.
@@ -19,10 +24,11 @@ sslabdata --config lab.yaml --output lab.yml
   order the lists are in, which fields are derived, when the version changes.
 - [`CHANGELOG.md`](https://github.com/siddhss5/sslabdata/blob/main/CHANGELOG.md) — what changed at each release, and what it
   replaced.
-- [`schema/v5/output.schema.json`](https://github.com/siddhss5/sslabdata/blob/main/schema/v5/output.schema.json) — the
+- [`schema/v6/output.schema.json`](https://github.com/siddhss5/sslabdata/blob/main/schema/v6/output.schema.json) — the
   document's JSON Schema. Published versions are immutable and live at their
-  own paths; [`schema/v3/`](https://github.com/siddhss5/sslabdata/blob/main/schema/v3/output.schema.json) and
-  [`schema/v4/`](https://github.com/siddhss5/sslabdata/blob/main/schema/v4/output.schema.json) are still there.
+  own paths; [`schema/v3/`](https://github.com/siddhss5/sslabdata/blob/main/schema/v3/output.schema.json),
+  [`schema/v4/`](https://github.com/siddhss5/sslabdata/blob/main/schema/v4/output.schema.json) and
+  [`schema/v5/`](https://github.com/siddhss5/sslabdata/blob/main/schema/v5/output.schema.json) are still there.
 - [`tests/COVERAGE.md`](https://github.com/siddhss5/sslabdata/blob/main/tests/COVERAGE.md) — every input case sslabdata
   supports, and every case it does not, with the fixture and test for each.
 
@@ -145,6 +151,7 @@ nothing else:
 | `doi`, `isbn`, `issn`, `eprint` + `archivePrefix` (or `eprinttype`) | `identifiers`, an open map from scheme to a list of identifiers, plus the links built from them. An `eprint`'s scheme is the repository `archivePrefix` or `eprinttype` named, lower-cased, so that field needs no property of its own — and an `eprint` in a repository other than arXiv gets no arXiv link |
 | `abstract` | `abstract` |
 | `note` | `note` |
+| `award` | `awards`, a list of `{name, year}` (see below). `note` is never read for awards |
 | `url` | A link of kind `video` when its host is YouTube or Vimeo (or a subdomain of either), otherwise of kind `url` |
 | `video` | A link of kind `video`, whatever its host, so `url` can hold the work's website |
 | `pdf` | The work's one link of kind `pdf`. An entry without it gets `pdf_base_url` plus its citation key, when `pdf_base_url` is set |
@@ -155,6 +162,26 @@ The entry is also re-serialized into a `bibtex` field, so fields sslabdata does
 not interpret are still carried. It is a re-serialization, not a copy
 ([`SPEC.md` §5](https://github.com/siddhss5/sslabdata/blob/main/SPEC.md#5-input-versus-derived)).
 
+### Awards
+
+A paper's awards go in its `award` field. Several are separated by `and`, as
+the names in `author` are, and braces keep an `and` inside one name. An award
+may start with the year it was given, as `YYYY:` and a space, when that is not
+the paper's year:
+
+```bibtex
+award = {2026: Test of Time Award and {Best Systems and Software Paper Award}}
+```
+
+Each award becomes `{name, year}` in the work's `awards`, in the order
+written, with its name converted from LaTeX as `title` is. An award without a
+year takes the work's `year`, or `null` when the work has none. `awards` is
+`[]` for a work with no `award` field. An empty award, or a prefix that looks
+like a year and is not four digits, a colon and a space, is reported
+(`BIB-AWARD-EMPTY`, `BIB-AWARD-YEAR-MALFORMED`); a malformed prefix stays in
+the name. Awards a person holds, such as fellowships, are not part of the
+document.
+
 ### The `project` tag
 
 sslabdata adds one custom BibTeX field, `project`, to link a paper to a research
@@ -168,6 +195,7 @@ project:
   year      = {2024},
   eprint    = {2406.99812},
   archivePrefix = {arXiv},
+  award     = {Best Paper Award},
   project   = {homebot}
 }
 ```
@@ -190,6 +218,9 @@ author names to people:
   website: "https://example.org/people/bbrown"
   co_advisor: "Peggy Park"
   start_year: 2021
+  bio: |
+    Bob Brown is a PhD student advised by Alice Adams and Peggy Park.
+    He works on shared control for assistive robot arms.
 
 - id: "iingram"
   name: "Ivan Ingram"
@@ -206,6 +237,16 @@ author names to people:
 `id` and `name` are required. `role` is any non-empty string, so any lab's
 roles fit; `status` is `current` (the default) or `alumni`.
 
+`bio` is a short biography in plain text, not Markdown or HTML: it is
+emitted as written and a renderer escapes it. Line breaks are kept as YAML
+reads them, so a block scalar (`|`) keeps each line, and a renderer may treat
+a blank line as a paragraph break. A person without one gets `bio: null`; an
+empty string is emitted as written, as any other person field is. Keep the
+structured facts in their own fields: nothing reads `degree`, years or
+`current_position` out of a bio, so an alumni line such as "PhD 2022, now
+Research Scientist at Example Robotics" is for the renderer to build from
+those fields.
+
 ### External co-authors (optional, `data/collaborators.yaml`)
 
 A list of co-authors outside the lab whose spellings you want grouped
@@ -241,24 +282,26 @@ deciding which URLs are safe to render is the renderer's job.
 ### Checking inputs in an editor
 
 Each input file has a JSON Schema in
-[`schema/input/v1/`](https://github.com/siddhss5/sslabdata/tree/main/schema/input/v1):
+[`schema/input/v2/`](https://github.com/siddhss5/sslabdata/tree/main/schema/input/v2):
 `lab.schema.json`, `people.schema.json`, `projects.schema.json` and
 `collaborators.schema.json`. The wheel installs them under
-`sslabdata/schema/input/v1/`. An editor can use them to check and complete
+`sslabdata/schema/input/v2/`. An editor can use them to check and complete
 the files as you write; `--validate` stays the check, and also reports what
 a schema cannot see, such as a repeated id or a missing file. With the YAML
 language server (the VS Code YAML extension, among others), name the schema
 in a comment at the top of the file:
 
 ```yaml
-# yaml-language-server: $schema=https://raw.githubusercontent.com/siddhss5/sslabdata/input-schema-v1/schema/input/v1/people.schema.json
+# yaml-language-server: $schema=https://raw.githubusercontent.com/siddhss5/sslabdata/input-schema-v2/schema/input/v2/people.schema.json
 - id: "aadams"
   name: "Alice Adams"
   role: "professor"
 ```
 
-The URL is the schema's `$id`, served from the `input-schema-v1` tag, which is
+The URL is the schema's `$id`, served from the `input-schema-v2` tag, which is
 never moved ([`SPEC.md` §6](https://github.com/siddhss5/sslabdata/blob/main/SPEC.md#6-version-policy)).
+A file that names v1 still validates, because v1 allows keys it does not
+list, but only v2 checks and completes `bio`.
 Use `lab.schema.json`, `projects.schema.json` or `collaborators.schema.json`
 in the same way for the other files.
 
@@ -312,7 +355,7 @@ pip install jsonschema
 python -c "
 import json, yaml, jsonschema
 from importlib.resources import files
-schema = json.loads(files('sslabdata.schema').joinpath('v5/output.schema.json').read_text())
+schema = json.loads(files('sslabdata.schema').joinpath('v6/output.schema.json').read_text())
 jsonschema.Draft202012Validator(schema).validate(yaml.safe_load(open('lab.yml')))
 print('valid')
 "

{sslabdata-3.1.0 → sslabdata-5.0.0}/SPEC.md

@@ -7,7 +7,7 @@ them.
 This file states the parts of that contract a JSON Schema cannot express:
 what the strings in the document are, what order the lists are in, what an
 absent key means, which fields are computed, when the version changes, and
-how a repeated `@string` macro resolves. `schema/v5/output.schema.json`
+how a repeated `@string` macro resolves. `schema/v7/output.schema.json`
 states the rest.
 
 Everything here is normative unless it carries a `Target` note. A `Target`
@@ -16,8 +16,8 @@ names the issue that will make it true. Until that issue lands, the rule is
 the intent and the note is the fact. What changed at each release, and what
 it replaced, is in [`CHANGELOG.md`](CHANGELOG.md), not here.
 
-- Applies to: `schema_version` 5 (`sslabdata.models.SCHEMA_VERSION`), package
-  version 3.0.0 (`sslabdata.__version__`).
+- Applies to: `schema_version` 7 (`sslabdata.models.SCHEMA_VERSION`), package
+  version 5.0.0 (`sslabdata.__version__`).
 
 ### How this file cites the code
 
@@ -25,7 +25,7 @@ Every rule below is grounded in a named part of the code rather than a line
 number, because line numbers rot silently: a function such as
 `sslabdata.parsers.bibtex.parse_all_works()`, a method such as
 `Person.to_dict()`, a module-level constant such as `TEXT_FIELDS`, a JSON
-Pointer into `schema/v5/output.schema.json` such as `/$defs/person/required`, or
+Pointer into `schema/v7/output.schema.json` such as `/$defs/person/required`, or
 a `tests/COVERAGE.md` row key such as `config.people_file.missing`. A bare
 statement is cited by its enclosing function.
 
@@ -201,7 +201,7 @@ without depending on English wording. Codes obey three rules:
    | **Fatal at load** | `Error loading configuration: <CODE> …` (`Error: <CODE> …` for `CONFIG-NOT-FOUND`) on standard error; exits `1` before anything is compiled, so there is no report. | The same. | `CONFIG-BIB-FILE-ABSOLUTE`, `CONFIG-BIB-FILE-OUTSIDE-BIB-DIR`, `CONFIG-NOT-A-MAPPING`, `CONFIG-KEY-MISSING`, `CONFIG-TYPE-INVALID`, `CONFIG-VALUE-NOT-JSON`, `CONFIG-KEY-REPEATED`, `CONFIG-NOT-FOUND`, `CONFIG-UNREADABLE` |
    | **Fatal** | Listed under `Bibliography errors` and counted; exits `1`. | Written to standard error unprefixed; exits `1`, and `--output` writes nothing. | `BIB-CROSSREF-UNSUPPORTED`, `BIB-ENCODING-INVALID`, `CONFIG-FILE-NOT-FOUND`, `CONFIG-PATH-WRONG-KIND`, `PEOPLE-YAML-INVALID`, `PEOPLE-NOT-A-LIST`, `PEOPLE-FIELD-MISSING`, `PROJECTS-YAML-INVALID`, `PROJECTS-NOT-A-LIST`, `PROJECTS-FIELD-MISSING`, `COLLABORATORS-YAML-INVALID`, `COLLABORATORS-NOT-A-LIST`, `COLLABORATORS-FIELD-MISSING`, `RECORD-KEY-REPEATED`, `OUTPUT-WRITE-FAILED`, `INIT-FILE-EXISTS`, `INIT-PATH-WRONG-KIND`, `INIT-PATH-OUTSIDE-DIR`, `INIT-WRITE-FAILED` |
    | **Validation error** | Listed under `Bibliography errors` and counted; exits `1`. | Prefixed `Warning: ` on standard error; the run continues and exits `0`. | `BIB-DUPLICATE-KEY`, `RESOLVE-PROJECT-UNKNOWN`, `PEOPLE-ID-DUPLICATE`, `PROJECTS-ID-DUPLICATE` |
-   | **Warning** | Listed under `Warnings`; not counted, and does not change the exit code. | Prefixed `Warning: ` on standard error; the run continues. | `BIB-YEAR-MISSING`, `BIB-YEAR-INVALID`, `BIB-DOI-INVALID`, `BIB-OTHERS-NOT-LAST`, `BIB-STRING-UNDEFINED`, `BIB-SYNTAX-ERROR`, `BIB-BRACE-MISMATCH`, `BIB-COMMENTED-COMMAND-READ`, `BIB-VENUE-MISSING`, `BIB-ENTRY-TYPE-UNSUPPORTED`, `LATEX-COMMAND-UNKNOWN`, `ID-GROUPING-SPANS-SPELLINGS`, `ID-GROUPING-INITIALS-AMBIGUOUS`, `RESOLVE-AMBIGUOUS-NAME`, `RESOLVE-SUGGESTION`, `RESOLVE-COLLABORATOR-ALIAS-IS-MEMBER`, `PEOPLE-ALIAS-AMBIGUOUS`, `PEOPLE-ROLE-INVALID`, `PEOPLE-STATUS-INVALID`, `PROJECTS-STATUS-INVALID`, `CONFIG-LAB-NAME-MISSING`, `CONFIG-KEY-UNKNOWN`, `RECORD-KEY-UNKNOWN`, `RECORD-TYPE-INVALID`, `CONFIG-BIB-FILES-MISSING`, `BIB-PARSER-MESSAGE`, `LATEX-CONVERSION-FAILED`, `LINK-SCHEME-UNSUPPORTED`, `TEXT-CONTROL-CHARACTER`, `BIB-WRITE-BACK-FAILED`, `BIB-STRING-REDEFINED`, `ID-GROUPING-AMBIGUOUS-DECLARED`, `RESOLVE-UNRESOLVED-NAME` |
+   | **Warning** | Listed under `Warnings`; not counted, and does not change the exit code. | Prefixed `Warning: ` on standard error; the run continues. | `BIB-YEAR-MISSING`, `BIB-YEAR-INVALID`, `BIB-DOI-INVALID`, `BIB-AWARD-EMPTY`, `BIB-AWARD-YEAR-MALFORMED`, `BIB-OTHERS-NOT-LAST`, `BIB-STRING-UNDEFINED`, `BIB-SYNTAX-ERROR`, `BIB-BRACE-MISMATCH`, `BIB-COMMENTED-COMMAND-READ`, `BIB-VENUE-MISSING`, `BIB-ENTRY-TYPE-UNSUPPORTED`, `LATEX-COMMAND-UNKNOWN`, `ID-GROUPING-SPANS-SPELLINGS`, `ID-GROUPING-INITIALS-AMBIGUOUS`, `RESOLVE-AMBIGUOUS-NAME`, `RESOLVE-SUGGESTION`, `RESOLVE-COLLABORATOR-ALIAS-IS-MEMBER`, `PEOPLE-ALIAS-AMBIGUOUS`, `PEOPLE-ROLE-INVALID`, `PEOPLE-STATUS-INVALID`, `PROJECTS-STATUS-INVALID`, `CONFIG-LAB-NAME-MISSING`, `CONFIG-KEY-UNKNOWN`, `RECORD-KEY-UNKNOWN`, `RECORD-TYPE-INVALID`, `CONFIG-BIB-FILES-MISSING`, `BIB-PARSER-MESSAGE`, `LATEX-CONVERSION-FAILED`, `LINK-SCHEME-UNSUPPORTED`, `TEXT-CONTROL-CHARACTER`, `BIB-WRITE-BACK-FAILED`, `BIB-STRING-REDEFINED`, `ID-GROUPING-AMBIGUOUS-DECLARED`, `RESOLVE-UNRESOLVED-NAME` |
 
    The same code always carries the same class. What varies with the mode is
    how the run reacts to it, which is why the class is not in the code, and
@@ -249,6 +249,8 @@ Codes in use:
 | `CONFIG-LAB-NAME-MISSING` | The `lab` header declares no `name`. A `lab` that is not a mapping at all is a different condition and is not reported under this code. A warning. |
 | `BIB-YEAR-INVALID` | An entry's `year` is present but is not an unsigned run of the ASCII digits `0`–`9` (`sslabdata.parsers.bibtex.YEAR_DIGITS`), such as `in press`, or `-5`, `+2020`, `2_020` and full-width `２０２０`, which Python's `int()` would read as numbers. The work is emitted with `year: null` and sorts last, as one with no year does. A warning. |
 | `BIB-DOI-INVALID` | An entry's `doi` is a DOI resolver URL with nothing after it, such as `https://doi.org/` (`sslabdata.parsers.bibtex.DOI_RESOLVERS`), so it names no DOI. Located at `<file>:<key>:doi`, naming the value. The work gets no DOI identifier and no link of kind `doi`, rather than an empty one; the entry is kept. A `doi` that is empty or blank is read as absent, and is not reported. A warning. |
+| `BIB-AWARD-EMPTY` | An entry's `award` field names no award: the field is empty or whitespace alone, or one of its awards is empty — two `and`s with nothing between them, an `and` that opens or closes the list, or a name that is empty once converted from LaTeX, such as `{}` — or is a year prefix with no name after it, such as `2026:` (`sslabdata.parsers.bibtex.parse_awards()`). Located at `<file>:<key>:award`; the prose names the award's place in the list, and the award as written when it has a year. The empty award is dropped and the others are kept, so an empty field gives `awards: []`. A warning. |
+| `BIB-AWARD-YEAR-MALFORMED` | An award in an entry's `award` field starts with what reads as a year but is not the prefix `YYYY:` — four ASCII digits, a colon and whitespace (`sslabdata.parsers.bibtex.AWARD_YEAR`): digits of any kind and a colon, such as `26: …`, `2026:…` with no space, or full-width `２０２６: …`, or four digits and a space with no colon, `2026 …` (`AWARD_YEAR_LIKE`). Located at `<file>:<key>:award`, naming the award as written and the part that is not a prefix. No year is read from it: **the text is kept as part of the name**, and the award takes the work's `year`. A prefix inside braces, `{2026}: …`, is text the author protected and is not reported. A warning. |
 | `LINK-SCHEME-UNSUPPORTED` | A link in `work.links` whose URL scheme is not `http`, `https` or `mailto` (`sslabdata.parsers.bibtex.LINK_SCHEMES`), such as `javascript:`, `data:` or `vbscript:`, which a renderer escaping the document (§2) should refuse to turn into a link. The scheme is the one Python's URL parser reads (`urllib.parse.urlsplit()`, in `sslabdata.parsers.bibtex.url_scheme()`) once surrounding whitespace is off, compared without regard to case; the parser drops a tab or line break anywhere in the URL first, as a browser does, so `java<tab>script:` is `javascript`. A URL with no scheme is a relative path and is not reported; that includes a protocol-relative `//host/path`, which takes the scheme of the page that links it. A scheme of one letter is a Windows drive, read by Windows rules as `sslabdata.config` reads one (`PureWindowsPath`), and not a scheme: `C:/papers`, `C:\papers` and the drive-relative `c:papers` are local paths and are not reported. No registered scheme is one letter long. Every link is checked, whether the entry wrote it (`url`, `video`, `pdf`) or sslabdata built it (`doi`, `arxiv`, and `pdf` from `pdf_base_url`). Located at `<file>:<key>:<field>`, the field the link came from, or at `<file>:<key>:` for the PDF link `pdf_base_url` builds, which no field of the entry wrote; the prose names the link's kind, which for `url` can be `video`, and the URL. Once per link. A person's `website` and `photo`, a project's `website` and `image`, and everything under `lab` are fields, not links, and are not checked. **The link is emitted unchanged**: this code only reports it. A warning. |
 | `BIB-OTHERS-NOT-LAST` | An `author` or `editor` list has `and others` somewhere other than at its end, the one place BibTeX reads it as "et al.". It names nobody there either, so it is dropped as a terminal one is, and the names around it are kept in their order, with `position` counting only them. Located at `<file>:<key>:author` or `:editor`, once per list however many times it occurs. A terminal `and others` is not reported. A warning. |
 | `BIB-STRING-UNDEFINED` | A field value names an `@string` macro that nothing defined earlier in the same file. Located at the entry and field that use it, and naming the macro. It is read as empty, as BibTeX reads it, and the entry and its neighbours are kept. A macro used inside another `@string` definition is located at the file alone. A warning. |
@@ -273,7 +275,7 @@ Codes in use:
 | `PROJECTS-ID-DUPLICATE` | Two projects declare one `id`. Located at the second. Both are kept. A validation error. |
 | `PROJECTS-STATUS-INVALID` | A project's `status` is present and is not `active` or `completed`. A missing status reads as `active`, and so does one that is not a string. A warning. |
 | `RECORD-KEY-UNKNOWN` | A person, project or collaborator record holds a key sslabdata does not read (`sslabdata.loaders.PERSON_KEYS`, `PROJECT_KEYS`, `COLLABORATOR_KEYS`), such as `hobby` or a misspelt `webiste`. One code for all three files. Located at `<people_file>:<id>:<key>`, `<projects_file>:<id>:<key>` or `<collaborators_file>:<collaborator name>:<key>`, once per key. The key is ignored and never emitted; the record is kept. Only a record that is loaded is checked, so a record missing a required field reports that alone. A warning. |
-| `RECORD-TYPE-INVALID` | An optional field of a person, project or collaborator record has a value of the wrong type, other than the `role` and `status` that have codes of their own. A person's `photo`, `website`, `email`, `co_advisor`, `degree`, `thesis_title` and `current_position`, and a project's `description`, `website` and `image`, are strings; a person's `start_year` and `end_year` are integers, not booleans; a person's or collaborator's `aliases` is a list of non-empty strings. One code for all three files, located at `<file>:<id>:<field>` (a collaborator's name for its id). The value is read as empty, so it is emitted as `null`, and a wrong `aliases` declares none; the record is kept. Only a record that is loaded is checked. A warning. |
+| `RECORD-TYPE-INVALID` | An optional field of a person, project or collaborator record has a value of the wrong type, other than the `role` and `status` that have codes of their own. A person's `photo`, `website`, `email`, `co_advisor`, `degree`, `thesis_title`, `current_position` and `bio`, and a project's `description`, `website` and `image`, are strings; a person's `start_year` and `end_year` are integers, not booleans; a person's or collaborator's `aliases` is a list of non-empty strings. One code for all three files, located at `<file>:<id>:<field>` (a collaborator's name for its id). The value is read as empty, so it is emitted as `null`, and a wrong `aliases` declares none; the record is kept. Only a record that is loaded is checked. A warning. |
 | `RECORD-KEY-REPEATED` | A key is given twice in one mapping of a people, projects or collaborators file, which YAML alone would read as its last value, silently dropping the first. Every YAML file sslabdata reads is read with one loader that finds these (`sslabdata.config.YAMLLoader`). Keys are compared as YAML reads them, so `1` and `0x1` are one key. A merge key (`<<`) is not a repeat: the keys it merges in are overridden by the mapping's own, as YAML merge keys are defined. One code for all three files. Located at `<file>:<id>:<key>` (a collaborator's name for its id), with the path below the record's top level joined by `.` and a list member's index in brackets; the record is named by nothing when the repeated key is its `id` (a collaborator's `name`), and a repeat outside any record is located at `<file>::<path>`. The prose names the key and both lines. Every repeat is reported; the record is not loaded, and the run is fatal, as for a missing field: which value was meant is not sslabdata's to guess. |
 | `CONFIG-NOT-A-MAPPING` | `lab.yaml` is not a mapping of keys, or is empty. Fatal at load. |
 | `CONFIG-KEY-MISSING` | A required key is absent: `bib_dir`, or the `name` or `category` of a `bib_files` entry (`lab.yaml:bib_files:name`). Fatal at load. |
@@ -359,7 +361,7 @@ What each mode puts in the array:
 
 **The Python API is convenience only.** Public: the names in `sslabdata.__all__`
 — `assemble`, `AssemblyResult`, `AssemblyError`, the models `LabData`,
-`Work`, `Author`, `Contributor`, `Venue`, `Link`, `Person`, `Project`,
+`Work`, `Award`, `Author`, `Contributor`, `Venue`, `Link`, `Person`, `Project`,
 `Collaborator`, the config loader `LabDataConfig` with `BibFile`, and the exporters
 `export_to_yaml` and `export_to_json`, and the exception
 `ConfigurationError`.
@@ -521,7 +523,8 @@ the URL, and in math it is escaped to `\&` or `\%`. Exactly the fields in
 `publisher`, `address`, `organization`, `archivePrefix` and `eprinttype` —
 applied in `entry_fields()`. Name
 parts are converted the same way, in `person_name_parts()`, for authors and
-editors alike.
+editors alike, and so is each award's name, once `award` is split into its
+awards and each award's year prefix is read (`parse_awards()`).
 
 Being converted is not the same as being emitted. Of these fields, `title`,
 `abstract`, `note`, `type`, `series`, `publisher`, `address` and
@@ -538,10 +541,20 @@ converts nor checks them:
 - **The person and project strings supplied in YAML.**
   `sslabdata.loaders.load_people()` and `load_projects()` perform no conversion
   of any kind — they check the types of a record's fields, a person's `role` and that a
-  `status` is one they know, but emit every string as written — so a person's `name`, `role`, `current_position` or
-  `thesis_title`, and a project's `title` or `description`, are copied
+  `status` is one they know, but emit every string as written — so a person's `name`, `role`, `current_position`,
+  `thesis_title` or `bio`, and a project's `title` or `description`, are copied
   straight from `people.yaml` and `projects.yaml`. Not every YAML string is
   emitted — `aliases` and the configuration paths are not; see heading 3.
+  "As written" is the string YAML reads, after control characters are
+  removed and NFC is applied as for every input string (above), and nothing
+  else: an empty or whitespace-only string is emitted as such, not as
+  `null`, and line breaks are kept. That matters most for a person's `bio`,
+  the one of these meant to run over several lines: a literal block scalar
+  (`|`) keeps each line break and the final one, a folded one (`>`) joins
+  lines with a space and keeps a blank line as a line break, and `\n` in a
+  double-quoted string is a line break. It is plain text like the rest — not
+  Markdown and not HTML — and a renderer escapes it, and may read a blank
+  line as a paragraph break.
 - **`work.category`**, which comes from the `category` of the `bib_files`
   entry in `lab.yaml`, not from the `.bib` file
   (`sslabdata.config.LabDataConfig.from_yaml()`, then
@@ -581,6 +594,7 @@ rule does not apply to the input itself — only to whatever it produces.
 | `pdf` | Becomes the work's one link of kind `pdf`, with `origin: input`, in place of the one `pdf_base_url` would give (`build_links()`). Empty or whitespace-only is read as absent. |
 | `author` | Parsed into the `authors` list (`parse_author_list()`); the name parts are converted under heading 1. |
 | `editor` | Parsed into the `editors` list (`parse_editor_list()`), resolved by the same machinery, and excluded from `person.work_ids`, from a project's people and from `collaborators`. |
+| `award` | Parsed into the `awards` list (`parse_awards()`), and emitted nowhere else: `note` is never read for awards, and an award in `note` stays there as text. The field is split into awards as BibTeX splits `author` into names: on `and`, in any case, with whitespace on both sides, outside braces, which are counted as BibTeX counts them, so `{Systems and Software Award}` is one award. An `and` that opens or closes the list, or follows another, separates an empty award, which is dropped and reported (`BIB-AWARD-EMPTY`). Each award may then start with the year it was given, four ASCII digits, a colon and whitespace, `2026: Test of Time Award` (`AWARD_YEAR`), read before the name is converted from LaTeX under heading 1 and trimmed; it is that award's `year`, which need not be the work's. An award without one takes the work's `year`, or `null` when the work has none. A prefix that reads as a year and is not one, `26:` or `2026 …`, is kept in the name and reported (`BIB-AWARD-YEAR-MALFORMED`). |
 | `year` | Emitted as the integer `year` — not a string — or `null` with a `BIB-YEAR-MISSING` diagnostic when the entry supplied none, or with `BIB-YEAR-INVALID` when it is not written in the digits `0`–`9` alone. It drives the works order (§3). |
 | `crossref` | **Rejected, on presence rather than on value.** An entry carrying the field is an error under `BIB-CROSSREF-UNSUPPORTED`, whatever is inside it: an empty `crossref = {}` is a field the entry carries, and letting it through would put the silent path back under a different spelling. The entry is not emitted and the run fails in every mode (`parse_all_works()`). No field of any entry is filled in from any other entry. |
 | `journal`, `booktitle`, `school`, `institution` | Converted under heading 1, then consumed by `build_venue()` into `venue.name`, with the `venue.kind` each implies. |
@@ -657,6 +671,7 @@ accident.
 | `works` | `year` **descending**, with works that have no year **last**. Ties keep *read order* (below). The sort is the final statement of `sslabdata.parsers.bibtex.parse_all_works()`. |
 | `work.authors` | The order the `author` field wrote them (`sslabdata.parsers.bibtex.parse_author_list()`). A terminal `and others` is BibTeX's "et al." and is dropped rather than emitted as an author; one anywhere else is dropped too, and reported as `BIB-OTHERS-NOT-LAST`. `position` is that order, 1-based, and counts only the names that reach the document. |
 | `work.editors` | The order the `editor` field wrote them, read the same way (`parse_editor_list()`). |
+| `work.awards` | The order the `award` field wrote them, with each empty award dropped (`parse_awards()`). |
 | `work.project_ids` | The order the `project` field wrote them, comma-separated, whitespace trimmed, empty entries dropped (`sslabdata.parsers.bibtex.parse_project_ids()`). |
 | `people` | The order of `people_file`. sslabdata does not sort people (`sslabdata.loaders.load_people()`, called by `sslabdata.assembler.assemble()`). |
 | `projects` | The order of `projects_file`, likewise (`sslabdata.loaders.load_projects()`). |
@@ -752,7 +767,7 @@ unconditionally, and by `LabData.to_dict()`, which always emits `lab`.
 itself and each entity type as **closed**: `/additionalProperties` and each
 of `/$defs/authorship`, `/$defs/editorship`, `/$defs/work`, `/$defs/person`,
 `/$defs/project`, `/$defs/collaborator`, `/$defs/venue`, `/$defs/link`,
-`/$defs/resolution`, and the `source` and `generator` objects, set
+`/$defs/resolution`, `/$defs/award`, and the `source` and `generator` objects, set
 `additionalProperties: false`. Within those, a property that is not declared
 cannot appear, and "absent" always means a declared property with no value.
 
@@ -783,6 +798,7 @@ sslabdata's own output as input, and a wrong derivation becomes permanent.
 | `work.source.file` | Input — the `name` of the `bib_files` entry the file was listed under, **never an absolute path**. A *relative* directory is fine and is passed through as written: `sub/journal.bib` is a name under `bib_dir`; one that leaves `bib_dir` is rejected under `CONFIG-BIB-FILE-OUTSIDE-BIB-DIR`. The guarantee is kept by rejecting the input rather than by rewriting it, which would quietly discard that directory, and is enforced under `CONFIG-BIB-FILE-ABSOLUTE` (§1, *`sslabdata.ConfigurationError`*). |
 | `work.entry_type` | Input — the BibTeX entry type, **lowercased** by `entry_fields()`. Of it and `bib_id`, it is the only one that is case-folded. |
 | `work.title`, `abstract`, `note` | Input — BibTeX fields, converted from LaTeX to text (§2). `note` additionally has trailing `.` and whitespace trimmed (`sslabdata.parsers.bibtex.extract_note()`). |
+| `work.awards` | Input — the BibTeX `award` field, split into awards, each `{name, year}`: `name` converted from LaTeX, and `year` the year the award was given, from its `YYYY:` prefix, else the work's `year`, else `null` (`sslabdata.parsers.bibtex.parse_awards()`, §2). `[]` when the entry writes none. These are a work's awards only; an award a person holds, such as a fellowship, is not in the document. |
 | `work.year` | Input — the BibTeX `year`, as an integer; `null` when the entry supplied none, with a diagnostic (`entry_year()`). |
 | `work.category` | Input — the `category` of the `bib_files` entry the file was listed under, not anything in the `.bib` file (`sslabdata.config.BibFile`, read by `parse_all_works()`). |
 | `work.venue` | **Derived** — the first of `journal`, `booktitle`, `school` and `institution` the entry wrote, as `name`, with the `kind` that field and the entry type imply; a preprint's repository when the entry has only an `eprint`; `null` when it names no container (`sslabdata.parsers.bibtex.build_venue()`). See below. |
@@ -799,7 +815,7 @@ sslabdata's own output as input, and a wrong derivation becomes permanent.
 | `author.resolution` | **Derived** — `status` over `resolved`, `unresolved` and `ambiguous`, and `method` `exact`, or `null` when nothing matched (`resolve_authors()`). Both are open strings; `fuzzy` is never emitted. |
 | `author.equal_contribution` | **Derived** — whether the entry wrote a `*` marker on any part of the name (`sslabdata.parsers.bibtex.marks_equal_contribution()`). |
 | `work.editors[*]` | The same, minus `collaborator_key` and `equal_contribution`. An editor that matched nobody is simply `person_id: null` (`parse_editor_list()`). |
-| `person.*` except the two below | Input — the fields of `people_file` (`sslabdata.loaders.load_people()`). `aliases` is read for matching and is **not** emitted. `status` is `current` or `alumni`, and `current` when absent; `role` is open, any non-empty string (`PEOPLE-STATUS-INVALID`, `PEOPLE-ROLE-INVALID`). |
+| `person.*` except the two below | Input — the fields of `people_file` (`sslabdata.loaders.load_people()`). `aliases` is read for matching and is **not** emitted. `status` is `current` or `alumni`, and `current` when absent; `role` is open, any non-empty string (`PEOPLE-STATUS-INVALID`, `PEOPLE-ROLE-INVALID`). `bio` is a short biography in plain text with its line breaks as written (§2), and `null` when absent; it is carried and never read: nothing in the document is derived from it, and no `degree`, year or `current_position` is read out of one. |
 | `person.work_ids` | **Derived** — back-links over authorships (`sslabdata.resolver.compute_backlinks()`). Editors are not authorships and are not listed. |
 | `project.id`, `title`, `description`, `website`, `image`, `status` | Input — the fields of `projects_file` (`sslabdata.loaders.load_projects()`). `status` is one of `active` and `completed`, and `active` when absent (`PROJECTS-STATUS-INVALID`). `image` is a URL or a site path, the same kind of value as a person's `photo`, carried as plain text: deciding which URLs are safe to render is the renderer's job. |
 | `project.work_ids`, `people_ids` | **Derived** — back-links, and the people reached through them (`compute_backlinks()`). |
@@ -1114,13 +1130,14 @@ meaning and guarantees, and each of them is a bump.
 has been published is never edited. Version `N`'s schema stays reachable, byte
 for byte, at its own path after version `N+1` ships, so a consumer pinned to
 `N` keeps a stable target. `schema/v3/output.schema.json`,
-`schema/v4/output.schema.json` and `schema/v5/output.schema.json` are those
+`schema/v4/output.schema.json`, `schema/v5/output.schema.json`,
+`schema/v6/output.schema.json` and `schema/v7/output.schema.json` are those
 paths, and `tests/COVERAGE.md` row `output.versioned_schema` asserts that the
-older two are unchanged byte for byte and still say `3` and `4`.
+older four are unchanged byte for byte and still say `3`, `4`, `5` and `6`.
 
-**The `$id` is a pinned tag URL.** v5's `$id` is
-`https://raw.githubusercontent.com/siddhss5/sslabdata/schema-v5/schema/v5/output.schema.json`.
-The rule that makes it a contract rather than a guess: **the `schema-v5` tag
+**The `$id` is a pinned tag URL.** v7's `$id` is
+`https://raw.githubusercontent.com/siddhss5/sslabdata/schema-v7/schema/v7/output.schema.json`.
+The rule that makes it a contract rather than a guess: **the `schema-v7` tag
 is created when this version ships and is never moved.** A branch URL such as
 `blob/main` is not usable — it serves an HTML page rather than the schema, so
 no consumer can ever have resolved v3's `$id` — and this repository publishes
@@ -1135,11 +1152,11 @@ rule.
 descriptions inside those files, name the repository `labdata`, and the files
 are left byte for byte as published rather than rewritten. v4's raw `$id`
 resolves, because GitHub redirects `labdata` to `sslabdata`. v3's `blob/main`
-`$id` does not resolve, as above. v5's `$id`, title and descriptions say
-`sslabdata`.
+`$id` does not resolve, as above. The `$id`s, titles and descriptions of v5,
+v6 and v7 say `sslabdata`.
 
 **The input schemas are versioned apart from the document.**
-`schema/input/v1/` holds a JSON Schema for each input file: `lab.schema.json`,
+`schema/input/v2/` holds a JSON Schema for each input file: `lab.schema.json`,
 `people.schema.json`, `projects.schema.json` and `collaborators.schema.json`.
 They describe what the loaders accept; the loaders stay the authority, and
 the diagnostic codes above report what a schema cannot see. The input format
@@ -1147,9 +1164,13 @@ and the document change for different reasons, so the input schemas carry
 their own version rather than `schema_version`. They follow the same rules:
 a published input schema is never edited, any change to one is a new
 version at a new path, and its `$id` is a pinned tag URL,
-`https://raw.githubusercontent.com/siddhss5/sslabdata/input-schema-v1/schema/input/v1/<file>.schema.json`,
-whose `input-schema-v1` tag is created when this version ships and is never
-moved.
+`https://raw.githubusercontent.com/siddhss5/sslabdata/input-schema-v2/schema/input/v2/<file>.schema.json`,
+whose `input-schema-v2` tag is created when this version ships and is never
+moved. A version holds all four files, so a change to one of them versions
+the set: v2 adds a person's `bio` to `people.schema.json`, and its other three
+files differ from v1's only in the tag their `$id`s and descriptions name. `schema/input/v1/`, served
+from the `input-schema-v1` tag, stays byte for byte as published; the wheel
+installs only the current version.
 
 **Version history.** What each `schema_version` changed is in
 [`CHANGELOG.md`](CHANGELOG.md).
@@ -1243,12 +1264,30 @@ So each rejected type is rejected for a stated reason, and each has a home:
 | Teaching and courses | A prose page in your site repository, or the institution's course catalogue. |
 | Press and media coverage | A typed link on the work it covers: `links` is an open map from kind to links, so #27 adds the kind without a version bump. |
 | Galleries, photos and videos | Your site repository; a video already reaches the document as a link of kind `video`. |
-| Awards and honours | An attribute of the work, today `work.note`; #27 moves it out of `note`. |
+| Awards and honours | A paper's awards are an attribute of the work, `work.awards`, read from its `award` field (§5). An award a person holds, such as a fellowship or an endowed chair, belongs in your site repository. |
 | Funding and grants | Your site repository. Nothing in the document depends on it. |
 | Software and datasets | Not a separate collection — they are kinds of *work*, added by #31. |
 | Alumni | Not a collection — a `status` on a person (`sslabdata.models.Person.status`). |
 | Robots, platforms, facilities | Your site repository; one of 27 surveyed sites had such a page. |
 
+**An attribute of an entity the document already has is not an entity.**
+The evidence above, and the question #60 asks of a candidate — would
+sslabdata do anything with it beyond carrying it — decide which *entities*
+the document has: collections with records of their own, ids, references
+and an order, each of which the compiler has to check and a renderer has to
+understand. A field
+on a person, work or project raises none of that. Its owner is already
+admitted, the field has one value of one type, and the only work it asks
+for is what every input string gets: control characters removed, NFC and
+the text rule (§2). A person already carries attributes sslabdata does
+nothing else with — `photo`, `website`, `thesis_title`, `current_position` —
+and a person's `bio` is one more. Such a field is judged on two questions
+instead: does it belong to that entity rather than to a page of the site,
+and is it the only place the fact can live, so that it does not copy a
+structured field into text that will drift from it. A bio passes both; an
+alumni line such as "PhD 2012, now at Example Robotics" fails the second,
+because `degree`, `end_year` and `current_position` already hold it.
+
 **There is no generic extension mechanism and no `collections` escape hatch.**
 What one would carry is mostly prose, and its one real service — catching
 references that point at nothing — is delivered by #58 without the document
@@ -1260,7 +1299,7 @@ vocabularies, not over arbitrary content.
 
 ## 9. What this file is not
 
-It does not list the document's fields; `schema/v5/output.schema.json` does.
+It does not list the document's fields; `schema/v7/output.schema.json` does.
 It does not describe renderers such as
 [sslabdata-site](https://github.com/siddhss5/sslabdata-site), which are
 downstream consumers in their own repositories. It does not describe the input formats `lab.yaml`,

{sslabdata-3.1.0 → sslabdata-5.0.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "sslabdata"
-version = "3.1.0"
+version = "5.0.0"
 description = "Renderer-agnostic academic lab data assembler: BibTeX + YAML → structured data"
 readme = "README.md"
 requires-python = ">=3.10"
@@ -58,8 +58,8 @@ requires = ["setuptools>=77"]
 build-backend = "setuptools.build_meta"
 
 # The current output schema and input schemas are public wheel data, installed
-# at sslabdata/schema/v5/output.schema.json and
-# sslabdata/schema/input/v1/*.schema.json. The package directory is mapped onto
+# at sslabdata/schema/v7/output.schema.json and
+# sslabdata/schema/input/v2/*.schema.json. The package directory is mapped onto
 # the repository's schema/ directory so each frozen file has one copy and one
 # path; earlier versions stay in the sdist only. schema/__init__.py makes the
 # mapped directory a regular package, which editable installs need to resolve.
@@ -71,7 +71,7 @@ packages = ["sslabdata", "sslabdata.parsers", "sslabdata.schema"]
 "sslabdata.schema" = "schema"
 
 [tool.setuptools.package-data]
-"sslabdata.schema" = ["v5/output.schema.json", "input/v1/*.schema.json"]
+"sslabdata.schema" = ["v7/output.schema.json", "input/v2/*.schema.json"]
 # The starting point `sslabdata init` copies.
 "sslabdata" = ["templates/init/*.yaml", "templates/init/bib/*.bib"]
 

sslabdata-5.0.0/schema/input/v2/collaborators.schema.json

@@ -0,0 +1,24 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://raw.githubusercontent.com/siddhss5/sslabdata/input-schema-v2/schema/input/v2/collaborators.schema.json",
+  "title": "sslabdata collaborators file",
+  "description": "The file lab.yaml names as collaborators_file: co-authors outside the lab whose spellings are grouped together, one record each. A record never makes anyone a lab member. It describes what sslabdata's loader accepts; the loader stays the authority, and reports each problem under a code in SPEC.md, Diagnostic codes. A record key not listed here is reported as RECORD-KEY-UNKNOWN and ignored, so it is allowed. Published input schemas are immutable: this one is served from the input-schema-v2 tag, which is created when this version ships and is never moved (SPEC.md §6).",
+  "type": ["array", "null"],
+  "items": { "$ref": "#/$defs/collaborator" },
+  "$defs": {
+    "nonEmptyString": { "type": "string", "pattern": "\\S" },
+    "collaborator": {
+      "type": "object",
+      "required": ["name"],
+      "additionalProperties": true,
+      "properties": {
+        "name": { "$ref": "#/$defs/nonEmptyString" },
+        "aliases": {
+          "description": "Other spellings of the name, grouped with it.",
+          "type": ["array", "null"],
+          "items": { "$ref": "#/$defs/nonEmptyString" }
+        }
+      }
+    }
+  }
+}