Update gbif-metadata-profile following changes to schema on 12 Apr 2013

13135
Reporter: kbraak
Assignee: kbraak
Type: Improvement
Summary: Update gbif-metadata-profile following changes to schema on 12 Apr 2013
Priority: Major
Resolution: Fixed
Status: Closed
Created: 2013-04-12 16:47:11.719
Updated: 2015-03-02 15:47:20.516
Resolved: 2015-03-02 15:47:20.491
        
Description: A number of changes to the GBIF Metadata Profile schema have been made in https://code.google.com/p/gbif-metadata/source/detail?r=402

This requires changes to the model classes and freemarker template for example.

There are a number of projects that still depend on this library:
http://sonar.gbif.org/dependencies/index?search=org.gbif:gbif-metadata-profile

The IPT will likely try and use the registry-metadata project once the new version of the Registry-API and Registry-WS become available.

Do we also plan to do the same for DwC-A Validator, DwC-A Reader, Crawler CLI, etc? If so, the upgrade to gbif-metadata-profile doesn't really need to be done if no project will continue using it. ]]>
    

Author: kbraak@gbif.org
Comment: [~mdoering@gbif.org] could you please comment? Thanks
Created: 2013-04-12 16:48:08.58
Updated: 2013-04-12 16:48:08.58

Author: mdoering@gbif.org
Comment: [~trobertson@gbif.org] will port the current EML API classes to the new labs registry and we should try to use that new package exclusively then. I'm happy to update dwca-reader and validator once this is available
Created: 2013-04-12 17:22:39.892
Updated: 2013-04-12 17:22:39.892

Author: kbraak@gbif.org
Created: 2015-03-02 15:47:20.514
Updated: 2015-03-02 15:47:20.514
        
Closing issue as fixed.

For IPT v2.2 gbif-metadata-profile has been brought up to date for GBIF Metadata Profile v1.1

Only the IPT uses gbif-metadata-profile now.