Metadata Management Implementers Topics
Please add questions and topics here. Topics or questions posted in slack will be added here as well.
Metadata Management implementation topics, questions or issues
Topic Status legend:
To be discussed
OPEN
The group is waiting for further information or some specific action to be completed before progress can continue
BLOCKED
Discussion is ongoing and work is potentially in progress
in progress
Discussion resolved and required actions completed
CLOSED
How to contribute to other people's discussion topics:
Do not add detail to closed or discussed topics as your comments may be overlooked. In this situation, it might be best to Add your details as a new topic and reference the previous topic.
To contribute to an existing topic. Add a new paragraph to the description column.
@mention yourself at the beginning of the paragraph
How to indicate you are also interested in a topic:
@mention yourself in the "Interested parties" column and add your institution name
How are topics archived:
When a topic status is set to closed by it's "Owner". The topic must also be moved to the "Metadata Management implementers Archive" page.
Copy the topic and paste it at the top of the Archived topics page that is nested under this page
Delete the topic from this page
Metadata Management Road Map Dashboard
Metadata Management Bug Tracker
List of Issues with label “metadatamanagement”:
Topic | Status | Description/Use Case | FOLIO App | Date Added to this Table | Contact Name | Interested Parties | Link to Meeting Discussion | Link to Jira Issue | Action | |
|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Reorder of Holdings and Items | in progress | We want to be able to reorder the holdings and items in how they are displayed. | Inventory | 2019-01-01 | @Laura E Daniels | @Laura E Daniels | https://folio-org.atlassian.net/wiki/spaces/MM/pages/647036967 |
| SME’s need to vote
|
| 2 | Inventory: Strip leading, trailing, and double spaces out of data in some elements (instance, holdings, item) | in progress | Don’t store leading and trailing spaces that are inserted in a field of any Inventory record. The SIG has not yet agreed how to handle double (multiple) spaces inside the metadata. | Inventory | 2025-01-20 | @Felix Hemme |
| https://folio-org.atlassian.net/wiki/spaces/MM/pages/4669951 https://folio-org.atlassian.net/wiki/spaces/Deutsche/pages/647200799 | Check with @Khalilah Gambrell about the status of this feature. See questions on UXPROD-3473 from 2025-01-20 and 2025-04-17. | |
| 3 | Multiple Graphical Representations | in progress | The instance schema does not provide a way to record and link vernacular and Latin script. | Inventory | 2025-01-21 | @Felix Hemme | @Laura E Daniels and others | https://folio-org.atlassian.net/wiki/spaces/MM/pages/516030501 https://folio-org.atlassian.net/wiki/spaces/MM/pages/4670355 … and other occasions since 2019.
| Get in touch with relevant POs and bring to their attention. Update the existing Jira features to reflect the current state of knowledge (papers from LoC and Laura Daniels, Christie Thomas, and Jacquie Samples). | |
| 4 | Ability to Hide Fields at the Tenant Level | Open | It should be possible to hide (not display to users) specific fields in view/edit as well as in-app reports. Out of scope: removing fields entirely? Related to, but not same as need for Templates | Inventory, Orders, all? | 2024-01-22 |
| @Laura E Daniels | https://folio-org.atlassian.net/wiki/x/HQDsKw https://folio-org.atlassian.net/wiki/spaces/MM/pages/779976705 | Update Jira SMEs need to vote
| |
| 5 | Separate Statistical Codes by Record Type | in progress | Would like to be able to assign a different set of statistical codes for each type of record (Instance, Holdings, Item) tempNote:
| Inventory | 2025-01-22 | Laura Daniels | @Laura E Daniels | https://folio-org.atlassian.net/wiki/spaces/MM/pages/862978052 | DRAFT Jira SMEs need to vote | |
| 6 | Holdings & Item Record Templates | Open | Currently, staff creating holdings and item records must select/enter the same elements repeatedly; we need the ability create, apply, and manage templates for Holdings and Item records; templates save staff time, reduce risk of repetitive motion injury, and reduce errors; Orders has a good model we could follow | Inventory | 2025-01-22 |
| @Laura E Daniels |
| ||
| 7 | Sort & Browse by Holdings level Call Number | Open | Currently we are only able to sort call numbers if there is an item record. Many institutions do not use item records for their serials, journals, etc. and thus they are invisible in the browse index. There is a high risk of duplicate call numbers being assigned. | Inventory | 2025-01-23 |
| @Lynne Fors @Laura E Daniels | SMEs need to vote | ||
| 8 | Inventory Hierarchical Navigation Structure (UI/UX refactor) | Open | The current use of the display in the second pane, displaying the search result as the Instance record, is not that useful, especially when searching on data specific for Holdings and Item data. We need to replace the MCL display with a clear view of the instance record with associated holdings and item records, a display illustrating the hierarchical relationship for the given search/result. | Inventory | 2025-01-23 |
| ALL | https://folio-org.atlassian.net/wiki/spaces/MM/pages/4663230 | ||
| 9 | Add “Item Cost” field on item record | Open | In FOLIO, there isn’t an adequate and consistent field to store an item’s monetary value. In every story or feature request for actual cost, one resounding prerequisite is this value existing on the item record. | Inventory | 2025-01-23 |
| @Joseph A Molloy @Lynne Fors | App Interaction SIG:https://folio-org.atlassian.net/wiki/spaces/AppInt/pages/442269787 | Invite Joey Malloy from the Public Library SIG to join us for the item cost discussion. | |
| 10 | Related Instances Data Element | Open | Allow for MARC linking fields (77x, 76x, 78x) to populate related Instances data elements. This would greatly enhance experiences with periodicals and serials and their many name changes over time. https://loc.gov/marc/bibliographic/bd760787.html As a staff user at the circulation desk I want to see related instances, e.g.
| Inventory | 2025-01-23 |
| @Lynne Fors | SME’s need to vote | ||
| 11 | Shared Bound-with and Analytics record display icon | Open | Book-Shadow Icon is not sufficiently helpful, because it does not distinguish between the record sharing out the Item and the record(s) being shared with the Item--so to speak (the “other titles”). Yes, I can see what the other titles are if I remember or know to scroll all the way down in the Item record, but … even there it would be good if it was then also indicated which records are which, since I have just scrolled away the title info at the very top. Then also it is further confusing because when I search by barcode, only the one record is retrieved. | Inventory | 2025-01-30 |
| @Sara Colglazier (MH/5C) | https://folio-org.atlassian.net/wiki/spaces/MM/pages/1286209537 |
| Discuss in MM SIG Wait for Ryan and Kimie to come back to MM SIG. Create Jira feature Schedule Jira feature |
| 12 | Make 336 (instance resource type) repeatable on Instance records | Open | While the 336 is repeatable in MARC, it is not repeatable on Instance records. This also affects filtering. | Inventory | 2025-01-30 |
|
|
| https://folio-org.atlassian.net/browse/UXPROD-3973 New stories: Backend: https://folio-org.atlassian.net/browse/MODINVSTOR-1412 | @Felix Hemme to write up a new story, link it to UXPROD-3973 and bring it to the attention of the PO’s. |
| 13 | Search MARC fields in UI | Open |
| Inventory and/or Bulk Edit and/or Lists App | 2025-01-30 |
|
|
| Investigation ticket: https://folio-org.atlassian.net/browse/UXPROD-5218 | |
| 14 | MARC Mapping/ MARC Mapping Updates | Open | New MARC fields/subfields and if and how to include them into the Inventory entities. This concerns mapping questions and the overall instance/holdings schema. We agreed to move the following question into the parking lot for further analysis:
| Inventory | 2025-01-30 |
|
| |||
| 15 | Ebooks and Ebook Packages | Open | Duplicative data; representing packages |
| 2025-01-30 |
|
|
| ||
| 16 | Indexing Symbols and Words | CLOSED | Support searching in inventory with strings containing “and” or “&” and getting results that contain the other (eg. “Propaganda and Misinformation” vs. “Propaganda & Misinformation”) |
| 2025-01-30 |
|
|
| Has been implemented with Ramsons. | |
| 17 | Different displays for different users | Open | In Inventory, change how the display looks depending on the user (Circ, Acq, Cataloging, etc.). This could also be an ECS issue for different institutions wanting different displays. | Inventory | 2025-02-06 |
|
|
|
| |
| 18 | Ability to maintain relationships with other apps when holdings/items are moved | Open | Work has been done with POL but not other data; reach out to RA SIG for further discussion | Inventory | 2025-02-06 |
|
|
| Reach out to RA SIG for further discussion | |
| 19 | Reporting | in progress | Not everyone has the same kind of access to reports (via MetaDB etc.); need high level discussion of what types of reports are wanted; reach out to Reporting SIG for further discussion | Inventory ; Data Import ; Data Export | 2025-02-06 |
| ALL | https://folio-org.atlassian.net/wiki/spaces/MM/pages/862978052 | Related Jiras found | Add to this document (Deadline April 24th 2025): |
| 20 | Spine Label Printing | Open | Be able to print spine labels directly in Folio | Inventory | 2025-02-06 |
|
|
| ||
| 21 | Managing Data Export Profiles | Open | Data Export profiles are easily managed within the UI. Once a profile has been used to export data, we can no longer edit or delete the profile and the underlying mapping profile. This creates an excessive amount of clutter within Data Export (and in the Data Export settings). We need to be able to manage these profiles within the User Interface just as we can manage our Data Import profiles. NB They can be deleted via the API, but that isn’t a good solution.20 | Data Export, Data Export Settings | 2025-02-06 | Lynne Fors | ALL |
| 2025-03-06: @Jennifer Eustis will reach out to Magda and check if it can be worked out and get a Jira ticket created. | |
| 22 | Add source URI to Inventory instance metadata | CLOSED | The scope of this feature is to create a new field for a URI in Inventory Instance administrative metadata. This URI would provide a bridge between a description maintained in a shared cataloging environment such as Sinopia, Share-VDE, Libris (National Library of Sweden), or Blue Core, and FOLIO Inventory. | Inventory | Feb 26, 2025 | Laura Daniels | National Library of Sweden ShareVDE parties
| https://folio-org.atlassian.net/wiki/spaces/MM/pages/843284481 | Seek funding of the work BE and FE estimate of required work (Index Data) Development team appointed Development work has started and is in scope for Trillium (2025-04-17) | |
| 23 | Revisit Instances source codes | Open | Source codes currently conflate different types of information in addition to affecting what can or cannot be edited in the instance data. Not all current or potential sources of instance data can represented in the default values. | Inventory | 2025-02-07 |
| @Laura E Daniels | https://folio-org.atlassian.net/wiki/spaces/MM/pages/4663650 | Related to but not encompassed by: |