[ 
https://issues.apache.org/jira/browse/CONNECTORS-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507335#comment-13507335
 ] 

Karl Wright commented on CONNECTORS-573:
----------------------------------------

If you were truly running on 0.5.1, you are quite far behind and therefore a 
patch would be dicey.  I would certainly upgrade at this point.  You could 
either download 1.0.1 and patch it, or if you are particularly optimistic, just 
try running trunk.  To do that just check out trunk, and build it according to 
the instructions in the "how to build and deploy" page online.


                
> Can we improve the LivelinkConnector to return the document name in Livelink?
> -----------------------------------------------------------------------------
>
>                 Key: CONNECTORS-573
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-573
>             Project: ManifoldCF
>          Issue Type: Improvement
>          Components: LiveLink connector
>    Affects Versions: ManifoldCF 0.5.1, ManifoldCF 0.6, ManifoldCF 1.0, 
> ManifoldCF 1.0.1
>         Environment: I'm running ManifoldCF v.5.1. with Solr 4.0 and OpenText 
> v10.5
>            Reporter: David Morana
>            Assignee: Karl Wright
>              Labels: patch
>             Fix For: ManifoldCF 1.1
>
>
> I noticed that when I crawl Livelink; Solr gets the extended metadata from 
> livelink (cats and atts) and the metadata from the document itself. 
> It doesn't appear to grab the *general* metadata from livelink (i.e. the 
> Livelink document name; which is what I desperately need).
> Can you verify this? Or am I missing something?
> I also examined the LivelinkConnector.java file in github and I think a patch 
> can be inserted around line 1055 to 1068 where you perform a LAPI call to 
> GetObjectInfo to retrieve the file name and add it into the category 
> attribute data returned.
>  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to