I have needs where I need tables to link to many tables, such as Meeting Notes and other decision-type tables I’m counting on to help my team in its roadmapping and goal planning. The method of a table linking to essentially just one other table via lookups is very limiting. I think it would be solved by reciprocal linking, as I’ve also talked about in the community, but don’t seem to have any insight back as to whether Coda itself is interested in introducing this soon. I have issues with my schema in figuring out how to link stuff to other stuff in Coda. I believe that this feature is_ too much linked to a product, but I think that Coda could at least integrate a better linking … Why am I pointing to this app in Coda? Because I think you could use some of its feature to make an even more shiny Codaīidirectional linking. I think I’ll use it for ever now that I tried it. I just began to use the beta of Roam Research ( ) which is a bullet based note taking app that is very disruptive. If Coda doesn’t solve this problem, someone else eventually will.Ĭoda has a nice set of feature requests on their recent voting page, so it’s a tough call what to prioritize first, but you can’t go wrong with good performance and some bugfixing.įeature request based on Roam Research Suggestion Box Now excluding all other Coda users, the data set complexity I’m referring to offers a trivial load for something like a Postgres DB, and many teams would be happy to host their own Coda servers. If the API ends up being powerful and speedy as it should be, users can make their own custom app views with their UI’s of choice if the web-app is too slow. And then all tables in the app can be views, probably all with some sort of filter/limits on data that the frontend model and UI needs to deal with. I’d be happy to have a place where I define the fields/columns for tables (schema definition place) - without the app needing to show the actual data, in lieu of the “Data” folder I currently have with the table sources. what’s our overall rate of opening and closing of work items over time, since the beginning of time? The delta between these lines is informative for project trajectory, milestone tracking and also as a historical guide for how future projects may track or be informed to create a better process. They are still usually needed for administrative or team wide analytics…e.g. I don’t have any uses for this in my current workflows. It’s very rare when all items, including archived ones, or even only archived ones, need to be inspected one, by one, individually. It’s an interesting proposal, especially given what you mentioned earlier, that webapps in general struggle to represent and deal with large amounts of data.Īt the same time it is something I am trying to avoid - exporting data and dealing with it somewhere else because the main tool is unable to. Why not stand up an instance of ElasticSearch and push the past off the table and into something that can make the data more useful?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |