Related: (and at the risk of slowly replicating core farmOS UI
) it would also be really helpful to be able to quickly bring up a list of logs associated with a particular asset, so that they can be edited, marked as done, etc.
1 Like
I would love to brainstorm what the best UX for these is… Are they just “asset actions”? Floating action button menu? Something else?
My instinct was to look for an “Add Log” button on /alink/asset/*, so I think the former? I’m not sure I know what the latter would look like.
2 Likes
I started playing around with this, but it turned out I needed to make a change so the new plugin for authoring logs could use query params to pre-populate the asset reference for this case.
I think the route should end up being something like /new/log/:logType?. So:
/new/logjust has buttons for each log type (clicking one adds the log type to the url and passes through any url params)- Then e.g.
/new/log/observation?asset=1234has some basic fields (name, images, notes) and an asset reference pre-populated
1 Like