| Line 9 was replaced by lines 9-10 |
| - * EOT working on upcoming RCN and KNB Metadata Tools training sessions |
| + * EOT working on |
| + ** Upcoming RCN and KNB Metadata Tools training sessions |
| At line 10 added 3 lines. |
| + *** 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 135 added 27 lines. |
| + |
| + !! 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. |
