Issue 10739
As a data publisher, I want my dataset's metadata to show as I edited them in the portal without delay, because questions about conflicting versions irritate me
10739
Reporter: ahahn
Type: Story
Summary: As a data publisher, I want my dataset's metadata to show as I edited them in the portal without delay, because questions about conflicting versions irritate me
Priority: Major
Resolution: Fixed
Status: Closed
Created: 2012-02-02 12:05:44.057
Updated: 2013-12-16 17:50:38.448
Resolved: 2013-12-10 14:34:03.143
Description: portal: registered dataset metadata currently turn up in the portal only with latency caused by indexing and rollover necessities. The should be available immediately after registration.
- connect metadata from registry rather than from index
- make sure registry stores relevant data (especially on datasets)
- make sure registry-stored metadata is kept up-to-date
- include information on datasets that are not indexed by GBIF]]>
Author: kbraak@gbif.org
Created: 2013-12-10 11:36:28.009
Updated: 2013-12-10 11:36:28.009
Latency in dataset metadata turning up in the portal, is only due to the portal's cache. Currently, it takes max 1 hour for the metadata update to appear.
Indeed dataset metadata comes from the Registry now, rather than the index.
At this time, the registry and portal do not store information about external datasets, such as those coming from KNB.
In lieu of these changes, [~ahahn@gbif.org] do you agree that we can close this user story?