About the organisation page with ordered rich-text sections and admin CRUD
An affiliation on every profile, asked for on the edit page and sent with the profile's JSON
Sign-ups file a request that an administrator approves or rejects
Developer API tokens: mint, verify, revoke, a registry where features declare the scopes they check, and a token decorator for the product's own API
An append-only audit trail: who did what, to what, from where and when, written by any feature through the framework's record_event, with an administrators' screen and retention
Accounts, login, logout, sessions and one password policy for every form that sets a password
Job applications with stored candidates (public form + admin inbox)
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
Visitor comments on posts with moderation (public form + admin approval)
Proves an address belongs to its account: a one-time link opening a page with a button that confirms it, never signing in or switching an account on, a page that mails a new link, the link that moves an account to a new address, and the link an account carried over from an older site is mailed at its first sign-in
Contact form with stored messages (public form + admin inbox)
courses feature
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
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
WordPress-style editorial roles scoped to a single edition (editor/author/contributor), refining events with an author and gating the events/editions admin
Editions of a recurring event (archive, current edition, programme by day), refining events
Events (talks, workshops, competitions and ceremonies) with public list/detail and admin CRUD
FM Fact Label of every UVL model: computed in the background, shown in the file workbench, materialised as typed metrics, the number of features explore narrows by, and the characterisation of the corpus and its export in statistics' dashboard
Sign in and sign up with GitHub, and connect a GitHub account to an account from its profile
The files of a dataset, of any type a hub takes: their registry of file types, storage by key, upload staging, view, raw and download, and the file workbench of the dataset page
Sign-in provider accounts (ORCID, GitHub…) linked to users, and the one OAuth flow every provider registers on (register_oauth_provider): sign-in, connect, and new accounts through /account/complete-signup, a typed address opening one only through a mailed link. With the identities page, disconnecting, the rule that keeps a product without signup closed, and an optional hint on the login page
What a booking runs on its machine while it is on: the model behind an OpenAI API with a key per booking, a chat, and a JupyterLab in the browser, through a gateway in front of the portal
A folder with a quota on the lab's shared storage for every approved account, created over SSH by the storage server's helper, with a page for each person and one for administrators
Permanent redirects (301, 308) and gone answers (410) for the addresses a hub used to answer, imported from rows of path, target, status and ref, answered where the hub would answer 404, with an administrators' list
Versioned legal documents (privacy notice, terms, cookies) with their history, acceptance at sign-up, the third parties and cookies the features declare, footer links and a panel
Transactional email delivery via SMTP (MailService for other features)
Media library to upload and manage files (the WordPress Media Library analogue)
What each machine is doing, live: an agent per machine posts its CPU, memory, GPU and processes; signed-in people see them next to what is booked
Sign in and sign up with ORCID, connect an ORCID iD to an account from its profile, and tell other features which iDs are linked here (OrcidService)
Partner logos and links (home section + admin CRUD)
Blog posts with categories (public list/detail + admin CRUD)
The name and surname of every account, with an edit page and a JSON endpoint that other features extend with fields, sections and keys
Funded research projects, active and past, with public list/detail grouped by status and admin CRUD
Like and dislike votes on published datasets, counted per version lineage
Research projects extending projects with academic metadata
Book the lab's machines by the hour: a week calendar, bookings confirmed at once or, if configured, an approval queue
Password reset feature: forgot password and token-based reset flow
Key-value site settings storage used by theme and admin
Hero image slider for the home page (layout.hero hook + admin CRUD)
Registry of software product lines and listed feature repositories, and the relay that publishes UVL models to UVLHub
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
Native questionnaires: a form builder (scale/text/choice questions), a public /survey/<slug> form, stored responses and admin aggregation
People directory grouped by role (faculty, organisers, speakers, or organisations with a description, a logo and a website) with public list/detail and admin CRUD
Research and SPL tools with a public list grouped by status, detail pages and admin CRUD
The UVL artifact type of a hub: the UVL model as a file type (its mandatory check, its feature model, its Glencoe, DIMACS and SPLOT formats), its viewer and LaTeX export, the import by URL and the bridge with flamapyIDE