Issue 17680
Display backbone sources in portal
17680
Reporter: mdoering
Assignee: mdoering
Type: NewFeature
Summary: Display backbone sources in portal
Priority: Major
Resolution: Fixed
Status: Closed
Created: 2015-07-13 17:35:57.008
Updated: 2015-08-14 18:26:39.738
Resolved: 2015-08-14 18:26:39.718
Description: The current list of backbone sources should be shown in the portal.
Consider to show:
- priority list of checklist names
- number of names taken from the dataset]]>
Author: mdoering@gbif.org
Comment: We should try and reuse the existing constituent tab for a dataset. The backbone already assigns the constituent datasetKey from the primary source usage, but the nub dataset needs to be modified to hold the list of all constituents. This should be part of the nub build workflow
Created: 2015-08-10 11:32:24.626
Updated: 2015-08-10 11:32:24.626
Author: mdoering@gbif.org
Created: 2015-08-10 14:24:36.37
Updated: 2015-08-10 14:24:36.37
Dataset constituents are unfortunately unsuitable, because they require the source dataset to specify a parentDataset. We don't want that for backbone sources which are independent datasets, can have many more usages than are included in the nub and might themselves have constituents.
We therefore use a network and manage the constituents after a nub build automatically:
http://www.gbif.org/network/542c9658-b512-4c1f-ae51-fdcf28c04b70
The UUID is added to the API Constants.