Feature Wiki
タブ
User Name Presentation
ページ全体概要
[非表示]1 Requirements
Problem description: When admins use the export of in the "Personalised surveys": Results » User specific Results, then they get a xls/csv-File with a first column "User Name". The combined names "Firstname Lastname" are not very usable for the admin, he needs at least two columns.
JL: There are different versions (spearate and combined) all over the place in ILIAS.
- Survey: Exports the values in the table GUI
- Participant export of course object: A combined name in the member table and separate values in the participant export.
see http://www.ilias.de/mantis/view.php?id=12756
So I suggest the following Guideline:
» All simple exports of tables should export two columns: "Lastname", "Firstname", instead of the combined "Username"
Additional confusion: Name, User Name, Login
Survey Partcipants Tab
Table GUI: Name "Lauener, Hansjörg"
Table GUI: Login "h.lauener2"
Survey Statistics, Userspecific Results Subtab
Table GUI: User Name "Lauener, Hansjörg"
Export column: User Name "Hansjörg Lauener"
Export column: Login "h.lauener2"
Course, Participant export
Table GUI: Name "Lauener, Hansjörg"
Table GUI: User Name "h.lauener2"
Export column: User Name "h.lauener2"
Export column: First Name "Hansjörg"
Export column: Last Name "Lauener"
Guideline suggestions:
a) In table GUIs, ILIAS should show "Last Name" and "First Name" in two columns, or if not possible, the combined "Last Name, First Name"
b) ILIAS should always use the following wording:
» First Name: "First Name"
» Last Name: "Last Name"
» Name: Combined Field "Last Name, First Name"
» Login: ex.: "login"
c) Abandon the combination: User Name "Last Name, First Name"
2 Suggested Guidelines
The Jour Fixe at 17 Feb 2014 has made the following decisions / guideline(s)
General Terms (Example)
- First Name / Vorname (Matthias)
- Last Name / Nachname (Kunkel)
- Name / Name (Kunkel, Matthias)
- Login / Benutzername (mkunkel)
User names in tables that are usually presented to tutors should include the columns (in this order)
- Name
- Login
- Last Name
- First Name
- Login
3 Additional Information
Related Page:
Configurable Name Presentation
Collection of Issues and Status of Implementation
Issue-collection: Name, (Table), (Export) | Implementation? |
---|---|
Survey, Export of "User Specific Results" | Yes, V 4.3.7 |
Survey, "User Specific Results", Wording of User names | Not yet |
Course and Group, table in tab "Members" | Not yet, Wording |
Course, tab Members, subtab "Membership in Groups" | Not yet |
Course, Tab Members => Edit Member | Not yet, Wording |
Course and Group, tab "Members", subtab "Export Participants" | Not yet, Wording |
Session, Tab "Edit Participants* | Not yet |
Course, Tab Members, Subtab Sessions | Not yet |
Booking Pool, Tab Reservations | Not yet |
Permissions, Owner of a Object | Not yet |
Permissions, Log | Not yet |
"Add users of current course"-feature | Not yet |
Exercise, Tab "Submissions and Grades", Subtab "Grades View" | Not yet |
Page Editor (e.g. Wiki), Tab History | Not yet |
Learning Progress Tab in a course, Subtab Course Participant | Not yet |
Learning Progress Tab in a course, Subtab Matrix View | Not yet |
Wiki, Tab Contributors | ? |
Blog, Tab Blog Contriubutors | Actual Implementation: Name (Kunkel, Matthias [mkunkel]), Role |
Forum, Tab Moderators | Actual Implementation: Login, Firstname, Lastname |
Consultation hours, Detailed Appointment model | Not yet |
4 Status
- Effective from release: Release 5.0
- Approved by Jour Fixe at: JourFixe-2014-09-15
- Implementation status: needs implementation for existing features until 4.5
- Funding for streamlining existing features: required
- Implementation of guideline: all developers
5 Components that are not compliant with guideline
- Contact
- My Courses
- My Groups
- My Mailing Lists > Members
- Forum
- Tab Moderators
6 Discussion
S. Wischniak: In addition the column "login" should be mandatory, since the last name + first name combination is not always unique.
JF 17 Feb 2014: We would like to add this guideline (under 1.1) for release 4.5 and keep the discussion open.
HL, 2.9.2014: We agree with the JFs suggestions. Would be great to have this as a 4.5+ Guideline.
JF 15 Sep 2014: We schedule the guideline for 4.5. From now on all new implementations should respect the guideline. We have to get funding for streamlining existing features.
最終更新: 26. Oct 2017, 10:35, Lauener, Hansjörg [lauener]