...
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Larry, Jay, Dan, Oliver DMT-182: Format structure issues raised in working on Use Cases. Data Description issue will discuss at next meeting. Darrin's example - can Jay see what you're doing - wendy email get his RDF Wendy will go through remaining views and potential view and draft for discussion DMT-148 - looked at specific issues (skip those in Qualitative) Final review piece is to identify those ComplexDataTypes that are total orphans - find them and isolate - Oliver will write script for validation of this problem Script to identify orphans in general - with package information - Oliver ISSUES for resolution before end of January Extensions to Workflow for Prototype - Jay will gather information, we'll create issue and determine what needs to be discussed Add lists of classes needing documentation in other packages in Prototype |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jay, Larry, Dan, Oliver, Kelly Workflows: PENTAHO etc. start with metadata and produce the transformation using that as a driver. Suggest the use of a MetadataDrivenAction. Add the ability to add a correspondence table which would hold the relationships used for recode. The user creates the correspondence table (ex. the IPUMS transformation table). Addresses Joins, recodes, renames Question: Are you aiming at being able to roundtrip and generate the PENTAHO from the DDI? Yes, we can do that. It's JAVA based. These systems also support formulas and can run scripts. They still want to use their statistical packages to do certain things. Don't want to do statistical analysis in a data management environment. Every time they changed data management they had to rewrite the STATA code because no one could understand another's code. If you capture the algorithm and generate the code as opposed to trying to derive the algorithm from the code. You can see what is going on within the eventual code. Jay will send to Wendy and Wendy will put in to verify that what Jay is proposing is clear. LION content: Jay to send Kelly a write up of the decisions made in Dagstuhl regarding the logical data description, some of which have not yet made it into the model. Wendy to follow up with Jay about creating an issue for integrating these decisions in the model. |
...