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

Karl Wright commented on CONNECTORS-1117:
-----------------------------------------

Hi Nisala,

There are actually three deliverables:

- Repository connector for LiveLink using REST API
- Authority connector for LiveLink using REST API
- Integration testing

The capabilities of the connectors must mostly match the capabilities of the 
current legacy LiveLink connector.  You can see those sources at:

https://svn.apache.org/repos/asf/manifoldcf/trunk/connectors/livelink

Much of this project will therefore involve working with the LiveLink REST API 
in order to figure out how to go about achieving the same results as was done 
with LAPI.  It's therefore imperative that you have a LiveLink instance 
available you to work with -- we do not have one here.

For good examples of connectors implemented for REST API's, have a look at the 
Jira connector, under:

https://svn.apache.org/repos/asf/manifoldcf/trunk/connectors/jira

Thanks, and please let me know if you are still interested; I will have to go 
through the mentoring sign-up process if you are, and there are deadlines I'd 
have to meet, so please be as prompt as possible.



> Create a livelink connector using the LiveLink REST API
> -------------------------------------------------------
>
>                 Key: CONNECTORS-1117
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-1117
>             Project: ManifoldCF
>          Issue Type: Improvement
>          Components: LiveLink connector
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>              Labels: gsoc2015
>             Fix For: ManifoldCF 1.9, ManifoldCF 2.1
>
>
> LAPI is deprecated, so develop a connector that doesn't use it.
> Here's API documentation:
> https://developer.opentext.com/awd/forums/questions/1130441#r1130448



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to