1. Scope There are now two levels of Scope: Site and LTER. Site (as units are submitted) LTER (vetted by the Units committee) A unit will retain its individual site scope even when it is upped to the LTER

2. Vetting Send the list of custom units back to each site and ask if they still would like these entered in the database. Some sites will want to refine their definitions. Local PI's get input here. Committee of IMs (UDWG) to review all the submitted. A unit is 'vetted' when it takes into account the Best Practices. In the future, every 10 units input into the db, committee meets to vet.

3. To Do: Put the ~800 into the unitsdb (Oct 31) TODD, MARK Finish Best Practices recommendations - for both attributes and units (Oct 31) TODD, MARGARET, HAP, MARK, KAREN Send 'Test' group [ ARC, HBR, CCE, PAL, PIE, SBC, NTL, AND ] a set of their own units to review and resubmit, and reply with comments on the best practices (Nov 30) JIM, JOHN C, KAREN, MASON,JAMES, HAP, MARGARET, DAVE, SUZANNE. Determine easy method of getting units back from the sites (webform? Excel file?).

4. And then… Re-factor database for multiple levels of scope on a unit. Alter db schema as needed. MASON, JAMES Repopulate database with any reformed units received from the 'Test' group (same scope)‏ Send units to individual sites once this process is sorted out. EVERYBODY No end in sight - going to keep growing and growing (hopefully)