2021-07-28 Meeting notes
Date
Attendees
Goals
- Discuss request to remove the setting to enable user profile pictures, per Erin Nettifee's Slack message.
- JIRA ticket here
- Erin's comment: "I'd like to encourage this SIG to reconsider whether the user profile picture setting should be hidden until UXPROD-36 - Getting issue details... STATUS is fully developed. A new adopter school commented on folio-implementers this morning asking how to get it to work. As long as it's visible in the UI and UXPROD-36 isn't prioritized, it will continue to be confusing to people (and difficult to document.) I'm just one voice here, but I do think this is important.If the concern is development time, there is essentially little to no development time needed to remove it (and hide the associated permission.) I could maybe even get a Duke developer to take care of it if there were no other resources available."
- Discuss/rank JIRA ticket asking that locally-created permission sets not be allowed to have names that match the names of other permission sets.
- Staff slip/Notice tokens
Discussion items
| Time | What | Who | Notes |
|---|---|---|---|
| 5 min | Note-taker | Christine | Christine has graciously agreed to take notes today. |
| 20 min | Profile pictures - should this setting be hidden until Profile pictures are actually implemented? | Maura | Profile pictures is a feature that is ranked low for most institutions. It has not been developed yet. Profile pictures are turned off by default in the Folio settings. But the presence of the setting has been confusing for a recent implementer. The options we discussed are as follows: 1) Remove the setting from the UI (only); 2) Place text such as NOT YET READY next the the setting. Patty reasoned that the work to make the setting disappear, is work that could just as easily be spent making this feature functional. The feature does work, to a point. The placeholder for a user photo disappears when the setting is turned off, which means that the setting itself functions. The lack of function comes from the fact that there is no way to store photos in Folio, and no way at this moment to link to an external database of photos. To put in a link, we'd have to extend the user record to have a field for the user photo link. Brooks suggested the possibility of using custom fields (text field to store an image URL) to accomplish a UI-only implementation of functionality that would allow linking to externally-hosted images (eg. an existing university ID system). (Brooks) There is no developer for this feature. Patty will develop the ticket for UI functionality. |
| 10 min | Should we not allow locally-created permission sets duplicate the names of other permission sets? | Maura | There was strong support for UI validation when creating permission sets, so that two permission sets can't have identical names. The validation should only have to exist in the UI; if you're using the API, you should know better, and you should include a validation test when you upload permission sets via the API. Brooks will write up a user story. Others will rank/add comments if necessary. |
| 5 min | Staff slip/Notice tokens | Brooks | There are very few user tokens available for staff slips, and those that are there are all hard-coded into the UI. Brooks proposed that more User data be made available to use when generating a slip, and that the tokens not be hard-coded. There were no objections from the SIG. Brooks will take this feedback to RA-SIG, where these slips (and the tokens) are being spec'd out. MO State will likely have to build a purpose-built slip generation tool for its delivery slips in the meantime. (Brooks) |