Describe the bug
On DSpace 7 the permanent uri of Communities and Collections is malformed, having http://localhost:3000 as domain instead of actual one.
See, as example https://dspace7-demo.atmire.com/collections/dd1240ae-d7dd-405c-bdc3-
(https://user-images.githubusercontent.com/70699836/95428261-15ec4380-0949-11eb-9874-f739039f167b.png)
d6c960609433 .

To Reproduce
Steps to reproduce the behavior:
- Navigate to a community or collection page of DSpace 7
Expected behavior
A permanent URI link not pointing to a local or malformed domain.
I think we can evaluate how this link has to be built, there can be two options: create the url at angular side, using for example, current installation domain. Otherwise we can use the dc.identifier.uri metadata as already done with Items, in this case it should be possible to deal with external links (hdl) as permanent URI of Communities and Collections.
Related work
#886
Describe the bug
On DSpace 7 the permanent uri of Communities and Collections is malformed, having http://localhost:3000 as domain instead of actual one.
See, as example https://dspace7-demo.atmire.com/collections/dd1240ae-d7dd-405c-bdc3-
(https://user-images.githubusercontent.com/70699836/95428261-15ec4380-0949-11eb-9874-f739039f167b.png)
d6c960609433 .
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A permanent URI link not pointing to a local or malformed domain.
I think we can evaluate how this link has to be built, there can be two options: create the url at angular side, using for example, current installation domain. Otherwise we can use the dc.identifier.uri metadata as already done with Items, in this case it should be possible to deal with external links (hdl) as permanent URI of Communities and Collections.
Related work
#886