Description of problem: When Importing the LGCL into APLAWS+ every <item> seems to have the preferred attribute set to "true". Version-Release number of selected component (if applicable): How reproducible: Always This is something Dan discovered looking at the database. Not sure you would be able to reproduce this behaviour other than by looking at the Category chooser widget. For example, if you choose the following category: LGCL --> Community & Living --> Charities You will see three categories under Charities. These three categories are: <Item Id="104" AddedInVersion="1.00" LastUpdatedInVersion="1.00" AToZ="false" Preferred="false"> <Name>Charity collections</Name> <ScopeNotes /> <BroaderItem Id="103" Default="true">Charities</BroaderItem> <UseItem Id="103">Charities</UseItem> </Item> <Item Id="105" AddedInVersion="1.00" LastUpdatedInVersion="1.00" AToZ="false" Preferred="false"> <Name>Charity register</Name> <ScopeNotes /> <BroaderItem Id="103" Default="true">Charities</BroaderItem> <UseItem Id="103">Charities</UseItem> </Item> <Item Id="106" AddedInVersion="1.00" LastUpdatedInVersion="1.00" AToZ="false" Preferred="false"> <Name>Charity shops</Name> <ScopeNotes /> <BroaderItem Id="103" Default="true">Charities</BroaderItem> <BroaderItem Id="184" Default="false">Voluntary organisations</BroaderItem> <UseItem Id="103">Charities</UseItem> <UseItem Id="184">Voluntary organisations</UseItem> </Item> As you see they all have the preferred="false" attribute but still appear in the Category widget. The bug could be that they all get imported with preferred="true" or that the UI is displaying all categories regardless of true|false in preferred attribute
The implementation of preferred terms in the importer was incorrect, being based on the equivalents mapping instead of the 'Preferred' attribute in the hierarchy mapping. The terms application will be updated to fix this mistake. Existing data will be upgradable merely be re-running the hierarchy builder on the new data files. Preferred status will be modelled using the 'isEnabled' flag on categories. Thus non-preferred terms will still be visible in the category admin tabs, but will be hidden from the authoring kit & public navigation pages. The first part of this work is completed in p4 40596 (cf bz 110728)
THe second part of the work is done in p4 40599. Need to run data model upgrade and re-import all the hierarchy xml files.