reintegrate reporting on indexing issues for data portal (gbif_log_message)

10607
Reporter: ahahn
Assignee: trobertson
Type: Improvement
Summary: reintegrate reporting on indexing issues for data portal (gbif_log_message)
Priority: Critical
Resolution: WontFix
Status: Closed
Created: 2012-01-09 15:33:03.878
Updated: 2016-02-25 13:42:23.136
Resolved: 2013-09-27 19:32:23.176
        
Description: Previously, messages on issues detected during extraction were written to the gbif_log_message table of the index, and reported summarised under a "Processing" step in the data tracking area (e.g. http://data.gbif.org/datasets/resource/13037/indexing/, in parallel to "Harvesting steps in the table at the bottom. This is used by data publishers to actively work on correcting such issues, and is regularly advertised by us as one of the quality improvement measures when people ask about data quality and reporting. Presently, not even old Processing messages seem to be available any more, so that currently there is no possibility to follow up on such issues.

Need to re-integrate this kind of reporting into the data portal.]]>
    

Author: ahahn@gbif.org
Created: 2012-01-19 13:45:33.993
Updated: 2012-01-19 13:50:35.189
        
Related issue: on an issue overview for a dataset (sample query below), the individual entries used to contain links back to the record itself. Those links got lost, so that it is currently not possible for a data publisher to make use of the error messages, especially since the record id are no longer displayed either

http://data.gbif.org/datasets/resource/12677/logs/?event=1001-1999&logGroup=&logLevel=40000&sd_day=15&sd_month=12&sd_year=2010&ed_day=20&ed_month=01&ed_year=2012

(user enquiry: 19.1.12)
    

Author: mdoering@gbif.org
Comment: We should really consider to maintain stable ids for occurrences too - or do we already?
Created: 2012-01-19 13:57:17.216
Updated: 2012-01-19 13:57:17.216

Author: ahahn@gbif.org
Comment: We do, but only as long as the records keep being served through the same dataset (and institutionCode/collectionCode/catalogNumber do not change). As long as this is the case, existing records get updated at re-indexing. Once deleted, however, an occurrence ID never gets resurrected, so that records that are deleted and then republished will change IDs.
Created: 2012-01-23 11:43:01.687
Updated: 2012-01-23 11:43:01.687

Author: trobertson@gbif.org
Comment: Will be readdressed in new portal
Created: 2013-09-27 19:32:23.206
Updated: 2013-09-27 19:32:23.206