Parking lot | Future topics
This page is to collect ideas and wishes for future topics to be discussed in the Serials subgroup.
Topic suggestions for future meetings
Start by listing all your ideas.
Idea | Why | Who | Status | |
|---|---|---|---|---|
| 1 | Sharing publication pattern templates | In Sunflower the Serials Management module supports publication pattern templates. Since the required templates are likely to be common across many libraries it would be good to find a way to share them | @Owen Stephens | Discussed 25th July 2025 Options:
Action: OS to add patterns to a wiki page as starting point. Include way of people requesting/suggesting templates Page now available at https://folio-org.atlassian.net/wiki/x/PoDaT |
| 2 | Establish a direct link from the Receiving record (receiving title) to the Serial record | Users could easily switch between these two apps this way | @Peter Sbrzesny | Action: OS & JR to collaborate on a feature/story to add “Serials management” accordion to Receiving view pane, containing link back to Serials Management & frequency (publication cycle) info Follow up on Aug 22nd Broad feature added https://folio-org.atlassian.net/browse/UXPROD-5579 , stories to come |
| 3 | The workflow for creating pieces requires double action at the moment: first you have to generate predicted pieces in Serials, after that receiving pieces can be created. Could generation of receiving pieces be made easier? Would it be possible to start some kind of automated workflow when the expected date of the last generated piece gets close? | Would be helpful to avoid double work which is making the workflow quite cumbersome right now. | @Peter Sbrzesny |
|
| 4 | Display or store more information from other apps (inventory, orders, serials …) in Receiving (shelfmark, acquisition notes …) and keep them in sync | Information is needed to decide on the next steps in the workflow. It would be easier for library staff to have this information at one glance when pieces are received.
| @Peter Sbrzesny |
|
| 5 | Printing of labels for received pieces | Pieces that are displayed in the reading room or any other public location need to be clearly identified as property of the library. This could be achieved by a label carrying the library’s name and the journal’s shelfmark/notation | @Peter Sbrzesny |
|
| 6 | How closely should receiving pieces and items be linked, particularly for received pieces? | Should updating the piece update the item? Should updating the item update the piece? (Examples include barcode changes, correcting chronology/enumeration, etc.) Do libraries use Receiving to update items? | @Joseph Reimers |
|
| 7 | Eureka roles management | Placeholder for the inevitable deep dive | @Joseph Reimers @Owen Stephens |
|
| 8 | Creating the new piece after the latest is marked received/ automated generation of pieces | Many of our libraries don’t want created pieces a year in advance. maybe there is a way to generate the new piece after the last one W1sser_L2ben_23 received | @Susanne Gill |
|
| 9 |
|
|
|
|
| 10 |
|
|
|
|
| 11 |
|
|
|
|