[
https://issues.apache.org/jira/browse/CONNECTORS-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14165211#comment-14165211
]
Karl Wright commented on CONNECTORS-1069:
-----------------------------------------
Hi Mary,
Please have a look at:
https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.7.1
If you look at the MCF source tree, among others you will see the following
high-level directories:
- framework
- connectors
Under the "connectors" directory are all the connectors that ManifoldCF
includes. In each such directory, you will find a "build.xml" file. This file
contains the ant build script for the connector.
Each connector builds against the distribution ("dist") directory. In order to
use the connector's build.xml script, you need to tell it where to find the
dist directory. You can either put your connector in the tree under
"connectors", OR set the MCF_DIST environment variable to point to the dist
area. After that you should be able to build your connector, and even have its
jars installed in the dist area and included in the connectors.xml registry
file with all the other connectors.
If I were you, I would use the ant build, and organize my connector's code in a
manner similar to that which you find for other connectors. You are also free
to make use of code and techniques from other connectors to do what you need to
do. I am available to answer questions you may have. I would also advise you
to read chapters 5 and 6 because they go over the ground rules that all
connectors must follow.
Thanks.
> Transformer or hook to allow tagging data at ingestion time
> -----------------------------------------------------------
>
> Key: CONNECTORS-1069
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1069
> Project: ManifoldCF
> Issue Type: Bug
> Components: LiveLink connector
> Affects Versions: ManifoldCF 1.7
> Environment: Redhat Linux, Tomcat Apache
> Reporter: Mary Green White
> Labels: Ingestion, LiveLink, Tagging
> Fix For: ManifoldCF 1.7
>
>
> We need the ability to create dynamic fields for metadata about documents in
> livelink. For example, we want to analyze the file name at ingestion time at
> determine the application type and create a field in the index called
> applicationType which is set to WORD for mimetypes of word and so on. Is
> there a hook or method available currently to be able to accomplish this type
> of functionality?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)