At line 2 added 12 lines. |
+ * Kepler User Interface meeting in Santa Barbara, meeting notes in CVS |
+ * EcoGrid group revamping resultset format, adding new dynamic data query methods based on EML |
+ * Kepler group working on |
+ ** ontology-driven data and actor browsing |
+ ** integrated EcoGrid data discovery and access |
+ ** Presenting Kepler demo paper at SSDBM in Greece |
+ * EOT working on |
+ ** Upcoming RCN and KNB Metadata Tools training sessions |
+ ** New website based on wiki about to come online, waiting on LDAP issues and final graphics tuning |
+ *** Prototype can be reviewed [http://lternet-227.lternet.edu:8080/seekwiki/] |
+ *** Will eventually replace the current SEEK website at http://seek.ecoinformatics.org/ |
+ * Taxon group focusing on LSID and user management issues and finishing the name server prototype |
At line 75 added 79 lines. |
+ |
+ !! Bing Zhu |
+ * Had a meeting with David Stockwell and Raja to discuss the data integration of Niche Modeling in Ecogrid system. Has been working on the setting up the SRB accounts and choosing physical storage for those niche modeling images. A SEEK new task was created for this data integration in SEEK’ Bugzilla. |
+ |
+ * Evaluated the schema and architecture of Ontology Server developed by STAR Lab ([http://www.starlab.vub.ac.be/research/dogma/OntologyServer.htm]) and discussed it with SEEK SDSC team in a UCSD SEEK meeting. Exchanged ideas with SEEK and GEON researchers about establishing ontology registry, search for ontology (what does this mean) and issues about future usage of ontology registry. |
+ |
+ !!Xianhua Liu |
+ |
+ Completed Tasks/ Bugs Fixed: |
+ * Revised National Vegetation Classification Revision System (NVCRS) |
+ ** Revised nvcrs database structure |
+ ** Revised the first jsp pages for all 3 roles: author, peer-viewer and manager |
+ ** Implemented uploading function for supporting documents. |
+ |
+ |
+ Current Work and Bugs: |
+ * Designing and developing Auto-Manager for nvcrs to automatically complete some system administration tasks, such as sending emails,assigning proposals to peer-viewers. |
+ |
+ Significant Issues |
+ * None |
+ |
+ !! Jing Tao |
+ |
+ Completed Tasks/ Bugs Fixed: |
+ * Attended the Kepler meeting in Santa Barbara and identify the tasks/bugs for next couple months. |
+ |
+ Current Work and Bugs: |
+ * Bug 1584(loading data into relation db) and 1586 (Data query engine |
+ implementation in Kepler) |
+ ** Design for those bugs(Collaboration diagram and class diagram design). |
+ ** Try to install and paly with SAS which is a candidate SQL engine for data query. |
+ |
+ Significant Issues |
+ * SAS is complicated and probably the learning curve is high. |
+ * Need to identify which SQL engine we should use to loading data. Some criteria about this engine |
+ ** Ease to install it in both Windows and Linux |
+ ** DDL is simple |
+ ** Good performance |
+ |
+ !! Chad Berkley |
+ |
+ Completed Tasks/ Bugs Fixed |
+ * researched ontology integration for kepler (bug 1591) |
+ * worked on bug 1579 with dan |
+ * helped debug the mac issues in kepler |
+ * attended the 2 day kepler meeting |
+ |
+ Current Work and Bugs |
+ * Working on getting ready for SSDBM. Mostly working on poster. |
+ |
+ Significant Issues |
+ * Need to have conf. call with matt and shawn about sparrow/ontology issues in kepler. we decided to hold the call after my return from greece |
+ |
+ !! Dave Thau |
+ |
+ Completed tasks/bugs fixed |
+ |
+ * Created and vetted initial basic feature set for Taxon LSID server |
+ |
+ Current Work and Bugs |
+ |
+ * Working on bug #1597 - the intial user management for the taxon server. |
+ * Getting current taxon server to work on my local box for testing purposes |
+ |
+ Significant issues |
+ |
+ Is there any centralization of user management across SEEK, or any |
+ standard information about users we want to maintain? Should I use LDAP, |
+ or something like that, or just maintain taxon server specific user |
+ information. Seems like the latter is fine - people contributing |
+ taxonomic concepts may not care about the rest of SEEK, so shouldn't |
+ necessarily be burdened by a SEEK-wide user management system. However, |
+ it'd be good to collect and name contact information similarly across |
+ SEEK. I'm going to start with the sorts of contact information used in |
+ the Darwin Core. |
+ |
+ |
+ !!! Other Status Reports |
+ You can see the [status reports|StatusReports] for other time periods as well. |