| JIRA | | serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | UXPROD-3525 |
|---|
|
- Have data duplicating in Serials, Receiving, and Inventory. In some cases, will not use receiving, but still use item records. In some cases, kind of happens the other way around.
- There are a variety of use cases that support different apps, so data needed to be in each othe apps.
- With Serials, increasing the amount of detail.
- Maybe not just as simple as the data should only live in one place, but you should be able to get it from somewhere, because maybe you only want to use one of the apps.
|
|
| Dennis | - ~ :45 - For those using receiving and item records and having information populate in discovery, are these fields in the item record sufficient? (Enumeration, chronology, volume, year, caption)
- Beverly - Accustomed to MARC format, where there is a caption and a value. Ended up putting everything in the volume field (partly because of migration). For bound volumes, all a string in the volume field. Didn't come over well, suppressed all the items for serials titles. For not serials, they do display, but it is much more straightforward because they do not have the other information.
- Julie - In our item records, put everything in the enumeration (distinctive information) - regardless of whether monograph or serial. Part of it had to do with migration and part of it where existing data lived and how it gets picked up for discovery. Unusual case in that not using receiving for serials
- Owen - We know that people have made different decisions about how to use these fields. For medium to longterm, need to consider what the migration path looks like. Will be important part for those who have already implemented.
- Beverly - Wanted to clarify that what I was describing is item records for bound volumes. For issues, came up with a system of editing the holdings record. Do use enumeration and chronology there for own purposes to know whether to claim and what has been received. Do not use receiving pieces. Very few print serials at this point.
- Sara - Key that people made different decisions when they migrated. What system did you come from? What did your data look like there? What were you advised to do when you came into FOLIO? Five Colleges had data for millions of items put in that needs to be interacted with, managed, etc. For periodicals have data in enum, chronology, and volume. Have to keep it the same so that when it is dealt with will be identical. Cannot underestimate how it is working with items in inventory and how difficult it is to see the items. Trying to find things and sort them is only possible if you can, across pages, sort on chronology for example. What will we do with all these migrated things?
- ~:58 - Only option for managing items is to find Instance and browse item records.
- Single field restricts ability to search and filter.
- :01 - Maybe worth looking at general solutions in next meeting and maybe talking through those will tease out some details.
|