Use a parent/child design.
The parent is a document that contains general demographic information about the user.
The response (child) docs are the assets; one response doc per asset. In this way you can embed a single category view that lists all the assets for one user (or just see it in the view). You can better sort and group data if each asset is its own doc. If you try and go with an actual table, when someone asks 'where are all the dell 9866 computers', you're screwed. If they are separate docs, just create a view that lists asset by <whatever you want to group by> and you now have an easy way to find all of the <whatever you've been asked to find>