When I load CSV file with “name” in org unit field (SERVICES → IMPORT-EXPORT → CSV DATA IMPORT (DRY RUN – YES)), I receive the error “ignored” for this name.
The example of my CSV file:
“dataelement”,“period”,“orgunit”,“categoryoptioncombo”,“value”,“storedby”,“timestamp”,“comment”,“followup”
“AzIkeEEMnWD”,“201303”,“London”,“lDg7pKq4CDk”,“4343”,“admin”,“2013-05-30”,“false”
Can we use name or code in the field «org unit» in CSV file for import?
yes you can use uid, code and name as identifier scheme (strategory for matching meta-data). A caveat, the name property of organisation unit is not unique after 2.11 and we consider removing that option.
In your import, did you click “more options” and selected name as org unit id scheme? Are you are there is an org unit in your db with name “London”?
When I load CSV file with “name” in org unit field (SERVICES → IMPORT-EXPORT → CSV DATA IMPORT (DRY RUN – YES)), I receive the error “ignored” for this name.
yes you can use uid, code and name as identifier scheme (strategory for
matching meta-data). A caveat, the name property of organisation unit is
not unique after 2.11 and we consider removing that option.
I actually would recommend we keep that option even though uniqueness of
names is (thankfully) no longer enforced by DHIS2. In a lot of situations,
names is all you have to match on, so it would be a pity to remove this
option.
It then becomes the user's responsibility to ensure uniqueness - but
perhaps we could aid the user by checking for uniqueness and sending out an
alert in case of duplicates? I think that would be the best solution.
Knut
···
On Fri, Jul 5, 2013 at 11:20 AM, Lars Helge Øverland <larshelge@gmail.com>wrote:
In your import, did you click "more options" and selected name as org unit
id scheme? Are you are there is an org unit in your db with name "London"?
regards,
Lars
On Thu, Jul 4, 2013 at 1:25 PM, <zebra_st@ukr.net> wrote:
Hello,
my DHIS is Version: 2.12 installed on UBUNTU 12.04 LTS (32bit).
I am going to import some data in the CSV format.
When I load CSV file with “name” in org unit field (SERVICES ->
IMPORT-EXPORT -> CSV DATA IMPORT (DRY RUN – YES)), I receive the error
“ignored” for this name.
The example of my CSV file:
"dataelement","period","orgunit","categoryoptioncombo","value","storedby"
,"timestamp","comment","followup"
"AzIkeEEMnWD","201303","London","lDg7pKq4CDk","4343","admin","2013-
05-30","false"
Can we use name or code in the field «org unit» in CSV file for import?
On Fri, Jul 5, 2013 at 11:20 AM, Lars Helge Øverland larshelge@gmail.com wrote:
Names might be all you have to match on when importing orgunits, bootstrapping. But after this is done, I think data import should always be able to work with codes or uids.
yes you can use uid, code and name as identifier scheme (strategory for matching meta-data). A caveat, the name property of organisation unit is not unique after 2.11 and we consider removing that option.
I actually would recommend we keep that option even though uniqueness of names is (thankfully) no longer enforced by DHIS2. In a lot of situations, names is all you have to match on, so it would be a pity to remove this option.
It then becomes the user’s responsibility to ensure uniqueness - but perhaps we could aid the user by checking for uniqueness and sending out an alert in case of duplicates? I think that would be the best solution.
Knut
In your import, did you click “more options” and selected name as org unit id scheme? Are you are there is an org unit in your db with name “London”?
When I load CSV file with “name” in org unit field (SERVICES → IMPORT-EXPORT → CSV DATA IMPORT (DRY RUN – YES)), I receive the error “ignored” for this name.
On Fri, Jul 5, 2013 at 11:20 AM, Lars Helge Øverland larshelge@gmail.com wrote:
Hi,
yes you can use uid, code and name as identifier scheme (strategory for matching meta-data). A caveat, the name property of organisation unit is not unique after 2.11 and we consider removing that option.
I actually would recommend we keep that option even though uniqueness of names is (thankfully) no longer enforced by DHIS2. In a lot of situations, names is all you have to match on, so it would be a pity to remove this option.
Names might be all you have to match on when importing orgunits, bootstrapping. But after this is done, I think data import should always be able to work with codes or uids.
Bob
It then becomes the user’s responsibility to ensure uniqueness - but perhaps we could aid the user by checking for uniqueness and sending out an alert in case of duplicates? I think that would be the best solution.
Knut
In your import, did you click “more options” and selected name as org unit id scheme? Are you are there is an org unit in your db with name “London”?
When I load CSV file with “name” in org unit field (SERVICES → IMPORT-EXPORT → CSV DATA IMPORT (DRY RUN – YES)), I receive the error “ignored” for this name.