Bug in portal 2 registry process: agent.category not populated for installations of type IPT

11018
Reporter: kbraak
Assignee: kbraak
Type: Bug
Summary: Bug in portal 2 registry process: agent.category not populated for installations of type IPT
Priority: Major
Resolution: Duplicate
Status: Closed
Created: 2012-03-27 15:32:34.931
Updated: 2013-12-16 17:50:49.53
Resolved: 2012-06-20 14:59:41.736
        
Description: An agent of type technical installation has

agent.type = 14100

Then depending on its technical installation type the agent.category is set using these persistence codes:

http://staging.gbif.org:8080/enum-web/enum?id=org.gbif.registry.api.model.vocabulary.TechnicalInstallationType

For Tapir, for example:

agent.category = 20010

Currently the category IS being set for
DiGIR: http://staging.gbif.org:8080/registry-ws/technical_installation/1ea68ce2-6ea2-11e1-a453-a4093f22ed41
BioCASE: http://staging.gbif.org:8080/registry-ws/technical_installation/1eaa625e-6ea2-11e1-a453-a4093f22ed41
TAPIR: http://staging.gbif.org:8080/registry-ws/technical_installation/1eb0d0bc-6ea2-11e1-a453-a4093f22ed41

but NOT for an IPT (it should be agent.category = 20030 / IPT_INSTALLATION)

http://staging.gbif.org:8080/registry-ws/technical_installation/7f76fd20-adf9-11de-aa9e-a6c552d1d2c9

Please note: to get around this problem today, I will populate the missing fields for IPT's in the registry staging db. ]]>
    

Author: fmendez@gbif.org
Comment: The migrations scripts populate that field for IPTs, please validate if the error is at application level (service/persistence layer).
Created: 2012-06-20 14:57:16.097
Updated: 2012-06-20 14:57:16.097

Author: kbraak@gbif.org
Comment: Was fixed in REG-243. Closing issue.
Created: 2012-06-20 14:59:41.762
Updated: 2012-06-20 14:59:41.762