Create occurrence service to retrieve single Occurrence details

11559
Reporter: mdoering
Assignee: mdoering
Type: NewFeature
Summary: Create occurrence service to retrieve single Occurrence details
Description: Requires new project or can we add a new service to the download project?
Priority: Major
Resolution: Fixed
Status: Closed
Created: 2012-07-12 16:55:31.372
Updated: 2013-12-17 15:17:00.978
Resolved: 2012-08-02 15:11:22.457

Author: omeyn@gbif.org
Comment: In discussion with Lars we decided that tidiest would be to create an occurrence project that is separate from the download project. This new project would follow our current pattern with separate api, service/ws, and ws-client projects. They can be a multi-module mvn project, and can in turn be part of an over-arching parent "occurrence-store project" (naming?) that would include the download, occurrence and presumably search projects.
Created: 2012-07-13 17:03:24.003
Updated: 2012-07-13 17:03:24.003

Author: mdoering@gbif.org
Comment: I find it cleaner to merge all occurrence related services into 1 multi module project, but if you both think differently ok. Just remember that the search in both registry and checklist bank is just a set of modules and not a separate project.
Created: 2012-07-17 09:56:13.612
Updated: 2012-07-17 09:56:13.612

Author: trobertson@gbif.org
Comment: In doing that, please consider combining the CRUD API and Search API into the occurrence-ws project.  We have intentions to consider the same for the registry-ws and registry-search-ws as the search one is simply a proxy to SOLR.  I presume the same will apply for occurrence.
Created: 2012-07-17 10:12:06.533
Updated: 2012-07-17 10:12:06.533