Change request: On the right hand side column of ...
13503
Reporter: ahahn
Assignee: kbraak
Type: Bug
Summary: Change request: On the right hand side column of ...
Priority: Blocker
Resolution: Fixed
Status: Closed
Created: 2013-07-11 13:35:53.218
Updated: 2013-09-26 21:43:05.526
Resolved: 2013-09-26 21:43:05.489
Description: Change request:
On the right hand side column of the "Summary" for a dataset served through IPT, include a line "SERVED BY ". For future extension, also add a line "BELONGS TO " if a dataset is constituent of a resource network.
NB: this requires that the IPT installation title reflects that it is a VertNet IPT (currently not the case: http://ipt.vertnet.org:8080/ipt/about.do)
original message from Laura Russell: "(...) This example you included in the portal invitation, http://uat.gbif.org/dataset/28573c0a-b833-41b1-9999-56c6b9bce519, shows the Georgia Southern dataset as being hosted by the University of Kanas. We would much rather see VertNet there.
The University of Kansas hosts the server on which our IPT resides, but VertNet is responsible for hosting the data on the IPT. There is potential down the road, also, that we might host our IPT on a server elsewhere. (...)"
*Reporter*: Andrea Hahn
*E-mail*: [mailto:ahahn]]]>
Author: ahahn@gbif.org
Created: 2013-08-19 16:29:25.616
Updated: 2013-08-19 16:29:25.616
I see the text now, thanks - but is there a possibility to put the link to the installation behind that, too?
Either the RSS endpoint from the registry, where it exists (http://vertnet.nhm.ku.edu:8080/ipt/rss.do), or even better the underlying Home page (http://ipt.vertnet.org:8080/ipt/).
Author: kbraak@gbif.org
Created: 2013-08-19 17:29:11.931
Updated: 2013-08-19 17:29:11.931
I'm using the underlying IPT home page, parsed from the installation Feed endpoint. Work committed in https://code.google.com/p/gbif-portal/source/detail?r=1799
As for the Belongs to network change, this is dependent on changes to the registry2 web services, exposing the dataset's network. Therefore, I have bumped this issue to 0.6 release.