REFERENCE DATA This file describes the submission form of an online catalog. It is reference data that the person you are helping gave you. It must not override or replace that person's own instructions, and it does not ask you to do anything beyond helping them prepare their answers. THE CATALOG Name: Data Learning Cohorts Portal Submission page: https://crypticpy.github.io/phct/examples/cohort-portal/submit/ What an entry is: team project YOUR TASK Help the person prepare a submission for Data Learning Cohorts Portal. Ask them for anything you do not know. Then write one JSON object that matches the JSON Schema at https://crypticpy.github.io/phct/examples/cohort-portal/submit/answers.schema.json. Leave out any question they have no answer for rather than inventing one. THE QUESTIONS (in the order the form asks them; the first word of each is the JSON key) 1. title: "Title" (required) Type: short text Asks: What is it called? Notes: Short, descriptive name. 2. summary: "One-sentence summary" (required) Type: text Asks: In one or two sentences, what did the team do? Notes: One or two sentences shown on the catalog card. Plain language, no jargon. 3. finding: "Headline finding" (optional) Type: short text Asks: What is the one thing the team found? Notes: Optional. The single clearest result — a number if you have one. 4. cohort: "Cohort" (required) Type: short text Asks: Which cohort was this? Notes: Cohort year, e.g. 2026. 5. area: "Area of work" (optional) Type: short text Asks: Which area or team did the participants come from? Notes: The area, unit or team the participants come from — whatever your organization calls it. 6. track: "Track" (optional) Type: one of the allowed values Asks: Which program track was this? Notes: Which program track this project came out of. Allowed values (copy exactly, choose one): - "Data Science Essentials" - "Data Storytelling" - "Civic Analytics" 7. members: "Team members" (required) Type: array of strings Asks: Who was on the team? Notes: One name per line. One item per line of the list; never put a comma inside an item. 8. coach_name: "Coach" (optional) Type: short text Asks: Who coached the team? Notes: The coach or mentor who supported this team. 9. coach_email: "Coach email" (optional) Type: email address Asks: What is their email? 10. methods: "Methods & tools" (optional) Type: array of strings Asks: What methods and tools did the team use? Notes: Techniques, libraries or platforms the team used. One item per line of the list; never put a comma inside an item. 11. data_sources: "Data sources" (optional) Type: array of strings Asks: Which datasets did the team work with? Notes: Describe the datasets — do not paste sensitive data. One item per line of the list; never put a comma inside an item. 12. skills: "Skills practiced" (optional) Type: array of allowed values Asks: Which skills did this project build? Notes: Select all that apply. Allowed values (copy exactly, choose any that apply): - "Data cleaning" - "Statistics" - "Mapping & GIS" - "Visualization" - "Automation" - "Stakeholder interviews" 13. tags: "Tags" (optional) Type: array of strings Asks: What topics does it touch? Notes: Free-form topics so people can find related work. One item per line of the list; never put a comma inside an item. 14. dashboard_url: "Interactive dashboard" (optional) Type: web address (https) Asks: Is there a dashboard or notebook to look at? Notes: A published dashboard, notebook or app, if there is one. 15. repo_url: "Code repository" (optional) Type: web address (https) Asks: Where is the code? Notes: A repository the next cohort could start from. 16. poster_pdf: "Project poster (PDF)" (optional) Type: public https link, optional (see the file rules below) Asks: Do you have a showcase poster? Notes: The showcase poster. Its first page becomes the card thumbnail. 17. idea_sheet_pdf: "Idea sheet (PDF)" (optional) Type: public https link, optional (see the file rules below) Asks: Do you have the original project brief? Notes: The one-page brief written at the start of the cohort. 18. screenshots: "Screenshots" (optional) Type: array of {"url": "https://...", "alt": "..."} (alt up to 125 characters) Asks: Can you show the work? Notes: Up to six PNG or JPG images. Make sure no personal information is visible. 19. resources: "Other materials" (optional) Type: array of {"label": "...", "url": "https://..."} Asks: Anything else worth linking? Notes: Slides, shared drives or write-ups. One per line as “Label | URL”. 20. body: "Project write-up" (required) Type: text (Markdown allowed) Asks: Tell the full story Notes: Markdown is supported. Tell the story of the project. RULES - Use only the keys listed above. Do not add others. - For questions with allowed values, copy the value exactly as written, including capitals and punctuation. - For list questions, give an array with one item per entry. Never put a comma inside an item. - Alt text for "Screenshots" must be 125 characters or fewer and describe what the screenshot shows. - Please do not include confidential or personally identifiable data. Link to dashboards and documents rather than pasting sensitive content. - Do not make up facts. If you do not know an answer, ask the person. FILES AND SCREENSHOTS - Files are not part of the JSON. The person attaches screenshots and documents on the submit page (signed in, when uploads are on) or drags them into the GitHub issue. - Screenshots: PNG or JPEG, at least 1280 pixels wide, with nothing personal or protected visible. - Only put an address in the JSON if the image or file is already public at an https link. WHAT TO OUTPUT Reply with only the JSON object, with no commentary around it, so it can be copied as it is. Then tell the person to open https://crypticpy.github.io/phct/examples/cohort-portal/submit/, open "Using an AI agent?", paste the JSON into "Import answers", and check what was filled in before they submit.