Date
1pm EST
...
Discussion items
| Time | Item | Who | Notes | ||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Welcome and Attendance |
| ||||||||||||||||||||||||||||||||||||||||||||||||||
| User Accounts/Permissions | Devon presented for the group. Have had some difficulty determining what "major record types" are. Mostly proposing more granular permissions - for example, separating "creating" and "updating" into different permissions. Working through Jira tickets - focus on authentication and managing user access and groups. Have two wireframes showing what they are proposing. One issue: people from single repositories mostly in their group - would like to hear from people that have multiple repositories. Some solutions they're proposing for specific tickets: ANW-97 - active/inactive users - in the user edit account view, have a checkbox to indicate whether active or not; down the road, make there be a way to facet by users qualities AR-1621 - default repository - also in the user edit account view, create a drop-down to select any of the repositories that you have permissions in Discussion: Lydia feels the setting up of user accounts is awkward overall, concerned about the temptation of the Grant system permissions checkbox. U-M uses external authentication so doesn't use. What about ability for users to change passwords or create own accounts with some prepopulated information? Devon says group has discussed some of the issues with giving users this level of control. Lydia suggests a Forgot Password? link even if users can't control the accounts themselves. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Editing and Data Entry | Lynn presented. Group worked across the board on the issues and did a bulk editing session. New concept they're working on for bulk edit - similar to RDE, with a popup screen that is spreadsheet-like. Starting to spec it out. Add a Bulk Edit button to the tree (in the area where Rapid Data Entry mode is). Dropdown menu to select what you want to do (bulk edit/bulk delete). Radio buttons/check boxes to select individual components for editing. Jira ticket to pass - AR-1718 - add new sibling or child directly beneath the current component. Agreement in the small group and larger group that this is desirable. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| JIRA tickets to discuss/pass |
|
...