PDA

View Full Version : any machine-parseable mode? (xmlrpc,soap,whatever)


gabor
06-07-04, 06:46 AM
hi,

i would like to use some other tools to extract data from dotProject. maybe also to insert some data into it.

does dotProject offer any way to get info from it in a non-html way?

like i send an xml with my username and password and some other info,
and for example he sends me back my last 10 task logs (just an example).

is there anything like that? (if not, then i will add a feat. req. ;)

thanks

ajdonnison
06-07-04, 09:13 AM
At the moment the only non-HTML way is to interrogate the database. This could be done using any database reporting tool, and an ODBC driver for MySQL.

cyberhorse
06-07-04, 11:29 PM
I have started work on an import/export module, which ideally will support different formats ... xml is second on the list. Let me know exactly what type of operations you would like to do so I bare it in mind while developing :)

mytto
09-07-04, 02:38 AM
cyberhorse: I'm very interesting in your import/export module. I'm working on this kind of topic most of my work time. Be aware of not reinventing the wheel (SQL/ODBC) however.

For what concerns exports: CSV, pure XML, RSS are good candidates from my perspective.

Import is much more troublesome. SOAP or XMLRPC could be useful but are very coder unfriendly, and other protocol or languages.

Please, give your thoughts...

cyberhorse
09-07-04, 05:03 PM
What I have so far is on dotmods cvs - import_export module
(cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/dotmods login

cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/dotmods co import_export)

it is in early stages of development and there is work only for sql, but you can get the idea.

The way it's going sql should be done within a week - the only major thing left to deal with is handling dynamic parent ids (ie. when you import a project, you remember it's id and pass it to tasks and other related items that you import with it). I have an idea how to do it - just have to try it out ...

I've structured the code in a way that will make it export to csv and xml really easy I think. csv should be easier to deal with than sql anyway

If you have time to look at what I have so far and you have any suggestions whatsoever - pleace let me know.