From a4cf1f6feac22d430c0fb34c8abcdee4b0aefc0d Mon Sep 17 00:00:00 2001 From: Dan Birman Date: Thu, 28 May 2026 13:07:33 -0700 Subject: [PATCH] docs: platform metadata --- docs/source/policies_practices/platform_support.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/source/policies_practices/platform_support.md b/docs/source/policies_practices/platform_support.md index 81816d3..7a3eccd 100644 --- a/docs/source/policies_practices/platform_support.md +++ b/docs/source/policies_practices/platform_support.md @@ -15,6 +15,9 @@ All platforms and pipelines must follow the [Data organization conventions](data ## Platform requirements +- Platform data assets should include valid aind-data-schema core files (minimum: data_description, subject, procedures, instrument, and acquisition). +- The `data_description.tags` field must include a unique string that *will not ever change* for each platform. We recommend using `platform:` to make it easy to find this string. + ### Logging Platforms should log all events to the [Loki server](https://github.com/AllenNeuralDynamics/aind-log-utils) maintained by SIPE. Events should be discrete information, warnings, and errors that need to be made visible to users in a dashboard. Logging of continuous metrics should be done in a log service that is specific to each tool and made visible in a dashboard attached to the tool.