Spaces:
Sleeping
Sleeping
|
Download case_study_pipeline/context/note_taking_guidelines.md from UWRFR/UWaterlooRFRChatBot: direct link, hf CLI and curl.
- Browser
- Download file 3.49 kB
-
https://huggingface.co/spaces/UWRFR/UWaterlooRFRChatBot/resolve/main/case_study_pipeline/context/note_taking_guidelines.md
- Command line
-
hf download hf://spaces/UWRFR/UWaterlooRFRChatBot/case_study_pipeline/context/note_taking_guidelines.md
-
curl -L -o note_taking_guidelines.md https://huggingface.co/spaces/UWRFR/UWaterlooRFRChatBot/resolve/main/case_study_pipeline/context/note_taking_guidelines.md
3.49 kB
| # Note-Taking Guidelines for Case Studies β LLMs | |
| ## Overview of the Note-Taking Document | |
| The case study note-taking document is used to register findings for each analytical category, supported by evidence from the literature. It includes predefined categories and potential types of responses (codes). The note-taking document is accompanied by a codebook, explaining each code, and by selected papers on the case study. | |
| ## 1. Extracting and Recording Case Study Information | |
| 1. Before beginning the reading process, make sure you are fully familiar with all categories and codes in the note-taking document. This will help you recognize relevant information more efficiently and optimize your note-taking workflow. Use the codebook any time for further clarification. | |
| 2. **Types of Notes** β when registering information, each entry falls into one of three classifications: | |
| **a) Factual Notes** β objective, descriptive pieces of information that report concrete characteristics of the case (e.g., name of the case study, total funding amount, hazard(s) considered). Factual notes should reflect verifiable data without interpretation. | |
| **b) Supporting Argument (Argument in Favour)** β notes indicating that a certain characteristic was present in the project's decision-making process or governance arrangements. Used when the source provides evidence supporting the presence, adoption, or positive implementation of a category (e.g., "the project incorporated long-term climate projections"; "the intervention followed a multi-stage retreat implementation"; "there were livelihood restoration initiatives in the project"). Supporting arguments must be evidence-based and cite the source directly. | |
| **c) Contradictory Argument (Argument Against)** β notes indicating criticism, absence, or insufficient incorporation of a characteristic in the project's decision-making process. Used when the literature explicitly highlights gaps, shortcomings, or failures related to a given category (e.g., "the project lacked integrated planning across agencies"; "local knowledge or community capacity was not considered, or participation was minimal"). Contradictory arguments help identify limitations, oversights, or contextual barriers relevant to the case. | |
| 3. For each piece of information entered: | |
| - Record the exact source for each note. Use the author-date system or identify the source by numbers: [1]. | |
| - If quoting directly, use quotation marks and include the page number. | |
| 4. Extract information from all sources jointly rather than coding papers individually. | |
| ## 2. Referencing Procedure | |
| 1. Add every source cited to the end of the document. | |
| 2. All references must follow IEEE style. | |
| 3. Ensure that: | |
| - Each reference is listed only once. | |
| - Sources cited in the note-taking part correspond exactly to the bibliography. | |
| - DOIs or URLs are included when available. | |
| ## Note-Taking Best Practices | |
| - Be concise but detailed: capture key information while avoiding unnecessary narrative. | |
| - Separate facts from interpretation: mark direct quotes or data; differentiate parts where information was summarized. | |
| - Highlight gaps: if information is missing or unclear, flag it for later follow-up. | |
| - Follow a uniform citation style. | |
| - Acknowledge limitations and uncertainties in the data. | |
| - Avoid assumptions not supported by evidence. | |
| ## Quality Assurance | |
| - Re-read notes for accuracy and coherence. | |
| - Cross-check information across multiple sources. | |