dhis2.com now a.k.a. dhis2.org

Will both continue to work ( I can see they are working right now as least)?
I have been using the node-based URLs around the wiki.

Ola

···

2009/10/28 Bob Jolliffe bobjolliffe@gmail.com

OK. Enabled Path module (Clean URLs were already enabled) and now when you edit a page there is an option to set the “user friendly” url.

So before where we had http://dhis2.org/node/9 we now have http://dhis2.org/documentation. Cool.


Cheers
Bob

2009/10/28 Bob Jolliffe bobjolliffe@gmail.com

OK. Will take a quick look.

BTW came across this article yesterday regarding REST, Drupal and Xproc:
http://broadcast.oreilly.com/2009/03/xproc-xml-pipelines-and-restfu.html

Cheers
Bob

2009/10/28 Jo Størset storset@gmail.com

Den 28. okt. 2009 kl. 11.56 skrev Bob Jolliffe:

I think there is a drupal config option to enable clean urls. And it depends upon Apache’s modrewrite. pathauto is just extra sugar to auto magically do the clean url naming for you.

Cheers

Bob

Jo are you “adminning” the site? I can take a quick look if you like. I have the password.

I don´t have the password, so go ahead :slight_smile:

Jo


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Seems like the both work.

I had another question regarding the links to the Documentation guide
on this node. I have just updated the guide, but now the PDF on the
site is out of sync with the documentation source.

I would think that there must be some plugin that allows drupal to
render DocBook XML in the site. Is it possible to do this?

Another possibility would be somehow to produce continuous builds of
the documentation, so that the documentation is always up to date when
linked against the site. I think this would be possible through a
relatively minor shell script.

Suggestions? I can have a stab at constructing the shell script if it
is possible on the machine which houses the site.

Regards,
Jason

···

On Wed, Oct 28, 2009 at 3:32 PM, Ola Hodne Titlestad <olatitle@gmail.com> wrote:

2009/10/28 Bob Jolliffe <bobjolliffe@gmail.com>

OK. Enabled Path module (Clean URLs were already enabled) and now when
you edit a page there is an option to set the "user friendly" url.

So before where we had http://dhis2.org/node/9 we now have
http://dhis2.org/documentation. Cool.

Will both continue to work ( I can see they are working right now as least)?
I have been using the node-based URLs around the wiki.

Ola
---------

Cheers
Bob

2009/10/28 Bob Jolliffe <bobjolliffe@gmail.com>

OK. Will take a quick look.

BTW came across this article yesterday regarding REST, Drupal and Xproc:
Radar – O’Reilly

Cheers
Bob

2009/10/28 Jo Størset <storset@gmail.com>

Den 28. okt. 2009 kl. 11.56 skrev Bob Jolliffe:

I think there is a drupal config option to enable clean urls. And it
depends upon Apache's modrewrite. pathauto is just extra sugar to auto
magically do the clean url naming for you.

Cheers
Bob

Jo are you "adminning" the site? I can take a quick look if you like.
I have the password.

I don´t have the password, so go ahead :slight_smile:

Jo

_______________________________________________
Mailing list: DHIS 2 developers in Launchpad
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : DHIS 2 developers in Launchpad
More help : ListHelp - Launchpad Help

_______________________________________________
Mailing list: DHIS 2 developers in Launchpad
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : DHIS 2 developers in Launchpad
More help : ListHelp - Launchpad Help

Automatic update would be great.

The site is hosted by AN Hosting. There’s no ssh access unfortunately.

http://www.anhosting.com/

Lars

···

On Wed, Oct 28, 2009 at 2:40 PM, Jason Pickering jason.p.pickering@gmail.com wrote:

Seems like the both work.

I had another question regarding the links to the Documentation guide

on this node. I have just updated the guide, but now the PDF on the

site is out of sync with the documentation source.

I would think that there must be some plugin that allows drupal to

render DocBook XML in the site. Is it possible to do this?

Another possibility would be somehow to produce continuous builds of

the documentation, so that the documentation is always up to date when

linked against the site. I think this would be possible through a

relatively minor shell script.

Suggestions? I can have a stab at constructing the shell script if it

is possible on the machine which houses the site.

Regards,

Jason

It is cool. Thanks didn’t spot that. I have updated the rest of the pages.

···

On Wed, Oct 28, 2009 at 12:34 PM, Bob Jolliffe bobjolliffe@gmail.com wrote:

OK. Enabled Path module (Clean URLs were already enabled) and now when you edit a page there is an option to set the “user friendly” url.

So before where we had http://dhis2.org/node/9 we now have http://dhis2.org/documentation. Cool.

This is making the subdomains sort of redundant. I have removed them. The new URLs are:

dhis2.org/downloads
dhis2.org/documentation

dhis2.org/features
dhis2.org/functionality
dhis2.org/development
dhis2.org/about

···

On Wed, Oct 28, 2009 at 3:44 PM, Lars Helge Øverland larshelge@gmail.com wrote:

On Wed, Oct 28, 2009 at 12:34 PM, Bob Jolliffe bobjolliffe@gmail.com wrote:

OK. Enabled Path module (Clean URLs were already enabled) and now when you edit a page there is an option to set the “user friendly” url.

So before where we had http://dhis2.org/node/9 we now have http://dhis2.org/documentation. Cool.

It is cool. Thanks didn’t spot that. I have updated the rest of the pages.

You’re right. Made support folks enable SSH now.

Lars

···

2009/10/28 Lars Helge Øverland larshelge@gmail.com

2009/10/28 Jason Pickering jason.p.pickering@gmail.com

With every Mega web hosting plan you get:

was 500 GB NOW 625 GB Web Hosting Disk Space

was 5000 GB NOW 6250 GB Bandwidth

Host up to 20 Domain Names

Unlimited MySQL dbs

SSH Included

Fantastico Library (Auto-Install over 90 free web apps)

Unlimited FTP Accounts

Unlimited Subdomains

Unlimited E-mail Addresses

Toll-free 24/7 Phone, Ticket, and Live Chat Support

No Mega Web Hosting plan?

I plan to set up a hudson [1] server at uio for continous builds from bazaar, asap. Maybe it could help?

[1] http://hudson-ci.org/

Jo

···

Den 28. okt. 2009 kl. 14.40 skrev Jason Pickering:

Seems like the both work.

I had another question regarding the links to the Documentation guide
on this node. I have just updated the guide, but now the PDF on the
site is out of sync with the documentation source.

I would think that there must be some plugin that allows drupal to
render DocBook XML in the site. Is it possible to do this?

Another possibility would be somehow to produce continuous builds of
the documentation, so that the documentation is always up to date when
linked against the site. I think this would be possible through a
relatively minor shell script.

Yeah, I think this would do the trick.

I do not think it would be possible to get bzr, mvn, and other tools
on the dhis2.com site. Having this server, combined with a cron job on
the dhis2.com site to pull fresh builds via rsync/wget on a regular
basis that do not require actually building the source on the
dhis2.com site, seems like it should work.

···

On Wed, Oct 28, 2009 at 7:06 PM, Jo Størset <storset@gmail.com> wrote:

Den 28. okt. 2009 kl. 14.40 skrev Jason Pickering:

Seems like the both work.

I had another question regarding the links to the Documentation guide
on this node. I have just updated the guide, but now the PDF on the
site is out of sync with the documentation source.

I would think that there must be some plugin that allows drupal to
render DocBook XML in the site. Is it possible to do this?

Another possibility would be somehow to produce continuous builds of
the documentation, so that the documentation is always up to date when
linked against the site. I think this would be possible through a
relatively minor shell script.

I plan to set up a hudson [1] server at uio for continous builds from
bazaar, asap. Maybe it could help?

[1] http://hudson-ci.org/

Jo

Ideally, you would just want to point the download link/download subdomain to the ci build that is generated on the uio server. No need for ssh, wget or anything else.

Hudson would be able to get the latest commit from launchpad using the bazaar plugin and start its build with different configurations (tests, javadoc, war, installer, whatever branches etc)

···

Regards,
Saptarshi PURKAYASTHA
Director R & D, HISP India
Health Information Systems Programme

My Tech Blog: http://sunnytalkstech.blogspot.com

You Live by CHOICE, Not by CHANCE

2009/10/28 Jason Pickering jason.p.pickering@gmail.com

Yeah, I think this would do the trick.

I do not think it would be possible to get bzr, mvn, and other tools

on the dhis2.com site. Having this server, combined with a cron job on

the dhis2.com site to pull fresh builds via rsync/wget on a regular

basis that do not require actually building the source on the

dhis2.com site, seems like it should work.

On Wed, Oct 28, 2009 at 7:06 PM, Jo Størset storset@gmail.com wrote:

Den 28. okt. 2009 kl. 14.40 skrev Jason Pickering:

Seems like the both work.

I had another question regarding the links to the Documentation guide

on this node. I have just updated the guide, but now the PDF on the

site is out of sync with the documentation source.

I would think that there must be some plugin that allows drupal to

render DocBook XML in the site. Is it possible to do this?

Another possibility would be somehow to produce continuous builds of

the documentation, so that the documentation is always up to date when

linked against the site. I think this would be possible through a

relatively minor shell script.

I plan to set up a hudson [1] server at uio for continous builds from

bazaar, asap. Maybe it could help?

[1] http://hudson-ci.org/

Jo


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Yeah, this would work as well, but I was considering bandwidth as
well. Not that we have that many downloads as far as I know, but it
would make more sense to me at least, to seperate the ci process from
the actually process of downloading it, which is probably best managed
by a web server. I guess either way would work though.

···

On Wed, Oct 28, 2009 at 7:55 PM, Saptarshi Purkayastha <sunbiz@gmail.com> wrote:

Ideally, you would just want to point the download link/download subdomain
to the ci build that is generated on the uio server. No need for ssh, wget
or anything else.
Hudson would be able to get the latest commit from launchpad using the
bazaar plugin and start its build with different configurations (tests,
javadoc, war, installer, whatever branches etc)

---
Regards,
Saptarshi PURKAYASTHA
Director R & D, HISP India
Health Information Systems Programme

My Tech Blog: http://sunnytalkstech.blogspot.com
You Live by CHOICE, Not by CHANCE

2009/10/28 Jason Pickering <jason.p.pickering@gmail.com>

Yeah, I think this would do the trick.

I do not think it would be possible to get bzr, mvn, and other tools
on the dhis2.com site. Having this server, combined with a cron job on
the dhis2.com site to pull fresh builds via rsync/wget on a regular
basis that do not require actually building the source on the
dhis2.com site, seems like it should work.

On Wed, Oct 28, 2009 at 7:06 PM, Jo Størset <storset@gmail.com> wrote:
>
> Den 28. okt. 2009 kl. 14.40 skrev Jason Pickering:
>
>> Seems like the both work.
>>
>> I had another question regarding the links to the Documentation guide
>> on this node. I have just updated the guide, but now the PDF on the
>> site is out of sync with the documentation source.
>>
>> I would think that there must be some plugin that allows drupal to
>> render DocBook XML in the site. Is it possible to do this?
>>
>> Another possibility would be somehow to produce continuous builds of
>> the documentation, so that the documentation is always up to date when
>> linked against the site. I think this would be possible through a
>> relatively minor shell script.
>
> I plan to set up a hudson [1] server at uio for continous builds from
> bazaar, asap. Maybe it could help?
>
> [1] http://hudson-ci.org/
>
> Jo
>

_______________________________________________
Mailing list: DHIS 2 developers in Launchpad
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : DHIS 2 developers in Launchpad
More help : ListHelp - Launchpad Help

The university can handle the load much better than us. So I agree with Saptarshi - no need to copy to dhis2.org

k

···

On Wed, Oct 28, 2009 at 7:16 PM, Jason Pickering jason.p.pickering@gmail.com wrote:

Yeah, this would work as well, but I was considering bandwidth as

well. Not that we have that many downloads as far as I know, but it

would make more sense to me at least, to seperate the ci process from

the actually process of downloading it, which is probably best managed

by a web server. I guess either way would work though.

On Wed, Oct 28, 2009 at 7:55 PM, Saptarshi Purkayastha sunbiz@gmail.com wrote:

Ideally, you would just want to point the download link/download subdomain

to the ci build that is generated on the uio server. No need for ssh, wget

or anything else.

Hudson would be able to get the latest commit from launchpad using the

bazaar plugin and start its build with different configurations (tests,

javadoc, war, installer, whatever branches etc)


Regards,

Saptarshi PURKAYASTHA

Director R & D, HISP India

Health Information Systems Programme

My Tech Blog: http://sunnytalkstech.blogspot.com

You Live by CHOICE, Not by CHANCE

2009/10/28 Jason Pickering jason.p.pickering@gmail.com

Yeah, I think this would do the trick.

I do not think it would be possible to get bzr, mvn, and other tools

on the dhis2.com site. Having this server, combined with a cron job on

the dhis2.com site to pull fresh builds via rsync/wget on a regular

basis that do not require actually building the source on the

dhis2.com site, seems like it should work.

On Wed, Oct 28, 2009 at 7:06 PM, Jo Størset storset@gmail.com wrote:

Den 28. okt. 2009 kl. 14.40 skrev Jason Pickering:

Seems like the both work.

I had another question regarding the links to the Documentation guide

on this node. I have just updated the guide, but now the PDF on the

site is out of sync with the documentation source.

I would think that there must be some plugin that allows drupal to

render DocBook XML in the site. Is it possible to do this?

Another possibility would be somehow to produce continuous builds of

the documentation, so that the documentation is always up to date when

linked against the site. I think this would be possible through a

relatively minor shell script.

I plan to set up a hudson [1] server at uio for continous builds from

bazaar, asap. Maybe it could help?

[1] http://hudson-ci.org/

Jo


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Cheers,
Knut Staring

Hi Jason

Seems like the both work.

I had another question regarding the links to the Documentation guide

on this node. I have just updated the guide, but now the PDF on the

site is out of sync with the documentation source.

I would think that there must be some plugin that allows drupal to

render DocBook XML in the site. Is it possible to do this?

Don’t know drupal well enough but in principle this is possible. The docbook rendering is all done through xslt which can certainly be pushed around through PHP, though the amount of rendering required would be heavy to do on each request.

Another possibility would be somehow to produce continuous builds of

the documentation, so that the documentation is always up to date when

linked against the site. I think this would be possible through a

relatively minor shell script.

Suggestions? I can have a stab at constructing the shell script if it

is possible on the machine which houses the site.

Up till now we haven’t had shell access to the site. Now I think we do I think we might be able to make a plan.

Regards
Bob

···

2009/10/28 Jason Pickering jason.p.pickering@gmail.com

Regards,

Jason

On Wed, Oct 28, 2009 at 3:32 PM, Ola Hodne Titlestad olatitle@gmail.com wrote:

2009/10/28 Bob Jolliffe bobjolliffe@gmail.com

OK. Enabled Path module (Clean URLs were already enabled) and now when

you edit a page there is an option to set the “user friendly” url.

So before where we had http://dhis2.org/node/9 we now have

http://dhis2.org/documentation. Cool.

Will both continue to work ( I can see they are working right now as least)?

I have been using the node-based URLs around the wiki.

Ola


Cheers

Bob

2009/10/28 Bob Jolliffe bobjolliffe@gmail.com

OK. Will take a quick look.

BTW came across this article yesterday regarding REST, Drupal and Xproc:

http://broadcast.oreilly.com/2009/03/xproc-xml-pipelines-and-restfu.html

Cheers

Bob

2009/10/28 Jo Størset storset@gmail.com

Den 28. okt. 2009 kl. 11.56 skrev Bob Jolliffe:

I think there is a drupal config option to enable clean urls. And it

depends upon Apache’s modrewrite. pathauto is just extra sugar to auto

magically do the clean url naming for you.

Cheers

Bob

Jo are you “adminning” the site? I can take a quick look if you like.

I have the password.

I don´t have the password, so go ahead :slight_smile:

Jo


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

On the topic of dhis2.org, I would appreciate some input on hisp.info. I would like to retire the old Confluence wiki soon.

We do get quite a number of hits to that domain, so we should point it to dhis2.org. But there may still be useful stuff there that must be replicated on dhis2.org first? What is still of value?

However, in my opinion, we do still need somewhere which people can edit. I am personally happy to do my edits at http://phitoolkit.org (and will give write access to anyone who asks).

Or we could add a blog or wiki module to Drupal.

Knut

···

On Wed, Oct 28, 2009 at 11:19 PM, Bob Jolliffe bobjolliffe@gmail.com wrote:

Hi Jason

2009/10/28 Jason Pickering jason.p.pickering@gmail.com

Seems like the both work.

I had another question regarding the links to the Documentation guide

on this node. I have just updated the guide, but now the PDF on the

site is out of sync with the documentation source.

I would think that there must be some plugin that allows drupal to

render DocBook XML in the site. Is it possible to do this?

Don’t know drupal well enough but in principle this is possible. The docbook rendering is all done through xslt which can certainly be pushed around through PHP, though the amount of rendering required would be heavy to do on each request.

Another possibility would be somehow to produce continuous builds of

the documentation, so that the documentation is always up to date when

linked against the site. I think this would be possible through a

relatively minor shell script.

Suggestions? I can have a stab at constructing the shell script if it

is possible on the machine which houses the site.

Up till now we haven’t had shell access to the site. Now I think we do I think we might be able to make a plan.

Regards
Bob

Regards,

Jason

On Wed, Oct 28, 2009 at 3:32 PM, Ola Hodne Titlestad olatitle@gmail.com wrote:

2009/10/28 Bob Jolliffe bobjolliffe@gmail.com

OK. Enabled Path module (Clean URLs were already enabled) and now when

you edit a page there is an option to set the “user friendly” url.

So before where we had http://dhis2.org/node/9 we now have

http://dhis2.org/documentation. Cool.

Will both continue to work ( I can see they are working right now as least)?

I have been using the node-based URLs around the wiki.

Ola


Cheers

Bob

2009/10/28 Bob Jolliffe bobjolliffe@gmail.com

OK. Will take a quick look.

BTW came across this article yesterday regarding REST, Drupal and Xproc:

http://broadcast.oreilly.com/2009/03/xproc-xml-pipelines-and-restfu.html

Cheers

Bob

2009/10/28 Jo Størset storset@gmail.com

Den 28. okt. 2009 kl. 11.56 skrev Bob Jolliffe:

I think there is a drupal config option to enable clean urls. And it

depends upon Apache’s modrewrite. pathauto is just extra sugar to auto

magically do the clean url naming for you.

Cheers

Bob

Jo are you “adminning” the site? I can take a quick look if you like.

I have the password.

I don´t have the password, so go ahead :slight_smile:

Jo


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Cheers,
Knut Staring

Actually Jo is working on a new HISP site in the UiO domain, we were thinking this domain should be redirected here.

Lars

···

On Thu, Oct 29, 2009 at 7:58 AM, Knut Staring knutst@gmail.com wrote:

On the topic of dhis2.org, I would appreciate some input on hisp.info. I would like to retire the old Confluence wiki soon.

We do get quite a number of hits to that domain, so we should point it to dhis2.org. But there may still be useful stuff there that must be replicated on dhis2.org first? What is still of value?

The rest of the content of this mail can be ignored, but anyway, my
feelings on this.

<flame>
We MUST simplify the number of sites. I know of the following that are
related to DHIS

1) hisp.info
2) dhis2.org
3) dhis2.com
4) phitoolkit.org
5) openhealthconsortium.org
6) http://208.76.222.114
7) hispkerala.org
8) dhismobile.info
9) launchpad

I think there are probably others. I realize that some of these sites
serve different purposes to different groups, but IMHO, DHIS is a
great product that suffers from really poor marketing. Having
information spread across all these different sites spreads thin
resources and creates confusion among people trying to access
information on DHIS. We, as a community, need to consolidate all of
this information into a single portal at the least, and a single site
at best.

I honestly think, if there is anyway, to create a single site, that
has documentation, demos, links to the source code, a wiki for more
informal documentation, a forum, etc...this would be the way to go. I
personally favour dhis2.org because it sounds less commercial than
dhis2.com. Most people have no idea what HISP is (I have been trying
to figure out for years but still have not a very good grip on it
either!) and it really does not matter for those using the prodcuct
DHIS2 or 1.4, born out of HISP.

I

I think if the university can host the site, this would be the best
way to ensure sustainability. It is just a DNS record. After all the
investment the university has put into the product, they should be
able to host a DNS record after all.

</flame>

OK, I am done. Lets get a single site with all the information in one place.

Regards,
jason

···

On Thu, Oct 29, 2009 at 8:58 AM, Knut Staring <knutst@gmail.com> wrote:

On the topic of dhis2.org, I would appreciate some input on hisp.info. I
would like to retire the old Confluence wiki soon.

We do get quite a number of hits to that domain, so we should point it to
dhis2.org. But there may still be useful stuff there that must be replicated
on dhis2.org first? What is still of value?

However, in my opinion, we do still need somewhere which people can edit. I
am personally happy to do my edits at http://phitoolkit.org (and will give
write access to anyone who asks).
Or we could add a blog or wiki module to Drupal.

Knut

On Wed, Oct 28, 2009 at 11:19 PM, Bob Jolliffe <bobjolliffe@gmail.com> > wrote:

Hi Jason

2009/10/28 Jason Pickering <jason.p.pickering@gmail.com>

Seems like the both work.

I had another question regarding the links to the Documentation guide
on this node. I have just updated the guide, but now the PDF on the
site is out of sync with the documentation source.

I would think that there must be some plugin that allows drupal to
render DocBook XML in the site. Is it possible to do this?

Don't know drupal well enough but in principle this is possible. The
docbook rendering is all done through xslt which can certainly be pushed
around through PHP, though the amount of rendering required would be heavy
to do on each request.

Another possibility would be somehow to produce continuous builds of
the documentation, so that the documentation is always up to date when
linked against the site. I think this would be possible through a
relatively minor shell script.

Suggestions? I can have a stab at constructing the shell script if it
is possible on the machine which houses the site.

Up till now we haven't had shell access to the site. Now I think we do I
think we might be able to make a plan.

Regards
Bob

Regards,
Jason

On Wed, Oct 28, 2009 at 3:32 PM, Ola Hodne Titlestad <olatitle@gmail.com> >>> wrote:
> 2009/10/28 Bob Jolliffe <bobjolliffe@gmail.com>
>>
>> OK. Enabled Path module (Clean URLs were already enabled) and now
>> when
>> you edit a page there is an option to set the "user friendly" url.
>>
>> So before where we had http://dhis2.org/node/9 we now have
>> http://dhis2.org/documentation. Cool.
>>
> Will both continue to work ( I can see they are working right now as
> least)?
> I have been using the node-based URLs around the wiki.
>
> Ola
> ---------
>
>>
>> Cheers
>> Bob
>>
>> 2009/10/28 Bob Jolliffe <bobjolliffe@gmail.com>
>>>
>>> OK. Will take a quick look.
>>>
>>> BTW came across this article yesterday regarding REST, Drupal and
>>> Xproc:
>>>
>>> Radar – O’Reilly
>>>
>>> Cheers
>>> Bob
>>>
>>> 2009/10/28 Jo Størset <storset@gmail.com>
>>>>
>>>> Den 28. okt. 2009 kl. 11.56 skrev Bob Jolliffe:
>>>>
>>>>> I think there is a drupal config option to enable clean urls. And
>>>>> it
>>>>> depends upon Apache's modrewrite. pathauto is just extra sugar to
>>>>> auto
>>>>> magically do the clean url naming for you.
>>>>>
>>>>> Cheers
>>>>> Bob
>>>>>
>>>>> Jo are you "adminning" the site? I can take a quick look if you
>>>>> like.
>>>>> I have the password.
>>>>
>>>> I don´t have the password, so go ahead :slight_smile:
>>>>
>>>> Jo
>>
>>
>> _______________________________________________
>> Mailing list: DHIS 2 developers in Launchpad
>> Post to : dhis2-devs@lists.launchpad.net
>> Unsubscribe : DHIS 2 developers in Launchpad
>> More help : ListHelp - Launchpad Help
>>
>
>
> _______________________________________________
> Mailing list: DHIS 2 developers in Launchpad
> Post to : dhis2-devs@lists.launchpad.net
> Unsubscribe : DHIS 2 developers in Launchpad
> More help : ListHelp - Launchpad Help
>
>

_______________________________________________
Mailing list: DHIS 2 developers in Launchpad
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : DHIS 2 developers in Launchpad
More help : ListHelp - Launchpad Help

--
Cheers,
Knut Staring

Agree completely on the single site. I think drupal on dhis2.org could host all of it. I am not too worried where as long as we have ssh access. I suspect the demo server would have to run separately (php hosting vs java hosting?) but that is not a real problem.

Regards
Bob

···

2009/10/29 Jason Pickering jason.p.pickering@gmail.com

The rest of the content of this mail can be ignored, but anyway, my

feelings on this.

We MUST simplify the number of sites. I know of the following that are

related to DHIS

  1. hisp.info

  2. dhis2.org

  3. dhis2.com

  4. phitoolkit.org

  5. openhealthconsortium.org

  6. http://208.76.222.114

  7. hispkerala.org

  8. dhismobile.info

  9. launchpad

I think there are probably others. I realize that some of these sites

serve different purposes to different groups, but IMHO, DHIS is a

great product that suffers from really poor marketing. Having

information spread across all these different sites spreads thin

resources and creates confusion among people trying to access

information on DHIS. We, as a community, need to consolidate all of

this information into a single portal at the least, and a single site

at best.

I honestly think, if there is anyway, to create a single site, that

has documentation, demos, links to the source code, a wiki for more

informal documentation, a forum, etc…this would be the way to go. I

personally favour dhis2.org because it sounds less commercial than

dhis2.com. Most people have no idea what HISP is (I have been trying

to figure out for years but still have not a very good grip on it

either!) and it really does not matter for those using the prodcuct

DHIS2 or 1.4, born out of HISP.

I

I think if the university can host the site, this would be the best

way to ensure sustainability. It is just a DNS record. After all the

investment the university has put into the product, they should be

able to host a DNS record after all.

OK, I am done. Lets get a single site with all the information in one place.

Regards,

jason

On Thu, Oct 29, 2009 at 8:58 AM, Knut Staring knutst@gmail.com wrote:

On the topic of dhis2.org, I would appreciate some input on hisp.info. I

would like to retire the old Confluence wiki soon.

We do get quite a number of hits to that domain, so we should point it to

dhis2.org. But there may still be useful stuff there that must be replicated

on dhis2.org first? What is still of value?

However, in my opinion, we do still need somewhere which people can edit. I

am personally happy to do my edits at http://phitoolkit.org (and will give

write access to anyone who asks).

Or we could add a blog or wiki module to Drupal.

Knut

On Wed, Oct 28, 2009 at 11:19 PM, Bob Jolliffe bobjolliffe@gmail.com > > > wrote:

Hi Jason

2009/10/28 Jason Pickering jason.p.pickering@gmail.com

Seems like the both work.

I had another question regarding the links to the Documentation guide

on this node. I have just updated the guide, but now the PDF on the

site is out of sync with the documentation source.

I would think that there must be some plugin that allows drupal to

render DocBook XML in the site. Is it possible to do this?

Don’t know drupal well enough but in principle this is possible. The

docbook rendering is all done through xslt which can certainly be pushed

around through PHP, though the amount of rendering required would be heavy

to do on each request.

Another possibility would be somehow to produce continuous builds of

the documentation, so that the documentation is always up to date when

linked against the site. I think this would be possible through a

relatively minor shell script.

Suggestions? I can have a stab at constructing the shell script if it

is possible on the machine which houses the site.

Up till now we haven’t had shell access to the site. Now I think we do I

think we might be able to make a plan.

Regards

Bob

Regards,

Jason

On Wed, Oct 28, 2009 at 3:32 PM, Ola Hodne Titlestad olatitle@gmail.com > > >>> wrote:

2009/10/28 Bob Jolliffe bobjolliffe@gmail.com

OK. Enabled Path module (Clean URLs were already enabled) and now

when

you edit a page there is an option to set the “user friendly” url.

So before where we had http://dhis2.org/node/9 we now have

http://dhis2.org/documentation. Cool.

Will both continue to work ( I can see they are working right now as

least)?

I have been using the node-based URLs around the wiki.

Ola


Cheers

Bob

2009/10/28 Bob Jolliffe bobjolliffe@gmail.com

OK. Will take a quick look.

BTW came across this article yesterday regarding REST, Drupal and

Xproc:

http://broadcast.oreilly.com/2009/03/xproc-xml-pipelines-and-restfu.html

Cheers

Bob

2009/10/28 Jo Størset storset@gmail.com

Den 28. okt. 2009 kl. 11.56 skrev Bob Jolliffe:

I think there is a drupal config option to enable clean urls. And

it

depends upon Apache’s modrewrite. pathauto is just extra sugar to

auto

magically do the clean url naming for you.

Cheers

Bob

Jo are you “adminning” the site? I can take a quick look if you

like.

I have the password.

I don´t have the password, so go ahead :slight_smile:

Jo


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Cheers,

Knut Staring

Hi, we definitely need to consolidate the info. But in fact this is what we are working on right now, let me explain a little. The idea is this: one site for the software / product (dhis2.org), one collaboration platform (launchpad) and one site for the network (hisp).

  1. dhis2.org

  2. dhis2.com

The dhis2 site will contain what you mention; downloads, docs, developer page, functionality info, link to demo etc. Bob questioned the use of the .com domain which we took into consideration and changed to .org. From now on we will promote the .org domain. Still I think it makes sense to keep the .com domain as well, if someone hears of dhis2 and types in dhis2.com in his browser something should be there. I have sent a request to AN Hosting support to redirect the dhis2.com to dhis2.org, rather than having it as a “parked” domain. Also, we will move the actual downloadable files to this server.

  1. launchpad.net

Launchpad, as you know, provides version control, issue management, bug tracking. This in in fact not overlapping with the dhis2.org except for the quick intro on the front page.

  1. hisp.info

The new HISP site will provide information on the HISP network, such as which countries we are in, who are working for us, our vision, our strategy/philosophy and so on. This will be hosted on the web hotel of the University of Oslo to ensure sustainability and greater visibility. Which URL to use is still up to discussion, hisp.org would be ideal but is taken by HISP SA. Anyway, users of DHIS 2 would not have to take this site into account.

  1. phitoolkit.org

  2. openhealthconsortium.org

These sites are set up by WHO, not HISP, and I cannot account for them, but DHIS 2 user would not have to use them.

  1. http://208.76.222.114

  2. hispkerala.org

Will not be used anymore.

  1. dhismobile.info

I have plans to work with Saptarshi/Ime to make the work they have done on the mobile application more visible in the HISP network and get this info onto dhis2.org.

Lars

···

On Thu, Oct 29, 2009 at 7:43 PM, Jason Pickering jason.p.pickering@gmail.com wrote:

The rest of the content of this mail can be ignored, but anyway, my

feelings on this.

We MUST simplify the number of sites. I know of the following that are

related to DHIS

I think there are probably others. I realize that some of these sites

serve different purposes to different groups, but IMHO, DHIS is a

great product that suffers from really poor marketing. Having

information spread across all these different sites spreads thin

resources and creates confusion among people trying to access

information on DHIS. We, as a community, need to consolidate all of

this information into a single portal at the least, and a single site

at best.

I honestly think, if there is anyway, to create a single site, that

has documentation, demos, links to the source code, a wiki for more

informal documentation, a forum, etc…this would be the way to go. I

personally favour dhis2.org because it sounds less commercial than

dhis2.com. Most people have no idea what HISP is (I have been trying

to figure out for years but still have not a very good grip on it

either!) and it really does not matter for those using the prodcuct

DHIS2 or 1.4, born out of HISP.

I

I think if the university can host the site, this would be the best

way to ensure sustainability. It is just a DNS record. After all the

investment the university has put into the product, they should be

able to host a DNS record after all.

OK, I am done. Lets get a single site with all the information in one place.

Regards,

jason

The rest of the content of this mail can be ignored, but anyway, my

feelings on this.

We MUST simplify the number of sites. I know of the following that are

related to DHIS

I think there are probably others. I realize that some of these sites

serve different purposes to different groups, but IMHO, DHIS is a

great product that suffers from really poor marketing. Having

information spread across all these different sites spreads thin

resources and creates confusion among people trying to access

information on DHIS. We, as a community, need to consolidate all of

this information into a single portal at the least, and a single site

at best.

I honestly think, if there is anyway, to create a single site, that

has documentation, demos, links to the source code, a wiki for more

informal documentation, a forum, etc…this would be the way to go. I

personally favour dhis2.org because it sounds less commercial than

dhis2.com. Most people have no idea what HISP is (I have been trying

to figure out for years but still have not a very good grip on it

either!) and it really does not matter for those using the prodcuct

DHIS2 or 1.4, born out of HISP.

I

I think if the university can host the site, this would be the best

way to ensure sustainability. It is just a DNS record. After all the

investment the university has put into the product, they should be

able to host a DNS record after all.

OK, I am done. Lets get a single site with all the information in one place.

Regards,

jason

Hi, we definitely need to consolidate the info. But in fact this is what we are working on right now, let me explain a little. The idea is this: one site for the software / product (dhis2.org), one collaboration platform (launchpad) and one site for the network (hisp).

  1. dhis2.org

  2. dhis2.com

The dhis2 site will contain what you mention; downloads, docs, developer page, functionality info, link to demo etc. Bob questioned the use of the .com domain which we took into consideration and changed to .org. From now on we will promote the .org domain. Still I think it makes sense to keep the .com domain as well, if someone hears of dhis2 and types in dhis2.com in his browser something should be there. I have sent a request to AN Hosting support to redirect the dhis2.com to dhis2.org, rather than having it as a “parked” domain. Also, we will move the actual downloadable files to this server.

  1. launchpad.net

Launchpad, as you know, provides version control, issue management, bug tracking. This in in fact not overlapping with the dhis2.org except for the quick intro on the front page.

  1. hisp.info

The new HISP site will provide information on the HISP network, such as which countries we are in, who are working for us, our vision, our strategy/philosophy and so on. This will be hosted on the web hotel of the University of Oslo to ensure sustainability and greater visibility. Which URL to use is still up to discussion, hisp.org would be ideal but is taken by HISP SA. Anyway, users of DHIS 2 would not have to take this site into account.

Hi,

Thanks for bringing up this discussion Jason and for letting us in on your strategy Lars, here are my comments:

Lars, I think you simplify the notion of DHIS users… I think they are definitely part of the network and should be aware of what it is, what can be gained from the network, and how to contribute to it.

The hisp.info domain is now widely recognised as a site about HISP so don’t see why we should move away from that.

Important to discuss though, but perhaps not on an open developer list is “what is the HISP network?”,“where is the center, is Oslo it? and do we need a center?”, what about the other sites like hisp.org for SA and their related projects (all over Africa), the hispindia.org site and Vietnam’s site, and probably more local HISP sites as well. That is also part of the network. That is a more interesting discussion I think.

That said, I totally agree with Jason on the need to be able to market HISP as a whole much better, as right now it is difficult to sense the “total strength” of the HISP network or e.g. the spread of DHIS usage around the world, as it more of an underground network that pops up on so many different sites and occasions, which can also be a strength…

I think HISP’s web presence need to be part of the planned strategic discussions in Oslo next month.

  1. phitoolkit.org

  2. openhealthconsortium.org

These sites are set up by WHO, not HISP, and I cannot account for them, but DHIS 2 user would not have to use them.

This of course becomes a bit more complicated the day DHIS 2 is also branded under a different name (tentative name is OpenHealthMapper) as a WHO tool… We definetely do not want to duplicate all information on the software.

  1. http://208.76.222.114

  2. hispkerala.org

Will not be used anymore.

  1. dhismobile.info

I have plans to work with Saptarshi/Ime to make the work they have done on the mobile application more visible in the HISP network and get this info onto dhis2.org.

That’s great news. The world really needs to know more about all the good stuff happening in HISP on this front.

Ola

···

2009/10/30 Lars Helge Øverland larshelge@gmail.com

On Thu, Oct 29, 2009 at 7:43 PM, Jason Pickering jason.p.pickering@gmail.com wrote:


Lars


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Just to underscore the point of keeping hisp.info, the little map on the front page of the wiki says that today there have been 11 different visitors from these countries;
Sweden 2
Indonesia 1

Cote d’Ivoire 1
Bosnia 1
Malawi 1
China 1
New Zealand 1
Norway 1
Switzerland 1

And totally over the last 22 months there have been a total of 8644 visits. Not bad, especially considering how often this page has been down over the last 6 months or so.

Ola

···

2009/10/30 Ola Hodne Titlestad olatitle@gmail.com

2009/10/30 Lars Helge Øverland larshelge@gmail.com

On Thu, Oct 29, 2009 at 7:43 PM, Jason Pickering jason.p.pickering@gmail.com wrote:

The rest of the content of this mail can be ignored, but anyway, my

feelings on this.

We MUST simplify the number of sites. I know of the following that are

related to DHIS

I think there are probably others. I realize that some of these sites

serve different purposes to different groups, but IMHO, DHIS is a

great product that suffers from really poor marketing. Having

information spread across all these different sites spreads thin

resources and creates confusion among people trying to access

information on DHIS. We, as a community, need to consolidate all of

this information into a single portal at the least, and a single site

at best.

I honestly think, if there is anyway, to create a single site, that

has documentation, demos, links to the source code, a wiki for more

informal documentation, a forum, etc…this would be the way to go. I

personally favour dhis2.org because it sounds less commercial than

dhis2.com. Most people have no idea what HISP is (I have been trying

to figure out for years but still have not a very good grip on it

either!) and it really does not matter for those using the prodcuct

DHIS2 or 1.4, born out of HISP.

I

I think if the university can host the site, this would be the best

way to ensure sustainability. It is just a DNS record. After all the

investment the university has put into the product, they should be

able to host a DNS record after all.

OK, I am done. Lets get a single site with all the information in one place.

Regards,

jason

Hi, we definitely need to consolidate the info. But in fact this is what we are working on right now, let me explain a little. The idea is this: one site for the software / product (dhis2.org), one collaboration platform (launchpad) and one site for the network (hisp).

  1. dhis2.org

  2. dhis2.com

The dhis2 site will contain what you mention; downloads, docs, developer page, functionality info, link to demo etc. Bob questioned the use of the .com domain which we took into consideration and changed to .org. From now on we will promote the .org domain. Still I think it makes sense to keep the .com domain as well, if someone hears of dhis2 and types in dhis2.com in his browser something should be there. I have sent a request to AN Hosting support to redirect the dhis2.com to dhis2.org, rather than having it as a “parked” domain. Also, we will move the actual downloadable files to this server.

  1. launchpad.net

Launchpad, as you know, provides version control, issue management, bug tracking. This in in fact not overlapping with the dhis2.org except for the quick intro on the front page.

  1. hisp.info

The new HISP site will provide information on the HISP network, such as which countries we are in, who are working for us, our vision, our strategy/philosophy and so on. This will be hosted on the web hotel of the University of Oslo to ensure sustainability and greater visibility. Which URL to use is still up to discussion, hisp.org would be ideal but is taken by HISP SA. Anyway, users of DHIS 2 would not have to take this site into account.

Hi,

Thanks for bringing up this discussion Jason and for letting us in on your strategy Lars, here are my comments:

Lars, I think you simplify the notion of DHIS users… I think they are definitely part of the network and should be aware of what it is, what can be gained from the network, and how to contribute to it.

The hisp.info domain is now widely recognised as a site about HISP so don’t see why we should move away from that.


Important to discuss though, but perhaps not on an open developer list is “what is the HISP network?”,“where is the center, is Oslo it? and do we need a center?”, what about the other sites like hisp.org for SA and their related projects (all over Africa), the hispindia.org site and Vietnam’s site, and probably more local HISP sites as well. That is also part of the network. That is a more interesting discussion I think.

That said, I totally agree with Jason on the need to be able to market HISP as a whole much better, as right now it is difficult to sense the “total strength” of the HISP network or e.g. the spread of DHIS usage around the world, as it more of an underground network that pops up on so many different sites and occasions, which can also be a strength…

I think HISP’s web presence need to be part of the planned strategic discussions in Oslo next month.

  1. phitoolkit.org

  2. openhealthconsortium.org

These sites are set up by WHO, not HISP, and I cannot account for them, but DHIS 2 user would not have to use them.

This of course becomes a bit more complicated the day DHIS 2 is also branded under a different name (tentative name is OpenHealthMapper) as a WHO tool… We definetely do not want to duplicate all information on the software.

  1. http://208.76.222.114

  2. hispkerala.org

Will not be used anymore.

  1. dhismobile.info

I have plans to work with Saptarshi/Ime to make the work they have done on the mobile application more visible in the HISP network and get this info onto dhis2.org.

That’s great news. The world really needs to know more about all the good stuff happening in HISP on this front.

Ola

Lars


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Added most of it now.

Lars

···

On Tue, Oct 27, 2009 at 10:16 AM, Ola Hodne Titlestad olatitle@gmail.com wrote:

Hi,

A few comments/suggestions:

The demo link on http://dhis2.org/node/8 does not work. Maybe use Knut’s link for now.

I like the functionality page, it is attractive. Although I have a few suggestions to make it better cover all key aspects of DHIS.

Maybe add something like:

Edit all your metadata from the user interfaceAll metadata can flexibly be edited by the end user, such as what data elements to collect, the forms to use, the organisational hierarchy and much more.

Multidimensional data model
Improve data analysis and efficiency of data collection by creating custom dimensions to your data.

**Create your own validation rules to improve data quality

**Set up custom expressions that validate your data, e.g “Live births under 2500g <= Total live births”.

User management and access controlControl who has access to what using a fine-grained privilege system for user roles and users.

Set up your integrated data repository
In DHIS you can store any kind of aggregated/statistical data which means you can store and analyse data across data sources like service delivery, human resources, census data, and equipment.

And move web based pivots down a bit, as this is not really the main functionality of DHIS2.

I guess we can reduce the number of charts and number of maps a bit to better cover all the core functionality without having to scroll down to much.

Move the maps up a bit, they are attractive.