[andrewelamb]

Problem:

• The functions in synapseclient/extensions/curator/schema_registry.py find JSON schema URIs by a SQL query on a schema registry table (syn69735275). The public functions are:
  • query_schema_registry
  • get_latest_schema_uri
• The Organization and JSONSchema models in synapseclient.models now let users find JSON schemas and their versions directly through the Synapse JSON schema API. Users do not need to keep a separate registry table up to date.
• We must tell users to move to the new APIs before we remove the registry functions.

Solution:

• Added the @deprecated decorator (from the deprecated package, as in models/organization.py) to query_schema_registry and get_latest_schema_uri:
  • version="4.15.0"
  • Reason: "To be removed in 5.0.0. Use the Organization and JSONSchema models from synapseclient.models to find JSON schemas instead."
• Added a deprecation note to each docstring. The note links to Organization and JSONSchema, and has an example that uses Organization.get_json_schemas() and JSONSchema.get_versions().
• The function behavior does not change. Callers only get a DeprecationWarning.
• Notes:
  • SchemaRegistryColumnConfig is not deprecated, because it is a dataclass, not a function. It is used only by the deprecated functions.
  • get_latest_schema_uri calls query_schema_registry, so one call shows two deprecation warnings.
  • docs/guides/extensions/curator/metadata_curation.md and synapseclient/extensions/curator/readme.md still show query_schema_registry. We can update them in a different PR.

[thomasyu888]

We should still make sure the function works even if it's plan is to be deprecated: https://sagebionetworks.slack.com/archives/C02M7QR8D46/p1791230490708289?thread_ts=1791225742.847109&cid=C02M7QR8D46

Perhaps it's a python 3.14 thing for our users but it would be good to diagnose.

[andrewelamb]

@thomasyu888 There's a separate issue for doing the actual fix: https://sagebionetworks.jira.com/browse/SYNPY-1931

[thomasyu888]

🔥 LGTM!