View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003538 | Composr | catalogues | public | 2018-02-12 11:08 | 2018-02-23 03:03 |
Reporter | Adam Edington | Assigned To | Chris Graham | ||
Severity | Feature-request | ||||
Status | closed | Resolution | not fixable | ||
Product Version | |||||
Fixed in Version | |||||
Summary | 0003538: Linked record fields | ||||
Description | I've been playing around with Airtable lately (https://airtable.com/) and I wondered if Composr Catalogues could provide a similar feature set (perhaps in v11). The ease of linking entries is the thing I find the most useful. | ||||
Additional Information | https://support.airtable.com/hc/en-us/articles/206452848-Linked-record-fields | ||||
Tags | No tags attached. | ||||
Time estimation (hours) | |||||
Sponsorship open | |||||
related to | 0003542 | non-assigned | Search and Find Page to Add/Link |
|
This issue is rather vague. I appreciate it, and I'll make a note where we list competing systems, but... Airtable has over $10.6 million in funding to produce this system. Essentially this issue is a "make a system as user friendly as Airtable" rather than a specific feature, and we couldn't do it without at least a six-figure investment specifically in that. |
|
I just meant the way they allow entries to link to other entries, wasn't asking for a full recreation of Airtable. |
|
Right, but we have entry cross-referencing already. |
|
True, but it would be nice to have the search function for entries rather than the tree list (or as well as). |
|
|
|
I also think that as we have templates for the different views, allowing these to be selected on the frontend (grid view, tabular, etc) would be a nice touch if no default is selected as an override to providing all 4 view options to members. |
|
That's a nice suggestion. Mythus suggested something similar re finding records (I linked the issue). To be clear the only reason this issue was closed is that it just wasn't something clear enough to manage. I am keeping Mythus's issue open as it's pretty specific, and if implemented could be done for all content types. It is very unlikely this feature would make v11 as we have so many basic UX things to do (e.g. auto-fixing photo orientation as recently discussed, or the major theme upgrading): tackling UX for people with huge amounts of content is much more minority use case. That doesn't mean I don't want it to happen, e.g. in the future or if someone can contribute the code. |
Date Modified | Username | Field | Change |
---|---|---|---|
2018-02-12 11:08 | Adam Edington | New Issue | |
2018-02-13 00:01 | Chris Graham | Note Added: 0005511 | |
2018-02-13 00:01 | Chris Graham | Status | non-assigned => closed |
2018-02-13 00:01 | Chris Graham | Assigned To | => Chris Graham |
2018-02-13 00:01 | Chris Graham | Resolution | open => not fixable |
2018-02-13 19:03 | Adam Edington | Note Added: 0005515 | |
2018-02-13 19:04 | Chris Graham | Note Added: 0005516 | |
2018-02-13 19:12 | Adam Edington | Note Added: 0005517 | |
2018-02-13 19:12 | Adam Edington | File Added: seach_records.png | |
2018-02-14 00:22 | Adam Edington | Note Edited: 0005517 | View Revisions |
2018-02-16 13:29 | Adam Edington | Note Added: 0005527 | |
2018-02-23 02:42 | Chris Graham | Relationship added | related to 0003542 |
2018-02-23 03:03 | Chris Graham | Note Added: 0005535 |