Structuring this DB

Hi all. I’m building a CMS style app that allows customers to upload, share, and track reads of documents. I’m struggling with the DB and how it can be visualised. The goal is to create a matrix style table/bunch of repeating groups that has:

  • Documents assigned across the top row (data type document)
  • Users names in column 1 (data type user)
  • Read status of each document for each user in the remaining grid space (data type read status)

I keep running into limitations. Ie, the table functionality does not allow me to easily display data from differing types. I’m then struggling to set up 3 separate repeating groups, each containing the relevant data type, as responsive and vaguely well-designed.

Should I change my DB set up? It’s

  • Users
  • Documents
  • Read status
  • Organisation (customer)

Or am I being dense and missing something here?

Any help, would be much appreciated.

I think the way I would think about it is that inside a table cell you might have another “table” (you probably don’t need another actual table element, but… you get the idea).

Interesting @rico.trevisan - thanks for responding. Can you elaborate slightly? Would I set up a table - using the table element - with minimal cells and add repeating groups into those cells?

How are these datasets related to each other? Is a read status record created for each user for each assigned document?

TLDR you should be able to make a RG of the documents dataset grouped by document

Yes, @code-escapee. A read status is created for each user on each document.