Currently an invalid UUID throws an errror, e.g. `/documents/1234`. It should instead provide an informative resonse in hal+json style. This may need to be fixed for other fetching routes?
Currently an invalid UUID throws an errror, e.g.
/documents/1234.It should instead provide an informative resonse in hal+json style.
This may need to be fixed for other fetching routes?