| Time | Item | Who | Notes |
|---|
| 5min | Housekeeping | | |
| 15min | Location Demo | | Demo of location settings functionality Cate demo'd creation/editing of Institutions, Campuses, Libraries and Locations in Settings - Discussion points:
- Locations (née Parking)
- name/value pairs, not controlled vocabularies, so staff can add any they want; type ahead can let you know what values are currently in use
- adding more info to the locations list to make it clearer what Institution/Campus/Library each belongs to has been discussed
- can be used in loan rules
- Name and Code must be unique
- Codes
- are free text, not limited to the demo'd format (3 characters separated by slashes)
- not auto-generated right now but it's been discussed
- codes are optional (current bug makes them required but that isn't the intended functionality)
- Can't delete anything that is in use
- Possibilities for making the mechanics of selecting Institution, Campus, Library at each level less repetitive
- retain previous choices
- set defaults
- Permanent and temporary locations in holdings and items
- model is being updated
- can assign temporary locations under the current model, Cate demo'd type-ahead
|
| 15min | Service Points Demo | | Demo of Service Points - Current functionality includes shelving lag time, is it a pickup locations, etc
- Ability to assign locations is coming
- How will printers be set
- Different printers may be installed and be used for different things (e.g. receipts go to receipt printer, notices go to network printer, etc)
- Using OS default printer & print dialog?
- setting the printers in the Service point config
- setting it some other way
- Setting service points for the session
- set at login?
- ability to change service points without logging out/back in is desired
- change service point temporarily in the context of the current app, like in checkin
- change service point permanently for the rest of the session across all apps, for all activity going forward
- logout/login is an option for changing service points
|
| 20min | Anonymization | | Anonymizing closed loans and closed fines/fees We need to decide what data should be anonymized and under what circumstances Three use cases: - Closed loan with no associated fines/fees
- yes anonymize
- keep user group, user status, user division/department, other relevant demographic data?
- do not keep expiration date, date enrolled, as this may enable identification of the user involved in the transacation
- if statistical codes are going to exist, that would be something to keep
- state institutions don't seem to have different requirements in this area (e.g. users' state of residence)
- Closed loan with an open fines/fees
- don't anonymize anything while there are open fees/fines associated with the loan
- Closed loan with closed fines/fees
- Anonymize the loan after a certain amount of time
- age of transaction should able to specified by the institution
- the process that anonymizes should be both manually-runnable and cron-able
- The fines/fees may need to be retained even if anonymized for accounting reasons
TO BE CONTINUED ON THURSDAY |