Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

CMS 2024.7.15

Recording

Coming soon.

Poppy approacheth

  • Poppy Dry Run environment available Monday 7/22

  • Poppy installed to Production early Friday morning, 7/26

    • Begin using new 949 on this day

Updates to practice

Updates from the field

Other business

  • Interim assignments update

  • Question – anyone using the MARC authorities app to consult our authority file?

  • Request from FOLIO governance group and Data Import SIG to create videos of routine work in Inventory, Data Import, etc.

    • Any volunteers?

  • Autumn out Friday 7/19, working remotely 7/22 - 7/26

...

CMS 2024.5.21

Recording

Coming soon.

1. CMS/TS updates

  • Interim roles for Joshua and Autumn concluding as planned in August

  • Technical Services AD position posting and timeline

  • Janice Ahee retiring, last day 6/25

  • Plans for cataloging Special Collections materials during their move, timelines, etc.

  • RDA Phase 1 training update

  • E-resources working group update

...

3. General updates

  • Moving June meeting

  • New Chewa translation number (thx Ruth Ann!)

  • TFBRD / Turfgrass update

  • Reminder to prevent duplicate imports

  • Autumn in-building schedule returning to M, T, F

4. Other business?

CMS 2024.4.16

Recording

1. Poppy update

  • CSP #3 released Thursday 4/11; will need this in Test before we can upgrade Production

  • Timeline still uncertain

  • Poppy training on hold until we know more

  • Because of issues with Poppy, EBSCO providing MSU with a special Quesnalia testing environment

...

  • Joshua now officially NACO coordinator for everything outside geographic and corporate body names

    • Series & titles not a focus, but can tackle in cases where needed

    • Send your questions/records his way

CMS 2024.3.19

Recording

1. Poppy update

  • New upgrade timeline now available

    • CSP #2 has been released and will be installed on Test and Dry Run week of the 18th

    • Dry Run testing 3/25 - 3/29

    • Production upgrade 4/1 - 4/5

  • Save the date for Poppy training, CMS meeting 4/2

    • Creating multiple holdings/items upon import, using multiple 9XX fields

    • Linking boundwiths & analytics

    • Running lists in Lists app

  • 949 configuration check-in

...

  • If manually entering any value in holdings/items:

    • Check for hard returns before and after

    • Check for spaces before and after

    • Review for typos

  • When cataloging an item from a T Loc, remember to remove the T Loc admin note and stat code from the Instance

    • Autumn can investigate using a Job Profile to do this, if there is interest (but will have to wait till Poppy!)

  • OCLC has updated the Bib Formats web page; mostly formatting changes, but FYI that it has a slightly different look

  • RDA webinars taking place Wednesdays at 2pm; not required, but open to anyone interested

  • PCC At-Large Virtual Forum – attend in person or virtually?

  • Autumn: temporary schedule change

CMS 2024.3.5

Recording

1. 9XX reconfiguration

  • 947, 948, and 949 combo going away

  • New approach will use one single 949 for all instance, holdings, & item data

    • Subfield codes will be different, but format will be the same

  • Documentation available on Confluence.

  • Awaiting service patch 2 on dry run environment later this week.

    • Try out in test environment before we switch to Poppy

    • Autumn will remap the job profiles once service patch 2 is installed on our test environment

  • Autumn asks us to create the constant data now, so that it’s ready when we switch to Poppy.

    • A template is available on both the Confluence site and in Connexion’s shared constant data.

    • Autumn is available to help - please reach out if you have questions!

    • Once you create it, you can test it on the test environment on Friday.

  • Tim noted that call number browse isn’t working in Dry Run or Test, but they’re behaving differently. Autumn advised waiting until service patch 2 to see if the problem resolves itself.

    • We can submit tickets in EBSCO Connect or the FOLIO Product JIRA site. 

    • Check in on Slack re: call number browsing issues.

    • We’ll also check JIRA to see if this has been reported.

...

  • Test environment vs Dry run environment

    • Recent snapshot of our production database with the newest release applied. It’s slightly more current and we have temporary access when we are testing a new release.

  • Sierra order records – sometimes they’re in FOLIO, sometimes they’re not – and what to do about it

    • Orders in Sierra older than 2 years old did not come over to FOLIO (though the bibliographic record migrated).

    • Try searching orders app and inventory app by title to see if it comes up

    • Alternatively, search Sierra archive to search for Sierra order number to retrieve related Sierra bibliographic number, which can be searched in FOLIO (with a ‘.’ at the beginning).

    • If none is found, go ahead and bring in a new record.

  • RDA Phase 1 webinars open to all

    • First one on March 13 - Wednesdays at 2pm from March-May and will be recorded

    • Expect calendar invitations from Autumn

  • Training for next CMS on new functionality in Poppy:

    • Using data import to create multiple holdings and item records

    • Creating analytics

    • In-depth look at the Lists app

CMS 2024.2.20

Recording

1. Poppy update

  • Updating Folio Production from Orchid to Poppy is on hold at the moment.

  • Implementation timeline is pushed back because of issues found by MSUL staff in testing which would severely impede our workflows.

  • Folio Service patch #2 is in development and promised to fix a lot of the issues identified as a problem by MSUL

  • MSU Dry-run instance is set to be updated around first of March. MSUL staff will resume testing at that point and we should know more regarding when implementation might happen in Folio Production.

...

CMS 2024.2.6

Notes: Autumn

Recording

1. Poppy update

  • Poppy installed in Test tenant; results of testing so far:

    • Lists app working well

      • Can run lists on a number of different item record fields, plus a limited number of instance record fields

      • Queries can be built with multiple lines; no “OR” option, though, only “AND”

      • Offers a preview of query results before running the entire list

      • Results can be exported to CSV, but limited to a select set of fields

      • No apparent limit on the number of lists that can be run/stored at any given time

    • Boundwiths/analytics

      • Function to add/delete linkages now available

      • Links are between one shared item record and the holdings records of the related instances

      • Viewing and editing these can be confusing! More training to come

  • Job profile 9XX configurations will be changing

    • New functionality to create multiple holdings/items for one instance using 9XX field mappings in Data Import

    • However, this means all values for one holdings/item pair must be in one single MARC field

    • We will be changing from the 947/948/949 configuration to just the 949 field

    • Autumn will be testing this thoroughly and helping everyone adjust their constant data accordingly

  • Possible issue with action profiles

    • Known issue with Poppy, where the “action profile” component of a job profile might be unlinked from all the job profiles it’s associated with

    • Catalogers don’t need to grasp all the details of the problem, but just know it could be a factor in when we ultimately move to Poppy

...

This was a brief off-cycle meeting immediately after the holiday break, only on Zoom.

Recording

1. New IMCO (Identity management) cooperative program

...