Your shared citations Sheet has 80 rows added by three co-authors over the last six months. Your draft paper is in Google Docs. In your current workflow, how do you check what's in the Sheet before the lit-review meeting?
I open the browser, find the Sheet, scan the rows. Which takes ten minutes because I also check the Docs draft for context. Two separate tabs, no connection between them.
This week you read both from Python. A Sheets row is a list of strings — the same data structure you used in Week 2 of the Python track. Appending a citation row is the same append operation. And a Docs document comes back as a dict with a body field you can parse. The data structures are familiar; only the action names change.
Can I read the actual text content of a Docs draft, not just the metadata?
Yes — GOOGLEDOCS_GET_DOCUMENT_BY_ID returns the document dict including the body content. Extracting clean text from the Docs JSON requires a bit of parsing, but the full content is there. By Friday you can read your citation Sheet, append a new row, and read your draft paper — all from the same Python function.
read_range: read a named range from the citations Sheetappend_row: append a new citation row to the Sheetsearch_sheets: find the right Sheet by titleread_doc: read a shared Docs draft by document IDcreate_doc: create a new literature-summary documentGoal: by Friday you can read the citation log, append to it, and read the draft paper — the data-collection layer of the literature-search pipeline.
Create a free account to get started. Paid plans unlock all tracks.
Your shared citations Sheet has 80 rows added by three co-authors over the last six months. Your draft paper is in Google Docs. In your current workflow, how do you check what's in the Sheet before the lit-review meeting?
I open the browser, find the Sheet, scan the rows. Which takes ten minutes because I also check the Docs draft for context. Two separate tabs, no connection between them.
This week you read both from Python. A Sheets row is a list of strings — the same data structure you used in Week 2 of the Python track. Appending a citation row is the same append operation. And a Docs document comes back as a dict with a body field you can parse. The data structures are familiar; only the action names change.
Can I read the actual text content of a Docs draft, not just the metadata?
Yes — GOOGLEDOCS_GET_DOCUMENT_BY_ID returns the document dict including the body content. Extracting clean text from the Docs JSON requires a bit of parsing, but the full content is there. By Friday you can read your citation Sheet, append a new row, and read your draft paper — all from the same Python function.
read_range: read a named range from the citations Sheetappend_row: append a new citation row to the Sheetsearch_sheets: find the right Sheet by titleread_doc: read a shared Docs draft by document IDcreate_doc: create a new literature-summary documentGoal: by Friday you can read the citation log, append to it, and read the draft paper — the data-collection layer of the literature-search pipeline.