How a hub's datasets are cited and described: BibTeX, RIS, APA, text and CSL-JSON, DataCite JSON, JSON-LD, Turtle and RDF/XML from one record with real dates and version relations, the signposting of the landing, cached QR codes with ETags, the canonical identity of a dataset and its concept DOI, the hub's own Cite us as data, and a sitemap of the landings
The review queue of a hub (GV-2): the datasets a curated policy sends to review before they are published, and the withdrawals their owners ask for, approved or rejected with a note the owner is mailed; and the rule of which accounts publish without review
Datasets: metadata, authors, versions, DOI landing pages (with FAIR metadata), BibTeX, QR and downloads. Their files come from hubfile, stacked on top
REST API v1 and v2 of the datasets and their files, out of dataset: fine token scopes, public reads of what is published, tokens limited to some datasets, versioned schemas and the audit trail of every write; v2 with public ids, cursor pages, problem+json, ETags and publication as a resource
Offers of a dataset and its versions to another account (DL-17): an inbox in the account area, a mail with a signed link, one answer whether or not the account exists, offers that lapse, locked answers, one live offer per lineage and a daily limit per account
The page of a hub's search: /explore, /api/v1/search with its declared schema and the header search box, over the public sources the features register in the framework's search registry (a hub's datasets and files, their facets and orders), which the search feature browses with Elasticsearch or in memory. It names no kind of material, so another hub explores its own.
Like and dislike votes on published datasets, counted per version lineage
Hub statistics derived from the records: the /statistics dashboard and the home card, with datasets counted by lineage and by version, distinct authors, a deduplicated registry of use (a visitor a day, no cookies, robots, owners and drafts left out) that holds the daily history carried over from uvlhub 2.12 with its public note, slots the features fill with KPIs, tables, sections and exports, and the CSV/JSON exports at uvlhub 2.12's addresses
Zenodo as a publication provider of dataset: deposits a hub's datasets and gets their DOIs (the sandbox outside production)