Skip to end of banner
Go to start of banner

2020-05-18 Resource Access Meeting Notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

Date

Attendees


Discussion Items

TimeItemWhoDescriptionGoals/Info
2minAdministrivia Andrea Loigman
20minNoticesTokens for fee/fine noticesQuestions regarding which item and/or loan tokens should be available and separating charge from action tokens.
20minAnonymizationEmma BoettcherAnonymization of claimed returned itemsDecide if this is a separate setting to other anonymization settings
15minDue datesAnyaNot naming/renaming the fixed due date schedule data entry table


Meeting Outcomes

Functional Area

Product Owner

Planned Release (if known)

Decision Reached

Reasoning

Link to supporting materials

Comments

e.g. loans, fees/finesNamee.g. Q4 2018, Q1 2019Clearly stated decision
  • Because...
  • Because...
e.g. mock-up, JIRA issue
LoansEmma BoettcherQ2 2020Don't automatically put in link to loan in user record note for a claimed returned item unless there is a tenant-level way to configure those links not being added GDPR compliance








Notes 

Darcy presents suggestion for notice tokens
fee/fine detail page displays more information than fee/fine record, should additional information be also available for fee/fine notices?
can be pulled in via itemID/loanID
does it make sense to offer full set of tokens?

there could be more information on the notice than on the detail page, is this odd?
probably not, because quick access to item record and loan details is possible from the detail page

often title only may not fully identify item to patron, full call number information, enumeration, volume etc (all existing item tokens) should be available for notice tokens

is there a way to state that an overdue fine was caused by someone recalling the item? it should be

fee/fine tokens need to be divided in charges and actions

date and dateTime are both needed
is it possible to break up dateTime into date and time? dateTime is already a token for other processes and should be kept this way

additionalInfo is info field from manual charges, there is not additional info on automated fees at this time

feeAction.amount and feeAction.remainingAmount refers to the latest balance

multiple charge notices won't be available first, but multiple action notices will

multiple actions on a fee can be summarized in one notice or sent separately
if an action notice is not wanted after a waive or transfer, it can always be deselected manually during the transaction


new function to include note on user record that an item was claimed returned - does this need to be anonymized?

This is really about what happens when the loan goes to missing. If it's declared lost, then the anonymization is governed by associated fee/fines.
If loan ID is included in the note, does that help? What about GDPR concerns?

Andrea - more concerned about claim returned and then we found it. That history is important from a customer service perspective.

GDPR concerns, possibility to turn it off? Yes, we would want that, or the ability to anonymize the note, or both.

if the note is done manually, barcode or title could be included instead of loan id

Emma - that seems like the right approach, until the ability to turn it off would be in place.
Andrea - yes, because the loan should eventually have the notice history as well, which is key for when you need this information.

Topics for Thursdays?
Cheryl - I'd still like to explore manual fee/fines and automated overdue notices, since I'm still confused.
Erin - you're not the only one who is still confused.
Anya - I'll ping Darcy and Holly to discuss whether that could be covered on Thursday.








cision: 

  • No labels