Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Functional Area

Product Owner

Planned Release (if known)

Decision Reached

Comments

RequestsQ4
  1. "Effective call number string", since block has a specific meaning in circulation
  2. Yes rename "Effective location"
  3. No need for column as long as data is in exports and on detail screen
  4. N/A
  5. Okay

SMEs also requested that we move the Effective location down one row and have it to the left of the Effective call number string













Notes

Announcements:
Meetings in November: No meeting Thanksgiving Day, November 28; we will meet on Monday, November 25.
Reminder: Fill out User Record Card Sort. Due Friday 11/8
Send Cheryl test scenarios for calculating due times for 24-hour+ library hours
Link to WOLFcon in College Station (January 22-24): https://openlibraryfoundation.org/about/wolfcon/. There is a call for participation: FOLIO Plenary suggestionsFOLIO meeting requests.

(1) Missing items, withdrawn items (Emma Boettcher)

Item missing and cannot be checked out; we need option to check this out;
Can we have a button on the modal, proceed with checkout? Yes.
Withdrawn? This doesn’t necessarily mean that it is suppressed.
Same option available? Make a decision pop-up here as well.
If we did check it out, would it show up in a report? An override report?
[LDP? Library data platform]

(2) Effective call number block on request record (Cate Boerema)

Create request
Call number block: prefix + effective call number + suffix + volume + enumeration + chronology + effective copy
Okay to call it effective call number block?
Let’s use the word string instead of block.
Shelving location: rename to effective location? Yes.
We do not have call number in the request search results. Do we need it here?
No, we don’t need to add it here.
For the export, the call number components will be in their own columns + call number sort code.
Heads-up: current thinking that effective call number spring will be assembled by pages that display it rather than storing it somewhere.
Request page: Can the shelving location and call number be located adjacent to one another?

(3) Check out and check in notes (Emma Boettcher)

Item record in inventory: ability to add notes and assign; are reusable notes of interest?
Notes need to stay within the app; we don’t need to see all types of notes in all apps.
This is kind of a nice to have. How would we use this?

(4) Discuss documentation needs (Erin Nettifee & Andrea Loigman)

Confluence: section labeled FOLIO app information tips & tricks;
Click on Check in to see template.
How do we want to move forward with this?
Next steps? Use Slack to communicate?
We might volunteer people on our staff; they will need a confluence account.