Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
See Acquisitions SIG meetings agenda and notes wiki here for more details if interested
Central ordering UAT ran from 8/27 - 8/30 (Dennis reviewed the results with the SIG on 9/10)
Duplicate invoice UAT ran from 9/3 - 9/9 (Joe reviewed the results with the SIG on 9/10)
Joe discussed/reviewed the latest mockup of claiming with the SIG on 9/10 & 9/10
Dennis called for interest in joining a small group to discuss acquisitions integration. The small group has met once and anticipates two more meetings to be held
ACQ SIG is planning a meeting with GOBI integration as the topic. Exact date TBD but it is anticipated to be one of the Tuesday's meetings in October
The group made it to the last topic entered for Implementers Topics list (in 9/17 ACQ SIG meeting) with several topics skipped due to those who submitted the topics weren't present at the time. Will circle back to the skipped topics in later meetings when those who submitted are available to attend
We had a presentation from OpenRS on how that product works for consortia, and how it integrates with FOLIO. We had a survey running in August, results are now in and we'll be reviewing at the next meeting. We also reached out to the Reporting SIG to see how we might interact with that group to get consortial reporting needs prioritized.
The Documentation Working Group discussed documentation workflow questions and Jira use for tracking documentation issues. In addition the WOLFcon presentation "Best practice - FOLIO Documentation in institutions" was discussed and prepared.
Libraries were asked to collect and describe use cases on ERM workflows that then were discussed in the SIG meeting. The collection of use cases can be found here: Collecting ERM workflow examples for WolfCon 2024. Everyone is welcome to add more.
The use cases will build the basis for two sessions at WOLFcon 2024. These are joint sessions between the ERM SIG and the Workflow SIG. The sessions are:
Bulk edit of FOLIO Instance’s notes UAT showed that the existing implementation is confusing as most participants attempted update instance with source MARC using Instance fields option. Proposed new UI options contain the label "Instances with source FOLIO" and "Instances with source MARC". What that acutally means is ~"Instance with source FOLIO = instance with no underlying SRS", because the instance source is just a string field and can contain any value other than FOLIO. Magda will work more on this.
With Ramsons the Bulk edit app supports editing instance administrative notes and all instance notes types.
UXPROD-4746: Sort, filter, and mapping changes for Dates
Decission that the instance fields publicationPeriod.start and publicationPeriod.end will be removed from the instance schema. These fields are not surfaced in the UI and will be replaced by new fields:
Date type: Controlled list, included in MARC mapping rules
Date 1: Text box - allows for four characters (alphanumeric) - no validation on UI; validation on backend and if data does not pass validation, it should be considered as 0000
Date 2: Text box - allows for four characters (alphanumeric) - no validation on backend and if data does not pass validation, it should be considered as 0000
The dates will be displayed in the Inventory result list in a new column calles Date after the Publishers column.
A new filter for the date data is added to the search & sort pane.
UIIN-2889: Spaces entered in Call number field are not saved; trailing and leading spaces are removed and the call number will be found in Browse. White spaces before the call number is also removed. Only impacts newly entered data, not existing/legacy data. Existing data has to be fixed separately.
Version History / Change Tracker
We're currently in the process of collecting use cases. This has to be done by September the latest.
Kimie has created mockups (WIP) how the change tracker would look like in Inventory.
The SIG agrees that the list of fields is good.
For privacy reasons there has to be a setting to turn off what user made changes.
We also talked about how long to store version logs or how many version logs should be stored. There has not been overall agreement but a feeling that having the latest 10-15 versions or 2-3 years of logs available in the UI would be okay for the beginning. Fetching older logs via the API could be okay for some users, but not the general librarian.
We also have to define what an update is that triggers an entry in the history. We added a section on the wiki page for what should not be considered an update, e.g. checking out an item.
