[
https://issues.apache.org/jira/browse/OODT-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020724#comment-13020724
]
Chris A. Mattmann commented on OODT-173:
----------------------------------------
I made the extractor a bit less brittle in r1094100. Now you can omit
specifying:
{code:xml}
<group name="TokenNameList">
..
</group>
{code}
or
{code:xml}
<group name="SubstringOffsetGroup">
...
</group>
{code}
In your config file and the extractor will not throw an exception.
> Improvements to the Filename Extractor
> --------------------------------------
>
> Key: OODT-173
> URL: https://issues.apache.org/jira/browse/OODT-173
> Project: OODT
> Issue Type: Improvement
> Components: metadata container
> Environment: indep. of env.
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Labels: cas, extractor, filename, metadata, oodt
> Fix For: 0.3
>
>
> We've been building out some improvements to the FilenameExtractor as part of
> the Children's Hospital Efforts. Specifically, we've been building:
> * the ability to specify token groups and then flow out what Met Field names
> those tokens flow into
> - this allows for arbitrary string extraction groups, not having to do with
> specific filename tok delimeters by tok size (as is the current way the
> extractor works)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
