CMS 2022.12.06

Recording

1. Available here: MSUL Cataloging & Metadata Services Team Meeting 2022-12-06

Update to Morning Glory upgrade timeline

1. Still a few loose ends, patches, etc. that have been addressed, but delayed the upgrade.

2. Now that it’s nearly finals season, we’re delaying until at least Dec. 16 to avoid any disruption to service.

Connexion 3.1 upgrades

1. Can upgrade on your own or with support from Systems (see Joshua’s TSStaff email Nov. 28, 2022).

2. Team reports upgrades have been proceeding smoothly.

Review of file management steps for cataloging: Connexion-to-Folio

1. As a refresher, Joshua demonstrated export from Connexion and upload to Data Import app in Folio with a monograph and a serial example.

2. Key to remember: renaming the .dat files exported from Connexion to your local computer prevents Connexion from appending additional records to that file. If you’re cataloging one item at a time, this renaming step is crucial to remember to avoid creating unintentional duplicates in Inventory.

VuFind

1. All are encouraged to attend a VuFind rollout session, Thursday Dec. 8 from 11AM-1PM

2. We spent a few minutes at meeting’s end looking at VuFind catalog beta and discussing some observations.

CMS 2022.11.15

Recording

1. Available here: MSUL Cataloging & Metadata Services Team Meeting 2022-11-15

Morning Glory rollout update

1. Serious issue related to field mapping profiles was discovered in Test; Jira ticket made; developers have a patch that fixes this; will roll out before Production upgrades from Lotus to Morning Glory.

2. Morning Glory on our Test tenant remains unpatched; Morning Glory in our dry run environment (containing more up-to-date data than Test) is patched.

3. Production likely to be upgraded in next couple weeks.

4. Morning Glory is missing the hoped-for analytics/bound-with functionality in the user interface; moratorium on this work will have to continue, but we are testing API-based tools to create and edit bound-withs and analytic relationships on the backend for high-priority items.

5. Bulk Edit app debuts. Will at least allow us to re-start the New Books workflow; hopefully other things, too.

6. Will allow us to re-start loading GOBI records in batch rather than one-by-one, which will free up a bottleneck in shelf-ready processing.

Moving holdings/items between instances and items within an instance

1. Documentation and videos on both processes forthcoming

2. Joshua demonstrated both in the meeting (see recording 8:50 to 27:00)

3. Moving holdings and/or items from one instance to another can be thought of as a “horizontal” movement: in the UI it happens from side to side, from one instance to another

4. Moving items within in an instance can be thought of as “vertical”: in the UI the item is moved up and down between holdings on a single instance

Use of VuFind catalog-beta for browsing and call number assignments

1. As of 11/15/22, VuFind is populated with unsuppressed records from our Test tenant (which was a snapshot from Production taken late October).

2. Browse functionality of indexes like call number, author, title and subject are working and present a reasonable alternative to ‘browse call number’ and ‘browse subject’ etc. in Inventory when those tools fail.

3. Find VuFind catalog-beta here: https://catalog-beta.lib.msu.edu/vufind/

4. Caveats:

   1. It is being actively developed and could be down at any time

   2. It is not yet being synced or kept up to date with Production data

   3. The call number index contains all effective call numbers regardless of type (LC and local call numbers are intermingled in a single index)

Backing up OCLC Connexion settings

1. More detailed documentation forthcoming

2. If you care to backup your Connexion client settings to prevent against loss of toolbar customizations, text strings, macros, etc., you may wish to create a copy of your OCLC Connexion folders to your X drive or some other location

3. Connexion folders are typically found here:

   1. Local Disk / Users / [your netid] / AppData / Roaming / OCLC / Connex

4. Once you arrive at that folder, right click, Send To, and select your X drive; or alternatively, copy the folder and paste the copy in another location of your choosing.

CMS 2022.10.19

Recording

1. Available here: MSUL Cataloging & Metadata Services Team Meeting 2022-10-19 recording

Copy cataloging during Autumn’s leave

1. Janet Baldwin serving in an interim support role for copy cataloging; roughly end of October through beginning of February.

2. Will handle questions, troubleshooting, etc. but Joshua will handle any personnel matters.

Update to Special Collections Remote cataloging procedures

1. If cataloging an item destined for an SPC Remote location (see Goldenrod streamer for location code), cataloger must supply a prescribed 590 note to the local bib.

2. We also discussed providing a check-in note to the SPC Remote item record, but this requirement was dropped after this meeting.

3. See updated procedures: Special Collections (general)

Update to Electronic Theses & Dissertations (ETDs) cataloging procedures

1. ETD procedure has been updated to account for cataloging in Folio; please read through the entire procedure carefully before proceeding: ETDs

2. Note that CAT5 is used because holdings and items are already created for all ETDs.

Update on workstats

1. Joshua is in the process of getting caught up on workstats; has a method for getting these out of Folio.

2. However, be reminded that when you create a new item by duplicating an existing item, you must delete all irrelevant notes inherited from the duplicated item - including the workstats note from the old item.

PCC update on RDA adoption

1. Announced in September that PCC will not adopt new RDA until June 2023 at earliest.

Discussion of circulation data in Folio items

1. Sierra circulation data was migrated into Folio items as a dedicated note; native Folio circulation data is tracked separately. Therefore, true circulation counts are the union of these two numbers.

2. Will need to communicate this to collections colleagues to inform adequate counts when needed.

CMS 2022.10.04

Recording

1. Available here: https://mediaspace.msu.edu/media/MSUL+Cataloging+%26+Metadata+Services+Team+Meeting+2022-10-04/1_cjtyfns3

Folio Test Tenant Update

1. End of September, wipe of Test was done to accommodate a need in Acquisitions; has been reloaded with a snapshot of data from Production.

2. Testing in Test now more meaningful because the data is much alike to Production; previously was quite different having been populated with data for migration testing.

3. Permissions in Test:

   1. Currently match permissions from Production.

   2. If you need more permissions in Test to try things, please reach out.

4. In progress: working to implement banner color change in Test to more easily tell which tenant one is in.

Accessing Sierra Archive

1. Steps from Dao work to change access from production Sierra to the archive for folks from Main Library.

2. Law pursuing other avenues to make this work for them.

3. Reach out if you need assistance with this.

CAT6 and CAT7 job profiles for records containing 856

1. These job profiles were moved to Production from Test ahead of the wipe of Test last week; both still need documentation in Confluence. Joshua is working on it!

2. Allow for mapping of 856 from bib record to holdings record created during a Data Import job. Populates the link in the “Electronic access” segment of the holdings record.

3. Relationship of link to resource defaults to “Resource” (i.e. the link is to the resource itself); other relationships must be specified in 948$d of incoming record, or manually edited after the holdings record is created.

4. Relationships and equivalents to 856+indicators are as follows:

   1. Resource (856 40)

   2. Version of resource (856 41)

   3. Related resource (856 42)

5. This entails the short-term prospect of maintaining links in both the bib record and the holdings record in order to surface access to these links now in EDS and in future when EDS is able to build e-access from our Folio holdings records.

Morning Glory timeline

1. MG was released to public on Sept. 26. We were expecting it mid-October after EBSCO waited for a few weeks to see how it went for others in the Folio community. Instead, EBSCO wants to install for us in early December after they’ve installed for other, smaller clients to see how that goes. An abundance of caution approach. But we’re waiting on key functionality from MG.

2. There may be some back and forth with EBSCO about the timeframe for MG roll out at MSU.

CMS 2022.09.20

Recording

1. Available here: https://mediaspace.msu.edu/media/MSUL+Cataloging+%26+Metadata++Services+Team+Meeting+2022-09-20/1_g87wyvb2

Updated to Lotus Hotfix 3 in Folio

1. Field protection improved:

   1. Previously, the presence in a target record of any protected field would prevent any other protected fields from coming in (e.g. if target record had 866, incoming record 590 would be rejected).

   2. Now, this has loosened up a little: e.g. if target record has 866, other fields like 590 will be received, but new 866s still are rejected, even if they don’t match.

   3. We expect this to improve even more with Morning Glory.

   4. Continue to ensure that all expected fields in your incoming record show up after overlay. If any aren’t present, add in Quickmarc.

2. Some improvement to browse call number noticed; allowing more searches when classification contains cutter before $b.

   1. More improvements coming in Morning Glory on this, too.

Current known issues in Folio cataloging

1. Reports of MARC SRS and Instance record mismatches: different record in SRS than is being surfaced in Instance in Folio

   1. At time of meeting, seemed isolated to Single Record Import and only a few cases; not pervasive.

   2. Report any cases of this to Joshua.

2. Erroneous 035s generated in MARC SRS

   1. Record updates in some cases are creating junk 035s that combine (OCoLC) prefix from 003 with the Instance HRID in the 001.

   2. These can be deleted if found, but we hope to delete them in batch later.

   3. This is supposed to stop happening after Morning Glory, per EBSCO.

“Call number” vs. “Browse call numbers” in Instance tab

1. “Call number” is a search of the classification element in Folio Instance records. It is not a search of our effective call numbers and can’t be assumed to correlate with call numbers applied to items on our shelves. Generally not helpful to catalogers and you’re advised to ignore it.

2. “Browse call numbers” is in fact a browse of our effective call numbers. This is the option to use.

3. On browse, you can navigate backward and forward in the shelflisting with “previous” and “next” at the bottom of the results page.

4. Also available: effective call number search on the Item tab - but this is a search and not a browse. Used “normalized”, ignore “eye readable”.

5. Heads up: our effective call numbers are all in the same index. LC call numbers and local call numbers from 099 are all together, not in separate indexes as they were in Sierra.

6. Interesting to note: following a result from “Browse call numbers” leads to a handoff in Inventory to a “Call number” search, but using the “shelving call number” element from the item record, which should yield the record(s) we want. Have to navigate back to browse manually to do a browse again.

Sierra-format order record numbers in Folio

1. Acquisitions migrated into Folio in summer 2021, a year before cataloging. They migrated in open orders from fiscal year 2019/2020 and 2020/2021. These generated instances, too.

2. Cataloging happening now on items implicated in the above may have order numbers that have that Sierra number format. These can generally be searched in the Orders App alongside native Folio numbers.

3. Related: if you need to link orders to different Instances (e.g. if brief, uncataloged Instance has multiple orders linked to it and these need to be moved to other Instances that you’re cataloging) there is a method for this, but it requires some guidance. Reach out to Joshua or Lisa Smith if you need to move linkages between any orders and Instances.

Catalog dates and statuses in Inventory

1. Confirmed that cataloged dates and cataloged status still need to be added manually to each Instance when it’s an overlay, if it doesn’t happen automatically.

2. Hoping that this isn’t as necessary with Morning Glory.

Open dates on set records in Inventory and Orders App

1. Inventory and Orders app fail to show the dash “-” in publication date field and in other places when the date is meant to show an open date.

2. Needs advocacy in Folio community to update the UI to show this dash.

3. In Inventory, open date can be seen in MARC SRS.

CMS 2022.08.16

Recording

1. Available here: https://mediaspace.msu.edu/media/MSUL+Cataloging+%26+Metadata+Services+Team+Meeting+2022-08-16/1_17g3m60t

Review and questions regarding checklist for general cataloging in Folio

1. Checklist available here.

2. Still a living document that could see changes.

3. Be mindful of the addition of a step to unsuppress instances once cataloging is complete for any instances that have been suppressed in Acquisitions workflows.

   1. The “Suppress from discovery” checkbox must be unchecked under Actions>Edit Instance.

   2. Suppressed instances are detectable by their red exclamation marks in initial search results and by a warning banner on the instance record itself.

Current MARC field protection behavior

1. MARC field protection is overly strict in our current Folio release, Lotus Hotfix 1.

2. In general, if a target record being overlaid contains a protected field, any other protected field in the incoming record will be rejected (e.g. if target records contains a 590 and incoming record contains a 866, the 866 will be rejected).

3. Rejected fields from incoming records have to be manually added via Quickmarc.

4. Current protected fields include: 590, 866, 867, 868 and 907 (which contains our legacy Sierra .b numbers)

5. This behavior is supposed to be improved with Lotus Hotfix 3 (hopefully September), and then improved even more with Morning Glory (hopefully October).

6. Main takeaway: every time you overlay a record, make sure that all the fields you want to see in the record are in fact there. If they’re not, add the missing fields in Quickmarc.

866, 867, 868 holdings statements

1. Holdings statements for multipart monographs will ideally be contained and surfaced in the “holdings statement” element of the Folio holdings record. Existing multipart mono holdings statements (all bib-level 86Xs) were migrated there.

2. However, EDS is not able to display the “holdings statement” element from the Folio holdings record for monographs, at least not right now.

3. Workaround: continuing to populate and maintain 86X in bib record and have EDS surface these fields as “notes” in the detailed display.

4. Job profiles CAT1 and CAT2 have a mapping to create “holdings statements” in the Folio holdings record from 86Xs in incoming bib records (but field protections are an impediment to this working correctly for overlays)

5. For now, holdings statements for multipart monos need to be maintained in both the bib and the holdings record.

Review of current Folio job profiles for cataloging

1. Job profiles with prefix CAT are those for use with the Data Import app

2. Job profiles with prefix TARGET are for use with Single Record Import in the Inventory app

CMS 2022.08.02

Recording

1. Available here: https://mediaspace.msu.edu/media/t/1_le28t2h8

Folio cataloging errors / issues to be aware of

1. multiple 050s in incoming copy

   1. If left unresolved, multiple 050s will add two call numbers to a created Folio item

   2. If using Desktop Method, you must either eliminate one 050 before exporting from Connexion, or add a 090 with the desired call number

   3. If using Single Record Import, undesired call number text must be manually deleted from the created item record

2. Sierra-formatted 949s causing item creation errors

   1. Records created during the “cataloging in limbo” period must have Sierra-formatted 949s removed before exporting from Connexion; otherwise Folio item creation will fail and cataloger will have to manually create the item

3. duplicate records in .dat or .mrc files exported from Connexion and options for resolving in MarcEdit

   1. Sporadic Connexion error exporting two copies of a bib to desktop

   2. For new cataloging, this will create duplicate SRS and Instance records in Folio

      1. To resolve, delete holdings and item from one of the duplicates, then either:

         1. Suppress Instance from discovery and add statistical code: CATMAN-Delete; or

         2. Copy the Instance HRID and overlay the duplicate record with your next new record (though this solution will not work if you primarily do overlay cataloging)

   3. Catalogers can use MarcEdit to check .mrc files for duplicate records and eliminate them

4. setting UTF8 as default encoding in MarcEdit

   1. Quickly reviewed how to make this setting

Recent changes to job profiles / field mappings in Data Import

1. job profiles renamed for easy reference (CAT1 for new records; CAT2 for overlays, etc.)

2. separate job profiles established for serials (CAT3, CAT4)

Using Folio "duplicate" feature to create items and holdings for add copy or add location processes

1. A potentially faster method for creating added copies or added locations

2. For add copies:

   1. Navigate to the appropriate Instance record, and then to an existing item on an existing holdings

   2. Under Actions menu, select “Duplicate”

   3. Edit the Item record to reflect the desired values (e.g. copy 2, edit workstat, etc.) and eliminate any irrelevant Sierra migration specific notes and fields; remove permanent location from new item; save

3. For add location:

   1. Follow same steps above to create a new item, then

   2. Navigate to an existing holdings record on the appropriate Instance

   3. Under Actions menu, select “Duplicate”

   4. Edit the new Holdings record to reflect the desired values, particularly the permanent location; save

   5. Back on the Instance record, under Actions menu, select “Move items within an Instance”

   6. Drag and drop your newly created Item to your newly created Holdings

   7. Under Actions menu, select “Stop item movement within an Instance”

Special CMS 2022.07.26

Recording

1. Available here: https://mediaspace.msu.edu/media/MSUL+Cataloging+and+Metadata+Services+Meeting+2022-07-26/1_5d18mn38

Folio overlay cataloging demo, using 9XX fields

1. This builds on demo of new cataloging from July 19 meeting (see below)

2. Updates to 9XXs:

   1. 949$g updated to include call number type; defaults to LC, but if cataloger is using a 099 call number, must include: 949$g Other scheme.

   2. 949$b for copy number now defaults to “1” if $b is not included; so this subfield isn’t required in 949 unless you’re creating an item for a copy other than 1.

   3. 949$g for item status now defaults to “In process” if $g is not included; items that require other status besides “In process” will need to have a term supplied in $g (e.g. “Restricted” for non-circulating items in Maps or Special Collections).

   4. 948$b can include holdings temporary location (used for Browsing and other temporary locations)

3. Overlay matchpoint is in 947 field; Instance HRID in $c is only working matchpoint at present.

4. Finding Instance HRID:

   1. Pieces with order streamers will include Folio POL number; search this in the Orders App; follow link in order record to find the associated Instance.

   2. Or, search by title, ISBN, etc. to find the matching Instance directly in Inventory.

   3. Either way, Instance HRID is in the “Administrative data” section of the Instance record and can be copied by clicking the clipboard icon to the right of the number.

5. Job profiles:

   1. CAT2 in Production will overlay on either a MARC source or Folio source record based on a matching Instance HRID in 947$c.

   2. In Test Tenant, use: CAT overlay on uncat instance, any source – create new HI

6. Updating MARC vs. updating Folio:

   1. Updated Folio records will show that MARC SRS is created, Instance is updated, and Holdings and Item are created.

   2. Updated MARC records will show that MARC SRS is updated, nothing happens to Instance, and Holdings and Item are created. The Instance record, however, will be updated as changes to MARC SRS flow up to the Instance.

7. Checking Instance data:

   1. For all overlays, please make sure that Instance values for “Cataloged data” and “Instance status” have been updated with today’s date and the status “Cataloged” respectively. If they are wrong or empty, they will need to be manually updated: use the “Actions” menu and “Edit Instance”

   2. Make sure that any desired 590s from incoming record are present. If not, they must be re-added manually in Quickmarc.

8. Overlaying without creating Holdings and Item (i.e. overlaying / updating MARC and Instance only)

   1. This can be done by deleting 948 and 949 from record in Connexion before exporting, but keeping 947 with $c for Instance HRID of target record to update.

   2. At present, this will successfully update the MARC and Instance, but Data Import will show an error code because it’s expecting data re: Holdings and Item.

   3. A separate job profile may be created later to avoid these error codes.

CMS 2022.07.19

Recording

1. Available here: MSUL Cataloging and Metadata Services Meeting 2022-07-19

2. Folio new cataloging demo (no overlays); skip to these times for:

   1. Context and background: 10:50

   2. Connexion constant data overview for Folio new catalog: 14:45

   3. Connexion export to file overview: 34:50

   4. Importing exported file into Data Import app: 47:14

   5. Navigating an imported record (Instance, holdings and item): 53:09

Announcements

1. EDS is live

   1. Known issues include no display of 856 links in records sourced from Inventory.

   2. There is a layer of remove between Inventory cataloging and EDS discovery; we don’t have the same direct impact on what displays and how as we did in Sierra. EDS display is controlled through a separate custom mapping currently overseen by the EDS Task Force (but maybe overseen with cataloging input at a later time).

   3. EDS display does not refresh immediately as cataloging changes are made. Our MARC SRS records are harvested nightly for changes. Those changes are supposed to show up in EDS after 24-36 hours, but we’re currently seeing longer turnaround times (cataloging from last Friday is still not showing up on this Tuesday).

2. SPC cataloging update

   1. We aren’t able to immediately print public display of SPC cataloging (given EDS turnaround above)

   2. Instead, we will supply the call number for the piece on a streamer (handwritten on any strip of paper for now; potentially a call number label printout on paper later)

Folio new cataloging demo, using 9XX fields

1. Overview of setting up local constant data.

2. Overview of setting up Connexion export to file (i.e. the “desktop method” of exporting records to Folio)

3. Overview of loading exported record into Data Import app.

4. Please note that as of right now (7/19/22) this can only be done with new cataloging - not overlays. That is, if you’re adding a brand new record to the system and not having to overlay anything like an ACQ stub or an already-cataloged record, you can follow this process. If an overlay is required, please await further instruction.

5. Please practice this in the Test Tenant before moving on to Production.

6. Joshua or someone else will go over this process with catalogers one-on-one to get started.

CMS 2022.06.21

Announcements

1. Folio migration is underway; still on schedule to go live on June 30.

   1. This includes full backfile processing with Backstage.

   2. EBSCO helped us catch and fill missing material type mappings; other missing mappings will remain and necessitate a small cleanup project after go-live.

2. July 1: celebrating the work that brought us to go-live; cake & ice cream on the North Patio (just west of cafe).

3. Joshua on vacation July 5-8.

   1. Autumn will be available this week.

   2. It will be the first full week of being live on Folio; we are hopeful we will have a plan and a procedure for catalogers to start exporting records and/or a process those experienced in Folio can help support others while making their first new records in the system.

   3. There is a chance that you will need to continue “cataloging in limbo” for part of that week until we can get you individually started. It all depends on how much progress we’re able to make on Data Import and building of job profiles in the meantime.

   4. This is admittedly an uncertain outlook for the short term. But we will get there.

4. Remote work agreements

   1. Direct reports to Joshua, please message sent on June 17 with Joshua’s instructions.

   2. RWAs are due by July 1.

Cataloging-in-limbo: how are you faring?

1. Observance of cataloging-in-limbo procedure should continue through at least June 30

2. Question: after June 30, should we plan on putting records directly into Folio?

   1. Best that we can say: we hope this will be the case; working in the meantime to build the infrastructure in Folio job profiles that will allow us to make this the case.

   2. There is a chance / likelihood that that infrastructure will not be ready for Folio Day 1, in which case, cataloging in limbo would have to continue.

   3. It’s possible that individual catalogers may need to wait until they receive assistance to set up Folio exports and get instruction before they are able to start putting records in Folio.

   4. Joshua wants to have one-on-one guidance available as catalogers get started.

   5. But we may not be ready for this on Day 1.

3. Lisa R.: keep in mind you will not see authority records alongside bibs in Inventory; if all goes as planned, LC authority records will be in Folio MARC Authorities App (a different app than Inventory)

Contributor searching in Inventory (pre-Morning Glory)

1. We are expecting browse functionality of the contributor index with Morning Glory; until then we have only a simple search available

2. Searching the contributor index via the dropdown on the Instance tab will function simple as a keyword search of contributor fields

3. Using the Query Search option can yield more precise results, using CQL queries:

   1. contributors==”kierkegaard, soren”

      1. This will search “kierkegaard soren” as a phrase in the contributor index, finding hits on the access point Kierkegaard, Søren, 1813-1855

   2. contributors==”smith john c”

      1. This will search “smith john c” as a phrase in the contributor index, finding hits on the access point Smith, John C. (John Cross), 1803-1878

4. So if you know the form of the access point for the contributor you’re trying to find, you can use Query Search to attempt to limit the number of Instances returned more precisely than a generic keyword search in contributor for “smith john c”.

Call number browse

1. This is available in the version that we are migrating to: Lotus.

2. Select “Browse call numbers” from drop down on Instance tab.

3. Has some minor discrepancies in LC call number ordering that are supposed to get fixed.

4. All effective call numbers (including those sourced from 099) are in the same index for now. Upshot is: MSS call numbers, Music CD call numbers etc. will be interfiled with call numbers in LC form.

5. Capitalization does not have to be precise.

6. Left and right truncation using asterisk as wild card is available.

7. Using this in the Test Tenant yielded buggy results; reported to EBSCO.

CMS 2022.04.19

Announcements

1. Custom Catalog Task Force has a survey issued through end of 4/19, seeking input on level of importance for certain missing functionality; catalogers are encouraged to respond

PCC recommendation on use of gender element (MARC 375) in name authority records

1. Do not apply this element to new NARs

2. Eliminate this element from NARs being maintained or updated (Lucas will take it out when reviewing and exporting records)

3. Maintenance of the element in Sierra is unnecessary; Backstage will update our authority records in Sierra and/or Folio in due course

Desktop method for importing records into Folio

1. Joshua demonstrated the desktop method; videos demonstrating this method will be made available in future

2. From our nascent Folio documentation on importing bib records into the system:

Download/upload a .mrc file
This method involves exporting a record from OCLC to file, and then importing that file into Folio using the Data Import app. It is more involved than the other methods listed above, but it does have the potential to meet cataloging workflow needs the other methods do not (carrying over local edits made in Connexion, overlaying existing stub records in Folio, etc.).

While we hope the pull and push methods will eventually have the same functionality, there may be some situations in the interim when this method is the most effective approach for copy and original catalogers.

Click the link below for a helpful screenshot tutorial on using this method, created by LoM's Tim Watters. If you have more questions, especially regarding the job profile options presented by the Data Import app, Autumn Faulkner is happy to share more detail.

https://app.tango.us/app/workflow/Import-a-new-bib-record-and-automatically-create-an-Instance--Holdings---Item-record-ae33d5b5f85d49a999a72ed57800cf4c

Access points for Indigenous peoples

1. Project nearing completion that replaces certain terms where “Indian” is used with alternative terminology

2. Local terms are input as 650_4 for now

3. Further information from Lisa Robinson (posted after this meeting):

I’m pleased to announce that we’ve remediated the nearly 4,000 Library of Congress subject terms used in our catalog for “Indians” and “Indian” by changing those terms to “Indigenous peoples” or “Indigenous” as appropriate. For example, the Library of Congress subject heading “Indians of North America” now appears in our catalog as “Indigenous peoples of North America” and the heading “Chippewa Indians” now appears as “Chippewa people.” These changes both remove language some people find insulting and makes clear the distinction between these terms and “Indian” as referring to the country of India.

Patrons searching on the Library of Congress terms (Indians or Indian …) will be redirected by local authority records created for us by our authorities vendor, Backstage Library Works. We could not have done a project of this scale without the timely and affordable assistance of Backstage.

So, you ask: Is the term “Indian” gone from the catalog?  No. It still appears in the names of corporate bodies (e.g. Indian Agricultural Research Institute), places (e.g. the Indian Ocean), and things (Indian motorcycle). Also, terms for groups of people who are not Indigenous peoples (e.g. Anglo-Indians, East Indians, West Indians) remain unchanged. And lastly, the local heading “Indian comic books, strips, etc.” remains unchanged since it refers to comics from India.

If you see a subject in the catalog that seems changed in error or a subject that should have been changed but was not, please let me know. And, I’m always happy to respond to any questions about this project.

And more information for catalogers from Lisa Robinson:

You do not need to use the remediated headings in your cataloging. When Backstage processes our bibliographic records each month, they will automatically flip the LC headings to the new local ones.

And just like the Illegal aliens heading replacement, we have not changed the FAST headings. So if you ever need to see what headings were originally in the record, you can by viewing the FAST headings.

If you want to see all the new local authority records, search the ARN index (tag z) in Sierra for “bslw”. All the control numbers of the new local authority records start with “bslw” since they were created by Backstage Library Works. Interestingly, these records make use of the 750 field to provide the LCCN of the authority record being replaced.

You may run across some duplicate authority records. This is OK! Backstage gave us some authority records for LC headings we were not replacing but which contained cross-references to headings we were replacing. For example, “Indigenous children” is a valid LC heading that we still use, so we want to keep that LC authority record. But we now also have a local authority record for “Indigenous children” that contains a cross-reference for “Indians |x Children” that we also want. So we keep both authority records for different purposes.

CMS 2022.03.01

Announcements

1. Save the date: March 15, 2PM, MSU FOLIO cataloging preview

   1. Scheduled during our regular CMS meeting slot (and extended slightly, duration TBD); will be inviting original & copy catalogers, others throughout TS. Following up with one-on-one meetings with members of the Cataloging & Metadata Task Force.

   2. Will review Folio record structure, navigation basics, methods for bringing bib records into the system, and MARC editing; basic documentation and videos also in the works.

   3. Will we be able to preview the Marc Authorities App?

      1. No, we won’t be on Lotus yet at that time.

2. Core Interest Group Week, March 7-11

   1. Discussion/presentation sessions, free to register and attend on Zoom; most or all sessions have caps of 300 attendees, so arrive early to avoid disappointment.

3. PCC FAQ documents on contacting authors/creators

   1. Use these as background for authors or creators you are contacting in the course of name authority work, or for your own decision making about making such contacts.

4. Folio Community and Ukraine

   1. The Folio Community is global and in many cases employs developers from around the world. There are development teams based in Belarus and Ukraine who have been active on tools and features that we are directly interested in and giving feedback on. Some of them are directly impacted by Russia’s invasion of Ukraine. We collectively acknowledge this and share our hopes for their safety, their well-being and peace for their country.

Tech Services Space Updates

1. New lighting in TS:

   1. First floor staff areas, including TS, having new LED light bulbs installed; work is ongoing.

   2. Kay obtained confirmation that we will be able to deactivate bulbs after IPF have installed them, to restore lower levels of light needed by some staff.

2. SPC move and TS personnel:

   1. Construction project to begin sometime this calendar year.

   2. TS personnel seated on 3E will be impacted, as everyone will have to be cleared from that floor. You may be brought back into TS space on 1W, or seated elsewhere in the building - none of this is settled yet. But please keep in mind that windows for movement currently discussed range from August to December of this year. Joshua will reach out individually as discussion progresses.

Folio updates

1. Copious feedback given to EBSCO regarding latest test migration throughout February.

2. Test tenant has been updated to Kiwi release, which includes new features such as initial bound-with linking functionality, Elastic Search; Theo reloading our data this week post-upgrade.

3. CMTF working on documentation, short videos for you, for our March 15 event.

Round robin

1. Tad: recataloging our 1492 copy of Malleus Maleficarum (Hammer of witches) to record marginalia that appears to originate from Poland, Slovakia.

2. Lisa:

   1. Indigenous peoples headings: we have approval and funding to change catalog subject language describing Indigenous peoples of North and South America with terminology other than “Indians”, partnering with Backstage. Collecting records to send forward for this project requires individual searches to sort through the various uses in our catalog of the term “Indian” in subject headings. Working to have this complete before migration to Folio.

   2. Visit to State Library of Victoria: a great exhibit on history of books, including coverage of marginalia. Also saw coverage of their zine collection. See videos on their YouTube channel.

3. Tim: now managing the Map Library’s Instagram account.

4. Nicole: re: contacting creators from above, Nicole worked with Elisa who contacted a creator group on Nicole’s behalf via Instagram, and got back a history of the group that way.

5. Joshua: working on a Sierra cleanup project to convert links in 880 fields to now-defunct 440 fields for series statements/headings. Considering re-overlaying these records from WorldCat. Had some group discussion on implications, ideas.

CMS 2022.02.01

Special Collections Paging Procedures for Catalogers

Open

1. Update 2/28/22: this full procedure is now posted here.

2. Welcome, Kris Baclawski and Dayna Topalian from SPC. They and Devon Davidoski will be contacts for this procedure.

3. Final documentation is in progress for this procedure.

4. Allows catalogers to retrieve materials from back door access to SPC stacks, picking up from SPC staff to take back to desk for cataloging work, rather than having to schedule Reading Room appointments.

5. Catalogers will use Aeon paging system (accessed through the Get It button in Sierra OPAC for desired item) to place a request. System is set up for Reading Room scheduling and requires setting a date, but in practice, catalogers will bypass the Reading Room and the date (though turnaround for retrieval from stacks or Remote Storage could still take 3-5 days).

6. In request form “special requests/comments” field, indicate that this is a request for cataloging. This will help SPC staff know to route your item(s) for back door pickup rather than to Reading Room.

7. If requesting particular volumes of a multipart resource, like serials, indicate volumes and/or years desired in appropriate fields in request form.

FOLIO updates

1. Assessment of 4th test migration is underway.

2. Record import processes had issues, but now resolved, so CMTF moving ahead with plans to schedule sessions for familiarizing more catalogers with FOLIO. Plan is to have one big group session, then one-on-one sessions between CMTF members and catalogers. Aiming to do within February. One-on-one sessions could be virtual or in-person depending on needs and preferences. This won’t be only opportunity to try out FOLIO cataloging; nor is this formal training. Just an opportunity to get familiar with it.

Announcements

1. Feb. 1 is deadline to input booster information per University requirement.

2. Exploring project to partner with Backstage to transform LCSH terms pertaining to Indigenous peoples in North America.

3. PCC Participants Meeting this Friday.

CMS 2022.01.18

Announcements

1. Increased volume of WFH, daycare issues, illness: we know this means there will be backlog buildup in the building. Important to know how/where to find things, but the volume of backlog is understood - don’t let this be a stressor right now.

2. Please read Terri Miller’s 1/7 email. Note that KN95 masks are available to staff at the circulation desk. These are more effective than cloth masks.

3. Booster requirement: vaccination info portal being updated to accept booster info on Jan. 26. Info is due by Feb. 1. Everyone eligible for a booster by that time is required to have one. Joshua will not be chasing this information down; HR will. This is a University expectation, unless one has an exemption.

4. Unclear what in-building schedule expectations will be after Feb. 1; library is awaiting further guidance from the University.

FOLIO updates

1. FOLIO Open Forum with Kay and Shawn on Jan. 25.

2. Custom Catalog Task Force being formed, reporting to EDS Task Force. Focused on the custom catalog slice of EDS, assessing what it can and can’t do. Assuming work as the latest test migration in Inventory is being used to populate a fresh load in our test instance of EDS. It’s anticipated that there will be wider assessment of this iteration of the test custom catalog than there has been to date.

3. The test migration currently in progress into test Inventory is the fourth iteration of these migrations. We’ve been through rounds of feedback from CMTF to EBSCO each time. Same will happen this time: CMTF documenting issues seen and reporting to EBSCO for resolution.

4. CMTF is hopeful about using this test migration as the basis for familiarizing more MSUL catalogers with FOLIO. Inevitably will involve some level of virtual group meetings and either virtual or in-person one-on-one meetings. CMTF is starting to plan how to roll this out. It won’t be formal training, but a chance to initiate you and gather initial questions from you to help inform later training.

RDA Toolkit Update

1. Our account was left behind in RDA’s recent server migration; this is now fixed.

2. However, our concurrent user count is off. We should have around 10; seems we only have one or two. Joshua will report to Diane.

Policy Statements in New RDA Toolkit

1. Tim Kiser attended given role on a cartographic cataloging committee. They have a best practices document they hope to convert into an RDA application profile with policy statements.

2. Policy statements work entirely differently in new RDA than in old: what were previously long texts have to be exploded into discrete statements.

3. Watching the recording (when available) will be worthwhile (at least the beginning, remedial part) as an overview or review of how policy statements and application profiles will function in the new Toolkit.

4. Application profiles function like a kind of cheat sheet of which RDA elements are required or not for a given cataloging context.

5. Policy statements indicate how / if to apply guidelines on elements collected in application profiles (or in general). These will be consulted more regularly. RDA will be wide open with options on how / if to apply certain guidelines. Policy statements will narrow scope on these options for a given cataloging context (e.g. PCC, LC). So policy statements will be a key aspect of how we navigate and use the new Toolkit.

LC BIBFRAME Update, Jan. 24

1. Upcoming webinar from LC on BIBFRAME developments, including a presentation from Stanford on the use of BIBFRAME connecting to FOLIO.

2. Stanford has made related presentations to the FOLIO Metadata Management Special Interest Group (MMSIG). Their descriptions actually live outside of Inventory; they have identifiers stored in Inventory that resolve to those external BIBFRAME descriptions (stored in Sinopia).

Other upcoming events

1. We are in ALA Midwinter seasons; a good time to keep an eye on listservs for events occurring virtually.

2. PCC Participants Meeting Feb. 4, 11-1

3. CORE Interest Group Week Mar. 7-11