owlcollab / owlcollab/owltools
OWLTools-Solr cleanup
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 115
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
Not clear how much to invest if we want to instead switch to loading from blazegraph, or reuse monarch solr-loader.
- test suite
- investigate best strategy for testing Flexdocs, cc @kltm
- some tests such as AllOntologyLoaderIntegrationRunner fail and are skipped. Why?
- do more thorough testing of logic
- add tests for panther
- populate redundancy field
- why is there two PANTHER classes? PANTHERGeneralSolrDocumentLoader and PANTHERSolrDocumentLoader
- now understood. one populates documents following the general schema
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 OWLTools-Solr loader classes, including PANTHERGeneralSolrDocumentLoader and PANTHERSolrDocumentLoader, then run AllOntologyLoaderIntegrationRunner to inspect the skipped failures. Investigate the Flexdocs testing strategy, logic coverage, Panther tests, and redundancy field; done means the cleanup plan is resolved and the applicable checklist items are addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, testing-qa
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100