WOLFCon 2024 proposals deadline - March 31st (please think about what you'd like to see presented or if you'd like to present ahead of meeting discussions, date TBD)
Next meeting - Tuesday, March 5, at 1 pm Eastern
Reminder - please review acq-sig-topics and vote to help prioritize the topics
WOLFCon 2024 proposals deadline - March 31st (please think about what you'd like to see presented or if you'd like to present ahead of meeting discussions, date TBD)
Will schedule a meeting or two to brainstorm
Next meeting - Tuesday, March 5, at 1 pm Eastern
Reminder - please review acq-sig-topics and vote to help prioritize the topics
Roadmap group has tried to update to keep current with what has been going on.
Still thinking about best way to keep current with every release.
Be a bit more prospective.
Everything needs to be appropriately tagged by POs for it to work.
Wiki/Atlassian migration broke everything and had to be cleaned up.
Holistic view of FOLIO development.
:11
Serials App Demo
Owen Stephens
Gap in functionality of FOLIO noticed by Duke and GBV - no way of generating lists of serials to check in
Makes it challenging in terms of check-in and consistency. Can be a lot to create for weekly or daily issues. Don’t know what you are not receiving, which is needed for claiming.
Focus on print serials, in particular being able to predict expected issues.
Jointly funded by Duke and GBV and Owen brought on as product owner.
Duke did not progress with FOLIO. Since then funded solely by GBV.
Lots of discussions early on in progress. Over last few months haven’t been very active in terms of those types of meetings because development team has been focused on developing functionality.
Works alongside orders and receiving.
:17 - Beginning of demo
Orders > Create order
Orders > Create POL
Receiving workflow - “independent order and receipt quantity”
Serials > Create new Serial record (will allow connecting everything together)
Search options
Title string
Description
PO line search - most powerful set of searching as you can search by any of the ways you search by order lines.
~ :22 Add publication pattern
Publication cycle:
Usually want to use most granular time unit (published every day vs 365 times a year)
Give system information about when within timeperiod it is published
Omission rules - publications skipped (e.g. doesn’t have a December publication)
Combination rules - issues combined (e.g. July/Aug in the Summer)
Labelling - how the issues are labelled (numbering system, etc.)
Enumeration
Numeric
Textual - used for cases where issue is labelled with seasonal labelling (Spring, Summer, Autumn, Winter)
Chronological
Template
:34 - Kristin: Is syntax for templates going to be included in documentation?
Clear that it is a challenging area for functionality right now. Not where we want to leave it, but is where we are today.
Jackie Magagnosc 8:35 AM I'm having trouble imagining some staff managing the Template bit.
Any standards for FOLIO? (Noticing differences between Data Import, etc.)
Susanne Gill (BVB) 8:35 AM I'm seeing me doing it for the smaller libraries with not so technical library staff...
Aim to get it similar to patron notice templates where you can add tokens, but not quite there.
Yes, will provide documentation. Also could do some examples. Community as a whole could document. Examples will probably be in the Wiki (can keep updated even after release).
Dung-Lan Chen 8:39 AM Once a template is created, I assumed it can be applied to other serials with the same structure (ex. monthly with vol./no./year) as in your demo?! Each template should have its own name to differentiate from other ones?!
Can copy/paste
Vary in how they work
Susanne Gill (BVB) 8:40 AM A screenshot of this would be a good start. it's a simple one :-) and you can easily see where each part is coming from
~ :41 - Generate predicted pieces
For every publication, only create pattern once. Generally do not need to change very much.
Once done, get taken to predicted pieces set. Can see everything that is expected.
Finally can generate receiving pieces.
If same journal is in multiple locations, can repeat generating receiving pieces
~:46 - Don’t want to click “generate receiving pieces” again
Once generated in receiving can do check-in as normal
If locations, will be prompted in Serials
Currently filling out “Display summary” field only.
Does not fill out Copy number, Enumeration, and Chronology
Group Dennis is leading looking at how this should work across Serials, Receiving, Inventory and Discovery
Made this decision as simplest approach for now
~ :50 Questions / feedback?
Looked really good
Steps to go through. Still some rough edges. Some aim to tidy up for Quesnalia or future releases.
To get into flower release need approval from Product Council and Technical Council.
Approved by Product Council
Technical Council has specific criteria needed to be met - it is possible that it may not be included in Quesnalia if changes are not met in time
If not formally part of release, could still be added individually by service provider once Serials is ready
