Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Coming out of WOLFCons cross consil council meetings

These are Questions asked by PC. (please everyone in RA SIG feel free to edit and add to this)

QuestionsAnswer RA SIG



















LMU (Julie, Product Owner)
institution XX
Duke (Erin)institution XXinstitution XXinstitution XX
Can you share the purpose of your SIG: functional area/cross cutting/affinity group, etc?

The Resource Access SIG works with developers to define essential circulation functions: checking out and discharging library materials. Defines patron types, loan types, fines and fees structures, recalls, holds. Defines essential reporting functions. Advises developers on the interactions needed between libraries and other parties necessary for successful sharing of resources, whether through shared consortial collections, interlibrary loan options, or other mechanisms.

Ths RA SIG works closely with the UM SIG, with members being present in both SIGs






What areas does your SIG have responsibility for?

all circulation components:

  • Circulation log, Remote storage, Material Requests Title Level Requests, Delivery and
trasfer
  • transfer services
  • Fees and fines, Lost Items, Patron Blocks, Claims returned
  • circ log
  • Loans, Check-in, Check-out, Loan information on Item Details
  • Patron notices, Printing slips
  • Courses: MOD-CR, UI-CR
  • APIs: NCIP: Protocol for service requests/fulfillment, Z39.50 Support MVP, SIP2
  • On the Fly Records / Fast Add
  • RTAC: provides item availability information to discovery





A: What do you feel like your SIGs purpose is currently?

B: Has it changed over time?

A: our purpose hasn't change (support development relating to our area) but can't fullfil it because of the lack of POs and dev ressources


B: more focused on libraries that are live - more problem solving than developement of new features

direct feedback to POs working on the backlog

we are doing the work we can rather than the work we should do

SIGs originally used to be to collect requirements (I think); now, because our backlog is already so large, any requirements collected now will take a long time to see the light of day. So the SIG has also become a place to disucss workarounds, solve problems, share best practices. I don't see this as a bad thing, rather as the natural evolution of an audiance who now also needs help implementing.

Orient new people joining the project to RA issues, provide training and question time for those institutions, share best practices and workarounds. 

It has changed over time as we have been developing fewer features and/or moving feature development into breakout groups (like was done with title level requesting.)




A: Do you have product owners who regularly work with the SIG?

B: Do you feel that your requirements are being successfully developed into FOLIO?

A: Yes


B: Sort of: No: 3-Part Item status, Workflow engine, Courses, German Reminder fees


Yes.

We have basic requirements and could function if we went live now, but there are major things we would really like to have, like a fix to the faculty delivery workflows, the ability to freeze a patron record, and the three part item status.




How do you feel about the resources allocated in the development areas that are focused on?

Vega is a fantastic team but there is too much work for just them to do.


A: What are some of the challenges facing your SIG/subgroup?

B: Are there ways in which you feel the SIG has been unable to accomplish it's mission?

A: Missing POs


B:


Missing product owners is the biggest challenge, as well as losing development teams. 


A: What has been successful with the SIG?

B: What things contributed to that success?

A:


B:


Collaboration and good humor - hopefully providing a safe space for people to admit what they know and don't know. Community members who are willing to chime in help make the space a learning community which I think is really valuable.


What could the Product Council do to help the SIG?





Do you feel like the Roadmap accurately represents the work of your SIG (both desired and already accounted for)?

Is that Google spreadsheet being actively reviewed or is the intention to do it yearly?

I don't really feel like it represents RA work well since most/all of our stuff is marked as "in the future."




A: How can we improve our communications with the SIG?

B: Does the current monthly reporting work?

C: Would have a dedicated PC meeting for your SIG be helpful?

A:


B:


C:


I think Sharon gives good updates, but also I go read the meeting notes, so I usually know what the PC is doing. I don't always read the PC monthly notes from the SIGs - that seems like its reporting up to the PC, not downward/outward to the community, if that makes sense.


A: What functions should the PC be accomplishing?

B: And how would the SIGs like to have those need met?

A:


B:

I don't think there is more the PC can do really, until there are more POs to make the backlog dev-ready, and more devs to program that backlog.We need resources, but that seems like a Community Council issue, not a PC Issue.


For groups that are on hiatus, can you talk a little about why and whether you think there are current activites that should be done?All subgroups on hiatus please leave a comment: