Bug 46707 - Usage of <name> in csv import for schema:displayName
Usage of <name> in csv import for schema:displayName
Status: CLOSED DUPLICATE of bug 46754
Product: UCS@school
Classification: Unclassified
Component: Import scripts
UCS@school 4.2
Other Linux
: P5 normal (vote)
: UCS@school 4.2 v9
Assigned To: Daniel Tröder
Sönke Schwardt-Krummrich
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-03-20 18:23 CET by Tobias Birkefeld
Modified: 2018-07-04 15:05 CEST (History)
3 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 5: Blocking further progress on the daily work
User Pain: 0.229
Enterprise Customer affected?:
School Customer affected?: Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments
import config (985 bytes, application/json)
2018-03-20 18:23 CET, Tobias Birkefeld
Details
example csv (79 bytes, text/csv)
2018-03-20 18:24 CET, Tobias Birkefeld
Details
import config (984 bytes, application/json)
2018-03-21 11:20 CET, Tobias Birkefeld
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tobias Birkefeld univentionstaff 2018-03-20 18:23:47 CET
Created attachment 9481 [details]
import config

Set <name> in schema:displayName doesn't work. In schema:email it works great. This make no sense to me.

For OX we need a unique displayName and so "<firstname> <lastname>" is not unique in a big environment. For me the best solution is to set the displayName to "<firstname> <lastname> (<name>)". This will be unique.


My config and an example import csv is attached.
Comment 1 Tobias Birkefeld univentionstaff 2018-03-20 18:24:05 CET
Created attachment 9482 [details]
example csv
Comment 2 Sönke Schwardt-Krummrich univentionstaff 2018-03-21 10:42:06 CET
(In reply to Tobias Birkefeld from comment #0)
> For OX we need a unique displayName and so "<firstname> <lastname>" is not
> unique in a big environment. For me the best solution is to set the
> displayName to "<firstname> <lastname> (<name>)". This will be unique.

For OX you need a unique "oxDisplayName". The "displayName" attribute does not have to be unique.
Comment 3 Tobias Birkefeld univentionstaff 2018-03-21 11:20:05 CET
Created attachment 9483 [details]
import config
Comment 4 Daniel Tröder univentionstaff 2018-03-21 11:59:22 CET
The root cause is this: Bug #42137.

In this specific case the reason is:

	def prepare_all(self, new_user=False):
		self.prepare_uids()
		self.prepare_udm_properties()
		self.prepare_attributes(new_user)


Both "oxDisplayName" and "displayName" are formatted in prepare_udm_properties(), while "name" is formatted in prepare_attributes().
Comment 5 Tobias Birkefeld univentionstaff 2018-03-21 12:17:04 CET
username(In reply to Sönke Schwardt-Krummrich from comment #2)
> For OX you need a unique "oxDisplayName". The "displayName" attribute does
> not have to be unique.

That's right, but also for oxDisplayName you can't use <name> or <username> like in ucs user templates.
Comment 6 Daniel Tröder univentionstaff 2018-03-28 16:00:49 CEST

*** This bug has been marked as a duplicate of bug 46754 ***
Comment 7 Sönke Schwardt-Krummrich univentionstaff 2018-04-09 14:09:02 CEST
Yes, it's a duplicate.