Page Comparison

Announcements

Christine on Slack:

Hi all! I have another UAT opportunity. We are proposing that in the short term, we stabilize call number browse functionality by:

• Changing the sort in “Call numbers (all)” to more closely mirror that of Orchid

• Retain options for LC, Dewey, and NLM but hide options that have been more problematic - SuDoc, Other scheme, and Local - until a full refactor effort in an upcoming release

We have created an environment using Quesnelia data for these changes as well as a form for testing scenarios. We are hoping to release these changes as soon as possible for Quesnelia so we are requesting feedback by the middle of next week (8/7/24). I know everyone is very busy, but any feedback you have would be greatly appreciated!Form: Quesnelia call number browse proposal: Feedback form
*Note: the other call number browse options (SuDoc, Other scheme, and Local) have not yet been hidden

Version History page - Version History Use Cases (Inventory app)

• Does anyone object to making two tables, version history and date updated? no objections

• LOC link - need to reach out to them to see if this is community work or LOC specific

• MM SIG should document all the community needs

Better sample data in Inventory

Charlotte Whitt

Short update on the work in the Product Council WG on better sample data in the reference environments

• PC has listened to feedback about problems with data - old, noisy, not exhaustive etc.

• Short-term - Hope to make Ramsons bugfest data better

• Looking to use real dataset from a larger library with anonymization - user data, fund codes etc. will be changed

  • might also massage dataset prior to loading to include typical data, e.g. Chicago doesn’t use item material type but most do

• Survey will go out to libraries to ask about data and expectations and can present at other SIGs if needed

• Other members welcome to join group

• Will help with use of reference environments and early testing

• Questions

  • Some experimentation was done to bring forward good data from testing and leave bad data behind. Is this part of the conversation? E.g. the “workhorse” data import profiles that get created for bugfest that would be useful to bring into each new environment.

    • Charlotte: would be useful for SIGs to make list of what, e.g. profiles, would need to be moved into each env.

  • How can we best create data that fits everyone’s needs, e.g. reflect location practices across institutions?

  • What marc mapping would be used?

    • Group is aware of issue but haven’t decided which dataset to use yet so unsure of mapping.

    • Maybe mapping used could be recorded somewhere for folks to reference

PC updates

Charlotte Whitt

No PC meeting this week.

I can provide a short update on the work in the PC Working Group on Better Sample Data in the reference environments (FOLIO Snapshot and FOLIO Bugfest) - Better Sample Data in FOLIO Test Environments Working Group

BELA (Bulk Edit and Lists App)

Jennifer Eustis

No meeting this week.

Data Import Working Group

Jennifer Eustis

No meeting this week.

quickMARC Subgroup update

Raegan Wiechert

All meetings for June and July have been cancelled