Hi UM folks:
Wanted to send an update about relevant topics discussed at the Face to Face meeting. I know Michelle and Phillip are also here, so they can chime in with stuff they heard or things I missed. And if you had colleagues who came here when
you weren’t able to, I encourage you to meet with them to ask them to dump info with you. There has been a lot of information sharing and discussion. My brain is leaking out of my ears. I’ll try to highlight things that I think might be of interest.
I heard no concrete updates about a PO for us. As far as I know, they are still looking.
-Erin
Monday
·
Opening session – Chalmers gave a talk. It was basically the same as what they did in the FOLIO Forum. They are scheduled to go live “in autumn.” I also heard “end of September” as a date.
·
Reporting – very active here, they gave an intro in the opening session on the work they have been doing. They are focused on the LDP (data warehouse.)
·
Workflow – presentation from Mike Gorell. Workflow is focused right now on manual workflow and a Camunda implementation. There is no assumption at this point that automatic workflows will be available for Summer 2020 adopters.
So if you were anticipating that, you will need to refresh / rethink those processes for workarounds to go live.
·
Implementers – I went to one meeting Monday afternoon about developing a holistic, all around understanding of FOLIO. One of the key takeaways from that was information sharing and the need for it between SIGs.
Tuesday
·
Permissions – there were two hour-long sessions on app permissions, which several of you called into.
·
Lots of discussion about location based permissions and whether they will have restrictions on them. I don’t know if there was a real consensus there, but discussion tended towards saying that that was asking FOLIO to solve a
political problem in a way that was super complex.
·
Lots of discussion about Teams, a proposed restriction feature being implemented right now in Acquisitions, where they have called it Acquisition Units. Units only attach to users, or to individual records. If you want to use
it you have to do it one by one. No association to locations, service points, or permission sets. The epic in Jira is UXPROD-1147.
·
Audit Trail functionality is being looked at in several ways, they did a proof of concept with RA that will turn into a circulation log feature.
·
Discussion of Templates, being developed right now in Acquisitions, as a way to provide limited views to records / limited actions, potentially. So the example was an on-the-fly or quick add record, which circ staff need to be
able to do, but circ staff don’t need to be able to make instance records or add instance records.
·
Some comments about the need for descriptive permission error messages. Intention is that if you don’t have a permission, you won’t see a thing (so no error would be generated.) That led to discussion about how that might lead
to people not understanding something is a permission issue and developing unmanaged workarounds.
·
There was conversation about data concerns and patron data being viewable / not viewable.
·
I asked Cate Boerema how there would be followup on this since we have no PO. Cate said she would take a look at the notes, generated by our moderators.
·
There was an additional meeting at 4:15 focused on Circulation, where quite a bit of users info was talked about.
·
Much of this is a need for custom fields. Custom Fields is currently an unstaffed epic. There is no information on when that might proceed.
·
There is a card sort exercise in the work for User information, that will be managed and distributed by Khalilah Gambrell.
·
RA needs Users to have a Preferred Pickup Location field – I believe Cate B. was putting that in as a Jira.
Wednesday
·
The morning meetings I went to didn’t have a ton of related stuff about users.
·
There was a recap meeting after lunch – last session. They announced that Wolfcon 2020 is a go, it will be hosted by Texas A&M and be the week of January 21, 2020.
·
The Product Council released a Market-Viable Product document:
https://docs.google.com/document/d/1JPRKF_FyZbP4Tv5ynTIhyDefTNt9juCpvaCkIcWH0A0/edit
--
Erin Nettifee
Pronouns: she/her/hers
IT Business Analyst, Library Systems and Integration Support
Duke University Libraries