{% extends "base.html" %} {% block content %} {% set box = "border:1px solid var(--border, #ddd); border-radius:6px; padding:0.9rem 1rem; margin:1rem 0;" %}
Publish to a SEEK instance in two stages: set up its data model from a profile, then push a dataset into that model. Both talk to SEEK over its API, using the URL and key from the Plugins page. You can also export a file and import it through SEEK yourself.
{% if action_error %}Choose a profile. Set up Sample Types creates it in SEEK as Sample Types, with a Controlled Vocabulary for each field that has a fixed list of allowed values. Safe to run again — it reuses whatever already exists. To sync a dataset later, set up the profile it was built on.
{# Repopulate the version list, and keep the Extended Metadata form's hidden profile/version in step, when the profile choice changes. #} {# Browsable projection of the selected profile: what Sample Types and Extended Metadata provisioning will create, before any upload. #}Then, as a SEEK admin: Server administration → Extended Metadata Types → New, pick the FAIR DS TTL tab, upload the file, and confirm on the preview.
Sends the dataset {{ dataset_name or "(unsaved)" }} (built on {{ profile }}) — {% for etype, n in entity_counts %}{{ etype }} ×{{ n }}{% if not loop.last %}, {% endif %}{% endfor %} — into SEEK as Investigations, Studies, Assays and Samples, matched to the Sample Types set up in step 1.
{% else %}No dataset is loaded. Step 1 needs only a profile, but this step acts on an open dataset — load or build one first.
{% endif %}Download the dataset as FAIR Data Station RDF and import it through SEEK's own Import from FAIR Data Station, which handles the full ISA structure and Extended Metadata in one step. No API key needed.
{% if exportable_count %} Download SEEK ISA RDF (.ttl) → {% else %} {% endif %} {% if seek_url %} · your instance: {% if seek_url.startswith(("http://", "https://")) %}{{ seek_url }}{% else %}{{ seek_url }}{% endif %}
{% endif %}
Note: SEEK places entities by where they sit in the ISA hierarchy, not by their name. With the ISA profile (which has no ObservationUnit level) entities below Study import one level high; Investigation and Study round-trip cleanly.