MW-E2ED Conference Call
May 7, 2008
Chas DiFatta, Carnegie Mellon University (chair)
Mark Poepping, Carnegie Mellon University
Michael Gettes, MIT
Steve Olshansky, Internet2
[AI] (Chas) will list proposed command line options for the eddy-grep command and send them to the email list.
[AI] (Chas) will develop manual pages for the recommended input and output for eddy-grep and send them to the email list.
**Carryover Action Items**
[AI] (Chas) will distribute the user requirement document to the list for comment.
[AI] (Chas) will email instructions on the workflow for changed documents, as well as the conventions for renaming files
The purpose of the call was to discuss the input and output options for the eddy-grep. eddy-grep would allow a user to search for specific values in an EDDY record. The grep would allow users to search for certain fields with input from either a file or by piping together a series of requests.
There would be three options for output:
1) CER, which would include all of the XML.
2) tag/value pairs – This output would have no XML and would be appropriate for someone to use with their own Perl scripts.
3) comma-separated and 3b) a record in which the first line is a header – the comma-separated tags – and the rest of the records are comma-separated values. This would be appropriate to use with Excel or some type of graphing software.
Chas will do a manual page for the output options and provide sample outputs and inputs.
There was also discussion about the potential for creating an “EDDY print” package to allow a user to specify the fields to be printed.
**Next Meeting – June 4, 2008 (5 p.m. EDT)**