Separating databases from docs

[Paulo_Silva]

One of the new features I’m most excited to see in Coda is the ability to have separate databases from our documents for better optimization. I saw this feature announced in Shishir’s latest announcement (unless I misunderstood)! I’d like to know if there’s any estimate for when this feature will be available to us, at least for testing?

[Christiaan_Huizer]

hi @Paulo_Silva

in this post @Nathan_Penner announced that the split of docs & tables is in the works. No time line was communicated by Coda yet.

Why does this update matter so much to you?

Cheers, Christiaan

Introducing Superhuman

Hi @Stefan_Huber! We’re working towards sub-doc sharing and know this is a top request. Many requests to share pages are for pages with data on them, where it’s important that users see only the data shown in views on that page. We’re focused on those use cases first, and one of the key goals in our work to separate data from docs is to make it possible to share parts of a table without sharing the full doc or table. We’ll enable ways to share views of data directly first, then over time add …

[Yannick_Pinta]

I agree completely, this will be so much easier for us and make so much sense not needing to see global company data being parts of docs. This coupled to the ability to filter “cross-doc tables” using active content from the docs themselves rather than from the original doc only would make a big difference. This will allow us to streamline the use of templates, using local input (AKA customers ID for instance) to only bring the relevant data into the docs seamlessly (not needing makers to change cross-doc filtering manually).

[Math_24]

Hello, in January I suggested something like this

Proposal for hidden data and table | Front < -- > back

I think I understand the difficulty and see the difficulty in managing this. But to ensure security with the search bar, the data visible on network, …; we need to find a solution! this topic is there to think about and see how we would like to see it This is how I would see it: Here are some ideas I’ve noticed in other tools that could be integrated into coda. Here’s an idea that might be similar to fibery : A modal or specific page to manage the document’s root databases…

[Christiaan_Huizer]

merci @Math_24 for the insights

seen the various database types /layers it won’t be a walk in the park, but as you demonstrate, Fibery has something that works, so we can have confidence that it will work as well one day in Coda.

[Math_24]

Yes, it’s not simple. There’s work to be done, but it could make documents, sharing, and cross-document management more efficient. Coda has additional features, and care must be taken to integrate them properly (packs, FormulaPack, etc.). They’ll get there.