@finbheara/archive-client 0.29.0 → 0.31.0

package/README.md

@@ -210,6 +210,14 @@ s.next;       // the next scheduled instance where the release knows one, else n
 A series is asked by any id of it (a feis, instance or brand id, a retired one followed), by a
 host code with or without its year (held codes `<stem><yy>` whose two digits are their own year,
 never a host id of digits alone, which is a sequence number), or by a name (a glob, or a plain word read as `*word*`). Two series answer `ambiguous` with both.
+A MAJORS EVENT IS NO FEIS SERIES. A code of the release's roster (`NAIDC`, either case) is never
+read as a name, so it never answers a feis whose name happens to print its letters. It answers the
+series the release files that event's platform captures under (the code in lowercase, its
+instances the code and a four-digit year, `via: "majors"`), or `none` with `why` naming the event,
+and `s.major` is its roster row (`{ code, tier, name }`). `rel.comps.place` reads it the same way: the captures of the asked event-year, held, or
+no feis with `why`. The roster is the manifest's `roster`; a release written before it carries one
+reads the codes its rows show are majors (a `T1` to `T3` event, a series filed under event-year
+instances), and a code those rows never name is not known there (`rosterOf(rel)`).
 `next` is the series' earliest occurrence of the feis-index dated on or after the cut's day
 (`rel.upcoming.feises`, state `upcoming`), under its brand id or one retired onto it: `{ feis_id,
 date, date_hi, occurrence_id, name_printed, hosts, captured_id, series_basis }`, `feis_id` the
@@ -777,7 +785,11 @@ codes, a plausible answer and a wrong one. So an unheld feis-year there answers
 over the newest earlier syllabus, and a code with no title is `none`, saying why. The code of a
 held feis-year is still read from that feis-year's own competitions.
 
-A feis the release holds names itself, its year and its series. A series instance or brand id
+A feis the release holds names itself, its year and its series. A platform feis id
+(`<token>:<host>`) the release holds competitions of and no `feises` line names (a source that
+carried a feis's results and not the feis itself) is held too, on its own id and its competitions'
+year (`via: "id"`, as a feis with its line is), its series the one its host code reaches if
+exactly one brand matches the stem, else null. A majors or championship event id is never held so: a roster code places only the platform captures filed under its event-year (`via: "majors"`), else nothing, saying why. A series instance or brand id
 names the series. A feis id the release does not hold is placed in a series by its host code
 (`<token>:<stem><yy>` where the held codes of that stem carry their own year), and a stem two
 series share answers `ambiguous`. A host id of digits alone (`qf:926`, `fw:1001`) is a sequence