collectionsonline
collectionsonline copied to clipboard
Suggestion: break down objects/docs on people&company page by type.
This still needs some thought/discussion, don't start on it yet.
Maybe we only do this if more than X results.
- documents (archive document as opposed to objects)
- designer: (as per logic on object page)
- inventor: (as per logic on object page)
- others: (as per logic on object page)
- related: everything else
@emilyfildes do you have any thoughts here?

Yes, I definitely agree that we should breakdown:
- objects (where there is a primary relationship)
- documents (where there is a primary relationship)
- objects (where there is a secondary relationship via 'Linked People' tab)
Maker / designer / inventor etc - maybe we need to think where we should or shouldn't be explicit about these relationships
A little bit of further work required on this from @jamieu before it can be worked on.
Decided that we'll include the relationship between the person and the related object (maker, user, designer etc.) in the data being sent through to the frontend, then decide exactly how to display them later.
The data now comes through to the front end and is available in the "role" field:
(screenshot just for illustration purposes, the role isn't actually shown)