OEWG 20110503: Difference between revisions
Jump to navigation
Jump to search
Line 57: | Line 57: | ||
===Discussion=== | ===Discussion=== | ||
* A user was puzzled that her Typedefs were disappearing from her filtered save results. David O-S said that she needed to check off the 'always save properties' option in the filtered save interface. This fixed the user's problems. Nomi added more info about this to the userguide. | * A user was puzzled that her Typedefs were disappearing from her filtered save results. David O-S said that she needed to check off the 'always save properties' option in the filtered save interface. This fixed the user's problems. Nomi added more info about this to the userguide. | ||
==Links== | ==Links== | ||
[[OBO-Edit_Working_Group_Meeting_Agenda_and_Minutes|Back to OEWG meeting agenda and minutes list]] | [[OBO-Edit_Working_Group_Meeting_Agenda_and_Minutes|Back to OEWG meeting agenda and minutes list]] |
Revision as of 19:00, 2 May 2011
OBO-Edit Working Group Meeting: Tuesday, May 5, 2011, 8:30am PDT
Conference call numbers:
US: 1 866 953 9688
UK: 0808 238 6001
PIN: 801561
Agenda/Chair: Nomi Harris
Minutes:
Attendees:
Bug and Feature Trackers
Discussion items
- OBO-Edit 2.1-beta12 released on April 25--release notes are here
- SourceForge trackers closed to anonymous posting due to spam.
Fixed since last meeting
- Cycle over mixed relationship types -> infinite loop
- Can't save fly_anatomy_XP.obo because OE goes into an infinite loop while running verification checks.
- Chris thought this was because fly_anatomy_XP has cycles over mixed relationship types, which is valid but was not considered valid when OBO-Edit was originally developed. This may be true, but in fact it turned out that the infinite loop was caused by a term that listed itself as an alternate ID. The validation process involves recursively checking the term's alternate ID, and since it's the same term, it just recurses over and over.
- Two ways to fix the infinite loop (it now does both):
- Before recursing on alt_id in the validation check, check whether it's the same as the primary ID.
- When reading in ontology, check for alt_id == primary_id and refuse to add it.
- adding words to dictionary removes uncommitted text edits
- Unfortunately, fixing this involved undoing a change I had made that fixed another, more minor bug:
Words added to dictionary in unedited term don't turn black immediately.
For now, we'll just have to live with the newly-added-to-dictionary word staying red until user does something that causes a commit (or moves to another term and then back).
- Unfortunately, fixing this involved undoing a change I had made that fixed another, more minor bug:
- ID Profile Mismatch dialogue box and multiple ontologies
- Loading multiple ontologies--PATO, GO, cell etc, Marcus gets message "ID profile mismatch--use profile loaded from the file"? Which ontology file is it referring to? It should say which.
- Thanks to Midori for providing two tiny ontologies with ID profiles so I could test this.
- This message now lists the two ID profiles, so at least it's somewhat clearer. However, it still seems a bit random which one it chooses as the new one if you have multiple ontologies loaded, and I have not yet added the new feature to let you select which of multiple ID profiles you want to use. (If there are only two, it does let you choose between the two.)
- Bogus warning messages during validation: if you have a URL in a comment or definition, you get complaints about there not being spaces between "sentences" and lack of capital letters.
- I have decreased the number of these (though not totally solved the problem)
- Search aspect is missing the "can be reached via" selector
- Fixed in 2.1-b13
Currently working on
- Search for children misses some (unless reasoner on)
- If you turn on one of the reasoners, you find more children. But what do we really mean by "children"? (Do we include inferred children or just asserted?)
- Weird nondeterministic behavior in Ontology Tree Editor: for some ontologies (such as teleost_anatomy_VAO_edit.obo), Tree Editor sometimes displays some non-root terms as roots. Which terms are shown as roots varies each time you restart!
- David O-S figured out how to prevent this weird nondeterministic behavior: "Strip our the OBO_REL: prefix from the relations that have it* and, as far as I can tell, the odd behavior goes away...My guess is that OBO-Edit has trouble parsing relationships and/or intersections with these relations."
- That fixes the weird behavior, but I still don't know what causes it!
- Is_a closure broken
- Filtered save with "is_a closure" checked doesn't save all the terms it should.
Next bugs to work on
- Filtered save with "child" aspect fails
- Maybe this is related to the bug mentioned above (child search not finding all the children it should)?
- Bad handling of unrecognized relation (text editor et al.)
- I looked into this some--will not be simple to fix. Has to do with how dangling objects (e.g., unrecognized relations) are handled in different components.
- scroll lock (aka lock view) for global OTE - If I click on terms in the locked OTE, it doesn't show them in the Text Editor or other components, and it should, right?
Discussion
- A user was puzzled that her Typedefs were disappearing from her filtered save results. David O-S said that she needed to check off the 'always save properties' option in the filtered save interface. This fixed the user's problems. Nomi added more info about this to the userguide.