Refactor field names in database (Agent.type, Agent.subtype etc)

10906
Reporter: trobertson
Assignee: kbraak
Type: Improvement
Summary: Refactor field names in database (Agent.type, Agent.subtype etc)
Priority: Major
Resolution: Fixed
Status: Closed
Created: 2012-02-22 07:49:54.252
Updated: 2013-12-16 17:50:52.456
Resolved: 2012-03-07 16:48:10.957
        
Description: We now have
  Agent.agent_type_id;
  Agent.type;
  Agent.subtype;

The following suggestions have been agreed upon by the team:

- rename Agent.agent_type_id to type and apply this to all the tables (service.type etc).
- rename Agent.type to category
- rename Agent.subtype to subcategory

Note that this affects the MyBATIS layer, and Agent, Service etc tables but the persistence API layer remains unaffected since they are all ENUMs
]]>
    

Author: kbraak@gbif.org
Comment: agent_type_id, type, and subtype fields in db have now been refactored according to the above instructions. 
Created: 2012-03-06 17:03:50.523
Updated: 2012-03-06 17:03:50.523

Author: kbraak@gbif.org
Comment: Issue resolved. Field names refactored and are properly populated for Agents of type Dataset. 
Created: 2012-03-07 16:48:10.977
Updated: 2012-03-07 16:48:10.977