internetarchive / internetarchive/dweb-mirror
Full support of special identifiers on dweb-mirror
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 330
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
The special identifiers `home` `local` `settings` are configured in dweb-archivecontroller/Util.js in `specialidentifiers` but Currently there is code in a variety of places to handle them including in both dweb-archive (UI) and dweb-mirror (server).
As far as possible dweb-mirror should provide reasonable responses to the common protocols so that the configuration happens on the server not in the UI.
Each of the following needs testing for each of `home` `local` `settings`
- [ ] /service/img/IDENTIFIER
- [x] local fixed
- [x] home
- [x] settings - goes to http://localhost:4244/archive/images/settings.svg which doesnt look right, may need file replacing if its used anywhere.
- [ ] /metadata/IDENTIFIER
- [x] [local](http://localhost:4244/metadata/local) fixed
- [x] [settings](http://localhost:4244/metadata/settings) good
- [x] [home](http://localhost:4244/metadata/home) - search collection with correct long query
- [ ] /advancedsearch.php ... query to get members ...
- [x] local - gets members in metadata so should be good
- [x] home will work as search collection, and collection:home wont add anything
- [x] settings - N/A
- [ ] related - is this needed ?
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 with dweb-archivecontroller/Util.js and its specialidentifiers configuration, then trace the dweb-mirror handlers for /service/img/IDENTIFIER, /metadata/IDENTIFIER, /advancedsearch.php, and related requests. Verify each endpoint for home, local, and settings, including whether the settings image and related behavior need changes; done means the common protocol responses are configured and behave reasonably on the server.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100