[
https://issues.apache.org/jira/browse/OODT-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann updated OODT-426:
-----------------------------------
Fix Version/s: (was: 0.5)
0.4
> Introduce a CAS-Metadata based renaming interface
> -------------------------------------------------
>
> Key: OODT-426
> URL: https://issues.apache.org/jira/browse/OODT-426
> Project: OODT
> Issue Type: Sub-task
> Components: crawler, metadata container, pge wrapper framework
> Affects Versions: 0.3
> Environment: none
> Reporter: Brian Foster
> Assignee: Brian Foster
> Priority: Minor
> Fix For: 0.4
>
> Attachments: OODT-426.2012-03-20.cas-crawler.patch.txt,
> OODT-426.2012-03-20.cas-metadata.patch.txt,
> OODT-426.2012-03-24.cas-crawler.patch.txt, OODT-426.2012-04-03.cas-pge.txt
>
>
> The idea here is that CAS-Metadata will introduce a new NamingConvention
> interface, which will allow for renaming of files. CAS-Crawler will then be
> modified to support specified NamingConventions which will be run after all
> preconditions have passed for a given file. This will then allow CAS-PGE to
> then use AutoDetectProductCrawler instead of StdProductCrawler, which will
> standardize across the board for file extraction (currently CAS-PGE has it's
> own file extraction interface which uses regular expression to determine
> files which should be extracted and ingested). The only missing feature in
> CAS-Crawler which CAS-PGE supports is file renaming, which this new
> NamingConvention interface will introduce. Here is what the NamingConvention
> interface will look like:
> {code}
> public interface NamingConvention {
> public File rename(File file, Metadata metadata)
> throws NamingConventionException;
> }
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
