Import to a 2-level containers tree does not work

brunetton

Hi,

Still working on importing data, and still having problems.

Here I'm trying to import a constant value to a metadata list inside a containers tree with this topology:

• [kindness_c]: container
  
• [subtree1]: container
• [kindness_level_meta2] => list [kindness_level]

=> The value is not imported

You'll find the mapping file attached.

The data file is really simple:
ID

50

Of course, "kind" entry exists in [kindness_level] list

=> the match is okay with one level of container less, or no level at all.

=> It seems to be the same problem when swiching from Constant to Mapping in the mapping file (and adding corresponding column to the data file).

=> in the case when [kindness_level_meta2] is required (checkbox checked in interface), an error message appears:

Could not import source ../../../import/problèmes/7/7.csv: (2017-01-19 22:58:35) [51] Could not add default label Value for kindness_level_meta2 [kindness_level_meta2] cannot be blank; (2017-01-19 22:58:35) [51] Invalid kindness_c; values were subtree1 = kindness_level_meta2 = 219; _related_related = ; _dontCreate = 1; _errorPolicy = stop; locale_id = 1:  Value for kindness_level_meta2 [kindness_level_meta2] cannot be blank

I'll fill two bugs for that, but I keep it here in forum in case someone have similar problem.

brunetton

And here's the bug request:
http://clangers.collectiveaccess.org/jira/browse/PROV-1990

seth

Even though we allow you to nest elements in containers, the bundle specifier namespace within a container is flattened. This means that no matter how many levels of subcontainers you have the specifies is never more than two levels, container and sub-element. In your mapping this:

ca_objects.kindness_c.subtree1.kindness_level_meta2

should be this:

ca_objects.kindness_c.kindness_level_meta2

brunetton

Thank you for pointing this out ! I would never have guessed that.

I think this is important to get the user avoided that he's using wrong bundle specifier namespace.

I got a lot of problems due to bundle specifier namespace while importing data. To avoid this kind of problems, this ticket seems very important in my opinion:

http://clangers.collectiveaccess.org/jira/browse/PROV-1969

Don't you think ?

Thanks !

seth

Yes, I agree we should add alerts, and really "lint" checking in general, to the importer. It's really a matter of time. Any volunteers want to help with it? :-)

brunetton

Honnestely I was volunteer, because I needed it ! But I'll need some help to follow the code in import module; I'm quickly lot there

seth

Thanks! I want other volunteers too :-)