2024-04-04 Metadata Management Meeting notes

Announcements

WolfCon24 call for submissions has been extended to 30 April 2024

Publication dates (sorting/filter/mapping changes)

@Christine Schultz-Richert

UXPROD-4746: Sort, filter, and mapping changes for DatesIn Review

Q: Take date from 008 field?

• consistently formatted

• more useful for serials

• The 008 should be used to populate publicationPeriod.start and publicationPeriod.end at least.

• Need reports of corrupted 008 date

• multiple 264 fields

• fixed fields indicate what kind of date (008)

• For films: distribution dates can be important in addition to the original date of release

Q: If we take the date from the 008 and discovery is being driven by Instance data, do we need a place to display the publication statement also?

Q: Source for dateOfPublication?

• Not sure about the source for this data point.

Idea: Display the 206/264 date in results list and use the 008 date for sorting

• Serials cataloging would find it useful to see the 008 in the search result display

Q: Add a new section of fields to Instance record for type of date/publication status?

• Yes, need to be able to edit and populate the data in a native FOLIO Instance record

Q: How does Bibframe represent date data?

Q: What do we call this column be in results list?

• sort date?

• date?

• Consolidate publishers column into a publication statement with the date at end?

Q: Does this cover use cases when the 008 has u, ex. 18uu?

Q: Converted date handling? Julian calendar into Gregorian calendar?

Chat comment from f-piscitelli: For rare books, I opt for more granularity in the publication data, keeping place, name of printer, date etc. separate. We use the date (in Arabic numerals) in the 008 for sorting.

@Christine Schultz-Richert Wiki link here: Publication date filter and sort requirements

Multiple Graphical Representation

@Laura E Daniels

Continuation of discussion during 2024-01-25 Metadata Management Meeting notes

Slide deck with proposal and outstanding questions

Q: What do we want labels to look like in the UI view mode?

Q: Search results display. How do we want it to be displayed in the results list?

Q: Statement of responsibility. is another element (e.g. title statement) needed?

Need a way to indicate what the vernacular script is (i.e. Chinese, Russian, Japanese, etc.).

Comments:

• Tenant Setting needed to not display vernacular based on local needs.

• Some staff would search for the original script if they knew the language because the transliterations are not always accurate.

• Need to loop in Marva Editor users to ensure this will work for them as well. And others using other metadata editors.

• Connection/impact to Orders App. Some libraries collect in other languages and acquisitions staff know the vernacular language.

• Library of Congress is interested in this functionality.

Please comment and ask questions on slide deck.

Want to join the informal group? Contact @Laura E Daniels

PC updates

@Charlotte Whitt

PC 2024-04-04 Meeting notes

Announcements: Submission of WOLFcon sessions has been extended to 4/30/2024

Linked Data Module - presentation by @Doug Loynes The Citation development team has worked on this for a year now. This new work is engaging with pilot libraries and the community.

The new module is building upon the triples approach (developed by Steve Martin). The linked data will be ‘stand alone’. Library will be able to down load the package, and not necessarily a FOLIO library. FOLIO libraries will be able to adopt it easily.

Linked data - data transformation (into / out of MARC). Support for BIBFRAME 2.0. Support for multiple vocabularies

MARVA → LC’s BIBFRAME editor (original cataloguing, copy cataloguing). MARVA is the UI catalogers will access and work in.

Data administration. Ability to support new ontologies.

Search is imbedded in the MARVA app.

Synchronisation with MARC and from MARC to Linked data. MARC will be the exchange format. The instance display is governed by the underlying MARC record. The MARC in SRS will not be editable, only a transformation layer. Authority Control in MARVA is to rely indirect on MARC Authority controlled data.

Potential will there be APIs for sharing data across institutions. Gloria explains that there will be unique identifiers to the data in Data Graph. From a technical perspective there is no limitations for data exchange.

API Overview - presentation by Brooks Travis and Maccabee - slide deck here

Overview and quick demo of how to do GET and PUT request in e.g. Postman.

BELA (Bulk Edit and Lists App)

Jennifer Eustis

2024-04-02 BELA Meeting Notes . If you have time to participate in bugfest, that would be helpful. There are several bugs that have been identified with Quesnelia (see notes for details). If you would like to participate in UAT for bulk editing of notes and electronic access in holdings, that would be helpful.

Data Import Working Group

Jennifer Eustis

2024-4-3 Data Import Subgroup meeting . The working group spent time discussion the creation of MARC orders with inventory. There are a some bugs that affect the quantity in the POL. FOLIJET is also working on the set to delete functionality. If you are interested in this and what features are important for you and your institution, this spreadsheet lists the Jira issues, definition for delete, and a number of enhancements/features.

quickMARC Subgroup update

Raegan Wiechert

2024-04-03 quickMARC subgroup Reviewed UAT of authorties and leader help and discussed Bugfest UAT.