Changeset 5308


Ignore:
Timestamp:
2003-08-27T16:35:36+12:00 (21 years ago)
Author:
jmt12
Message:

Always forcing extracted metadata caused 'hardcoded' metadata sets not to be loaded. Moved the adding of the extracted set to after the other metadata set testing is done

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/gli/src/org/greenstone/gatherer/collection/CollectionManager.java

    r5299 r5308  
    253253        msm = collection.msm; // Legacy
    254254        collection.msm.load();
    255         // Always import the extracted metadata set
    256         collection.msm.importMDS(new File(Utility.METADATA_DIR + Utility.EXTRACTED_METADATA_NAMESPACE + StaticStrings.METADATA_SET_EXTENSION), false);
     255
    257256        // Import default metadata sets if any.
    258257        for(int i = 0; metadata_sets != null && i < metadata_sets.size(); i++) {
     
    330329            }
    331330        }
     331        // Always import the extracted metadata set
     332        collection.msm.importMDS(new File(Utility.METADATA_DIR + Utility.EXTRACTED_METADATA_NAMESPACE + StaticStrings.METADATA_SET_EXTENSION), false);
    332333        // Do a dry metadata import run over the entire base collection, recording profile mappings. We do this by finding the archive files, and then iterating over them using the GreenstoneArchiveParser to retrieve metadata from them. We then process the importing of new metadata elements using the selectElement prompt used in a file action metadata import. However the big change is that we don't actually import any metadata, just create importing profiles.
    333334        if(!skip_import_phase) {
Note: See TracChangeset for help on using the changeset viewer.