Page tree
Skip to end of metadata
Go to start of metadata

Date

Attendees



Discussion Items

TimeItemWhoDescriptionGoals/Info
2minAdministrivia Andrea Loigman
15minImplementation NewsBrooks Travis and Anya ArnoldUpdate from MSU
30minUsersUser fields and RA needsUpdated user fields list


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














Notes 

  1. Implementation News:
    1. MSU went live on Monday with circulation
    2. ran into a few bugs
    3. regarding service points and notices - hot fix on the way
    4. 101st record will not be loaded
    5. migration of active loans via check-out-by-barcode-APIs
    6. scheduled notices were created via script
    7. fees/fines were not migrated
    8. Darcy wonders if, something simliar to the loans notices would be needed for the request notices


2. User Management discussion:

a. Maura Byrne and Patty Wanninger from User Management shared the User Fields spreadsheet: https://docs.google.com/spreadsheets/d/1F2vVsiNJhms7dqZbjSE6mMJ58WT1miBbo254i0QkbUc/edit?pli=1#gid=0

key to color codes:

blue - supplied by system. already present
red - repeatable
green - no jira tickets yet
purple - have jira tickets

b. Patty Wanninger and Erin Nettifee discussed User Management and the issues of custom fields as a token in notices and custom fields in the LDP. There are jiras for these.

c. Preferred pronouns with prominent placement in the user record should be a separate feature to be ranked.

d. Custom fields in the user record with a controlled vocabulary? Yes.