Ignore:
Timestamp:
2019-03-04T15:49:22+13:00 (5 years ago)
Author:
ak19
Message:

Undoing 32841 afgter discussion with Dr Bainbridge who worked out that forcing metamode to be written out as override has no meaning in doc.xml files.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • main/trunk/greenstone2/perllib/cgiactions/modmetadataaction.pm

    r32841 r32849  
    859859                $attrHash->{'_content'} = $metavalue;
    860860               
    861                 print STDERR "**** WARNING, NOT SURE IF IT'S ALWAYS THE RIGHT TO DO, but setting metamode to override as requested";
    862                
    863                 $attrHash->{'mode'} = $metamode; # if it was set to accumulate the first time this meta was added, make sure it is set to override now
     861                # until we have clearly determined the role of metamode in doc.xml files (we know what it means in import/metadata.xml files)
     862                # we're not setting metamode to override here.
    864863               
    865864                # Don't want it to wipe out any other pieces of metadata
     
    873872                $attrHash->{'_content'} = $metavalue;
    874873               
    875                 print STDERR "**** WARNING, NOT SURE IF IT'S ALWAYS THE RIGHT TO DO, but setting metamode to override as requested";
    876                 $attrHash->{'mode'} = $metamode; # if it was set to accumulate the first time this meta was added, make sure it is set to override now
     874                # until we have clearly determined the role of metamode in doc.xml files (we know what it means in import/metadata.xml files)
     875                # we're not setting metamode to override here.
    877876               
    878877                $parser->{'parameters'}->{'metamode'} = "done";
Note: See TracChangeset for help on using the changeset viewer.