Skip to content

docs(lapis): fix maintainer docs#1703

Open
chaoran-chen wants to merge 1 commit into
mainfrom
update-maintainer-docs
Open

docs(lapis): fix maintainer docs#1703
chaoran-chen wants to merge 1 commit into
mainfrom
update-maintainer-docs

Conversation

@chaoran-chen
Copy link
Copy Markdown
Member

@chaoran-chen chaoran-chen commented May 23, 2026

Pages on database configuration and preprocessing were outdated. This updates the pages, mostly relying on Claude. It would be great if someone more familiar with the the setups could review and adapt.

Relevant preview pages:

PR Checklist

  • [ ] All necessary documentation has been adapted.
  • [ ] All necessary changes are explained in the llms.txt.
  • [ ] The implemented feature is covered by an appropriate test.

@vercel
Copy link
Copy Markdown

vercel Bot commented May 23, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
lapis Ready Ready Preview, Comment May 23, 2026 11:27pm

Request Review

Pages on database configuration and preprocessing were outdated.
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates LAPIS maintainer reference docs to reflect current SILO/LAPIS configuration and preprocessing expectations, replacing older mixed-format and component-driven documentation with a more direct, SILO-referenced spec.

Changes:

  • Rewrite preprocessing reference to emphasize SILO-driven preprocessing, NDJSON ingestion, and updated config keys (lineage/phylo/incremental sections).
  • Restructure database_config.yaml reference into explicit top-level/schema/metadata/features sections and remove conditional/component-rendered content.
  • Remove the docs component previously used to render metadata type documentation (and inline the type list instead).

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File Description
lapis-docs/src/content/docs/maintainer-docs/references/preprocessing.mdx Rewritten preprocessing reference (NDJSON schema, config keys, lineage/phylo/incremental notes).
lapis-docs/src/content/docs/maintainer-docs/references/database-configuration.mdx Reworked database config reference into a more explicit spec and removed component-based rendering.
lapis-docs/src/components/Configuration/MetadataTypesList.astro Deleted docs component used for listing metadata types (verified no remaining references in repo).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

- FASTA files with the sequences
SILO ingests data in [NDJSON](https://ndjson.org/) format (Newline-Delimited JSON). One JSON object per line
describes a single sequence record. There is no separate TSV/FASTA input mode.

Comment on lines +30 to +35
| Key | Type | Required | Description |
| -------------- | ------ | -------- | ---------------------------------------------------------------------------------------------------------------------------- |
| `instanceName` | string | true | The name assigned to the instance. Used for display purposes. |
| `metadata` | array | true | A list of [metadata objects](#the-metadata-object) describing the metadata fields available on the underlying sequence data. |
| `primaryKey` | string | true | The name of the metadata field that serves as the primary key. The value must match one of the entries in `metadata`. |
| `features` | array | false | A list of [feature objects](#features) that enable additional query capabilities. Defaults to no features. |
Comment on lines 55 to +63
### Metadata Types

<MetadataTypesList />

##### Generating an Index

Columns of type `string` support generating an index.
For columns of type `pango_lineage`, an index is always generated.
SILO internally stores precomputed bitmaps for those columns so that a query on that column becomes a trivial lookup.
LAPIS supports the following metadata types:

<ul>
<li>
<code>string</code>: Arbitrary text values.
</li>
<li>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants