This link is not correct. It will point to something like `<base_url>/requests/<request_uuid>`
A request, for wich user has access to, should be accessible via <base_url>/me/requests/<request_uuid>. But I am not sure about other implications this might have. For a community manager, it would make sense to direct them to <base_url>/communities/<community_slug>/requests/<request_uuid> , as this is the context where the request should be reviewed.
We could of course construct the request url per template like
A request, for wich user has access to, should be accessible via
<base_url>/me/requests/<request_uuid>
. But I am not sure about other implications this might have. For a community manager, it would make sense to direct them to<base_url>/communities/<community_slug>/requests/<request_uuid>
, as this is the context where the request should be reviewed.We could of course construct the request url per template like
Any suggestions on this? @slint @ntarocco
_Originally posted by @rekt-hard in https://github.com/inveniosoftware/invenio-rdm-records/pull/990#discussion_r1214296691_
Check files for links to update: