2012-01-19 conference call¶
Agenda¶
- Reminder: We switch to the new meeting time next week: Fridays at 1 PM PST, 2 PM MST, 4 PM EST beginning January 27th.
- Review the work plan timeline: December 8 2011 WebEx meeting
- Review of Jan. 12 To Do list items: scroll to bottom at 2012-01-12 conference call
- Are we clear about the decisions made regarding the issues raised on the VegBIEN schema email thread?
Alternatives to e-mail threads¶
Create new issue in issue tracker and each person responds in the tracker¶
- Create a new issue instead of a new e-mail subject, and post replies in the tracker rather than replying to an e-mail
- Only interested parties watch an issue
- Instead of e-mailing people, create an issue and add those people as watchers
- People can set their notification settings to turn new post notification e-mails on or off
| Pros | Cons |
| Less noise on the BIEN list | Rest of BIEN list is in the dark about conversations going on |
| Conversations automatically archived in the issue tracker | Conversations not archived in the BIEN list archives |
Structural changes to VegX¶
- Make it easier to map to
- Don't make the person doing the mapping fill in IDs for every element to get everything to match up
- Just use VegBank XML format of putting child elements inside parent elements, and pointer targets inside the pointer field
- Can we just alter large portions of VegX? This would be a completely different structural design, but keeping the same entity names
Switching from DOM to SAX to parse large VegX files¶
Some of the CTFS VegX files are over 100MB. My XML editor (Oxygen) can't open these, so I can't imagine Python will be any happier. To avoid a long pause while the entire file gets read into memory, we might want to switch to a stream-based parser.
This was not an issue previously because we were mapping straight from the database, so the data could just be fetched row-by-row. (We might, however, switch to using a server-side cursor to reduce the number of queries to the server.)