CentreForDigitalHumanities / CentreForDigitalHumanities/EDPOP
Single record endpoint
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
The backend should have an endpoint to retrieve information about a single endpoint based on its URI.
This is useful in itself, but the functionality it a good intermediate step for fetching the contents of a collection (#162). The collection graph only contains a reference to the record, not its contents. In order to generate a page with results, we need some way to get the contents of a record from a URI.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the backend routing and the code that represents the collection graph, then trace how a record URI is currently handled. Define the single-record response from the existing record data, and verify that the endpoint can provide the contents needed when generating collection result pages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100