Versions Compared

Old Version 7

changes.mady.by.user Jana Freytag

Saved on

compared with

New Version 8

changes.mady.by.user julie.bickle

Saved on

Key

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

...

Molly Driscoll 

Cornelia Awenius 

Brooks Travis 

Thomas Trutt 

Jana Freytag 

Discussion Items:

TimeItemWhoDescriptionGoals/Info/notes
20 min

Administrivia

Jana Freytag 

https://docs.google.com/spreadsheets/d/1hr7Vx-swyCGfQ3571AK8nYx2MMWb1VFoaqrCYOPE8mM/edit#gid=1954860094
Note taker: Jana Freytag 
20 MinPermissions - Bug reported to the Support SIGSharon Wiles-Young 

Permission should allow for renewal of Aged to Lost items, but generates error message

Julie will be updating this bug.
20 MinBulk editMagda Zacharska UXPROD-3806
  • Request Record Identifiers:

    • Brooks in Chat: UUIDs is really the only viable one, in my mind, before we get to query support.

    • Andrea: Patron expiration date
    • Problem of hanging requests
    • hold shelf expiration date or request expiration date
    • Molly in Chat: 

      I wonder if request UUID could be added to the CSV export from the Requests app to support the gathering of the IDs using the filters available in the Requests app. Otherwise, gathering of UUIDs would either be manual or via API right?

    • Brooks: 

      I definitely think we need to add a story to add the request UUID to the CSV export from requests search/filter.

    • Cheryl in Chat: 

      Your query to create list to be edited will need to include hold shelf expiration date to be updated as well as other criteria like service point

    • use case for a update the whole expiration date for the user with a specific expiration date?
      • To renew the date for a specific group of patrons
    • For the Query Work on Bulk edit: UXPROD-3785
  • Request preview columns:
    • the item Barcode is nessecary
    • is queue position important?

      • Erin W. in Chat: Queue position is not important for msu

      • Brooks: no
      • Question in Chat: 

        Can we add the date/time a request was placed?


Coming out of WOLFCons cross consil meetings

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

QuestionsAnswer RA SIG
institution XX




















LMU (Julie, Product Owner)institution XXinstitution 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 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.



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






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





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:






A: What has been successful with the SIG?

B: What things contributed to that success?

A:


B:






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)?





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:






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.



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:

...