Skip to content

Conversation

@andrewelamb
Copy link
Contributor

@andrewelamb andrewelamb commented Feb 3, 2026

Problem:

There was some confusion on when to use the Pattern column vs the Format column in the Curator CSV data model.

Solution:

Added some notes to show when to use which.

https://synapsepythonclient--1314.org.readthedocs.build/en/1314/explanations/curator_data_model/

@andrewelamb andrewelamb requested a review from a team as a code owner February 3, 2026 18:15
@andrewelamb andrewelamb requested review from a team and removed request for a team February 3, 2026 18:15

The format of this attribute. See [format](https://json-schema.org/understanding-json-schema/reference/type#format) The type of this attribute must be "string" or "string_list". The value of this column will appear as the `format` of this attribute in the JSON Schema. Must be one of:

Note: If you want your data to MATCH a regex use the `Pattern` column. If you want your data to BE a regex pattern use this column, with the the `regex` value.
Copy link
Contributor

Choose a reason for hiding this comment

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

I think this block should not followed "Must be one of:"

Image

Copy link
Contributor

Choose a reason for hiding this comment

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

How about something like this:

Note: The Format and Pattern columns serve different purposes:

Pattern: Use to validate that data matches a specific regex pattern (e.g., enforce that email addresses follow a certain format)

Format: Use with the regex value to indicate that the data itself is a regex pattern being stored (not validated against one)

Available format values:

date-time
email
hostname
xxx

Choose a reason for hiding this comment

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

@andrewelamb LGTM, thanks!

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.

3 participants