- 
                Notifications
    
You must be signed in to change notification settings  - Fork 1
 
Update not-connected.md #6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
          
WalkthroughThe markdown document was restructured to replace bullet points and collapsible sections with a comprehensive HTML table mapping SSEN datasets to user needs. Explanatory text was removed, and the new format directly presents datasets, use cases, and links in a simplified and visually organized manner. No code or API changes occurred. Changes
 Poem
 Tip ⚡️ Faster reviews with caching
 Enjoy the performance boost—your workflow just got faster. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit: 
 SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
 Other keywords and placeholders
 CodeRabbit Configuration File (
 | 
    
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 2
🧹 Nitpick comments (2)
usecases/not-connected.md (2)
10-12: Remove<body>tags from Markdown
The<body>element isn’t valid in a Markdown document and may be stripped or ignored by many renderers. Enclose only the table in the file without wrapping it in<body>/</body>.Apply this diff:
- <body> ... - </body>Also applies to: 123-124
12-121: Consider using Markdown table syntax for maintainability
A pure Markdown table improves readability in source form, avoids inline styles, and ensures consistent rendering across platforms. You can use Unicode checkmarks (✔) instead of HTML entities.
| <table style="width:100%"> | ||
| <tr> | ||
| <th>Dataset</th> | ||
| <th>Understand Connected Resources</th> | ||
| <th>Understand Network Requirements</th> | ||
| <th>Anticipate Future Network Demand</th> | ||
| <th>Review Network Development Plans</th> | ||
| <th>Identify Opportunities to Engage with SSE</th> | ||
| <th>Understand Ability to Connect</th> | ||
| </tr> | ||
| <tr> | ||
| <td><a href="https://data.ssen.co.uk/@ssen-distribution/shepd_network_development_report">SHEPD</a> & <a href="https://data.ssen.co.uk/@ssen-distribution/sepd_network_development_report">SEPD</a> Network Development Report</td> | ||
| <td> </td> | ||
| <td> </td> | ||
| <td> </td> | ||
| <td> </td> | ||
| <td>✔</td> | ||
| <td> </td> | ||
| </tr> | ||
| <tr> | ||
| <td><a href="https://data.ssen.co.uk/@ssen-distribution/shepd_long_term_development_statement">SHEPD</a> & <a href="https://data.ssen.co.uk/@ssen-distribution/sepd_long_term_development_statement">SEPD</a> Long Term Development Statement</td> | ||
| <td> </td> | ||
| <td> </td> | ||
| <td> </td> | ||
| <td>✔</td> | ||
| <td>✔</td> | ||
| <td> </td> | ||
| </tr> | ||
| <tr> | ||
| <td><a href="https://data.ssen.co.uk/@ssen-distribution/embedded_capacity_register">Embedded Capacity Register</a></td> | ||
| <td>✔</td> | ||
| <td>✔</td> | ||
| <td> </td> | ||
| <td> </td> | ||
| <td> </td> | ||
| <td> </td> | ||
| </tr> | ||
| <tr> | ||
| <td><a href="https://data.ssen.co.uk/@ssen-distribution/ssen_smart_meter_prod_lv_feeder">Smart Meter LV Feeder Usage</a></td> | ||
| <td>✔</td> | ||
| <td> </td> | ||
| <td> </td> | ||
| <td> </td> | ||
| <td> </td> | ||
| <td> </td> | ||
| </tr> | ||
| <tr> | ||
| <td><a href="https://data.ssen.co.uk/@ssen-distribution/ssen-substation-data">SSEN Substation Data</a></td> | ||
| <td>✔</td> | ||
| <td> </td> | ||
| <td> </td> | ||
| <td> </td> | ||
| <td> </td> | ||
| <td> </td> | ||
| </tr> | ||
| <tr> | ||
| <td><a href="https://data.ssen.co.uk/@ssen-distribution/nerda_opengrid_dashboard">NeRDA Opengrid Dashboard</a></td> | ||
| <td>✔</td> | ||
| <td> </td> | ||
| <td>✔</td> | ||
| <td> </td> | ||
| <td> </td> | ||
| <td> </td> | ||
| </tr> | ||
| <tr> | ||
| <td><a href="https://data.ssen.co.uk/@ssen-distribution/realtime_outage_dataset">Real Time Outage</a> & <a href="https://data.ssen.co.uk/@ssen-distribution/nafirs">NaFIRS Yearly Export</a></td> | ||
| <td> </td> | ||
| <td> </td> | ||
| <td> </td> | ||
| <td> </td> | ||
| <td> </td> | ||
| <td>✔</td> | ||
| </tr> | ||
| <tr> | ||
| <td><a href="https://data.ssen.co.uk/@ssen-distribution/generation-availability-and-network-capacity">Generation availability & Network Capacity</a></td> | ||
| <td> </td> | ||
| <td> </td> | ||
| <td> </td> | ||
| <td> </td> | ||
| <td> </td> | ||
| <td>✔</td> | ||
| </tr> | ||
| <tr> | ||
| <td><a href="https://data.ssen.co.uk/@ssen-distribution/orkney_active_network_management">Orkney</a> & <a href="https://data.ssen.co.uk/@ssen-distribution/isle_of_wight_active_network_management"<Isle of Wight Active Network Management</a></td> | ||
| <td> </td> | ||
| <td> </td> | ||
| <td> </td> | ||
| <td> </td> | ||
| <td>✔</td> | ||
| <td>✔</td> | ||
| </tr> | ||
| <tr> | ||
| <td><a href="https://data.ssen.co.uk/@ssen-distribution/low_carbon_technologies">Distributed Future Energy Scenarios</a></td> | ||
| <td> </td> | ||
| <td> </td> | ||
| <td>✔</td> | ||
| <td> </td> | ||
| <td> </td> | ||
| <td> </td> | ||
| </tr> | ||
| <tr> | ||
| <td><a href="https://data.ssen.co.uk/@ssen-distribution/flexibility-services-contract-register">Flexibility Services</a>, <a href="https://data.ssen.co.uk/@ssen-distribution/sepd-flexibility-market-price-statement-april-2023">Flexibility Market Price</a>, & <a href="https://data.ssen.co.uk/@ssen-distribution/can-reporting-contract-award-notice">Contract Award Notice</a></td> | ||
| <td>✔</td> | ||
| <td>✔</td> | ||
| <td> </td> | ||
| <td> </td> | ||
| <td>✔</td> | ||
| <td> </td> | ||
| </tr> | ||
| </table> | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Critical: Fix malformed HTML in the table
- Every 
✔entity needs a trailing semicolon (✔) or it won’t render correctly. - The “Isle of Wight” anchor tag is missing its closing 
>before the link text. 
Example fixes:
- <td>✔</td>
+ <td>✔</td>
- <a href="https://data.ssen.co.uk/@ssen-distribution/isle_of_wight_active_network_management"<Isle of Wight Active Network Management</a>
+ <a href="https://data.ssen.co.uk/@ssen-distribution/isle_of_wight_active_network_management">Isle of Wight Active Network Management</a>Run this script to correct all ✔ occurrences:
#!/bin/bash
# Fix missing semicolons in checkmark entities
rg -l '✔' --files-with-matches | xargs sed -i 's/✔/✔/g'| --- | ||
| 
               | 
          ||
| <b>What can SSEN's data help me with?</b> | ||
| 
               | 
          ||
| --- | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🛠️ Refactor suggestion
Avoid raw HTML for emphasis and separators; use Markdown syntax
Mixing HTML tags (<b>) and ambiguous --- separators in the body can trigger front-matter parsing or render inconsistently across Markdown engines. Prefer Markdown’s native syntax for readability and consistency.
Apply this diff:
- ---
-
- <b>What can SSEN's data help me with?</b>
-
- ---
+ <hr>
+
+ **What can SSEN's data help me with?**
+
+ <hr>📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| --- | |
| <b>What can SSEN's data help me with?</b> | |
| --- | |
| <hr> | |
| **What can SSEN's data help me with?** | |
| <hr> | 
Summary by CodeRabbit