Native TMS and EmbARK formats aren't consumed directly. Convert the export to CSV or JSON in your existing tooling — TMS has a built-in export, EmbARK supports XML export that you can transform with XSLT or a Python script. SleekRank consumes the flat file via csv_file or json_file. Most museums already run a periodic export for analytics or vendor integrations, so the pipeline often exists; SleekRank becomes another consumer of the same flat file.

Store image URLs in columns and map them via selector mappings for on-page rendering and meta mappings for og:image. Hosting and rights enforcement stay in your DAM — Piction, NetX, or a custom asset server. SleekRank only references the URL, so rights restrictions, watermarking, and access controls remain in the DAM where they belong. For zoomable image experiences, embed a IIIF viewer on the base page and pass the manifest URL via selector.

Use language-specific columns or page groups per language. A bilingual museum typically runs /collection/en/{slug}/ and /collection/fr/{slug}/ as separate page groups, each with its own base template and URL prefix. The same export can drive both groups if it includes language-specific label and description columns; the page-group config filters by language code or pulls the relevant column per group.

Two clean approaches. Drop the row entirely and the page returns 404 on next regeneration — appropriate for objects that should leave the public record. Or flag the row as deaccessioned and render a notice in the template explaining the disposition, which preserves URL backlinks from scholarly citations and Wikipedia. Most museums pick the second approach for objects with significant scholarly engagement and the first for routine deaccessions.

No. The database — TMS, EmbARK, Mimsy XG, or custom — stays the system of record for cataloging, accessioning, location tracking, condition reports, and conservation history. SleekRank only publishes pages from its export, acting as the public publishing layer. Curatorial staff continue working in the registrar's tools, and the open-web presence updates from the same source whenever a new export runs.

Each object URL is a real WordPress page in the sitemap. The base template stays noindex'd so only object pages compete in search. This means /collection/2014-1182-quiet-currents/ ranks for the artist's name, the work's title, and combinations like 'Holloway 2014 oil canvas Quiet Currents' — exactly the queries researchers and curious visitors use, and exactly the ones that previously routed to commercial sites instead of the institution.

Add a 'sensitivity' or 'context_required' column and use it in the template to render contextual statements, content warnings, or community-collaborated language. Some institutions also gate certain views — Indigenous restricted material, for example — behind a click-to-acknowledge layer driven by a column flag. The same export drives consistent treatment across the catalog rather than ad-hoc decisions per object page.

Yes. Add columns for Wikidata Q-IDs, ULAN identifiers, JSTOR links, or institutional bibliography URLs. Map them via selector mappings to render outbound links in a 'further research' section of the template. Wikidata in particular acts as a hub for cross-institutional linking, so surfacing the Q-ID and a link makes the object pages discoverable through the broader linked-open-data ecosystem that scholarly databases increasingly use.