owlcollab / owlcollab/owltools
Make taxon check a workable long-term service
Open
Nobody has claimed this yet.
bug
imported
- Dominant language
- Java
- Stars
- 115
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
From sjcar...@lbl.gov on December 09, 2014 13:48:56
The taxon-check tools is located at a strange URL and is hard to monitor. A possible solution would be to:
- Add a CNAME to a proxy server to give it a more standard location
- Add a /status route so that it can be easily monitored remotely
Original issue: http://code.google.com/p/owltools/issues/detail?id=109
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 locating the taxon-check service, its deployment or proxy configuration, and its web entry point; no specific files or tests are named. Confirm how the service is currently exposed and monitored. Done means it has a standard CNAME-backed location and a remotely usable /status route.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100