View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 1079 | Composr | catalogues | public | 2013-03-15 09:45 | 2014-11-27 03:43 |
| Reporter | Chris Graham | Assigned To | Guest | ||
| Priority | normal | Severity | feature | ||
| Status | new | Resolution | open | ||
| Summary | 1079: Cascaded form inputter driven by catalogue references | ||||
| Description | Let's say I have a list of venue names in one catalogue (as entries), and a list of countries in another catalogue (as entries), and when I add an entry for a new venue, I use a 'referenced' entry to specify the country that that venue is in. Then, let's say I have a further catalogue that specifies specific events. I create the catalogue with reference fields to both the 'countries' and the 'venues' catalogues. When I add a new event, I can select a 'country', then the 'venues' list would automatically filter itself to only display the venues that are in the country I've selected (and it knows this because I've already referenced the entries in their own catalogues). Basically, it will allow people to filter form options as they go, making it easier to add things if there are a lot of entries lower down the hierarchy. (i.e. if I have 5,000 venues across the world, narrowing them first by country would make adding them much easier) | ||||
| Additional Information | This goes against database normalisation rules, but catalogues are not quite databases. --- This builds on "Cascaded form inputter", but needs to read through catalogue entry relationships, and be able to run on whatever field selection inputs are used for entry selection. | ||||
| Tags | No tags attached. | ||||
| Attach Tags | |||||
| Time estimation (hours) | 32 | ||||
| Sponsorship open | |||||
