CiviCRM Community Forums (archive)

Thanks.

Updates:

In today's meeting with Joe McLaughlin we discussed about mapping more fields between OSDI and Civi. We looked at common fields present on OSDI documentation ( here http://opensupporter.github.io/osdi-docs/ ) and discussed on the idea of adopting custom fields in place of those fields which are not present in Civi system.

Also Joe got a response from Jason Rosenbaum of Action Network over setting up the data communication between OSDI spec based servers for performing control actions. So I learned that I have to develop a person-signup helper which is a helper endpoint to aid in the creation of People resources via POST.

So I will now primarily focus on developing the person-signup helper which would allow me to perform these control actions and also I will map more relevant fields between the two systems.

Thanks.

Anudit, thanks. You don't think this library is useful for doing GET, POST, PUT, DELETE - https://github.com/Jmeyering/hal-explorer  ?

Updates:

Today in the weekly Hangout project check -in meeting with Joe McLaughlin, Eileen, Jason from Action Network and Josh Cohen from OSDI, I presented and reviewed my work done in past couple of weeks. I presented the basic person-sign helper which would allow the user to POST and add the data to people's collection resource. Right now I am currently testing it with CURL for POSTing the data to OSDI API sample-people's collection page and also I would test this on the other CiviCRM site which has been created by Eileen on the same camus server. These testing processes would also serve the purpose for checking the data communication and interoperability between different servers. Given below are the links for accessing these resources I worked on:

AEP: http://camus.fuzion.co.nz/hal-browser/browser.html#/sites/all/modules/civicrm/extern/osdi.php

Person-signup Helper: http://camus.fuzion.co.nz/sites/default/ext/osdi/api/v3/post.php
^This file has been removed from the server as the person-signup helper would not be form rather non-get options provided on the HAL-browser would be utilized for it.

Code on the Github : https://github.com/anuditverma/OSDI-Implementation/blob/master/api/v3/post.php

Next Targets:

I am planning to utilize this coming weekend to create and add a dedicated page for person-sign up helper to my custom extension by using the Civi resources. Further I would work on adding support for DELETE and then PUT.  Also Jason had been advising if I follow these methods in this particular order as “PUT is more complex and probably optional”.

So this weekend I would be engaged for achieving these targets and would report to the team on the daily project-check-in on Monday 7:30am IST

Updates:

Developed the person-sign up helper, now currently I am adding receiving endpoints (adding person's record in Civi system first, then will move on to other sites.) I'll push the code to git hub for review.

Updates:

Past couple of days I have been conversing with Eileen in an email correspondence about implementing REST calls for POSTing the data in the Civi system. I used var_dump method and checked console logs for getting details about the data posted into the system and checked if civi is blocking the POST requests. But working with REST calls stands ineffective so In today's daily project check-in meeting with Joe McLaughlin and Eileen, after discussing more about POSTing data, I have decided to use PHP method for this functionality and I would be implementing the debug code into it to check its working. Also I am simultaneously working on remaining issues raised on the github repository.

Updates:

I have added PUT & DELETE support on the person signup helper's end point but in yesterday's weekly OSDI Tech committee meeting when I discussed these updates with Josh and Jason so they mentioned that PUT & DELETE should be available on the person's endpoint instead of person signup helper's endpoint.

So I have raised this issue on my repository along with few minor issues which will be fixed very soon. On the daily check-in meeting, Joe McLaughlin and I have decided to get a final review on the project from the team members in the next weekly Hangout meeting and of course feedback from the community members are always welcomed and appreciated.
Link to the repository : https://github.com/anuditverma/org.civicrm.osdi

I am looking forward to the next week that will be utilized for finalizing the documentation, project summary and fixes to close the remaining issues.
Thanks.