Broken link fragments in BIDS specification
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 90/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- html
- Domain
- documentation
Research direction
The issue points to a specific page in the BIDS specification documentation. Locate the file for the coordinate systems appendix, likely in the repository's documentation source. Find the two broken anchor links and replace them with the suggested new fragments. Verify the changes by checking the updated links on the live documentation site.
Written by the indexing model from the issue text.
Description
In Appendices - Coordinate Systems - EEG Specific Coordinate Systems:
- EEGLAB: ALS orientation and the origin exactly between LPA and RPA. For more information, see the EEGLAB wiki page.
- EEGLAB-HJ: ALS orientation and the origin exactly between LHJ and RHJ. For more information, see the EEGLAB wiki page.
The page still exists, but the fragments pointing to sections are now broken. #eeglab-coordinate-system was broken in 44c0152320f7a38c620df6c9b4c1cd5de251ee1d and #eeglab-hj-coordinate-system was broken in d5ff16004fe9bbe6fd672565c020a3e2ae3aa854.
These fragments can be updated to #eeglab-template-files and #use-the-helix-tragus-junction-for-fiducials, but the content no longer seems to clearly relate to the terms "EEGLAB" and "EEGLAB-HJ", so I wanted to check if this is what you'd recommend.
It might help to avoid situations like this in the future if you add an explicit <a name="eeglab-coordinate-system"></a> or similar to the page when linking externally in long-lived documents. This will serve as a signal that the section is being referenced, and also preserve the link fragments when you decide to go ahead and change the section headings.
- Dominant language
- HTML
- Stars
- 7
- Forks
- 20
- Avg merge
- 11m
- Merged PRs (30d)
- 2
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from sccn/sccn.github.io
-
sccn/sccn.github.io#94 · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
sccn/sccn.github.io#90 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
sccn/sccn.github.io#87 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
sccn/sccn.github.io#80 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
sccn/sccn.github.io#69 ·
All issues in sccn/sccn.github.io
Similar issues
-
Crush Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
catppuccin/catppuccin#3125 ·
-
Link Checker Report Openautomated issue report
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
VoltAgent/awesome-design-md#469 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
KhronosGroup/glTF#2648 ·
-
Add a SECURITY.md Open
Difficulty 1/5 Under an hour Newbie friendliness 90/100
ElementsProject/cln-application#167 · 1 comment · 1 reaction ·