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
Status colour Blue title OPEN
The group is waiting for further information or some specific action to be completed before progress can continue
Status title BLOCKED
Discussion is ongoing and work is potentially in progress
Status colour Yellow title in progress
Discussion resolved and required actions completed
Status colour Green title 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”:
| Gadget | ||||
|---|---|---|---|---|
|
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 |
| We want to be able to reorder the holdings and items in how they are displayed. | Inventory | 2019-01-01 |
|
| |||||||||||||||||||||||||||||||||||||||||||
| 2 | Inventory: Strip leading, trailing, and double spaces out of data in some elements (instance, holdings, item) |
| 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 |
|
| |||||||||||||||||||||||||||||||||||||||||||
| 3 | Multiple Graphical Representations |
| The instance schema does not provide a way to record and link vernacular and Latin script. | Inventory | 2025-01-21 | Laura E Daniels and others | 2024-10-17 Metadata Management Meeting notes 2024-01-25 Metadata Management Meeting notes … and other occasions since 2019. |
|
| |||||||||||||||||||||||||||||||||||||||||
| 4 | Ability to Hide Fields at the Tenant Level |
| 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 |
|
| |||||||||||||||||||||||||||||||||||||||||||
| 5 | Separate Statistical Codes by Record Type |
| 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 |
|
| ||||||||||||||||||||||||||||||||||||||||||
| 6 | Holdings & Item Record Templates |
| 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 |
| ||||||||||||||||||||||||||||||||||||||||||||
| 7 | Sort & Browse by Holdings level Call Number |
| 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 |
|
| |||||||||||||||||||||||||||||||||||||||||||
| 8 | Inventory Hierarchical Navigation Structure (UI/UX refactor) |
| 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.
| Inventory | 2025-01-23 | ALL |
| |||||||||||||||||||||||||||||||||||||||||||
| 9 | Add “Item Cost” field on item record |
| 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 |
|
| |||||||||||||||||||||||||||||||||||||||||||
| 10 | Related Instances Data Element |
| 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.
| Inventory | 2025-01-23 |
|
| |||||||||||||||||||||||||||||||||||||||||||
| 11 | Shared Bound-with and Analytics record display icon |
| 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) | ||||||||||||||||||||||||||||||||||||||||||||
| 12 | Make 336 (instance resource type) repeatable on Instance records |
| While the 336 is repeatable in MARC, it is not repeatable on Instance records. This also affects filtering. | Inventory | 2025-01-30 |
New stories: Backend:
Frontend:
|
| |||||||||||||||||||||||||||||||||||||||||||
| 13 | Search MARC fields in UI |
| Inventory and/or Bulk Edit and/or Lists App | 2025-01-30 | Investigation ticket:
| |||||||||||||||||||||||||||||||||||||||||||||
| 14 | MARC Mapping/ MARC Mapping Updates |
| New MARC fields/subfields and if and how to include them into the Inventory entities.
| Inventory | 2025-01-30 |
| ||||||||||||||||||||||||||||||||||||||||||||
| 15 | Ebooks and Ebook Packages |
| Duplicative data; representing packages | 2025-01-30 |
| |||||||||||||||||||||||||||||||||||||||||||||
| 16 | Indexing Symbols and Words |
| 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 |
|
| ||||||||||||||||||||||||||||||||||||||||||||
| 17 | Different displays for different users |
| 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 |
| Work has been done with POL but not other data; reach out to RA SIG for further discussion | Inventory | 2025-02-06 |
|
| |||||||||||||||||||||||||||||||||||||||||||
| 19 | Reporting |
| 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 | Related Jiras found
|
| ||||||||||||||||||||||||||||||||||||||||||
| 20 | Spine Label Printing |
| Be able to print spine labels directly in Folio | Inventory | 2025-02-06 |
| ||||||||||||||||||||||||||||||||||||||||||||
| 21 | Managing Data Export Profiles |
| Data Export profiles are easily managed within the UI.
| Data Export, Data Export Settings | 2025-02-06 | Lynne Fors | ALL |
|
| |||||||||||||||||||||||||||||||||||||||||
| 22 | Add source URI to Inventory instance metadata |
| 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 |
| Laura Daniels | National Library of Sweden ShareVDE parties |
|
| |||||||||||||||||||||||||||||||||||||||||
| 23 | Revisit Instances source codes |
| 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 | Related to but not encompassed by:
| ||||||||||||||||||||||||||||||||||||||||||||
| 24 | Ability to see staff suppression when searching for holdings and item - Review of Staff Suppression and how this behaves in FOLIO Inventory |
| Currently when you are searching for an item (by barcode or other value) or an holdings record that you know should be there and you get no results, there is no way to tell if the records are connected to an instance that has been staff suppressed. The only filter for items and holdings is suppress from discovery. Propose to add a new filter or something that allows to see if holdings or item are connected to a instance that is staff suppressed. Or at best have a message display that the holdings or items are connected to an instance that is staff suppressed. | Inventory | 2025-02-27 | ALL |
|
| ||||||||||||||||||||||||||||||||||||||||||
| 25 | Enable records (Instances & Holdings) that are connected by Shared Items (shared by Bound-with and analytics function) to be retrieved/surfaced when searching in Inventory Item segment as well as re: other Apps like Lists |
| Compare also #11 above as well as Lists App Implementers Topics page #13. Currently (in Q) only the Parent title/Instance (and Holdings) is found and then displayed, when I click out of the Item itself, when searching by anything from the Inventory Item segment. Yes, I can scroll to the bottom on the Item to the Bound-with and analytics section to see what is linked, but it is then very cumbersome to work through the different records or to properly be able to browse them, etc. … While it is nice that at the very top “and other titles” is in a bright red font, it would be even better if in additional when one clicked on “and other titles” one would be popped to the bottom where the other titles are at least listed (for some reason, I keep trying to do that, and forgetting to just scroll down; the red is so inviting ?!) | Inventory | 2025-03-06 | Sara Colglazier (MH/5C) | ||||||||||||||||||||||||||||||||||||||||||||
| 26 | Holdings Record Effective Shelving Order |
| As an institution that does not use item records for serial/journal runs, the effective shelving order is important in sorting call numbers when running reports. We want to replicate the Holdings effective shelving order from what was done for the Item record effective shelving order. | Inventory | 2025-03-10 | Lynne Fors (Wellesley College) |
| |||||||||||||||||||||||||||||||||||||||||||
| 27 | Damaged item status |
| Enhance the flexibility of recording damage to physical items. Libraries would like to record the kind of damage that occurred and when. Certain types of damage would trigger an assessment for replacement or deaccession. Related User Stories:
| Inventory | 2025-03-20 |
| ||||||||||||||||||||||||||||||||||||||||||||
| 28 | Implement Container record structure |
| The Container record represents a package of either Instances and/or Items. As such it provides the ability to group these together for any number of reasons. A given Instance or Item may be placed in any number of Packages since these are ostensibly independent groupings and there are many possible ways to group resources. | Inventory | 2025-04-11 |
|
| |||||||||||||||||||||||||||||||||||||||||||
| 29 | Implement Electronic portfolio record type |
| Working with eResources in Inventory can be difficult. There are no places to slot information on acquisition, agreements, other related eResource invnetory, etc. It would be great to be able to have a record type for eresources. These record types could be combined to form a collection.  | Inventory | 2025-04-23 | |||||||||||||||||||||||||||||||||||||||||||||
| 30 | Support search within list |
| Provide the ability to search within lists like items connected to a holdings. | Inventory | 2025-05-06 |
|
| |||||||||||||||||||||||||||||||||||||||||||
| 31 | Date Acquired (without Acquisition app(s) connection) |
| Many legacy items in Special Collections have dates noting when they were given to the institution by a donor or acquired in general. We would like to be able to have the standardized dates available in the Item record for each item, as opposed to a note or multiple notes in the bibliographic record for multiple copies (similar to the Item damaged status with date in Condition accordion). This has been a requested report from our special collections librarians and this field would make sorting by date much easier. | Inventory | 2025-06-12 | Lynne Fors | ||||||||||||||||||||||||||||||||||||||||||||
| 32 |