CentreForDigitalHumanities / CentreForDigitalHumanities/EDPOP

/rdf/ endpoint to retrieve our data as LOD

Open
#227 4 comments 0 reactions 0 assignees View on GitHub
enhancement quality
Dominant language
Python
Stars
1
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Collections, and possibly other RDF entities, currently get IRIs under the `/rdf/*` path prefix. The Django backend does not recognize those paths (at least not in the case of `/rdf/collections/*`), so the user is redirected to the index page.

Possible fixes:

| Fix | Pro | Con |
|---|---|---|
| Rename `/rdf/*` entities to `/api/*` | Straightforward | Departs from #156 |
| Move RDF-producing endpoints from `/api/*` to `/rdf/*` | Arguably correct | Requires splitting the API router |
| Change all `/api/` routes to `/rdf/` | Straightforward | Only valid if all API endpoints produce RDF data |

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reading the Django backend route definitions for `/rdf/collections/*` and the current `/api/` endpoints, then review the linked discussion in #156. Determine which routing approach preserves the intended LOD IRIs and identify the affected RDF entities. Done means RDF entity URLs resolve to their data rather than redirecting to the index page.

Written by the indexing model from the issue text.

Assessment

Tech stack
django, python
Domain
api, backend
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.