Publishing and Appearance
Visibility
Setting a site (database) to public makes it appear in:
- the "Published sites" directory on the platform top page (archivebase.ldas.jp)
- its own URL
/{account}/dl/{database}(it returns 404 while private)
Items flagged private stay hidden from listings, search and the API even on a public site (see Items and Collections).
Standard site pages
Every library automatically gets a top page plus listing/search pages per resource type. A page whose type has zero resources is hidden from the nav (data-driven).
| URL | Contents |
|---|---|
/{account}/dl/{db} | Top (per-type counts and links to each search) |
…/items | Item search |
…/collections | Collection listing |
…/pages | Image (facsimile) listing |
…/annotations | Annotations (tag / motivation facets) |
…/map | Map of georeferenced resources |
…/fulltext | Per-page OCR full-text search (supported backends only) |
…/visual | Visual search (supported backends only) |
…/assoc | Associative search (indexed libraries only) |
The site card (how your site looks on the top page)
In the "Published sites" directory each site appears as a card with a thumbnail and description. Set it under the dashboard's site detail → "Site card" (image, description, English description).
When unset it falls back automatically: the image uses the hero image → the newest item's thumbnail; the description uses the footer description → a summary of the site description. The description can be set separately for Japanese and English.
Custom domains
A public site can be served under its own host name such as xxxx.ldas.jp (the same idea as a Vercel custom domain). Once assigned, the contents of archivebase.ldas.jp/{account}/dl/{database} appear as the top page of that host name (the address bar keeps the custom host — it is resolved to the tenant internally).
- Configure it under the dashboard's site detail → "Custom domain". Enter the label you want (e.g.
haga) and click "Add" to assignhaga.ldas.jp. - DNS and the TLS certificate are automatic (Cloudflare); an addition takes effect within seconds.
- The site must be public (assigning a domain to a private site still returns 404) — publish it first.
- Reserved labels such as
archivebaseandwwwcannot be used. A site can have more than one domain.
Canonical URL
Pages served under a custom domain emit a canonical / OG URL pointing at that domain (https://haga.ldas.jp/).
The top-page hero
A site with a hero configured shows a full-bleed top page (background image + gradient + buttons) and a "featured" thumbnail grid (otherwise a simple header). Set the background image and subtitle in the dashboard's site detail.
Detail-page viewer
The display of an item's detail page (/{account}/dl/{db}/item/{id}) can be chosen per site (dashboard site detail → "Detail-page viewer").
- simple (default) — metadata table + thumbnail
- osd — an OpenSeadragon viewer layout; child resources' images are shown as views with a view-list tab on the right. Falls back to simple when there is no image
- av — an audio/video player (Clover IIIF), supporting IIIF manifests and WebVTT captions
Materials that carry a IIIF manifest show a "View in VR gallery" link by default (can be disabled per site). An item with a 3D model (metadata.model3d) is shown in a 3D viewer regardless of the site's viewer setting.
Other display settings
The dashboard's site detail also lets you configure:
- Search facets — per type, the metadata keys and labels used for filtering (Postgres-backed sites)
- Menu visibility — hide individual header tabs (items / collections / pages / map, etc.)
- Gallery view — enable a gallery page that pairs parent materials with cropped regions
Footer and static pages
- The footer (site description, related links, copyright) currently has no dashboard editor and is set via an API key (
PATCH /api/{account}/databases/{db}, thefooterfield) - Static pages — "About this database" and similar are surfaced via the page (About) feature
Work in progress
Screenshots, how to enter bilingual text, the conditions under which each backend (full-text / visual / associative search) becomes available, and a dashboard editor for the footer are yet to be documented.