[
https://issues.apache.org/jira/browse/CONNECTORS-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506787#comment-13506787
]
David Morana commented on CONNECTORS-573:
-----------------------------------------
I tried the path metadata and it will work in most cases but if there is a
slash in the filename it won't work correctly. I don't think there's a regex to
distinguish between folder slashes and a slash in a filename, is there? For
example, if we have this path in livelink Enterprise/folder1/RR/Suri/text, the
file name is actually Suri/text but the path metadata just returns text as the
filename.
Is there an easy work around for this? I have at least 6000 documents in
livelink with slashes in the document name, since slashes are currently allowed.
> 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
> Labels: patch
> Fix For: ManifoldCF 0.5.1, ManifoldCF next
>
>
> 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
