Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change wording on adding a new reader in workflow #70

Open
twinkietoes-on opened this issue Jan 16, 2021 · 1 comment
Open

Change wording on adding a new reader in workflow #70

twinkietoes-on opened this issue Jan 16, 2021 · 1 comment

Comments

@twinkietoes-on
Copy link
Collaborator

It would be nice if back in the database, when adding a brand new reader, it would say "forum name" and "catalog name" (instead of "user name" and "display name")
addnewreader

Priority: 4

@kgroeneveld
Copy link
Collaborator

It seems the terms User Name and Display Name are used in more spots than just the above screenshot. For example if you press Add new reader in the Section Compiler you get a very similar (but different) screen. Or when viewing lists of people in the Management Dashboard the table has headings for Name (which is the same as User Name) and Display Name. There may also be other spots I did not find yet. I would guess all of these places should maybe be changed and not just the specific example originally mentioned in this issue?

I also wonder a bit about changing User Name to Forum Name. In the context of the main LibriVox catalog system this is the user name. For example when you log in to the LibriVox Management Dashboard it asks for Username / Password. Should this Username then also be Forum Name? Maybe in some places it should be User Name / Forum Name or User (Forum) Name and maybe just left as User Name in other places?

It would probably be less confusing if the catalog system and the forum actually shared a user database. But that would be a major undertaking...

It would also be nice to clean up as many inconsistencies (such as User Name vs Username vs Name) as possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants