OData / OData/odataorg.github.io
Broken Links
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 73
- Forks
- 106
- PR merge metrics
- No merged PRs in 30d
Description
There are a number of links on odata.org that are outdated or otherwise not working. It would be great to update these links to make sure they are still working and relevant to OData.
Previously Documented Occurrences
- #195: OData Powershell Explorer linked on Ecosystem > Consumers (server IP address could not be found)
- #196: "This link" under TripPin(read/write) linked on Reference Services > OData v4 (404 Not Found)
- #315: Italy Ministry of Health Open Data Portal linked on Reference Services > OData v2 (server IP address could not be found)
Some Additional Occurrences
- Conduit linked on Ecosystem > Producers (404 Not Found)
- Harmony Core by Synergex linked on Ecosystem > Producers (new blog website)
- ScanJour WorkZone Content Server linked on Ecosystem > Producers (server IP address cannot be found)
- Self-Service DATA linked on Ecosystem > Producers (leads to 404 Not Found)
- "This link" under Self-Service DATA linked on Ecosystem > Producers (404 Not Found)
- Team Foundation Server linked on Ecosystem > Producers (404 Not Found)
- inova8-OData2SPARQL linked on Ecosystem > Producers (404 Not Found)
- Core Protocol PDF linked on OData Version 3.0 (404 Not Found)
- Common Schema Definition Language (CSDL) PDF linked on OData Version 3.0 (404 Not Found)
- RFC3986 linked on ODL V3 URL Conventions under 5.3 URL Equivalence (empty link)
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.
Research direction
Start by reviewing the listed Ecosystem, Reference Services, OData Version 3.0, and URL Conventions pages and checking each reported URL. Update or remove links that are no longer working or relevant, and verify that all listed occurrences resolve correctly when the work is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100