Hi,
Den 14. sep. 2011 kl. 16.13 skrev Bob Jolliffe:
OK. Lets try Friday morning 09h30 my time - that's 10h30 Oslo time
Dial-in number: +1-424-203-8000
or Skype call to: freeconferencing.8000
Code: 553472
I know you are under pressure to finish this stuff so the intent is
not to slow
A decent recap, Bob and Morten?
Yes, that seems to be a good recap. Its good enough for now ;)
--
Morten
Jo
___
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe :
Could we also add users to the objects with dynamic attributes? We
need some more fields for alternative telephone numbers, fax, etc etc.
Thanks,
Jason
On Fri, Sep 16, 2011 at 12:23 PM, Morten Olav Hansen morte...@gmail.com wrote:
A decent recap, Bob and Morten?
Yes, that seems to be a good
On 16 September 2011 11:23, Morten Olav Hansen morte...@gmail.com wrote:
A decent recap, Bob and Morten?
Yes thanks for calling in and good recap. Scope creep on which
objects can have extensible attributes could render it cumbersome
eventually, but while the number of such objects is few it
On 16 September 2011 11:54, Jason Pickering jason.p.picker...@gmail.com wrote:
Could we also add users to the objects with dynamic attributes? We
need some more fields for alternative telephone numbers, fax, etc etc.
and so it begins ...
Sounds reasonable to me :-) Or use ldap.
Bob
Fine with me if you want to integrate LDAP while you are at it.
:)
On Fri, Sep 16, 2011 at 1:40 PM, Bob Jolliffe bobjolli...@gmail.com wrote:
On 16 September 2011 11:54, Jason Pickering jason.p.picker...@gmail.com
wrote:
Could we also add users to the objects with dynamic attributes? We
On 16 September 2011 13:07, Jason Pickering jason.p.picker...@gmail.com wrote:
Fine with me if you want to integrate LDAP while you are at it.
:)
Yes I see there's even a blueprint for this (I wonder who from?). I
actually did this once - ie setup dhis so you can autthenticate
against ldap.
LDAP is really overkill for what we need at this point. We just have a
few more fields like alternate telephone number which we manage
through a seperate Excel sheet. Not ideal really. No real requirement
for LDAP just to get another number in. :)
On Fri, Sep 16, 2011 at 2:21 PM, Bob Jolliffe
Hi
I also agree that User would benefit from dynamic attributes. Right
now, I will concentrate on DE/I/OU only, but when that is finished, it
should be easy enough to add support for Users also (but no reporting
for now).
--
Morten
On Fri, Sep 16, 2011 at 2:32 PM, Jason Pickering
Breaking out from our current hard coded set of object attributes is
certainly a great step forward. There is also some advantage in
trying to think a bit generally about what we are doing. We are
seeing lots of progress in the right direction. I was about to start
a discussion about names
Hi Morten
On a more concrete note than before ... :-)
I've finally had a chance to look more closely at what you are doing.
Can I make a small suggestion? Currently you are replicating a lot of
code as you implement attributes across dataelements, indicators and
orgunits. Currently these all
Hi Bob
I've finally had a chance to look more closely at what you are doing.
Can I make a small suggestion? Currently you are replicating a lot of
code as you implement attributes across dataelements, indicators and
orgunits. Currently these all extend AbstractNameable object.
Currently,
On 14 September 2011 14:05, Morten Olav Hansen morte...@gmail.com wrote:
Hi Bob
I've finally had a chance to look more closely at what you are doing.
Can I make a small suggestion? Currently you are replicating a lot of
code as you implement attributes across dataelements, indicators and
Can I suggest we fit in a brief design call this week to touch base?
I have a freeconference number we can use. Maybe tomorrow or Friday?
Lars are you around and/or available as well?
Sure. I can tomorrow or Friday. Lars is in Uganda, but I'm sure he'll
respond later if he has time for a
Den 14. sep. 2011 kl. 15.32 skrev Morten Olav Hansen:
Can I suggest we fit in a brief design call this week to touch base?
I have a freeconference number we can use. Maybe tomorrow or Friday?
Lars are you around and/or available as well?
Sure. I can tomorrow or Friday. Lars is in Uganda,
OK. Lets try Friday morning 09h30 my time - that's 10h30 Oslo time
Dial-in number: +1-424-203-8000
or Skype call to: freeconferencing.8000
Code: 553472
I know you are under pressure to finish this stuff so the intent is
not to slow things up. Just keep us all pointing in same direction
:-)
Hi All,
I was just watching this thread and wanted to share our possibly
similar experiences from iHRIS. Admittedly I have not looked at the
details of how DHIS is implementing dynamic attributes in the
database, but I would suspect the design pattern is similar to how
On 14 September 2011 15:32, Carl Leitner litlf...@ibiblio.org wrote:
Hi All,
I was just watching this thread and wanted to share our possibly similar
experiences from iHRIS. Admittedly I have not looked at the details of how
DHIS is implementing dynamic attributes in the database, but I
Final thought from me for now ...
On 14 September 2011 17:11, Bob Jolliffe bobjolli...@gmail.com wrote:
On 14 September 2011 15:32, Carl Leitner litlf...@ibiblio.org wrote:
Hi All,
I was just watching this thread and wanted to share our possibly similar
experiences from iHRIS. Admittedly I
Hi
- What is the planned use cases for this?
This is part of my work for Rwanda, the system they are using today
has quite a bit more attributes connected to each data element (or
indicator as it was known in that system), and it was decided that
instead of expanding the set of attributes
For the specific use case, what they want is:
1) Add more meta-attributes to data elements (but we also add support
for indicators, organisation units)
2) Create a data repository report (data dictionary) in PDF. For this,
I will expand the Export to PDF functionality that already exists in
- It doesn't seem to be linked to the general classes of
nameable/identifiable object. Is it meant to be implemented just for
specific meta object types?
We are planning to implement for data element, indicator, org unit
only at least for this release. But it can easily be extended if we
Thanks for the responses.
So I guess this might very well be a start of a general evolution in the meta
model? It might be worth already now thinking a little through the possible
consequences of this direction going forward. I think this is something we need
:)
As we work through how to
Hi,
I see there is development going on for dynamic attributes [1] on some meta
objects (DataElement, Indicator, DataSet, OrganisationUnit?).
Some questions:
- What is the planned use cases for this?
- Is this significantly different from the attributes in the tracking module (I
guess these
24 matches
Mail list logo
