Occurrence datasets not associated to a technical service

11497
Reporter: fmendez
Assignee: fmendez
Type: Bug
Summary: Occurrence datasets not associated to a technical service
Priority: Minor
Resolution: Fixed
Status: Closed
Created: 2012-06-26 14:43:36.586
Updated: 2013-12-16 17:50:51.73
Resolved: 2013-07-30 09:33:57.648
        
Description: This list can be retrieved by using:
SELECT ar.from_agent_id,a.* FROM agent a
LEFT OUTER JOIN service s ON s.agent_id = a.id AND s.deleted IS NULL
JOIN agent_relation ar ON ar.to_agent_id = a.id AND ar.deleted IS NULL
WHERE a.type = 14020 AND a.deleted IS NULL AND s.id IS NULL AND a.category = 18010

Most of the services are related to checklist 'The Catalogue of Life Partnership']]>
    

Author: mdoering@gbif.org
Created: 2012-06-26 15:50:30.328
Updated: 2012-06-26 15:50:30.328
        
There should be no occurrence dataset linked to  'The Catalogue of Life Partnership' as far as I know.
What db is this and can you give one example?
    

Author: jcuadra@gbif.org
Comment: I think the problem here is that these resources where migrated into the registry_uat (new registry) as simple RESOURCEs from the current live registry and unfortunatedly this live-registry does not support resource categories. I am asumming the migration script just sets the category automatically to 18010 (OCCURRENCE) for all resources. I think this will be part of the manual curating of the migrated-new registry.
Created: 2012-06-26 16:12:45.856
Updated: 2012-06-26 16:13:16.974

Author: jcuadra@gbif.org
Comment: Well, there is an option to inspect the service_type for each resource and according to that, make the decision whether it is an OCCURRENCE or CHECKLIST type. But I really don't know how the migration script behaves in this sense...
Created: 2012-06-26 16:15:44.086
Updated: 2012-06-26 16:15:44.086

Author: mdoering@gbif.org
Comment: it could simply make all resources linked to CoL a checklist type dataset.
Created: 2012-06-26 16:17:53.705
Updated: 2012-06-26 16:17:53.705

Author: fmendez@gbif.org
Comment: this was fixed a long time ago
Created: 2013-07-30 09:33:57.678
Updated: 2013-07-30 09:33:57.678