Now that we've approved the workplan, we migrated it to trac as a mix of milestones, components, keywords, and tickets. For details on the correspondence, see the mash-up<https://docs.google.com/spreadsheet/ccc?key=0Ak2nuw10QdWQdHR4Z21KT0RqSUFGMFhtUGRsUlRlMnc&usp=sharing> of JRC's worklist, trac, and the PCORI milestones, especially the 1st (JRC) sheet.
The lake milestone names just weren't working for me. The milestones<http://informatics.gpcnetwork.org/trac/Project/report/9> are now: Date <http://informatics.gpcnetwork.org/trac/Project/report/9?sort=date&asc=1&page=1> Name <http://informatics.gpcnetwork.org/trac/Project/report/9?sort=name&asc=1&page=1> Apr 10, 2014 deid-plan Apr 25, 2014 initial-data-domains May 1, 2014 data-stds-gov-plan May 20, 2014 data-stds-plan May 30, 2014 data-sec-check Jun 15, 2014 data-quality-plan Jun 30, 2014 data-domains2 Oct 15, 2014 emr-align-mu2 Details on each are in the roadmap<http://informatics.gpcnetwork.org/trac/Project/roadmap>. SoftwareDev#tracking<http://informatics.gpcnetwork.org/trac/Project/wiki/SoftwareDev#tracking> shows tickets grouped by milestone, eliding low-priority tickets (e.g. tickets whose start date has not yet arrived). -- Dan ________________________________ From: Dan Connolly Sent: Thursday, February 27, 2014 6:07 PM To: Campbell, James R; [email protected] Subject: RE: Data standardization notes and workplan from Hackathon As to ALL: Technical team leads to review and validate these procedures above and attached schedule (Data Standardization Worklist 20140225) by next GPC STD/DEV conference call I went over the the workload and schedule proposed for KUMC with Nathan and Matt (Bhargav, I hope you appreciate that I let you do more fun stuff ;-). We think we can meet the schedule. Of course, several items in the schedule are of the form "start with the way KUMC does it..." which is ~0 work for us. There are some aspects of the plan that aren't entirely clear to me, but they seem to be far enough into the future that I expect they'll become clear in due course. -- Dan ________________________________ From: Dan Connolly Sent: Wednesday, February 26, 2014 10:50 AM To: Campbell, James R; [email protected] Subject: RE: Data standardization notes and workplan from Hackathon I'd like to see the workplan structured as in my 21 Jan feedback<http://www.mail-archive.com/[email protected]/msg00028.html> so we can bulk-import it into trac. I think I can tack a crack at it, but it might be better if you do it, Jim. -- Dan ________________________________ From: Greater Plains Collaborative Software Development [[email protected]] on behalf of Campbell, James R [[email protected]] Sent: Tuesday, February 25, 2014 6:17 PM To: [email protected] Subject: Data standardization notes and workplan from Hackathon I have summarized discussion points from Monday and Tuesday for review and correction, revised the workplan for Milestone 2 for comment and listed a number of deliverables for team members from our hackathon discussion; in particular - myself and the technical leads from all sites. The information in this e-mail may be privileged and confidential, intended only for the use of the addressee(s) above. Any unauthorized use or disclosure of this information is prohibited. If you have received this e-mail by mistake, please delete it and immediately contact the sender.
_______________________________________________ Gpc-dev mailing list [email protected] http://listserv.kumc.edu/mailman/listinfo/gpc-dev
