2024-09-05 Agenda and meeting notes

Owned by Thomas Trutt
Last updated: Sep 19, 2024
1 min read

Attendees:

@Nina Morgenstern @Andreas Mace @Uschi Klute @Jana Freytag @Stephanie Buck @Anne Ekblad @Thomas Trutt @Kajsa Bäckius @Cornelia Awenius @lisa perchermeier @Niels Erik Nielsen @David Bottorff @Amelia Sutton @Anja Kakau @Charlotte Whitt

Section 2: Routing, notices, and slips

Discussion Items:

  • Administrative topics

  • What tokens other tokens are need

    • does this extend the requests model?

  • Are any additional slips needed

    • Return receipt

Meeting notes:

Overview

The conversation included a review of current staff slips and considerations for adding tokens like publication year and edition, as well as the complexities involved with item notes. The group debated the prioritization and implementation of various tokens, including instance ID and barcode image tokens. Discussions further explored the need for statistical codes for RFID tags and the addition of staff notes to requests, along with considerations for a new media requests app. The meeting also covered the review of pick slip layouts, particularly from the National Library of Sweden, and the necessity of tokens for email notifications. Finally, participants discussed notice workflows related to item needs and potentially extending service point models for patron notifications while outlining action items for future meetings regarding email notification tokens and the need for return slips.

Notes

📄 Staff Slips and Notices (07:00 - 14:33)

  • Review of current tokens used in staff slips

    • Current tokens include details such as item publication year, addition, and physical description, which are essential for accurate processing.

    • Discussion on the necessity of including certain tokens, like instance ID and statistical codes, to enhance workflow efficiency and information retrieval.

    • Consideration of how tokens are displayed in the slips and their relevance to staff versus patron needs, ensuring that only necessary information is included for each audience.

  • Discussion on adding year of publication and edition tokens

  • Consideration of item notes and their complexity

  • Exploration of physical description field and its usefulness

    • The physical description field can help differentiate between similar items when searching for books.

    • Having details like number of pages and dimensions aids in visual identification of materials.

    • Physical descriptions are useful for staff when scanning books that are mis-shelved, improving efficiency in locating items.

🏷️ Token Implementation and Priorities (14:34 - 26:14)

  • Debate on implementation of various tokens (e.g., year publication, edition)

  • Discussion on complexity of implementing item notes

  • Consideration of staff notes and their usefulness

  • Exploration of instance ID and barcode image tokens

📊 Statistical Codes and Workflow (26:15 - 37:15)

  • Discussion on implementing statistical codes for RFID tags

    • Statistical codes can indicate whether an item has an RFID tag, allowing staff to categorize items efficiently during processing.

    • The implementation may involve creating a system to filter and display statistical codes based on their association with items, holdings, or instances.

    • Libraries may have varying requirements for displaying statistical codes, necessitating a flexible approach to accommodate different needs.

  • Exploration of workflow for adding staff notes to requests

  • Consideration of new media requests app and its potential for staff notes

🖨️ Pick Slip Layout and Email Tokens (37:18 - 46:39)

  • Review of National Library of Sweden's pick slip layout

  • Discussion on which tokens are necessary for email notifications

  • Consideration of adding year of publication and edition to email tokens

📬 Notice Workflows and Service Point Model (46:39 - 56:55)

  • Discussion on handling notices for items still needed

  • Consideration of checkout service point token for patron notifications

  • Exploration of extending service point model to include email addresses

  • Brief mention of return slip necessity

Action items

unassigned

  • Think about which tokens are necessary for email notifications and discuss at the next meeting (49:10)

  • Consider if a return slip is needed and discuss at the next meeting (56:19)

 

Tokens Discussed

  • {{item.dateOfPublication}} Year of publication -- at the instance level and not the item level -- needed for monographs held at the instance level

  • {{item.editions}} Edition - is part of the instance record

  • {{ item.physicalDescription }} Physical description

  • {{item.instnaceHrid}} {{item.instnaceHridImage}} Instance HRID - A text and barcode representation of the Instance HRID

  • {{item.notes}} Item Notes -

    • Does this include check-in / out notes.

    • If the enumeration issue is set aside this is not needed..

    • If added simplest would be doing a note dump..

  • {{item.staffNotes}} Staff Notes -

    • This may not be needed because this is kind of against the normal workflow.

    • This may be useful in mediated requests

  • {{item.itemStatCode.---CodeType---}} statistical codes

Patron Notices Only

  • {{ loan.checkoutServicePoint}} Check-out service point -- the service point where the item was checked out.

 

Decisions:

 

Action Items: