PyGraphistry Connectors

Doc routing (local + canonical)

• First route with ../pygraphistry/references/pygraphistry-readthedocs-toc.md.
• Use ../pygraphistry/references/pygraphistry-readthedocs-top-level.tsv for section-level shortcuts.
• Only scan ../pygraphistry/references/pygraphistry-readthedocs-sitemap.xml when a needed page is missing.
• Use one batched discovery read before deep-page reads; avoid cat * and serial micro-reads.
• In user-facing answers, prefer canonical https://pygraphistry.readthedocs.io/en/latest/... links.

Strategy

• Prefer dataframe-first ingestion when practical, then bind with edges()/nodes().
• Use connector-specific notebook patterns when auth/query semantics are specialized.
• For very large datasets, push filtering/aggregation upstream before plotting.
• Keep connector and Graphistry credentials in env vars or secret stores; no hardcoded keys.
• Never use placeholder literals like username='user' / password='pass' / username='...'; use os.environ[...] or os.environ.get(...).
• For concise tasks, respond with a single compact code block and minimal prose.
• In concise snippets, prefer explicit privacy literals ('private' or 'organization') over placeholder variables.

Connector triage rubric