September 4, 2026

See time zone conversion Meeting norms Present: Crystal, Cerberus, Ellie, Jorge, Jian, Laura Absent: Deborah Time: Notes:

Informal Co-working session

August 27, 2026

See time zone conversion Meeting norms Present: Absent: Deborah, Cypress Time: Notes:

Informal Co-working session

August 21, 2026

See time zone conversion Meeting norms Present:Crystal, Laura, Jorge, Ebe, Dee, Sita, Jian Absent: Deborah, Cypress, Ellie Time: Notes:

Roles for meeting/agenda review (5)

Updates (5)

• Scheduling poll for main meeting coming soon: of course, Crystal's new job has a required meeting at exactly the same time
• Crystal is scheduling 1:1 mapping sessions with Ellie and Sita. If anyone else would like one, email Crystal

Questions from Deborah (15)

• Visiting with NLNZ folks next week. They hope to have M2R spreadsheets ready to share with her by then
• OK for her to share a copy of our WEM mapping spreadsheets with them? Just static copies
• Do these need a similar CC-BY-SA license, or something different?
• Attribution: "The MARC2RDA Project"?
• Are we still happy with the licence we chose during Phase I?

Co-working session (rest)

• See Current Project Priorities

Wrap-up (10)

Action Items

Backburner

August 14, 2026

See time zone conversion Meeting norms Present: Crystal, Laura, Deborah, Ebe, Jian, Kyla, sita, Doreen Absent: Time: Ebe Notes: Doreen

Roles for meeting/agenda review (10)

Updates (5)

• Recording source on hold pending further discussion (tied to data provenance; cannot proceed until that is resolved)
  • New status created: "On hold pending further discussion" (aka "Discussion needed") so parked items don't look stalled as "In progress"
• Deborah in NZ: participates asynchronously and joins only non-main-group meetings
• WikiBase workshop for SWIB: Crystal will run official RDA cataloging session; plans a short project showcase demonstrating an RDA application profile in RDA/RDF
• BSR official RDA metadata application profile: PCC draft/beta open for feedback
  • Crystal submitted extensive feedback; form only takes one small item at a time (requires BSR element name per submission)
• NLNZ document raised as another official-RDA resource; Ebe noted this is public, no need to log in.

Mapping Manifestation Elements Table (45)

• Ready: RDA Element Label, RDA curie column
• Needs checking: Datatype, Source: Searched MARC
  • Source: Searched MARC: is the MARC field/subfield/position a reliable source of data for this element? Check RDA definition for the element against the MARC field instructions and examples. If in doubt about suitability check the Example file provided. If still in doubt, bring to the group in a later meeting
• Source: TK optional to add
• Volunteer needed: NLNZ R2M, Source: PCC
• Source: M2R Mapping: follow current instructions
• Source: M2R Coding: leave for now
• RDA Vocab: volunteer needed to copy link from elements & vocabularies table to its appropriate element
• Searched MARC is the priority column. Check RDA definition against MARC field instructions/examples to judge if the field/subfield/position is reliable; use Example files when unsure
• How to fill Searched MARC: AI only matches exact terms and misses much (MARC vs RDA wording). Resolved: tackle collaboratively (manual + search + AI), cataloging expertise required
• Source: TK worthwhile? Overlaps M2R mapping. Resolved: optional; if done, do the whole column at once, not per-element
• Deleted rows reconsidered case-by-case, not automatically; 500 note field undependable unless from a controlled vocabulary
• Clarification: verify datatype/object per row (at least one was wrong); Searched MARC column is still raw

Reviewing Expression and work tables (5)

• Approved MARC-first pass
• If this workflow is not clear, please email Crystal to set up a 1:1!
• Two-step workflow: proof mark = first pass judging if a MARC field is a reliable source; review = a different person confirms before it advances
• Red rows (element maps to structured description, not an IRI) are expected and handled by the FMV table; no action needed
• Reminder: No comments in Drive tables; all comments go in GitHub issues

How data provenance works (15)

• Demo deferred (meeting ran long); scheduled as a future-meeting topic

Workflow: Approved Mark → Ready for FMV → Mapping Spreadsheet Update

• Review must be done by someone other than the first-pass author
• Crystal owns mapping-spreadsheet updates (others trained later only if they did the mapping work)
• Conditions: new condition = new row; if too complex, record in the GitHub issue and reference from approved mark

Wrap-up (5)

• Possible topic for next meeting Co-working / working session; Crystal suggested next week could be co-working time to go through some of the flagged (red) questions in the work and expression tables together, rather than a formal agenda.

Action items

• Crystal:create GitHub issues for all manifestation elements; update spreadsheets after FM reviews

Backburner

August 7, 2026

See time zone conversion Meeting norms Present: Deborah, Crystal, Ebe, Jian, Adam, Laura, Ellie, Doreen Absent: Cypress, Sita, Zhuo, Ying-Hsiang Time: Ebe Notes: Deborah, with some additions from Ebe

Roles for meeting/agenda review (5)

Updates (5)

• Working with iSchool to see about options for storage of project triplestore data. Email Crystal if you're interested in what's happening, she's working with Rick and Gordon currently.
• Crystal has a training September 11, meeting canceled
• Email Crystal for a 1:1 mapping session if you haven't already and you want one!
• Fill out the punctuation survey and time/work assignment survey
• Crystal proposing Wikibase RDA/RDF cataloging workshop for SWIB
• Crystal can attend IFLA in person next year. Probably want to do a presentation there. If you're going too let's collaborate
• Next week is Deborah's last synchronous meeting until December
• Crystal now has access to Oxygen (via her iSchool account) for use on the project. She can give licenses to students on the M2R project as well--email her for access!
• Crystal has added Current Project Priorities

Action items (ongoing) (5)

• Qualifiers - ongoing
• Phase II instructions have been added to Github workflow
• Current project priorities in righthand side of wiki
• Use self assignment tab for Work elements. Crystal will create issues for these in Github

Stored MARC Records (5)

• Suggestion made to move stored MARC records from output as note on (metadata) manifestation to a separate online store. Set up as viewing only, not for downloading purposes
• Each MARC record will get a URI and be pointed to from the transformed triple
• Each record is in text so these will not be downloadable
• See: [TRIPLESTORE]: Testing load scaling and filtering#901
• Suggestion approved by group

Remove “F” from MARC field tags in displays (5)

• A suggestion has been made to strip "F" from MARC field tags in stored MARC records output by processing.
• See: [TRIPLESTORE]: Display of MARC record as metadata includes "F" before MARC field tags #902
• Suggestion approved by group
• DF suggested that CP could "grey out" the coding that added the letter, in case it was needed again in the future

Updating our String encoding schemes_SES (20)

• We need a new version of our current SES for access points. This is essential for deduplication progress
• Lower case terms for vocabularies used as qualifiers (aside from proper nouns)
• OK to map 245$a$n$p + =$b + ;$b as Title proper?
• What about initial articles in 245 $a a. Map as title of manifestation with and without b. Map as access point for manifestation a. With? b. Without? c. Both? d. What about ellipses at the start of a 245$a a. Map as title of manifestation with and without b. Map as access point for manifestation a. With? b. Without? c. Both?
• In MARC the indicators did 2 things. They were used for indexing and display
• LC may not exclude initial article in indexing
• AP for Manifestation - aggregating works do not currently exist so us '=' for parallel titles
• if we are looking for disambiguation then including a parallel title may disambiguate it from a title that doesn't include it
• if we are talking about semi-colons then we are talking about a different Work
• A point was made that it may not be conceptually correct to include other elements into title proper
• CY set up discussion: String Encoding Scheme Discussion #903
  • These and other questions in 'red' will be added here for asynchronous and/or meeting discussion
  • The document will be discussed in later Group meetings and:
  • Missing instructions for Items, Agents, Places, Timespans added
• Individuals can study the paper and add questions here for asynchronous and/or meeting discussion
• Kyla will develop a shortened version formatted as a table, with:
  • Entities
  • Base AP:
    • RDA element
    • MARC
  • Qualifiers
    • RDA element
    • MARC
    • Including new ones identified as useful for various content or carrier types, etc., as they are identified

Mapping 100% MARC (15)

• A suggestion has been made that we should try to push a sample file of every MARC record through the transformation code and load the results to a separate Experimental triplestore for public viewing alongside the current public triplestore “M2R-PROJECT”
• Estimates are that under current processing:
  • the transform of approx. 50% of records will look reasonably complete
  • the remaining 50% will look wonky, but will be improved as mapping and coding continues
• This will get a "skeleton" of WEM up for records we want to process for Phase II
• In future presentations we can be very specific with the caveats about what looks wonky and why
• For authority records for Work PCC only requires a 1XX and 670 MARC field

Notes

• Warning notices about the test/alpha/wonky triplestore will be posted prominently and stated early and often in any presentations using the same
• The Alpha version of M2R-PROJECT will be updated in synch with the Beta version
• CY, CP, DF to meet and discuss before bringing a more fully formed proposal to the group

Identifying the parallel expressions in a record for a parallel aggregate (rest)

• How can we reliably identify the parallel expressions in a record that we have identified as describing a parallel aggregate:

• When 7XX I2=2 fields are present:

  • all with language subfields
  • one without a language subfield, one or more with them
  • When no 7XX I2=2 fields are present, but 041 language codes are:
  • 1XX + 24X + 1st 041 code
  • 1XX + 24X + 2nd 041 code

Notes:

• Q: what about records with multiple 041$a AND multiple works?
• A: A: Such records should be identified by the Aggregates patterns as CAM (collection aggregates) not PAM (parallel aggregates). If they do get through the net and if each 7XX does not have its own $l then each 7XX without $l will be given as a separate expression for each 041$a present. Contributing libraries should make every effort to ensure that each 7XX has its own $l added in legacy records and new records going forward.
• See examples at: PAM Questions--a work in progress
• The analysis is fine for older records but not Original RDA records

Wrap-up (5)

Action items

• Crystal will finish adding mapping work elements issues to GitHub today (this is done)
• All will fill out Punctuation polland Hours/work assignment poll
• Continue mapping work elements
• Schedule 1:1 mapping sessions

July 31, 2026

See time zone conversion Meeting norms Present: Crystal, Cypress, Deborah, Ellie, Jian, Jorge, Ebe, Doreen, Laura Absent: Time: Jian Notes: Cypress

Roles for meeting/agenda review (5)

Introductions (5)

Updates (5)

• Punctuation poll
• Crystal setting up 1:1's with mappers, email if you'd like one!
• 3 more meetings with Deborah before her vacation! Will start doing more working meetings
• Cypress is on vacation the next two Fridays!

Action items (ongoing) (5)

• Punctuation ✔
• Crystal will send out a poll on time commitment - in progress
• Cypress will send out a poll on punctuation ✔
• Deborah and (? Crystal?) will fill in the Qualifier column in Elements and Vocabularies table - will be happening in the next couple of months
• Discuss with Crystal the meaning of status label "Done" in the issue and clarify workflow for various scenarios after Review in the documentation
  • dual purpose - mapping issues go from 'ready for transform evaluation' to 'done'
  • Transform issues go from 'transformation in progress' to 'done'
  • See project board
  • so if there is no FM, does it go straight to ready for mapping spreadsheet update?
    • yes
  • and if no changes need to be made to the spreadsheet or transform, does it go straight to 'ready for transform issue evaluation'?
    • yes
• When the MARC files to use with MARC report are available, Deborah will put "clickable" links in the meeting notes when she did the tutorial (July 10) or share them in some other way if she prefers ✔

Phase II Workflow & Priorities (20)

• Step by step instructions are finalized enough for us to get going
• Crystal will move them to our Instructions area today
• Crystal will make a tab in the wiki for current priorities
• Crystal will meet with Ying-Hsiang about de-duplication work
  • She will loop Deborah and Cypress in on this
• See Phase II Master plan

M2R-Search & RIMMF6 for Review (45)

• See steps
• Discussed point of identifiers while looking at manifestation in M2R-Search
• Make sure review things get into GitHub - put where you think it makes sense, we can always move issues and discussions around
• No inverses makes things complicated in triplestore
• Discussed UWLSWD vocabs

Wrap-up (5)

Action items

• Crystal will move phase II workflow to our Instructions area today
• Crystal will make a tab in the wiki for current priorities

Backburner

• UWLSWD vocab alternatives/issue

July 24, 2026

See time zone conversion Meeting norms Present:Cypress, Deborah, Laura, Ebe, Sita, Kyla, Jian Absent:Crystal, Jorge Time:Ebe Notes:Laura

Roles for meeting/agenda review (5)

Updates (5)

• M2R-search now shows element labels and vocabulary terms in any language for which TK has translations.
• Crystal will be sending out a work poll to project members soon for an update on
  • Approx. how many hours per week you can spend on the project
  • Whether you prefer to be assigned work, rather than doing self-assigning?
• Crystal has said that she will hold one-on-one mapping sessions with any interested mapping team member to get going on the "Approved MARC" step; throughout late July and August
• Cypress re. coding for mapping from FMV tables is ready; still working on instructions for mappers. Then need FMV tables to be ready for coding
• Laura installed MARC Report and had trouble reaching the links in the slides to download files to find examples in. Deb0rah said the files were temporarily offline but should be available now. She'll put clickable links in the meeting notes for the MARC Report session.

Punctuation (10 min.)

• Issue: Subfield codes appearing in element values #651: Retaining, replacing, or adding punctuation in aggregated statements (250, 260, 264, 200, 440, 490)
• If ISBD punctuation is not present before a subfield code:
  • but other punctuation is, then should we:
    • retain it
    • or replace it with ISBD punctuation (see the MARC Punctuation Guide for Field Strings; see the instructions above?
  • but if no punctuation is present, should we add:
    • ISBD punctuation
    • or our separating punctuation for qualifiers ' : '
    • or another character (since these are not qualifiers), e.g., ' | ' A poll will be sent. It will refer those who don't understand to the meeting recording/notes.

Short term priorities for deduping entity descriptions (30)

• Because we use our Access points as the basis for our IRIs for entity MDS (metadata description sets), our focus has been and will continue to be on the following:

  • Fix end of subfield value punctuation
  • SES for APs: String encoding schemes_SES needs enhancements
    • Needs list of current APs for WEM and Agents, and their qualifiers
    • Needs additional qualifiers to be identified
      • see column in Elements & Vocabularies
      • Note - resolve what properties are entity boundaries -- aspect ratio? (post-comment, see RDA Expression which explicitly says it is == la)
    • Needs values for those qualifiers to be made available - and "mined" if not specifically fielded, if feasible - from:
      • WEM Element tables (Mapping expression elements & Mapping work elements); need:
        • "M2R mapping column filled in for:
          • Work table: attributes and other tabs
          • Expression table: other tabs
        • "Approved MARC" column filled in
        • All Field/subfields reviewed and ready for:
          • Adding to FMV tables
          • M2R mapping spreadsheets
            • Adding if not done
            • Revising if review shows it is nec
      • FMV Tables (Vocab tables) need
        • Proof reading for minor glitches, questions indicated, needs completion, etc.
        • Reviewing for:
          • RDA specific fields
          • Other fields
      • FMNV Tables (Non-Vocab tables)
        • Can any AP qualifiers be
          • Structured descriptions, e.g., terms that are not from a vocabulary; dates
          • Unstructured descriptions

Approve and review something simple (30)

• Steps * Approve * Steps: Phase II mapping workflow * III.B. Source: M2R Mapping (Mapping team) * II.B. Project statuses for mapping issues * Review * Phase II mapping workflow: Review (Group)

  • Mapping expression elements:

    • Award
    • We were uncertain of status assignment if no FMV or FMNV is involved and mapping has already been reviewed and coded in Phase I and no changes are indicated. Is it "done" or is there another layer of review (maybe for the code, which was reviewed in Phase I)?
    • We are also uncertain if FMV/FMNV is indicated but mapping table also needs updating - how/when do we assign statuses after review so nothing falls through cracks?

  • The following items were not reviewed due to time - maybe next meeting? Meanwhile Deborah is working on a detailed step-by-step scenario for the Review stage

    • Form of musical notation

  • Mapping work elements:

    • academic degree

Wrap-up (5)

Backburner

Action items

• Crystal will send out a poll on time commitment
• Cypress will send out a poll on punctuation
• Deborah and (? Crystal?) will fill in the Qualifier column in Elements and Vocabularies table.
• Discuss with Crystal the meaning of status label "Done" in the issue and clarify workflow for various scenarios after Review in the documentation.
• When the MARC files to use with MARC report are available, Deborah will put "clickable" links in the meeting notes when she did the tutorial (July 10) or share them in some other way if she prefers.

July 17, 2026

See time zone conversion Meeting norms Present: Cypress, Crystal, Deborah, Ebe, Sita, Kyla, Jian, Laura Absent: Jorge Time: Ebe Notes: Crystal

Roles for meeting/agenda review (5)

Updates (5)

• Cypress needs to reschedule the upcoming transform meeting. If you want to attend, please fill out this when2meet as soon as possible
• Crystal sent out triplestore and planning team polls this morning
• Last week's (internal) meeting recording is here

Approved MARC for expression elements - explanation (15)

• Next step is "Approved MARC"
• Today, take it from "Ready for Approved MARC" through to "Awaiting Review" or "Ready for FM"
  • See instructions here
• Discussion of when to indicate a FMV table is needed (See: Elements & Vocabularies Table)
• Assess: What are the values that this element needs?
• Go to the MARC document page cell, and go to the MARC field. Look for your value
• A way of double-checking the work that was done in the first place

Approved MARC for expression elements - working time (30)

• Mapping expression elements table

Review together (30)

Wrap-up (5)

Backburner

Action items

July 10, 2026

See time zone conversion Meeting norms Present: Deborah, Laura, Ebe, Jian, Jorge, Kyla, Sita, Ying-Hsiang, Doreen Absent: Cypress, Crystal Time: Jian Notes: Doreen

Roles for meeting/agenda review (5)

Updates (15)

• Crystal needs to attend a family funeral on the 24th: can anyone else facilitate that meeting?

Review to-do items from last month (15)

MARC Report Tutorial (30)

• Using MARC Report for creating text reports of examples for MARC fields/subfields that may carry RDA element values (populating the "Example files" column in the WEM element mapping tables) Full walkthrough is in the zoom video recording and the slide deck; notes below capture only the decisions and takeaways.

• Purpose: use MARC Report to build text reports of examples for MARC fields/subfields that may carry RDA element values, to populate the "Example files" column in the WEM element mapping tables. Examples let the team judge whether a field/subfield actually works for a mapping and whether conditions are needed.
• Recommended file: run against the large complete file. Small files do not give a good sample; the full run takes ~10 minutes. Links to the two files are on slide 4 of slide deck and here:
  • m2r-phase1-complete.mrc (compilation of UW, NLNZ, and LC records) Download from: https://marcofquality.com/pages/m2r-phase1-complete.zip
  • m2r979.mrc (SEM, AAMnotAW records; what actually loaded to the triplestore) Download from: [https://marcofquality.com/pages/m2r.979.mrc.zip](https://marcofquality.com/pages/m2r.979.mrc.zip)
• Software notes: MARC Report is now free to download and includes a portable installer that runs from a thumb drive (useful where libraries restrict downloads). MARC Edit is an acceptable alternative if it produces similar example output.
• Output handling: once a review is done, the report is uploaded to the web examples folder on Google Drive and the link pasted into the relevant WEM element table.
• Field 518 (Laura's question): parked as a complete review to revisit with simpler sample records. Open question on how to handle data about the finding of a physical object, and whether terms like "captured" / "executed" introduce ambiguity, before writing transform conditions.

Mapping Work elements reviews using example files (30)

• FMV tables that are or could be used as qualifiers for WEM, such as the Elements & Vocabularies table. These are the ones that should be finished first and have ready for coding.
• the intended column work could not be completed without Crystal and Cypress.

Access point qualifiers

• Start with elements containing a value usable as an access point qualifier. Qualifiers should come from controlled vocabularies, since free-text values are unreliable for matching.
• Last year's access point decisions (manifestation, single-work expressions, works) need revisiting. Manifestation had to be constructed by the team (no MARC access point exists) from a preferred title plus qualifiers such as date, edition statement, carrier type, encoding format (e.g., PDF, XML), and 347 / 300$a terms.
• Category of work rejected as a blanket qualifier (would appear on every entity, behaves more like a subject); may still help in limited cases.
• Aspect ratio designation (expression element): use both the MARC terms (full-screen / mixed-aspect / wide-screen) and LC's additional terms, mapped to the RDA vocabulary. In an access point the term is used, not the IRI. Likely useful only as a third or fourth qualifier in limited situations.

Entity boundaries

• Laura: is the same film in a different aspect ratio a different expression? The RDA Toolkit gives principles, not a fixed list, so the application profile must decide. Different catalogers may draw the boundary differently, which is why a community application profile is needed. To be settled.

IRIs, matching, and de-duplication

• The application profile must specify the order of controlled-vocabulary elements, because the AP is concatenated and lowercased to generate the entity IRI. Without a fixed order, IRIs for the same entity differ and fail to match, defeating de-duplication in the triple store.
• New idea (relayed by Deborah from Gordon): an element can be excluded from the displayed access point but still appended to the IRI (concatenated, normalized) for matching. The value stays visible in the description, so it is not hidden. Helps avoid overly long access points while still preventing duplicates. See the SES document, which currently covers the access point string encoding scheme.
• Comment from Laura: You could filter for specific terms/IRI for category of work or expression before applying them as qualifier. Deborah agreed: It would have to be based on our application profile for SES.

Wrap-up notes

Backburner

Action items

July 3, 2026

NO MEETING

June 26, 2026

See time zone conversion Meeting norms Present: Doreen, Crystal, Deborah, Jorge, Cypress, Ebe, Jian, Kyla, Dee Absent: Time: Ebe Notes: Doreen

Roles for meeting/agenda review (5)

Updates (15)

• TSIG pre-conference presentation (slides)
• Sarah stepping back from project, started a new job post-graduation (Thank you and congratulations, Sarah!)
• MLIS student Ellie Petersen joining imminently
• Things we will cover in upcoming meetings
  • Plan to fit in demos, roughly one per meeting: RIMMF, Sinopia, MARC report, and M2R online.
• Action items from last week:
  • Crystal did the ALA CORE TSIG presentation, with review from Cypress, Ebe, and Deborah (thank you!)
  • Crystal rewrote the mapping and reviewing instructions. We'll go over them in this meeting
  • Crystal created a test issue for Aspect ratio designation
  • Source: M2R mapping progress check
  • Pattern searches in Example files column (Deborah)
  • Investigate ISBD punctuation code from #651 and report back, for #765, start by removing the title ISBD/leader condition and test (Cypress; in progress)

Workflow review (30)

• Draft workflow for Phase II mapping, take 2
  • Crystal rewrote most of the workflow based on feedback. It's now sequential with clearer roles, and all statuses across the project board and spreadsheets were revamped to match, with new statuses added to show where each item is in the process.
  • Statuses for mapping issues: to do, in progress, ready for approved mark, approved mark first pass, awaiting review, review in progress, almost done / waiting for decision, ready for FM, FM in progress, ready for FM review, ready for mapping spreadsheet update, mapping spreadsheet update in progress, ready for transform issue evaluation. Multiple statuses can now be assigned to one item (e.g. needs a decision while also in another state); remove a status once it no longer applies.
  • Decisions and disagreements: complete the data type/object column, make agreed changes, review changes. If unresolved, take it to an asynchronous poll/vote for about a week (with the option to abstain), then bring it back the following week.
  • Examples: the example files column is optional; examples are never required. If consulted, the first-pass person or the group at review can add them. Example records will be stored in an "examples" folder on Google Drive (not in the FMV examples tab, which was an experiment). Deborah can demo generating examples via MARC report next time; revisit at the next meeting whether examples are added all at once or by the approved-mark person.
  • FM / FMV evaluation (Deborah): Deborah decides whether FM/FMV tables are needed and links them. Vocab tables are already done; non-vocab ones wait until approved mark is decided. Needed → status "ready for FM" (unless already done); not needed → "ready for mapping spreadsheet update"; in progress → link table and set status accordingly.
  • Mapping spreadsheet update: Crystal is the backstop to ensure all get done and will do many; Laura and others who did Phase I mapping can help. Self-assign, set "mapping spreadsheet update in progress," update the field-by-field spreadsheets for the transform team. Don't repeat info from the FM tables; link to them instead. If no changes are needed, note it in the issue rather than adding to the spreadsheet.
  • Transform issue evaluation: Crystal and Cypress evaluate which transform issues are needed, self-assign, set "transform issue evaluation" status, then create field-by-field transformation issues (one per field/element pair) and close the mapping issues. The mapper isn't expected to judge whether coding is needed; Crystal or Cypress decides.

FMV Table Instructions (30)

• Not discussed given only about 7 empty FMV tables are left now.

Wrap-up (5)

Action items

• Crystal: send a poll about attendance for next week (July 3rd observed US holiday) and decide whether to meet.
• Crystal: create element-mapping issues for expressions and works (assigning current assignees and best-guess statuses). When assigned, check that the status is right and that items are in fact ready for approved mark.
• Crystal: mark the old assignment tab "deprecated" and gray out elements that now have issues, leaving the rest live during the migration.
• Everyone to keep filling the Source / M2R mapping column, focusing on the work table, and self-assign on GitHub issues.
• Deborah: important to qualifier columns for works (what would be added to a work to qualify it as a boundary element) to support de-duping; fuller discussion in the future.
• Cypress to continue #651 and #765.

Backburner

June 12, 2026

See time zone conversion Meeting norms Present: Crystal, Cypress, Ebe, Kyla, Doreen, Jorge, Jian, Deborah, Laura, Sita Absent: Time: Jian Notes: Doreen

Roles for meeting/agenda assembly (10)

Updates (5)

• Crystal presenting a brief overview of project outputs at ALA CORE TSIG next week
• The proposal was accepted. Crystal will give a quick overview of where the Phase One outputs live and how to access them. With Rick's permission, she would like to show the web transform program Rick built and the related triplestore search/display tool, so attendees can see and open them.
• Date is June 23rd, online. It is short (roughly 10 to 20 minutes). Anyone who wants to review or collaborate on the presentation should email Crystal.

Action items from last week (5)

• Crystal will send out reminder email for project plan approval
• Crystal will work on mapping and reviewing instructions - will test with Aspect ration designation
• In progress. Instructions will be made more sequential and assigned to specific groups/roles (as Laura suggested), so it is clear which role does what at each stage. Testing of the aspect ratio designation still needs to happen; the project plan will be adjusted after that test.
• Cypress will work on ISBD stuff once she has her Oxygen license back :)
• Cypress has her Oxygen license back, so this is in progress or starting shortly.
• Mappers will work on work elements

Mapping work elements (5)

• Deborah did some more work on the Source columns but can’t see that any work has been done on the "Source: M2R mapping" column.

• Deborah adding Pattern searches in the “Example files” column, for providing MARC examples of the suggested fields/subfields

• Status updates: do not use "awaiting review" for this work. The presence of values in the Source M2R mapping column indicates the row has been done. If someone hits a problem, add a question mark to the status (as was done in the Phase One main mapping) rather than using "awaiting review." Crystal will put this in the instructions.

  • "Approved mark" means the group decided to map it. That is part of the first pass and is reviewed later in the review stage. The approved-mark column is not in use yet.
  • New workflow: once one element is run through end to end, Crystal will create a GitHub issue per element so progress can be tracked there ("source M2R mapping done," "approved mark done," etc.) and questions discussed in the issue. The missing piece is agreeing the workflow itself; Crystal, Deborah, and Cypress need to settle it first. Dorian's questions from trying the workflow are helpful for finding where it breaks.
  • Subjects: not in the element assignment yet. Hold off on subjects for now and concentrate on attributes; the group would get tangled up going down the subject road. Dorian will stop work on subjects, pick up attributes, and an element assignment for subjects can be added later.

FMV Tables (10)

• Doreen and Deborah continue to work on the F&MV tables. We had an issue with the F&MV: Illustrative Content table re. singular and plural terms, and I would like to get your feedback on this. Here is the discussion.
• Gordon provided feedback async. Decision: treat the singular terms as acceptable matches. LC plural terms will map to the RDA singular term, the same way other literal LC matches are handled. The plural versions will be added as alternate labels. The singular/plural difference does not break the correspondence between the two.
• Clarification on alternate labels: "RDA alternate label" should refer only to alternate labels that come from the RDA registry vocabulary, because those live in the RDA XML lookup files and are searchable for retrieving the IRI. Other alternate labels (such as LC plural forms) need to go in their own column so they can be put into a separate XML file to search.
• Suggestion: Keep the RDA alternate label column separate and add an "additional alternate label" column in the mapping table. Keep the mapping table itself clean; source detail can be indicated with a note in the comparison/informational tab. Deborah, Cypress, and Doreen can work out the exact columns and how to indicate source.

Issue: Maintenance #810 (5 min)

• Richard is doing maintenance on the M2R-Project public triplestore . I have let the Triplestore team know.
• The triplestore will go offline June 12th starting at 5 PM and should be back up by the end of the weekend. Richard will post a note in the issue when it is back online. Nothing further needed from the team.

Issue: Subfield codes appearing in element values #651 (15 min)

• See issue

  • Subfield codes are included in aggregated statements when no ISBD punctuation is provided. Decision: check for ISBD punctuation and supply it in place of subfield codes if it isn't there.

• MARC Punctuation Guide for Field Strings

• Deborah provided a list of ISBD punctuation for the affected statement fields (245, 246, 250, 260, 264, 300, 440 and 490 series). The group agreed not to fully reconstruct ISBD: it is too hard to code and supplying it when missing would double up on records that already carry odd punctuation.

  • Cypress: the 245 currently splits on subfields when there is no ISBD and looks for markers like "=" only when the record indicates ISBD; it never supplies ISBD. This needs to change.
  • Proposed simpler approach: instead of recreating ISBD, if a subfield code is not preceded by a space and punctuation, insert a consistent separator (e.g., space semicolon space) between pieces.
  • Three options remain: (1) supply/normalize the punctuation, (2) handle end-of-subfield punctuation (leads into #765), or (3) reconsider aggregating these values into statements at all.
  • Next step: Deborah is gathering real examples (punctuation present vs absent); Cypress will check what the code is doing and report back next week.

Issue: [BUG] Transform embedded punctuation #765 (20)

• See Issue

  • Do we need to write a BUG report for #1? If so, can someone do that?
  • Can we discuss #2 today?

• Problem: retained end-of-subfield punctuation means an element value does not exactly match an identical value without it, producing duplicate values in the triplestore (for example, the same subject coming from two libraries with different trailing punctuation). This affects essentially all elements coming from MARC subfields that end in punctuation, and matters most for the 245, which is used for de-duping manifestation complete descriptions.

  • Suggestion: remove trailing punctuation for all elements of subfields that end in punctuation, regardless of the leader/ISBD coding.
  • On #1 (title ISBD not being removed because ISBD is not indicated in the record): Decision: start here by ignoring the MARC leader / removing that coding condition, and see if it resolves most cases. Test using the markXML records Deborah put in Google Drive (link in the issue) and review the results in RDF, or load to the triplestore and use SPARQL, or pass them through RIMMF/RIPS.
  • On #2 (removing punctuation preceded by a space and followed by a subfield code): needs a bit more discussion, but agreed in principle. Deborah provided a list of punctuation that can end a subfield. Decision: remove that trailing punctuation, except a period, question mark, or exclamation mark, which remain. We do not add punctuation back, since these are individual values.
  • Cypress: periods are special. The code can check a period against the abbreviations list (and already checks that it is not preceded by other periods), so a period is only removed when appropriate. Decision: treat a period specially, "period if not abbreviation," checking the abbreviations list. Cypress noted regex can strip everything except a whitelist, so the keep-list can be defined and the rest removed; she will look up the standard punctuation list.
  • Action: Deborah to add the "period if not abbreviation" note and the list of punctuation to remove to the instructions.

Issue: [TRIPLESTORE]: Testing collection aggregate manifestations (CAM) #808 (Rest)

• We have loaded a larger set of CAM records into the public M2R-Testing triplestore. It could be fun for you to look at the results and would be great if you could provide feedback (at the linked issue) on what you see.

  • go to the triplestore

    • click M2R-PROJECT top right

    • select M2R-TESTING

    • execute Saved SPARQL query: *Search source M21 records

      • pick an example

        • copy the 245$a

  • go to M2R-search

    • Chose Search in: M2R-TESTING

    • Paste the title in the Title proper search box

    • Click on the hit in the Hitlist

      • See how the MARC data mapped for the aggregate manifestation

      • Right click on the ‘work manifested’ element value to open the description of the work in a separate window (you may need to try this twice for some reason)

        • See how the MARC data mapped for the aggregating work

• Cypress demoed the public M2R-Testing triplestore live: searching an aggregate record, then viewing the aggregating work, its related entities, and the manifestation.

  • The demo showed the slash/punctuation issue: a "/" stripped in one expression but not another creates two titles, so one expression ends up with several manifestations (and duplicate titles) due to de-duplication. Traced to one record via the manifestation metadata. Reinforces the punctuation work in #765.
  • A bad-input record surfaced: country code (place of manifestation) is "xx" but $a says New York. Since 264$a is transcribed it can vary, so the code is fine; just one bad record that got through.
  • Richard's tool is a prototype, not ready for public release. Showing it at ALA would invite criticism despite the prototype label, and the program itself still has rough edges. Decision: the current public-facing triplestore is enough for now; hold the prototype until Richard decides it is ready.
  • Gordon's suggested review workflow (per Deborah): open the source MARC record (via his SPARQL query) beside the M2R search results, compare, and check the 979 for the aggregate pattern match, then decide whether it needs tweaking or is an error that got through. Good for casual review.

Wrap-up (5)

Note: Deborah will be away for about 3 months, starting in roughly 10 weeks.

Action items

• Crystal: Send the main planning document and review the ALA Core presentation; anyone interested can review.
• Crystal: Continue work on the mapping and reviewing instructions: make them more sequential, assign to specific groups/roles, and clarify the "source TK (Toolkit) element reference."
• Crystal: Test the aspect ratio designation, then adjust the project plan.
• Everyone: Concentrate on attributes and the "Source: M2R mapping" column; use a question mark in the status if a problem comes up, not "awaiting review."
• Deborah: Continue adding pattern searches in the "Example files" column for MARC examples.
• Cypress: Investigate what the code is doing regarding ISBD punctuation for #651 and report back; for #765, start by removing the title ISBD/leader condition and test.

Backburner

June 5, 2026

See time zone conversion Meeting norms Present: Cypress, Crystal, Deborah, Laura, Jorge, Dee, Ebe, Jian, Kyla, Sita Absent: Time: Ebe Notes: Cypress

Roles for meeting/agenda assembly (10)

Updates (5)

• Project options

  • Turning project into research institute at UW iSchool and get resources from them potentially

    • Could be helpful for exploring Oxygen license, storage space, computing power, etc.
    • Crystal getting more information

  • Laura - are we here for just this one project or are there other things/projects the group may want to address?

  • Want to discuss and think about this more

• Master plan vote update

  • Crystal will send out an email to remind people

Asynchronous discussion needed Bugs (10)

• Link

• Had time to discuss issue 765

  • see comment

• Take time to look at issue 651

F&MV tables for LC vocabs (15)

Do we need to create tables for LC vocabularies that do not have RDA equivalents? See: https://docs.google.com/spreadsheets/d/1YKOFuwdt6ie9NZ9O7VZYF0JyZL5Z-QJo/edit?gid=1709365539#gid=1709365539

• What would be the purpose? To map values from anywhere we can to an lc IRI when no rda vocabulary
• 4 vocabs with no RDA equivalent vocabularies
• Yes, because we may map 00X etc. to these IRIs
• Deborah will take this further and bring back to group
• Do we need FMV tables for UWLSWD?

LC source codes for LC-specific vocabulary terms (10)

Some vocabulary terms come from an LC vocabulary instead of an RDA vocabulary. Our transformation plan is to map those terms as lcURIs. However, I have only been able to find LC specific source codes for the terms and codes provided in 33X fields.

• issue
• 348 $b and $d for example
• RDA code issue, lc source code issue

In the last meeting, we talked about needing review workflow and instructions for the Mapping expression elements table and the Work and Manifestation tables (30)

• Are instructions clear?
• What columns should mappers work on?
• Status is for whether a row has been reviewed
• Need label for ready for transform and then a coder will create the issues for coding.
• Who is doing review?
• Crystal will create mapping issue for every single element
• Mappers should not worry about review just yet, work on Work expression source M2R mapping
• still in progress and not ready for review until Approved MARC is filled out and FMV table is done.
• Crystal will flesh out instructions more and make everything clear

Review F&MV tables (rest, to 11:55 PDT)

F&MV: interactivity mode. No special MARC field is available for RDA element. Review the proposed fields + examples

• Mapping expression elements: what do the notes mean? F&MV: Form of notated movement

wrap-up (5)

Action items

• Crystal will send out reminder email for project plan approval
• Crystal will work on mapping and reviewing instructions - will test with Aspect ration designation
• Cypress will work on ISBD stuff once she has her Oxygen license back :)
• Mappers will work on work elements

Backburner

May 29, 2026

See time zone conversion Meeting norms Present: Cypress, Deborah, Ebe, Laura Absent: Crystal Time: Notes: Cypress

Roles for meeting/agenda assembly (10)

Updates (5)

• Progress being made on translation portion of transform
• Early testing of CAM aggregates work and manifestation in transform being reviewed by Triplestore team - issue
• Crystal updated the Mapping elements tables for works and expressions to be consistent with one another as far as columns, column headings, format, and general instructions. She took down the outdated instructions from the first iteration of the tables and replaced them with a new draft here.
• Crystal created a poll for voting on the Master Plan. She will email it out this morning. Please vote!

Review previous action items (10)

• Everyone continue with mapping work elements spreadsheet and FMV tables
• Cypress continue working on code/translation/etc.
• Everyone review master plan - poll will be sent out for approving the plan

Co-working time

Mapping expression elements

• Purpose of Source: M2R coding column
  • Status or link to template in code
  • What does Phase II mean in the field spreadsheets?
  • Discussed 538$a aspect ratio
  • What does the status mean? 'Reviewed' - we've decided to map, or we've decided point blank either yes or no.
• We need a review workflow and instructions
  • Can we do this level of reviewing without example files?
  • Need a way to identify if further mapping needs to take place or if it has been completed in phase I
• Finished up with looking at 518$a

Wrap-up (5)

Action items

Backburner

No meeting May 22

May 15, 2026

See time zone conversion Meeting norms Present: Cypress, Crystal, Ebe, Laura, Deborah, Kyla Absent: Time: Ebe Notes: Cypress, Crystal

Roles for meeting/agenda assembly (10)

Updates (5)

• Crystal needs to miss this meeting next week--can anyone else facilitate?
  • For CALMA AI in metadata discussion!
• Cypress also is missing next week's meeting
• Other people are attending CALMA presentation and/or cannot attend
• No meeting next week!

To-do from last week (15)

• All: Continue mapping work elements.
  • Crystal made sure all column headings are identical between Work and Expression tables
  • MGDs still say not finalized, so we probably don't want to use these
  • Crystal will ping Adam on GitHub discussion to ask about other potential pcc documentation
  • Crystal will take another look at the status column dropdown options
  • Need people to work on the mapping work elements spreadsheet
• All (F&MV Group): Continue F&MV tables : check updated instructions first.
• All: Add yourself to work stream teams in the master plan as desired.
• All: Review master plan once circulated; provide comments before next meeting.
  • We will have a poll for everyone to approve/look at the plan
  • General 2-year plan for the phase, but those goal posts can move
  • Putting timelines on phase II will be difficult, we're working on the hard stuff. We can revisit/check in on timelines periodically.
• Crystal: Finalize master plan with Cypress; circulate to planning team, then this group.
• Crystal: Send 501(c)(3)/501(c)(4) proposal to planning committee.
  • Crystal has done more research on this. Different options with different benefits/requirements
  • 501c3 would give us a lot of rights to be an organization
  • 501c4 is lower effort but might meet our needs
• Cypress: Finish Transformation master plan section this weekend; add translation section.
  • Done!
• Jorge: Look into exporting sample Spanish records for testing.
  • Crystal has asked Jorge for this

FMV Tables (15)

• 'Other marc fields' column mapping and coding

Translation decisions (10)

Master Plan Review (15)

• Google Document
• Crystal will be working on issue creation for font size and sending this out for people to look at
• Talked through workflow and issue creation
• Cypress run transform section by transform team

Wrap-up (5)

• No meeting next week!

Action items

• Everyone continue with mapping work elements spreadsheet and FMV tables
• Cypress continue working on code/translation/etc.
• Everyone review master plan - poll will be sent out for approving the plan

Backburner

May 8, 2026

See time zone conversion Meeting norms Present: Crystal, Laura, Cypress, Ebe, Jian, Jorge, Doreen Absent: Time: Jian Notes: Doreen

Roles for meeting/agenda assembly (10)

Updates (5)

• Crystal looking into 501C(3) 501C(4) thinking about incorporating in WA State/US
  • Project is no longer housed at a specific institution; nonprofit status would unlock free Google Drive storage, discounts on Oxygen, GitHub nonprofit benefits, and (longer-term) the ability to administer grants independently and accept tax-deductible donations.
  • Gordon noted formalizing as an organization could potentially help with uptake by ALA and the RBA steering committee.
  • Requirements are straightforward: paperwork, articles of incorporation (can be based on current project documentation), a board, and a registered agent (Crystal willing, but open to others). Would also need a bank account and a project email address.
  • Crystal leaning toward 501(c)(4). No income/sales planned, so annual return would be simple.
  • Crystal will send a proposal to the planning committee first, then bring it to the larger group.

To-do from last week (5)

• Continue working on mapping work elements (Source: M2R column, top down, prioritizing elements with RDA Vocabs)
• Continue working on F&MV Tables (check updated instructions before starting)
• Crystal: Finish first pass of Phase 2 master plan / project management document next week; send to Cyprus for review, then to the planning committee.
• Crystal: Continue working on GitHub organization; planning committee meeting soon to discuss project infrastructure (Google Drive, hosting, status)
• Ebe: Fill in the Source: NLNZ column.
• Continue working on mapping work element source:m2r mapping column
• Continue doing F&MV tables - setting up and filling out
• Cypress, Deborah, and Crystal will meet about project organization

Master Plan informal review (30)

• Terminology: Crystal used the project/subproject/workstream/work-package/work-packet hierarchy : open to suggestions if anyone has better terminology.
• Sub-project 5 (Deduplication) placement: Cypress noted it may end up being post-Phase 2 since it combines triple store and transform work. Group agreed to let it "cook" before deciding whether it lives as a standalone sub-project or as a work stream inside transformation. Depends in part on whether dedup stays in the demo triple store or moves into the transform tool itself.
  • Laura raised concerns about IRI generation and data-sharing implications when others reuse the tool. Current IRIs are experimental and not meant to be reused.
• Aggregates mapping : Cypress's question: in the mapping aggregating works table, mapsRepX maps to what : is the assumption always the aggregating work? To be clarified later; Crystal added a note in the doc.
• Decision tracking — significant open question (Laura): Need a way to record decisions for each option in the mapping tables (e.g., "this MARC field isn't worth mapping because the data is too hard to extract") with a review process. Phase 1 had similar discussions but it's unclear where decisions were recorded. Group discussed:
  • Walking through every element as a group isn't feasible (too time-consuming).
  • Approach instead: handle case-by-case as elements come up (e.g., for degree-granting institution, check the deleted/delete tab).
  • For Phase 1 elements with no aggregate-specific change needed: no Phase 2 issue required unless mapping changes.
  • Laura will draft thoughts on a decision-tracking workflow once she can see the tables clearly; Crystal added a placeholder note in the master plan.
  • Cypress proposed adding a column to the mapping work elements table indicating whether each category is actually being mapped/used.
• Condition syntax revision: Crystal will revise condition syntax in the mapping tables to consistently indicate mode (single expression, manifestation, collection aggregating work, etc.) so additional logic can be applied cleanly. Conditions to go in the existing hidden columns.
• GitHub wikis vs. GitHub Pages: Cypress clarified : work streams will be documented on GitHub wiki pages, not GitHub Pages (which is the live website feature). Crystal will create the wiki pages; transform-related wikis will need Cypress's review.
• Translation sub-project scope: Phase 2 focuses only on the aggregates portion (using natural language in non-English to identify aggregates). Broader translation (fields, then outputs/notes/access points) is Phase 3+.
• Spanish testing records: Crystal will email Jorge separately about exporting sample Spanish records from his institution for aggregates testing (after the transformation list for aggregates is done). Subject to whatever export rights Jorge's institution allows.
• Manifestation properties (aggregates): Crystal doesn't expect significant changes during Phase 2 since aggregation doesn't much affect manifestation description — possibly add a category indicating aggregate type to each manifestation output. Laura noted there are a lot of properties; group may try an automated approach (e.g., extract from spreadsheets) rather than manual review.
• F&MV table coding instructions: Cypress considering splitting these into a separate work stream from element coding rather than keeping them together.
• One issue per term list? Cypress confirmed it'll be one issue for aggregates translation; broader translation lists separated into XML files later. Once translation is complete, Joe's script handles spreadsheet → XML; nothing additional needed in the transform.
• Internal documentation continues to live in the Google Drive; wikis will primarily point to it. If nonprofit status comes through, the Drive can move to independent storage without paying.

Does everyone have work/is everything being worked on that can be

• Most work streams have people assigned (see master plan for current team rosters).

Wrap-up

• Crystal will finalize the master plan with Cypress, then send to the planning team for edits, then to this group for approval before building out workflow tracking.
• If approval comes through before next meeting, Crystal will send an email so the team can review changes async.
• Cypress will finish her section this weekend and email Crystal.

Action items

Action items

• All: Continue mapping work elements.
• All (F&MV Group): Continue F&MV tables : check updated instructions first.
• All: Add yourself to work stream teams in the master plan as desired.
• All: Review master plan once circulated; provide comments before next meeting.
• Crystal: Finalize master plan with Cypress; circulate to planning team, then this group.
• Crystal: Send 501(c)(3)/501(c)(4) proposal to planning committee.
• Cypress: Finish Transformation master plan section this weekend; add translation section.
• Jorge: Look into exporting sample Spanish records for testing.

Backburner

May 1, 2026

See time zone conversion Meeting norms Present: Cypress, Crystal, Deborah, Laura, Dee, Ebe, Emily, Kyla Absent: Time: Ebe Notes: Cypress

Roles for meeting/agenda review (10)

Updates (5)

• Planning committee meeting later today to discuss trajectory and planning of project
• Phase II master plan not quite ready for review
• Laura finished her expression properties
• Cypress working on figuring out coding for fmv tables

To-do from last week (5)

Still to-do/in progress

• Continue working on mapping work elements (Source: M2R column, top down, prioritizing elements with RDA Vocabs)
• Continue working on F&MV Tables (check updated instructions before starting)
• Crystal: Finish first pass of Phase 2 master plan / project management document next week; send to Cyprus for review, then to the planning committee.
• Crystal: Continue working on GitHub organization; planning committee meeting soon to discuss project infrastructure (Google Drive, hosting, status)
• Ebe: Fill in the Source: NLNZ column.

Done

• Deborah: Add archive folder for rewritten F&MV tables.
• Laura: Fill in the Source: PCC column in the work element mapping table.

Discussed the PCC MGD files. They aren't done so it may be too much work to search these PDFs when they aren't even completed. Not worth the time.

Changes document might be worth looking at for source:PCC column.

Mapping work elements (5 min)

1. Deborah added fields from the Source: Registry RDA to MARC 21 Bib to see whether any of those fields are feasible for providing usable values for mapping. If multiple sources of encoding guidance give the same field as a source of data for mapping for an RDA element, then that should make that field more likely to be useful.

2. Volunteers can start self-assigning and filling in the Source: M2R mapping column whenever they are ready to do so. Remember that instructions are at How to fill out M2R Mapping column

• New column - Source: registry RDA to MARC 21 Bib

• Laura filled in the Source:pcc column

• Discussed the Work-SKOS tab and subjects, Laura will work on this

• 'Approved Marc. filled in last' column is new. This is where we decide what we approve, and will not be filled in yet.

  • Is this duplicIative of status column? We could change drop down to indicate approved or not approved in status
  • Moved this column to the end, and will need further discussion

• We need to be cautious about changing column names and definitions so that everyone is able to work on these

• Lots of discussion about workflow and use of these tables

  • F&M table for each element
  • Person who does F&M table integrates phase I documentation and the tables we're working on now.
  • We need mapping issues (element by element)
  • And transformation issues for each f&m table that are marc field by marc field

• either need to translate phase I format into phase II format or phase II format into phase I format.

F&MV Tables (5 min for #1 and #2; … min for #3)

• 1. I added RDA Alternate Label and LC Variant Term columns to the Compare term definitions tab and the Mapping table of the F&MV Blank template. Those columns need to be added to the tables that have already been created.
  • need to compare definition of 'variant term' in RDA and LC
• 2. I added an archive folder to the F&MV Tables folder to put all the old versions of the tables, when it is easier to start over than to update an existing table.
• 3. We can look at some tables that have already been created, to get people accustomed to how they are filled out and to encourage volunteers to fill them out.

Mapping expression elements (… min)

• 1. We can check the reliability of some more of the fields that have been added as possible sources of values for mapping to RDA elements. The group can continue with this process while I am away.

Wrap-up (5)

Action items

• Continue working on mapping work element source:m2r mapping column
• Continue doing F&MV tables - setting up and filling out
• Cypress, Deborah, and Crystal will meet about project organization

Backburner

April 24, 2026

See time zone conversion Meeting norms Present: Crystal, Deborah, Jorge, Laura, Cypress, Dee, Ebe, Jian, Kyla, Doreen Absent: Time: Ebe Notes: Doreen

Roles for meeting/agenda review (10)

Updates (5)

• F&MV Tables. A number of tables have been created since last week. Thanks to Doreen and anyone else who has done any. We aren't currently tracking ownership, but we probably should do so, so as to give kudos to those who do the work. Crystal suggested using GitHub issues to track who has done what, rather than maintaining separate tracking lists in multiple places.
• Due to increased responsibilities at her primary job, Xiaoli needed to step back from the project. Thanks for your work Xiaoli!
• Will not be discussing recording a value of RepEx when a work is an aggregating work, i.e., Mapping for aggregating works. The work group has met and is still discussing next steps. We will return to this in mid June.

Action items from last week (5)

• Crystal provide workflow updates for all 3 teams by end of month. -- working on it. Crystal plans to finish a first pass next week and send it to Cypress, then the planning committee, and then to the full team for review.
• Cypress and Crystal look into creating organization for this project on the GitHub. -- in progress

F&MV Tables (20 min.)

• Deborah to add a few steps to the instructions, based on the work done in the last week. So, if you are feeling comfortable about creating tables without having to look at the instructions, check for new instructions when you first start working on a table.
• A new archive folder will be added to store tables created from the old template.

Mapping variant terms (5 min.)

• F&MV: configuration of playback channels
• If so, will this approach work for coding?
• F&M: Aspect ratio designation
• The approach: RDA terms map to RDA IRIs. If an LC definition matches, it also maps to the RDA IRI. If there's a mismatch, the LC term maps to the LC IRI as a separate source. For variant spellings (such "full screen" / "fullscreen"), both forms are included using a double bar (||) meaning "or," so coders know to code for both terms.
• Where variants appear: In designated RDA fields (340 with subfield 2 starting with "rda"), terms should match exactly. Variants are more likely in free-text fields (520, 538, 500).

Coding F&M Tables

• Cyprus raised several questions about coding the F&M tables, using font size as an example.

• Validation scope: Crystal confirmed validation is out of scope for this project (consistent with an earlier decision). If it has "rdaregistry.info" in it, use it. Validation may be revisited in Phase 3

• The 340 field Field 340 contains multiple subfields for different properties. A subfield $0 or $1 can't be reliably matched to a specific property when multiple subfields are present. Decision: The 340 will need to be treated similarly to the 336/337/338 fields; checking the entire string for each element. This means a field-level coding table for the 340 specifically, beyond just the F&M table.

• Hardcoding vs. lookup functions: Some mappings are simpler to hardcode (such as 008 position 23 = "d" always maps to "large print" for font size) rather than running through a lookup table. Decision: Deborah confirmed that the non-designated-vocabulary fields (additional MARC fields beyond the standard RDA fields) are intended to be hardcoded field-by-field. The F&M table lookup function will apply to RDA terms/codes/IRIs and LC terms/codes/IRIs; the rest will be hardcoded as conditions in the code.

Mapping work elements (30)

• Element Assignment. I have set up the assignment page. The instructions for filling out the Source M2R coding column are the same as for the Expression table How to fill out M2R Mapping column
• I am working on the "Searched MARC" column (for MARC fields, subfields/positions found via the M21 Bib Format manual and other searches) and might have what I have found finished before I leave, but it will need checking. And others should feel free to add whatever they find anywhere else--just add a NOTE with their initials and give a link to their source (to the MARC Bib field if that was their source, otherwise to wherever said that the field could be used)
• I have also been working on the Source: TK >> Element Reference column using the Registry Alignment from RDA elements to MARC 21 Bibliographic encodings. Just in case there are some useful pointers there. Ebe is going to fill in the Source: NLNZR2M column Is anyone willing to fill in the Source: PCC column (Provides links to "MARC Coding Changes" section of PCC "Changes from Original RDA for Monographs")
  • Laura volunteered.
• Has anyone come up with any other sources that tell us which MARC element they will use to encode an RDA element?
  • PCC metadata guidance documents were discussed but considered difficult to use, they are PDFs, not well organized for our purposes. Crystal will check with Adam, who has been working on them. General consensus: probably not worth mining.
• Is it worth providing a link to the transformation coding m2r-… .xsl folder that contains the main coding for the mapping from the mapping spreadsheet instructions?
  • Did not discuss
• The main thing for everyone to work on is the Source: M2R mapping column, preferably starting at the top and working your way down the list, beginning with the elements that have associated RDA Vocabs so that we can create F&M tables Ignore F&M Table column
  • Status tracking discussion: Crystal plans to move tracking to GitHub issues in the next couple of weeks, with each element getting its own issue. Current spreadsheet tracking is fine for now.

F&MV Tables (if any time is left over; Did not get to it)

Look at some of the tables

Wrap-up

Action items

• Continue working on mapping work elements (Source: M2R column, top down, prioritizing elements with RDA Vocabs)
• Continue working on F&MV Tables (check updated instructions before starting)
• Crystal: Finish first pass of Phase 2 master plan / project management document next week; send to Cyprus for review, then to the planning committee.
• Crystal: Crystal: Continue working on GitHub organization; planning committee meeting soon to discuss project infrastructure (Google Drive, hosting, status)
• Deborah: Add archive folder for rewritten F&MV tables.
• Laura: Fill in the Source: PCC column in the work element mapping table.
• Ebe: Fill in the Source: NLNZ column.

Next week topic: TBD

Backburner

• Developing a consistent "mapping language" or standardized way to represent all mappings across phases 1 and 2; to be addressed toward the end of Phase 2.
• 501(c)(3) status and project infrastructure decisions; planning committee to discuss.

April 17, 2026

See time zone conversion Meeting norms **Present:**Crystal, Doreen, Laura, Ebe, Deborah, Jian Ping, Jorge Gomez, Dee, Kyla Absent: Time: Ebe Notes: Laura

Roles for meeting/agenda review (10)

Updates (5)

• question from Laura about status of issue for tag 348 Notated Music Characteristics which was mapped but not coded - Crystal says not to worry, will be incorporated into new Phase 2 workflow for RDA properties, F&M tables, etc.

Action Items from last week (10)

• Crystal send poll out to everybody again. Even if no opinion, comment I am not a cataloger. -- This didn't happen, but she will send this week.
• Crystal provide workflow updates for all 3 teams by end of month. -- working on it.
• Crystal make sure Dee is on the GitHub repo, project participant list and project roster. -- done.
• Crystal email Gordon inviting him to join meetings anytime to discuss representative expressions on aggregating works. -- he knows he is invited anytime
• Transformation team fill out Cypress' availability form. -- Done?
• Cypress and Crystal look into creating organization for this project on the GitHub. -- in progress
• All - sign up for remaining unassigned items in the expression spreadsheet. -- every Expression attribute is assigned
• Potentially hear from Deborah on:
  • discussion with Gordon about recording a value of RepEx when a work is an aggregating work (representative expressions). -- not this meeting
  • Discuss remaining mapping expression category items with the group. -- all are assigned, 2-3 remain

Mapping Expression elements for aggregating works) - tabled until next week

• Report on discussion with Gordon about recording a value of RepEx when a work is an aggregating work -- next week?

F&M Tables (45)

Deborah went over the workflow and documentation for the Finding and Mapping Vocabularies work. The tables will be for public consumption. Documents:

• F&MV Templates Instructions
• F&MV Blank template (F&MV)
• F&MV: Font size (completed table)
• Elements & Vocabularies (E&V)

As we encounter potential use or mapping of LC, RDA or other value vocabularies in reviewing mappings, a table needs to be created. Follow the Templates Instructions in detailed order. The Elements & Vocabularies spreadsheet has a list of all elements related to vocabularie(F&M tables created to date. so check first to see if a table has been created before making a new one. If there isn't a table there, make a copy of the Blank template in the same Google drive folder (Non-mapping Materials/Attribute fields/Finding and Mapping RDA Elements), give it a title as per instructions, put a link to it in Elements & Vocabularies tab Elements Matched to Vocabs tab, F&M LINK column.
Crystal will add column(s) for Assignments and workflow to this table (she did).

Following the instructions, Deborah demo-ed the Compare Terms tab in a F&M table - RDA vocabulary terms can be copied en masse from the Registry and pasted in, sort alphabetically by term, LC terms in id.loc.gov can be pasted but need to be individually opened to capture definition and scope notes if any. If the definitions have even a slight difference that might be significant, highlight it with red text, but if it doesn't seem significant you can choose "near match" as the comparison. These choices will be reviewed before the table as a whole is marked as "done".

The Registry may be difficult to access the first time - browser may give a security warning but usually there's a way to work around this in the browser - it's a known problem.

The status columns in Elements & Vocabularies are being reviewed by Deborah to see if more or less are needed. Also, only one tag associated with an RDA element is to be identified in the F & M table column header - Deborah will have to think about how to handle multiple tags that could be mapped to an RDA element vocabulary.

Doreen asked what to do if the term relationships are more complex than a simple 1:1 relationship. Two possibilities - there is a Discussion (Setting up F&MV tables from a Blank template: Questions & Answers #801 where questions like this can be asked, if the situation needs more discussion, create an Issue for that table. Crystal is setting up a workflow that will probably use Issues for these tables and other projects. She plans to have workflow tracking in Github worked out, discussed and approved by the steering committee in the next 2 1/2 weeks . Deborah will be "out" for 5 weeks starting May 5.

Mapping Work elements

Table is set up Mapping work elements - (15) We ended up not having a lot of time to discuss this, but Deborah suggested looking at the table between now and next meeting. It's similar to the table for mapping expression elements that we are almost done with. We will discuss next time, whether a column for BIBFRAME RDA in MARC specs from PCC would be useful or not. Ebe will populate the NLNZ column. Once this is started, anyone with time available could choose to work on element mapping or F&M table work. We will not record any mappings from 500 tags.

Wrap-up (5)

Action items

• Deborah to decide how status columns will be used for F&M table workflow in Elements & Vocabularies.
• Deborah to decide how to handle vocabularies used in multiple MARC tags.

Backburner

April 10, 2026

See time zone conversion Meeting norms Present: Crystal, Ebe, Jorge, Laura, Cypress, Dee, Kyla, Zhuo, Doreen Absent: Time: Notes: Doreen

Water Cooler/Agenda Review/Roles for Meeting (5)

Updates

• Crystal will be working on updates to workflows for all three teams in the next couple of weeks
• Transformation team availability form

Action items from last week

• Mapping expression categories: still some "in progress" and unassigned expression elements in the Element Assignment tab
• Mapping for aggregating works: Kyla working on document tracking RDA Toolkit policy statement inconsistencies
  • TK condition/a value of options for recording a value of RepEx when a work is an aggregating work (Poll) - two people filled it out. if you have an opinion, please fill it out today
  • Discussion about the poll:
  • Cypress: Is the poll asking about creating metadata in official RDA linked data, or about how to actually transform old MARC metadata?
  • Laura suggested adding a choice for "if all aggregated expressions are the same content type, record it." Crystal added that as an option in the poll.
  • Concern: that a machine likely can't determine predominance (e.g., a coffee table book with images and text — which is dominant?). Crystal agreed that's a problem to solve after the survey.
  • everyone should fill out the poll, even if they don't have a strong opinion. It's okay to select "other" and write "I don't know, I'm not a cataloger." Deborah can then compare the number of responses to the number of project participants and know that everyone at least looked at it and thought about it, which makes it easier for the group to move forward.
  • Consensus: fill out the poll to see if there's a dominant answer; if not, further discussion needed. Even if no
• Deborah: report on discussion with Gordon about the options; next week?

Mapping expression categories

• Interactivity mode: examples: 500 interactivity LC 2022.txt|655$aInteractivemultimedia LC 2022.txt|245$hInteractive LC 2022.txt - too old a use?
• Possible: 655$a LC Genre/Form terms LCGFT
  • Audio interactive games
  • Hypertext fiction
  • Choose-your-own story comics
  • Choose-your-own stories
• Form of music notation
  • Hits: 546$b; 348 $c; 250 $a
  • No hits: 251$a; 254$a; 300$a
  • 300$e MusNot_Phase1.txt
  • Other
  • See: Finding & Mapping Form of musical notation
• Scale
  • 255$aScale_Phase1.txt
  • 255$a_034Scale Phase 1.txt

Next table: Work properties mapping table

• Once expression attributes are done, a similar table needs to be created for mapping work categories.
• Anyone can do this: export all work properties from the RDA registry as CSV, then sort by range (no range = attribute) into category tabs. ~608 active work properties (slightly more than the 516 expressions).
• Note: CSV download from the RDA registry appears to be broken (XML works). May need to email the RDA registry team about it, or scrape the data.

Mapping for aggregating works

• Report on discussion with Gordon about recording a value of RepEx when a work is an aggregating work

Repo Co-ownership

• Cypress will be given co-admin/settings access to the repository for long-term sustainability.
• Crystal will check how many people can be given admin roles — wants to avoid single or dual points of failure.

GitHub Organization

• Since the project now has two repositories (main + triple store), organization makes sense?
• The project already has content copyrighted under the MARC-to-RDA project name.
• Crystal and Cypress will look into setting up an organization.

Wrap-up

Action Items

• Crystal send poll out to everybody again. Even if no opinion, comment I am not a cataloger.
• Crystal provide workflow updates for all 3 teams by end of month.
• Crystal make sure Dee is on the GitHub repo, project participant list and project roster.
• Crystal email Gordon inviting him to join meetings anytime to discuss representative expressions on aggregating works.
• Transformation team fill out Cypress' availability form.
• Cypress and Crystal look into creating organization for this project on the GitHub.
• All - sign up for remaining unassigned items in the expression spreadsheet.
• Potentially hear from Deborah on:
  • discussion with Gordon about recording a value of RepEx when a work is an aggregating work (representative expressions).
  • Discuss remaining mapping expression category items with the group.

Backburner

March 27, 2026

See time zone conversion Meeting norms Present: Crystal, Cypress, Deborah, Sita, Ebe, Laura, Jian, Jorge, Kyla, Doreen Absent: Time: Jian Notes: Doreen

Water Cooler/Agenda Review/Roles for Meeting (5)

Updates (10)

• Update from GitHub: On April 24 we'll start using GitHub Copilot interaction data for AI model training unless you opt out. Review this update and manage your preferences in your GitHub account settings.
• Triplestore team met last week
• Crystal is working on building out our GitHub workflows for Phase II. Will send a draft to CP and GD then to the rest of the group in the next couple of weeks.
• Crystal will move 2024 meeting recordings off GitHub in the next month to make space. She will also start migrating recordings from the UW OneDrive to an external hard drive. If you need access to a pre-2025 recording, send Crystal an email and she will get it to you :)

Action items from last week (5)

• Crystal will upload the zoom recording from last week.
• Kyla to look for MARC examples of musical notation fields: Done: See this folder
• Laura to continue investigating Form of Notated Movement/choreographic notation property (already assigned)
• Deborah can tidy up and share the document tracking RDA Toolkit instruction inconsistencies. Volunteers are welcomed.
• All: Continue filling out the expression categories table
• All: Review Phase 2 Master Plan and sign up for/switch teams as desired (volunteer basis)

Discussions & issues (20) * hard time limit! if we don't get to everything that is ok.

• Laura’s Discussion Form of Notated Movement (Discussion #798)
• Crystal's 255 $a Mapping from NLNZ in Mapping Expression Categories Table #782 (additional scale information)
• Re-Evaluate 377 Inclusion in Mapping #781 (377 associated language)

Mapping for aggregating works - Deborah (20)

• spreadsheet Poll created: Crystal made a Google Form based on Deborah's draft. Everyone should respond. Will discuss next week.

Mapping expression categories (40)

• go back to what we were reviewing last week
• Deborah added a column from a PCC document on coding changes from original RDA for monographs. Request: email Deborah with any additional MARC-to-RDA mapping sources.
• Need a tracking system for element-by-element status ; help welcome.
• MARC record examples might be needed in advance of meetings for efficient decision-making.

Elements reviewed:

• Color: Not working on: specific colors never standard in 300 $b.
• Form of Tactile Notation: Skipped. Not processing tactile records currently.
• Form of Musical Notation: Will check 348 $a/$b, 250, 251, 254, and 300 $a/$e. Need examples.
• Interactivity Mode: Only known source is 500 $a (Other examples?). Will investigate MARC 341.
• Scale / Scale Designation: There is consensus.
  • 255 $a is the source for both "scale" and "scale designation." It should not map to "additional scale information" (despite NLNZ's approach), and 245 should not be used as a scale source.
  • Deciding which RDA element: If 255 $a contains a numeric ratio (e.g., 1:24,000), map to "scale." If no numbers, map to "scale designation." The abbreviation "ca." should be programmatically converted to "approximately" per RDA instructions.
  • Future refinement: MARC 034 contains coded numeric scale data that is more reliable for distinguishing scale types (vertical, horizontal, linear) can be used later.
  • Legacy terms: Many non-standard scale terms exist in 255 $a. Match to RDA vocabulary terms where possible via the F&M table (already set up); anything unmatched gets recorded as an unstructured description.
• We are going to work on elements without vocabularies next time.

Wrap-up (5)

Action items

• Everyone: Fill out the Mapping for aggregating works poll from Deborah
• Everyone: Finish remaining 4 expression attributes.
• Laura and Crystal(?): Post to LD4 Arts Slack on choreographic notation contacts or reach out to colleagues.

Backburner

March 20, 2026

See time zone conversion Meeting norms Present: Doreen, Cypress, Deborah, Laura, Ebe, Jian, Kyla, Sarah, Zhuo, adam, Jorge, Sita, Crystal Absent: Time: Ebe Notes: Doreen

Water Cooler/Agenda Review/Roles for Meeting (5)

Updates (10)

• Triplestore team meeting scheduled for next Wednesday at 2pm Eastern Time.
• Adam provided key examples from last week, and looped in Cate
  • MLA (Music Library Association) community is leaving it up to individual institutions to decide whether to add the 380-384 fields
  • Some catalogers are adding these fields but not many
  • Multiple 384s can be recorded for a single work when the tonal center varies (e.g., first movement is minor, second movement is major)
• Discussion on inconsistency in RDA Toolkit instructions for different expression elements (content type vs. key of expression vs. language of expression)
  • Deborah started a document tracking what different sources say about each element
  • Suggestion that this confusion may warrant feedback to the RSC (RDA Steering Committee)

Mapping Expression Categories

• We'll not re-evaluate past mappings today
• Focus on reviewing the viability of each MARC element when more than one element is listed for an RDA element as a reliable source of data for the RDA element. Beginning with the RDA elements that have associated vocabularies
• To do this, we will look at the MARC instructions, and the RDA vocabulary terms and where they or codes for them appear in MARC fields.
• If we are not certain about how the MARC instructions have actually been applied, we can look for some examples from the LC 2022 file of records using MARC Report.

Aspect Ratio Designation Discussion

• Reviewed MARC fields 250 (edition statement), 520, and 538 (system details) for aspect ratio terms
• Found examples of "full screen," "widescreen," "anamorphic" in the 538 field
• Agreed that 538 is a reliable source for extracting aspect ratio designation terms
• Need to handle variants (fullscreen vs. full screen, widescreen vs. wide screen)
• Discussed that numerical aspect ratios (1.33:1, 1.85:1) are separate from aspect ratio designations
• Decision: We would map both values for complex terms like "anamorphic widescreen." Instead of choosing one over the other, we decided to extract RDA IRI for "widescreen" while also including the more granular LC IRI for "anamorphic" to preserve detailed information for users.

Form of Musical Notation Discussion

• We discussed the mapping of field 348, which was specifically designed for musical notation.
• Mapping IRIs: Concerns were raised regarding how to identify the correct property when IRIs are present without clear subfield definitions. Adam noted that the PCC URIs and MARC implementation test group has mapped these fields and can provide guidance on the use of $0 and $1.
• Best Practices: To avoid ambiguity, the team recommended repeating the field for multiple values rather than grouping them, ensuring each IRI clearly applies to its corresponding subfield.
• Legacy Sources:
  • Field 546 subfield $b: Historically used for notation terms before field 348 existed; we think it is reliable for extraction if RDA terms are found.
  • Field 655 (Index Term): While mentioned in discussion papers, Kyla rarely see these terms in field 655.

Form of Notated Movement Discussion

• This was identified as a brand new RDA concept relating to choreographic notation (e.g., scores for movement).
• New MARC Field: A specific field for notated movement has been recently approved, but technical details and implementation are still being finalized.
• Until the new field is widely adopted, we will "fish" for these terms in **fields 546$b and 655$a.
• Reliability: The group agreed that choreographic notation terms are sufficiently unique that if they are found in these fields, they can be confidently mapped to the "notated movement" property rather than being confused with musical notation.

If time, (Did not get to them)

• Laura’s Discussion Form of Notated Movement (Discussion #798)
• Crystal's 255 $a Mapping from NLNZ in Mapping Expression Categories Table #782 (additional scale information)
• Re-Evaluate 377 Inclusion in Mapping #781 (377 associated language)

Wrap-up

• Phase 2 Master Plan document shared with current team assignments
• Reminder that the Mapping Expression Categories table is more difficult for those who didn't do Phase 1 mapping. Phase 1 mappers encouraged to help move this work along

Action items

• Crystal will upload the zoom recording from last week.
• Kyla to look for MARC examples of musical notation fields
• Laura to continue investigating Form of Notated Movement/choreographic notation property (already assigned)
• Deborah can tidy up and share the document tracking RDA Toolkit instruction inconsistencies. Volunteers are welcomed.
• All: Continue filling out the expression categories table
• All: Review Phase 2 Master Plan and sign up for/switch teams as desired (volunteer basis)

Backburner

• Further investigation of whether "standard format" = "full screen format" (1.33:1) for aspect ratio mapping
• Document what different communities/sources say about each expression element to identify inconsistencies for potential RSC feedback

March 13, 2026

See time zone conversion Meeting norms Present: Crystal, Cypress, Emily, Alicia, Ebe, Deborah, Sarah, Adam, Kyla, Jorge Absent: Time: Ebe Notes: Cypress

Water Cooler/Agenda Review/Roles for Meeting (5)

Introductions (5)

Updates (10)

• We have a few new recruits! Emily is interested in joining the transformation team and Alicia may join the triplestore team
• Email sent out to triplestore team for scheduling next meeting

Phase II Planning Review (20)

• Decide sequence for reviewing mapping sub-parts in detail

• Reviewed Phase II Master Plan

• All elements will have an F&M table

  • Deborah currently working on vocabulary types, will design mapping types

• Mapping for aggregating works table identifies what applies to types of aggregates

  • Kyla and Xiaoli have volunteered to work on this

• Break up into teams

• Rework to make it more understandable to public and transform team at the end

• Repeat process for Works and some for Manifestations

• Possibly rework Phase I mapping to match this format

• Transform - not reasonable to do transform as mapping is happening.

  • Transform will focus on debugging and translation work

• Triplestore

  • Plenty to work on. May want to wait on developing an interface

• Once a few F&M tables are set up, mapping and transformaton team will meet to make sure it works for everybody

Assign teams for mapping parts

• Teams in Phase II master plan doc

Mapping for aggregating works

• The coders will use this table to know which elements apply to which types of aggregates and their entities
• What attributes for expression can be applied to the aggregating work (e.g. collection aggregating work) as a rep ex or note
• Discussed key of expression and other music specific properties
• Related agents for expressions

Wrap-up (5)

Action items

• Work on stuff for the team you are on/sign up for the team(s) you want to be on
• Deborah, Crystal, Cypress, Ebe - review master plan
• Cypress and Emily will touch base and begin onboarding Emily
• Next three meetings look at each phase II plan mapping aspect in detail
• Adam will look for examples for key of expression - multiple keys in a MARC record describing a collection work

Backburner

March 6, 2026

See time zone conversion Meeting norms Present: Laura, Crystal, Deborah, Clair, Ebe, Jian, Cypress, Sarah, Sita Absent: Time: Jian Notes: Sarah

Water Cooler/Agenda Review/Roles for Meeting (5)

Updates (10)

• Sarah and Crystal presented at ALA Core Week for LDIG yesterday
• New table: Elements & Vocabularies connects the RDA vocabularies to their associated RDA elements. Also includes associated LC LDS vocabularies (in progress)
  • Needed for F&M table construction and coding.
  • Would this be useful for catalogers? If so, which columns for a public list (F&M tables are private)
• Crystal drafted a vocabulary for us to use with Source:M2R Mapping in the Mapping expression categories table
  • We'll need to decide whether we want to create a specific term for conditions that are in "delete" tabs in the Phase I field-by-field tables, or if these should just be "not mapped" or "n/a".
• Daylight savings is on Sunday in the U.S., so the meeting time will change for everyone outside of the U.S. Crystal will send updated meeting times.
• Getty gave a very interesting presentation on Linked Data at ALA Core Week for LDIG. They presented in the Bibliographic Conceptual Models interest group. We should watch the recording once it is up.
• If you have an issue/discussion that you want to bring to the meeting, you can use the "meeting discussion needed" tag. Crystal uses this tag to make the agenda for meetings.
• There's a WikiHackathon in May, Clair can work on the WikiBase Cloud then and get some other people working on it, as well.

Last week's action items (10)

• Download Mapping for aggregating works and look at the representative expressions
• Crystal will create standardized mapping-status vocabulary
• Continue expression mapping work
• Still need to discuss the M2R coding status column in the Expr Attributes sheet
• F&M Tables
  • Still working on instructions for setting up tables, with help from Ebe and Sarah
  • Expression elements
    • Basic tables with RDA terms, codes and URIs have been set up for Expression elements. Thank you Doreen
    • Once instructions are completed, we will need volunteers to set up tables for adding MARC terms, codes, and URIs for Works and Manifestations
      • First, we need: M2R mapping spreadsheets added for the fields with F&M tables (Mapping expression categories)
      • Review of feasibility of using fields that have not been mapped by spreadsheets (See Agenda item Aspect ratio designation)

Mapping expression categories (15)

• Approve MARC fields for RDA vocabulary terms
  • Aspect ratio designation

String encoding schemes_SES.20250808_2 (20)

• Manifestation

  • [BUG] Transform deduplication of manifestations: My suggestion "Should we add font size to our Manifestation SES as another qualifier, after Carrier type ?"

  • New Issue: Font size: Phase II #794

  • New F&M: F&M: Font size

    • Question: should this be part of the access point, or just the IRI? How would that impact coding?
    • Answer: for disambiguation and deduplication purposes we should add it to both the access point and IRI so that manifestations have different aps. We'll have to change the code either way as we will either have to add it to the ap and then the code will also pick it up for the IRI, or we have to add it to the IRI.

  • Question: Need an order for "Carrier qualifiers"

• It doesn't matter what order these qualifiers are in, but we need to decide on a standardized order.
• Question: How do we handle large print vs. giant print? Most giant print materials are designated as "large print" in font size. The MARC record may have a note that clarifies that the resource is actually giant print, but we don't know how catalogers generally approach giant print materials.

  • There's no way to determine whether a resource is giant print or large print based on the font size in a MARC record, but we want to avoid merging two manifestations.

  • We could ask users to make sure that giant print materials have a note in pre-processing, however most libraries that carry giant print are public libraries and don't have a metadata librarian to do this work. We should expect that public libraries don't have the resources to do any pre-processing, at all.

  • We could ask public libraries for more test data that include giant and large print, to see how the records look and how the transformation handles them.

  • Write SPARQL queries to pull giant and large print resources in the test data to see what they look like, and how they are differentiated.

Mapping for aggregating works (20)

• Representative expression elements can be applied to an aggregating work of which there is only one.
• Question: How do we want to apply elements to an aggregating work? Are we applying elements generally to the entire collection, or does an element only apply to specific pieces of the collection?
• We'll take 40 minutes in the meeting next week to look at aggregating works and do the mapping for a few examples so that everyone can get a better grip on it and then we can make decisions.

Wrap-up (5)

Action items

• Crystal will send updated times for meetings to account for Daylight savings in the U.S.
• Crystal will send a GitHub repo invite to Clair.
• Everyone can continue work on the mapping expression table -- if you need to make an issue/discussion and don't know which to make, the Decisions Index has guidelines on the difference between an issue and discussion.
• We'll take another look at mapping aggregating works next week.
• Crystal will schedule meetings for the translation and Triplestore teams.
• Transformation team will meet next week at Wednesday at 8:00 PT.

Backburner

February 27, 2026

See time zone conversion Meeting norms Present: Cypress, Deborah, Sita, Kyla, Jorge, Doreen, Ebe, Laura, Sarah, Zhuo Absent: Crystal, Clair Time: Kyla Notes: Cypress

Water Cooler/Agenda Review/Roles for Meeting (5)

• Assign time keeper and note taker

Updates (10)

• Crystal is working on her action items from last week today, stay tuned. And sorry
• Clair is returning next week
• Sarah and Crystal are presenting at the ALA Core Interest Group Week Linked Data Interest Group Session on Thursday. Be there or be square!
  • https://connect.ala.org/core/discussion/core-linked-data-ig-session-march-5th-10-11-am-ct#bm3ba3b982-9054-436d-b7a5-99d038eb0d74
  • Registration Link
• Tynan and Crystal met with Lazaros from Open Knowledge Greece, and they are hosting a Wikibase Suite for us. Hooray! Crystal is in communication with Rick about HTTP things she doesn't understand about domains, and Lazaros is loading properties from RDA Registry into our fancy new Wikibase instance over the weekend.
  • We should add a link in the project wiki page when we have this!
• Crystal met with Sarah for a mapping 1:1 this week, and is meeting with Xiaoli today. Kyla and Jorge are scheduled for next week and week after next, and Crystal still needs to get Ebe on the schedule. If she missed anyone, please reach out!

Last week's action items (10)

• Mapping expression categories
  • Laura will go through the element assignment page and strike through the struck-through elements to streamline element assignment: done, Laura added a new status in the drop-down menu: "deprecated"
    • Question: Do we still need to distinguish between "not currently mapped" and "not going to map"?
    • If we were assigned something that was deprecated, we will need to update the status to "deprecated"
  • Crystal will create standardized mapping-status vocabulary: she will do that this week
  • Continue expression mapping work
  • Still need to discuss the M2R coding status column in the Expr Attributes sheet
• Investigate additional organization code sources (British Library and others): we needed to email someone at the British Library about this. Updates from Gordon and Matthew in this discussion. Zhuo will take the lead on this issue. 
• Everyone should regularly review asynchronous discussions & issues: you can filter discussions and issues by searching "asynchronous discussion needed" under Labels
  • Check for updates to issues/discussions between now and the meeting next week.
  • Can apply a label in the issues to filter when searching the issues.
  • We have a 'meeting discussion needed' label that we should add to those that need synchronous conversation, and we should regularly check that label to add to agendas!
  • Anyone can add/edit these issues and labels!
• Aggregate manifestation access point problem remains open for next meeting (Consult with Adam and Gordon): Deborah recommends that we move forward with what we currently have and make updates as needed.
• Crystal will upload meeting recordings
• Add discussions/tags in Github for post-processing and pre-processing tasks that we want to do - need Crystal to explain this one

F&M Tables (30)

• Set up basic tables with RDA terms, codes, and URIs using Blank template

• Add MARC terms, codes, and URIs, e.g., Scale Designation

• Add additional MARC fields from Mapping expression categories, e.g., Font size

• Deborah provided a walkthrough of these steps - instructions in the spreadsheet

• Crosswalking MARC vocabulary terms and codes to RDA vocabulary terms and codes where they are used in MARC fields

• Tab in spreadsheet for comparing terms and definitions - have to go through and determine if the terms & definitions match. If they do, they can be equated. Otherwise, we have to decide if it is safe to map or if the definitions do not match

• Sidenote - don't have a method of tracking who's doing what for this side project at this point

• Some of this requires detective work - determining what MARC fields have that information and if it has a vocabulary - either in an example or from the marc field/subfield proposal, etc.

• These tables are so that the coders can determine what to do with these values

• Doreen is going to adjust the templates and instructions

• Let Deborah know if you want to work on this

Mapping Expressions Categories Table (30)

• Currently, most mappers are working up to column "Source: M2R Mapping". Ebe/Deborah are working on RDA Vocab. Deborah, Doreen, and Sarah are working on F&M tables.

• Do not work on columns after "example input files"

  • New table that is a clean copy of "Mapping expression categories": Mapping for aggregating works

• These columns tell the coders what 'mode' in the code to use to apply these property mappings to that type of resource (single expression manifestation, augmentations, etc.)

• New table corresponds with the mapping expressions table but de-dups the RDA elements

• Can elements that apply to expressions that are aggregated be applied to an aggregating work (as either representative expression or note on work)?

• Guidance in toolkit on what aggregating work is

• We need to provide as much information as possible into the aggregating work description

  • RDA Toolkit on representative expressions
  • The representative expressions of the aggregating work are the aggregated expressions, not the aggregating expression
  • values of representative expression elements for an aggregating work are derived from one or more expressions that are aggregated
  • With each element, we have to decide if it will be mapped to the aggregating work or not.
  • Subfield $3 might indicate which expression something applies to? Needs more discussion
    • e.g. book intended for children w/ additional materials for teacher
  • People can download the spreadsheet and do this work locally, then we can discuss if we should map and why

Wrap-up (5)

Action items

• Download Mapping for aggregating works and look at the representative expressions

Backburner

• Deborah will give us a presentation in the near future on how to use RIMMF and Marc Report.
• $3 and representative expressions

February 20, 2026

See time zone conversion Meeting norms Present:Laura, Sarah C., Crystal, Jian, Ebe, Sita, Deborah, Jorge, Doreen, Zhuo, Xiaoli Absent: Time: N/A Notes: Sarah C.

Water Cooler/Agenda Review/Roles for Meeting (5)

Updates (10)

• Issues & discussions RE: triplestore work go in triplestore repository now, which is private. Crystal will work on documentation for workflows and ways for triplestore and transformation teams to communicate between separate repositories
  • later triplestore work will be moved to public repositories, probably GraphDB and Git.
  • One of the eventual goals for the GraphDB is to have participants take the records they are creating with M2R online and put them into the GraphDB. However, we may have to scale up and go to a different triplestore for this. This may be something we'll have to apply for grants to support.
• Crystal and Sarah are doing a brief presentation for the ALA Core Linked Data Interest Group (LDIG) in March. We'll share the triplestore, m2r online, gloss over what we accomplished in Phase I (and where folks can find deliverables) and discuss our goals for Phase II. It will be pretty brief but a good opportunity to update the community face-to-face (online)
• Change in transform team meeting frequency (maybe every other week, or once a month until we get more transform work. Cypress will contact transform team about this.)
• Triplestore meeting for about a month from now--Crystal will send a scheduling poll next week
• Crystal is scheduling 1:1 meetings with new mappers. Thanks for your patience!
• Xiaoli shared that PCC has a subcommittee to promote/support linked data efforts (RDA/RDF as well as BIBFRAME), they are creating a living document with links to RDA resources that will come out around April: we'd like to add the GraphDB, M2R online, and the repository with the transform code to this document.
• UW has incomplete templates for RDA in Sinopia. They all start with "WA;" UW doesn't have the resources at the moment to finish these templates, but other people are free to work on this. We can also explore the potential to batch load RDA records into Wikibase.
• A comment from Ebe: "NLNZ have all their application profiles up in Toolkit so these can be used as a basis for templates."

Last week's action items (5)

• Laura will go through the element assignment page and strike through the struck-through elements to streamline element assignment: done, Laura added a new status in the drop-down menu: "deprecated", do we still need to distinguish between "not currently mapped" and "not going to map"?
  • If we were assigned something that was deprecated, we will need to update the status to "deprecated"
• Crystal will create standardized mapping-status vocabulary: she will do that this week 
• Investigate additional organization code sources (British Library and others): we needed to email someone at the British Library about this. Updates from Gordon and Matthew in this discussion. Zhuo will take the lead on this issue. 
• Continue expression mapping work: Deborah will look at 
• Everyone should regularly review asynchronous discussion issues: you can sort discussions and issues by the label "asynchronous discussion needed" 
• Aggregate manifestation access point problem remains open for next meeting (Consult with Adam and Gordon): Deborah recommends that we move forward with what we currently have and make updates as needed.

F&M Tables (30)

• Go over what Deborah/Doreen have done

  • An RDA element often maps to/can draw from multiple MARC21 fields.
  • Some MARC21 fields already use RDA vocabularies and codes. When this is the case, we have set up three mapping tables.
  • Three mapping tables for content, carrier, and media type with RDA vocabulary terms. This is vital for translation efforts because then users can switch between vocabulary terms in their desired language.
  • Some of the columns have "[Value; Case=N]", this is a note for coders that means you need to use the phrase in each row in its entirety for the code and not to capitalize words.
  • third tab on sheet "compare term defs" establishes whether the RDA definition of a term matches the MARC21 definition for the same term. Definitions in green are an exact match between MARC and RDA, definitions in blue are very similar with minor differences, and definitions in red are where Deborah could not determine whether the definitions are the same.
  • If the RDA and LC/MARC terms have the same definitions, we can map the MARC to RDA and use RDA IRIs and translations for codes/terms.

• Deborah's questions and discussion:

  • Question: Is it safe to map id.loc.gov terms in LC/MARC vocabularies that appear in 348$c for musical notation to RDA and use RDA IRIs? Or, do the definitions not match sufficiently and we should only map to the id.loc.gov URI? Further, do we need to make tables comparing each definition for all vocabularies, or can we generally trust the definitions to be similar enough/the same?
    • Decision: Yes, we should make the term definition comparison tables because it is case-by-case and terms are so variable that we have to check them individually. It is safe to map the terms when the definitions are identical, however when they are similar but not the same we'll need to ask subject experts to weigh in.
    • We can complete these tables with the goal that we will eventually publish them publicly for all institutions interested in linked data, but don't have the resources to get this granular.
  • Could we map to both LOC and RDA, so that institutions could make a decision about which they would like to use? Answer: no because we don't want to equate terms that have different definitions.
  • Kyla has expertise with music, so she is likely the best person to weigh in on this particular table. We should prepare the tables with definitions to identify which ones are different and then go to people who have specialized knowledge of different formats to determine whether terms are equivalent between LOC and RDA.

• Question: If a LOC term is given without an IRI in the record and there is not a match in RDA (for example, deprecated RDA terms), should we replace the term with the LOC URI, or leave it as the term?

  • Decision: we will use the LOC URI, in the case that there is no RDA match.

• Question: fields 500, 546, and 650 have notes/terms related to notation, but should these be included in our notation coding?

  • Decision: we can look at these fields as a clean-up project in the triplestore. Create an issue/discussion to remind us to do this and other post-processing/clean up tasks. (also, create a discussion and flag for pre-processing tasks)

• Have we identified all of the RDA elements that will need mapping tables for the terms? Answer: The current ones are just expressions, we will also need to look at elements for works.

• Anyone want to help? Email Deborah

Wrap-up (10)

Action items

• Crystal will upload meeting recordings
• Add discussions/tags in Github for post-processing and pre-processing tasks that we want to do.
• Crystal won't be able to attend the meeting next week, so Deborah will lead the meeting if Cypress is unable to.
• Check for updates to issues/discussions between now and the meeting next week.

Backburner

• Deborah will give us a presentation in the near future on how to use RIMMF and Marc Report.

February 13, 2026

See time zone conversion Meeting norms Present: Crystal, Cypress, Sarah, Jian, Deborah, Ebe, Doreen, Xiaoli, Sita, Kyla, Laura, Jorge, Zhuo Absent: Time: Ebe Notes: Doreen

Water Cooler/Agenda Review/Roles for Meeting (5)

Updates (10)

• Crystal submitted proposal for an ALA Core Linked Data Interest Group presentation (Mar 2 - 6) and invited co-presenters.
• Reminder that to check discussions that has "async discussion needed" tag and that asynchronous discussions should be used for questions between meetings.
• Decision index includes info on discussion vs an issue 
• “Phase 2” should be used instead of “not mapped” when an element is expected to be mapped later 
  • “Not mapped” should only be used for deliberate decisions not to map 
  • Group will review prior “not mapped” entries for accuracy 
  • Crystal will create standardized vocabulary describing mapping status 
• Continue completing attribute mappings before expression elements

Bugs that need discussion (35)

• Look at them, gear up for asynchronous discussion
• Organization code problem (subfield $5)
  • British Library records include codes (e.g., “UK”) not found in LC MARC Organization Code list 
  • Current workflow:
  1. Pre-processing XSLT mints organizations from LC code list
  2. Transform links items to those organizations 
  • Proposed solution:
  • Obtain additional code lists (possibly from the British Library) and incorporate them into the pipeline 
  • Investigate other missing national codes (Canada, Germany, Estonia, etc.) 
• Carrier type IRIs
  • Multiple IRIs exist for the same terms because they were created from different MARC contexts 
  • For access points, only RDA carrier types should be used 
  • Property mappings (Leader/06 and 008) may need to be remapped to RDA terms 
• ISBD punctuation handling
  • Records often contain ISBD punctuation even when encoding flags indicate otherwise 
  • Decision:
  • Strip terminal punctuation from subfields (e.g., “ /”, “ :”, etc.) 
  • Update the punctuation-removal function to cover missing cases 
• Subfield codes in output
  • Output currently contains literal MARC subfield markers ($a $b) 
  • Decision:
  • Remove subfield codes
  • Replace with appropriate punctuation instead 

Mapping MARC records identified as describing Aggregate manifestations (35)

• issues that we need to raise with the group about our SES for AP for Aggregating work
  • AP provided
  • AP not provided
• Current approach
  • Begin with work access points for aggregating works 
  • Use X30 fields or compiled 1XX + 240 headings 
  • Retain expression attributes because aggregation makes work vs expression ambiguous 
  • Add a qualifier identifying the entity as an aggregating work 
• Major issue identified
  • In many records, the 130/245 first title represents the first work, not the collection 
  • RDA requires a collective title for aggregate manifestations 
• Proposed handling
  • Treat 245 $b preceded by a semicolon as additional work titles 
  • Combine titles into a collective title string 
  • Some cases (titles in 245 $c) cannot be algorithmically resolved → post-processing cataloger review required 
• Open questions
  • How to distinguish:, first-work title, uniform title, collective title
  • May require PCC or RSC guidance

Wrap-up (5)

Action items

• Laura will go through the element assignment page and strike through the struck-through elements to streamline element assignment
• Crystal will create standardized mapping-status vocabulary 
• Investigate additional organization code sources (British Library and others) 
• Continue expression mapping work 
• Everyone should regularly review asynchronous discussion issues 
• Aggregate manifestation access point problem remains open for next meeting (Consult with Adam and Gordon)

Backburner

February 6, 2026 (optional working meeting)

See time zone conversion Meeting norms Present: Cypress, Deborah, Ebe, Doreen, Xiaoli, Sita, Kyla, Laura, Jorge, Zhuo Absent: Time: N/A Notes: Cypress

Water Cooler/Agenda Review/Roles for Meeting (5)

Updates

Collection aggregate manifestations mapping

Examples of MARC records

• Look at some examples of MARC records that we have identified as describing collection aggregate manifestations
• Links to are provided in a document that will be made available after the meeting.

Steps

• Today: Focus on Heading Table >> Appellations: Access points only

  • Collection aggregating work
    • Main entry headings
      • Include expression values as terms qualifying collection aggregating works
        • Our SES for collection aggregating works is here: String encoding schemes_SES.20250808_2 >> Work AP (aggregating work)
        • For the AP of the collection aggregating work, we will use the main entry as our source
          • Problem: sometimes the m.e. is not for the collection aggregating work but for the first collected work, with or without a.e. for other collected works.
            • Look at some examples
            • How can we identify these? If we can do so, we can follow the SES instructions at Work AP (aggregating work) >> APs not provided
  • Collected aggregated works
    • Analytical added entry headings

• Maybe today: Focus on Heading Table >> Appellations: Titles

  • Collection aggregating work
    • 245
  • Collected aggregated works
    • 700-710$t and 730$a

• Then: Focus on Heading Table >> Attributes from headings:

  • Collection aggregating work
  • Collected aggregated works

Working session notes

• Is the new change to not requiring certain ISBD punctuation going to be an issue with the aggregate patterns?

• Looked at outputs of different aggregate patterns

• Are selections from a single work aggregates? If not, what are they? Need to ask RSC

• 740s may be left over in older records pre-246

• Xiaoli was looking in to aggregates

  • We looked at 776 field
  • LC-PCC Metadata guidance document on aggregates
  • Zhuo notes that MGD documents are not supposed to be used by catalogers now until the adoption of Official RDA
  • Ebe: Mac discussion paper

• Xiaoli, Ebe, Laura, and Sita interested in continuing to work on this in future meetings.

• Problem: 240s that contain only one title of a collection aggregating work, not the title of the whole collection aggregating work

• Ebe - how many of these are there? Is it a small proportion that we could pull out?

• Xiaoli - not every collection aggregating work may have a collective title. This project isn't to try and correct legacy data, just to follow practice that was done.

• Deborah - current default is to just use the access point provided.

• We have to take what we've been given in the MARC.

• Ebe: NLNZ has guidance in the toolkit in the document section on aggregates

Wrap-up

Action items

• Deborah will reach out to Crystal and set up future meetings for this mini team

Backburner

• Need to discuss multiple titles in 245 ( ; )

January 30, 2026

See time zone conversion Meeting norms Present: Laura, Sarah C., Cypress, Crystal, Xiaoli, Jian, Ebe, Deborah, Jorge, Kyla Absent: Time: N/A Notes: Sarah C.

Water Cooler/Agenda Review/Roles for Meeting (5)

Updates

• Crystal, Deborah, Rick, and Cypress working on proposal for ALA Core LDIG session - a short 15 minute update on what we've accomplished in "phase 1.5" and what we are working on for phase 2, with time for q&a. deadline for this is February 13--we need to get it in soon!
• Triplestore team meeting again February 19
• Transform now outputs the aggregate pattern that caused an aggregate to not be processed.
  • This will help people on the transform team identify what is causing something to be identified as an aggregate in the transform.
• Transform team hard at work on the translation implementation set-up

Entities & their attributes - high-level Phase II work distribution (60)

Entities for Phase II manifestation types, work types, and their appellations

• WEMI stack created first thing in transform for SEM
• Need coding for creating a WM stack for aggregating works; this will provide a framework for manifestations and works to which we can add appellations, attributes, and relationships
• Small team needed to flesh out -- Xiaoli and Kyla interested in working with Deborah on this?
• Concentrating on collection aggregating works to begin with, since very few elements will not map to the aggregating work

Identifying Aggregate manifestations

• The patterns that were coded during Phase I are provided in the “Pattern match” column of the CW_DW_AM_Markers.20241112 spreadsheet
• A summary of those patterns is provided in a newly added Aggregate Patterns general list
  • Xiaoli - different elements in different contexts might need a description where they don't in other contexts. How do we handle this? Answer: sometimes we don't describe aggregating works when we are describing augmentation aggregate manifestations. This is under AAM in the aggregate patterns general list document.
  • Jorge - the introduction, the prologue, and the epilogue are augmented works, but are they augmented expressions or augmented works? Answer - They are augmented expressions and works, but we don't have enough information to describe them separately, so they will just be described using manifestation notes. If it is a professor/agent associated with your university, you can add description on the work or expression level, but our transform won't get to that level.

Augmentation aggregate manifestations mapping

The primary focus of the MARC record is a primary augmented single-expression work and its expression and manifestation

• Headings Mapping table
  • appellation values (titles and access points) found in headings fields
    • for the WEM stack: 130; 100-111+240; 100-111+245; 245 (without 100-111)
      • See Headings Mapping Table >> Headings for WEM >> rows for Appellations
  • other expression/work values found in the above headings fields
    • See Headings Mapping Table >> Headings for WEM >> rows for Attributes: Find in: (note that those rows might be hidden)
  • other expression/work values found in other fields
    • See Mapping Spreadsheets or other mapping tables

Collection aggregate manifestations mapping

The primary focus of the MARC record is a collection aggregating work and its manifestation

• To begin, we are just describing the collection work:
  • If there is a representative expression element in a record, we can move that information up to the collection work. Otherwise, it may have to go into an manifestation note.
  • We can go through the headings mapping table and make decisions about what goes into the collection aggregating work and what goes into the collection manifestation. There is no expression, we go directly from work to manifestation.
  • Right now we're focused on making decisions about the aggregating work, we will look at the collected/aggregated work later.
  • Music headings:
    • Kyla, Cypress, and Cate can be consulted on music cataloging questions.
    • Medium of Performance of musical content of representative expression.
      • We cannot include medium of performance in the aggregating work when medium of performance only applies to the first work that is being used to describe the collection, the second work may have a different medium of performance.
    • We need to decide when a 100/240 is describing the first work in a collection versus when it is describing the collection as a whole.
    • If we make changes to mapping tables that have already been implemented in the code, we should create issues regarding the change in Github for the coders to see.
  • Title of Work:
    • Question: is there a list of fields we're looking at for the heading mapping table? Answer: Yes, they are provided in the columns
    • We don't want to show the 130 or 240 as the title of work because we can't distinguish whether it is a collective title or a single title of a work in the collection. We will have to discuss this point further in the future.
• Deborah needs help discussing and making decisions about the Headings Mapping Table:
  • This requires synchronous meetings/discussion.
  • Laura, Kyla, Ebe, and Xiaoli have volunteered to help.

Wrap-up

• Crystal will be on vacation next week, so Crystal won't be attending our next meeting on Feb. 6th.
• We can make the Feb. 6th a working meeting, Deborah and Cypress can give guidance.
• Crystal will set up exact meeting times to do mapping training with individual people once she's back from vacation.
  • If you need anything for M2R while Crystal is out, you can contact Cypress.
  • We can email Kate (Crystal's supervisor) if we need anything from University of Washington, i.e. Google Drive items owned by UW.

Backburner

Action items

• We still need help on the expressions mapping table, people can work on that between our meetings. We can make changes as we go and discuss questions in future meetings.

January 23, 2026

See time zone conversion Meeting norms Present: Crystal, Deborah, Jian, Jorge, Laura, Doreen, Kyla, Sarah C., Ebe Absent: Time: N/A Notes: Sarah C.

Water Cooler/Agenda Review/Roles for Meeting (5)

Updates

• Crystal, Deborah, Rick working on proposal for ALA Core LDIG session - a short 15 minute update on what we've accomplished in "phase 1.5" and what we are working on for phase 2, with time for q&a

• Translation workflow is coming along, transformation team is working on getting spreadsheets that can be converted into XML and implemented in the XSL

• Crystal sent scheduling poll for the next triplestore team meeting, Gordon drafted an agenda

• Crystal cloned Clair's repository with queries and accompanying scripts and shared with the rest of the triplestore team, as Clair is out on leave

• Tynan working with Lazaros on Wikibase Suite instance for us to share with Open Knowledge Greece, with an experimental dataset. Possible interest to triplestore team, but also will be neat as a proof-of-concept

• Questions on Updates:

  • Will our Wikibase Suite instance be separate from Greece's? Answer: Yes, it will.

Expressions Mapping Table working session

• Add a new column for "MARC Field Links" (DF)
• Rename " Source: MRC Field" as "Source: Searched MARC fields" (DF)
• Clarify together what goes in notes column, what goes in an issue, and what goes in a discussion
  • In Columns: notes on a field that do not need action.
  • Issues: action items that do not need further discussion.
  • Discussions: ask questions, discuss ideas.

Mapping Notes and Questions

• Stage 3 under expression table work form has step-by-step instructions.
• Self-deprecated fields are marked with "not mapped".
• If you run into challenges that need further input from team members, you can create discussion posts. Add labels to better organize discussions. Remember to put discussion link in "Github Discussion or Issue Link" column and row associated with field in the sheet. (Can keep main workflow discussion link, or replace it with specific discussion link).
• All information for a MARC field associated with a given RDA curie should stay in one row of the sheet, even if the conditions/subfield are different. Just add it to the same row to avoid creating more rows in sheet.
• 255 $a - NLNZ says this is mapped to "additional scale information", which is different than existing M2R mapping. Should we change mapping to match NLNZ, or keep it as is? View and contribute to discussion here
• If a field needs info from mappings heading table or F&M, this information does not have to be added to individual field-by-field tables. Rather, we can just link the relevant tables in the mapping expression categories sheet.

Wrap-up

Action items

• Work asynchronously on mapping in mapping expression categories.
• Crystal will update all tabs in "Mapping expression categories" with new column for "MARC field Links" and rename.
• Crystal will add descriptions for distinguishing what goes into columns, issues, and discussions to notes, to Wiki, and to "Welcome to MARC2RDA Discussions!" section.
• Crystal will finish individual on-boarding.

Backburner

January 16, 2026

See time zone conversion Meeting norms Present: Laura, Crystal, Deborah, Cypress, Ebe, Sita, Doreen, Jian, Xiaoli, Kyla, Jorge, Sarah C., Zhuo, Dee Absent: Time:Ebe Notes:Doreen

Water Cooler/Agenda Review/Roles for Meeting (5)

Updates (5)

• Richard made some updates to M2R-online:
  • Security updates
  • Minor improvements to UI
  • Support for uploading .mrc files
  • Statistics on processing
  • Existing links are not affected--shouldn't be very noticeable on surface
• Crystal, Deborah and Cypress met about the transformation workflow
  • Initial translation workflow will take time to set up
  • Once established, translations to additional languages (beyond Spanish) will be easier
• Crystal and Deborah spent time on the expressions mapping table workflow. Crystal did some formatting cleanup on the spreadsheet. Things should be ready to use
• Crystal and Gordon exchanged emails about the next triplestore meeting. Crystal will send a scheduling poll today
• Clair is on parental leave--Crystal will likely clone and re-upload her repository and then share with triplestore team members

Conceptual Discussion: RDA ↔ BIBFRAME / SHARE-VDE

• Question (Xiaoli): whether BIBFRAME → RDA mapping exists.
• Response (Crystal):
  • RDA → BIBFRAME mapping is possible.
  • BIBFRAME → RDA is generally not feasible due to lower granularity and inconsistent semantics.
• Notes:
  • SHARE-VDE uses a modified BIBFRAME profile; interoperability with other BIBFRAME variants remains unclear.
  • LC “hubs” are inconsistently defined and cannot be reliably mapped into RDA.
• RDA remains the source-of-truth model; reverse mapping from BIBFRAME is out of scope.

Expressions Mapping Table Workflow Review

• You can access the table here
• You can access Phase II mapping instructions here

Overall plan review (10)

• Review overall plan, making sure everything is clear and order of steps makes sense

RDA Vocab column (5)

• RDA vocabularies tab should be kept up to date
• Important for future creation of F&M tables
• Deprecated RDA vocabularies remain consultative, not primary

Notes column (5)

• Notes that represent needed changes should be turned into GitHub issues
• Notes that are purely informational can remain notes
• If an issue already exists:
  • either reopen it (if appropriate), or
  • create a new issue and link to the old one
• Notes tab needs additional documentation clarifying:
  • when to create an issue
  • when to create a discussion
  • when a note is sufficient
• Blank Source Mapping cells are ambiguous:
  • unclear whether a mapping exists but is not yet done
  • recommendation: include a link to the relevant sheet even if mapping is not complete

M2R Mapping Column (40)

• Test the Source: M2R Mapping column again
• Co-working session: everyone self-assign an element and walk through the workflow, asking questions as we go along
• Example discussed:
  • 041 $a / $d
  • Existing condition (Leader 06 = J) identified as redundant
  • Decision: do not include unnecessary conditions in mapping
  • Action: create GitHub issue to remove redundant condition and trigger code recheck
• When working independently:
  • It is acceptable to mark “needs further discussion”
  • Issues/discussions can be created without full resolution

F&M Tables (10)

• Stage 4 (F&M tables) expected Feb–Mar 2025, likely longer
• Two-step process:
  1. Identify needed / not needed
  2. Determine whether an F&M table already exists or must be created
• Best suited for contributors with experience in both:
  • mapping
  • transformation coding
• Volunteers encouraged; not expected for one person to do all work

Wrap-Up (5)

Backburner

Action Items

• Crystal to send triplestore scheduling poll
• Crystal to clone and re-upload Claire’s repository and re-share access
• Add documentation clarifying use of Notes tab (issue vs discussion vs note)
• Begin self-assignment and start filling M2R Mapping column
• Set up individual onboarding sessions if needed:
  • Crystal with Kyla and Xiaoli
• Explore optional co-working sessions if helpful

January 9, 2026

See time zone conversion Meeting norms Present: Laura, Crystal, Deborah, Cypress, Ebe, Sita, Doreen, Jian, Xiaoli, Kyla, Jorge, Sarah C., Zhuo Absent: Time:Ebe Notes:Sarah

Water Cooler/Agenda Review/Roles for Meeting (5)

• Reminder that anyone can add agenda items which they want to address in meetings.

Updates (5)

• National Library of Norway (Deborah)
  • They are looking for ways to convert good-quality MARC21 records to RDA/RDF in RIMMF.
  • Should we suggest that they get involved in our project?
  • Crystal suggested that it would be great to get them involved, especially with consideration to our recent translation efforts. We could invite them to a meeting to get to know more about M2R.
  • Cypress suggested that even if they don't want to get heavily involved, they can use our conversion tool and provide feedback.
  • We could possibly get records for them, once we've established translations more.
  • Deborah will reach out to them and ask about how/if they want to be involved.
• Translations workflow is coming along
• Crystal has been added to Clair's GitHub Repository with GraphDB queries, but needs to check in with Clair (who is on leave) about permissions to add others

Expressions Mapping Table Workflow Review: Column H (40)

• You can access the table here
• You can access Phase II mapping instructions here
• Do a couple of properties, ask questions for Deborah
• Once this is clear and working well for everyone, Crystal can reach out to new folks for individual mapping training sessions
• We will continue discussion and development of mapping instructions for Phase II asynchronously. The discussion on Github is here

Expressions Mapping Table Workflow Review: Columns J & K (30)

• Deborah explanation

Column K (F&M Table):

• Provides a link to a "Finding and mapping table" for the RDA element. Example: Frequency mapping table
• If an element is associated with an RDA vocabulary, then it will need a simple F&M table. It would be helpful if someone could fill out portions of these types of tables, using a blank template that will be provided (example of blank template from Deborah)
• If an element is associated with multiple MARC fields, then:
  • Those fields could be added to a Vocab F&M Table
  • Or they might require the creation of a more complicated F&M Table
• Question: for the document versions of these tables, would it be helpful if they all lived in the same Google Drive folder? Once Crystal understands how to identify them she's happy to move things around to make them more findable for everyone else.

Wrap-Up (5)

Backburner

Action Items

• Crystal get in touch with Clair and add everyone to her repository
• Triplestore team meet again to talk about work plan (Crystal to schedule)