From: Steve F. <sfi...@pc...> - 2005-02-09 21:44:05
|
folks- here is what dave and i worked up. comments encouraged. MODEL In the Model XML file: - in <recordClass> - lose <tableQuery> - add <nestedRecord> - add <nestedRecordList> <nestedRecord> and <nestedRecordList> are identical except that the former has cardinality 0 or 1 and the latter 0, 1 or more. They each specify: - a reference to a query that provides primary keys for the nested records. the query can have interpolated into it any attribute values from the containing record - a reference to a recordClass. This specifies the type of the nested record A given recordClass can have 0, 1 or more <nestedRecord>s and/or <nestedRecordList>s Circular references are allowed. (Eg, a Gene can have an RNA and vice versa) VIEW A summary display still shows only attributes of a record, not nested records. A detail display shows shows its nested records in summary form. Display of a nestedRecordList will look a lot like the current table display. A nestedRecord will be similar, but have only one row. In addition to the current ability to customize a detailed view for a record class (by providing a .jsp page named for the record class) we will introduce: - a customizable view for a nestedRecord. the .jsp file will be named xxxxxxxxxSummary.jsp where xxxxxxxxxx is the name of the record class. (this won't be used for a standard summary page, just for a nested record summary) - a customizable view for a nestedRecordList. the .jsp file will be named xxxxxxxListSummary.jsp The .jsp files for nested records and lists will be dropped into the detail page of the containing record. We anticipate using this as the hook for plugging in graphics to a detail page steve |