OEWG 20090602: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 19: | Line 19: | ||
# Jen - Filtering system in OBO-Edit. <br> | # Jen - Filtering system in OBO-Edit. <br> | ||
My work on cross products and taxon links is badly held back just now by the lack of a good filtered save in OBO-Edit. I'm wondering if the need is great enough that I should start adding this feature even though we are still bug fixing. I have figured out what the interface could look like:<br> | * My work on cross products and taxon links is badly held back just now by the lack of a good filtered save in OBO-Edit. I'm wondering if the need is great enough that I should start adding this feature even though we are still bug fixing. I have figured out what the interface could look like:<br> | ||
1) Add a new checkbox: 'choose tags to include'<br> | 1) Add a new checkbox: 'choose tags to include'<br> | ||
| Line 29: | Line 29: | ||
[[Image:save4.jpg]] | [[Image:save4.jpg]] | ||
Chris's comment: | ** Chris's comment: | ||
* Hardcode an option for exporting a file with only {id,intersection_of} tags, as this would be satisfactory for the majority of use cases involving working with xps as separate files. I think this could be implemented fairly easily. <br> | *** Hardcode an option for exporting a file with only {id,intersection_of} tags, as this would be satisfactory for the majority of use cases involving working with xps as separate files. I think this could be implemented fairly easily. <br> | ||
* Alternative approach is to always namespace links and xp defs, and | *** Alternative approach is to always namespace links and xp defs, and | ||
have the tag filtering done automatically from this. But I think this | have the tag filtering done automatically from this. But I think this | ||
involves more work on the editors part as they have to ensure all | involves more work on the editors part as they have to ensure all | ||
links are correctly namespaced <br> | links are correctly namespaced <br> | ||
* Follow OBO-Edit on Twitter! | |||
http://twitter.com/OBOEdit | |||
==Demos/ Tips/ Ticks== | ==Demos/ Tips/ Ticks== | ||
Revision as of 15:17, 28 May 2009
OBO-Edit Working Group, Tuesday June 2nd, 2009 9.30 a.m. PST
Conference call details:
US: 1-888-727-6732
Outside US: 1-719-867-3417
pin: 601425
Agenda/Chair: DavidOS
Minutes: Midori
Attendees:
Action items carried over
Discussion items
- Jen - Filtering system in OBO-Edit.
- My work on cross products and taxon links is badly held back just now by the lack of a good filtered save in OBO-Edit. I'm wondering if the need is great enough that I should start adding this feature even though we are still bug fixing. I have figured out what the interface could look like:
1) Add a new checkbox: 'choose tags to include'
2) When checked, this box calls up an auto-populated list of all the tag types in the file and the user can then choose which tags to include in each file.
- Chris's comment:
- Hardcode an option for exporting a file with only {id,intersection_of} tags, as this would be satisfactory for the majority of use cases involving working with xps as separate files. I think this could be implemented fairly easily.
- Hardcode an option for exporting a file with only {id,intersection_of} tags, as this would be satisfactory for the majority of use cases involving working with xps as separate files. I think this could be implemented fairly easily.
- Chris's comment:
- Alternative approach is to always namespace links and xp defs, and
have the tag filtering done automatically from this. But I think this
involves more work on the editors part as they have to ensure all
links are correctly namespaced
- Follow OBO-Edit on Twitter!
Demos/ Tips/ Ticks
- Ontology Tree Editor - missing/new features now implemented in OBO-Edit2.1
Tip of the week
- If we don't have anything here until the meeting time - the agenda chair can pick one of the attendees and put them on the spot about their favorite tip