Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
0.2
-
None
-
none
Description
Instead of <_comment> element in Tika mime-type file being use as ProductType value, the value will became a key value list of metadata fields to be added to the RemoteFile metadata.
Example:
... <mime-type type="product/pgp_signature"> <_comment>ProductNameGenerator=[GREP_RM('\.sig&','[FILENAME]')]</_comment> <glob pattern="*.sig"/> </mime-type> <mime-type type="product/rtg_sst"> <sub-class-of type="ncep/model"/> <_comment>ProductType=RTG_SST && UniqueElement=RetrievedFromLoc</_comment> <glob pattern="rtg_sst_grb_0\.5\.\d{8}" isregex="true"/> <glob pattern="sst\.\d{8}_rtgssthr_grb_0\.5\.grib2" isregex="true"/> </mime-type> ...
The metadata field 'ProductNameGenerator' will be used to generate a dynamic ProductName. It can be set to any renaming convention supported by the second parameter for Pushpull's RenamingConvention static method: rename(ProtocolFile, String).
The metadata field 'UniqueElement' can be use to override the 'queryElement' attribute specified for the current daemon in the RemoteSpecs.xml <dataInfo> element.