2024-11-20 Meeting notes

5 min

Note taker

25 min

Practices for loading users

5C uses automated scripts each night. Each of the 5 members sends their own file to the central server; gets processed by daily load script. [Note, UMass does incremental loads, have a script which identifies new / changed records. Full loads ideally done once per year, in practice somewhat more often. The other 4 institutions do full loads each night.] Current script used is based on old EBSCO script, but work is being done to replace this with a simpler & easier to maintain script.

Michigan State gets a nightly feed from central University. Library IT works with Campus IT. Community borrowers are added manually. Community borrowers use the user barcode for External system ID – this ensures that community borrower accounts do not get over-written by the nightly feed. As needed, records are manually deleted.

U Chicago gets a feed from Campus IT. A scheduled process using direct SQL (bypassing mod-user-import, which has been found problematic) gets the feed into the database. records are kept forever, as people sometimes come back (student graduates, then comes back as staff member, etc.).

30 min

Feature prioritization

Questions for discussion (cribbed from Product Council 11-07 meeting notes):

• Do you already have a mechanism for your SIG for collecting priorities?

Ans: Amelia has created a Gap list, similar to the one the RA SIG has. Can use it for prioritization. Discuss regularly in meetings, decide which features are most important.

• Are priorities represented in Jira or through another means?

• Do you keep a topic backlog/topic page that you can draw on to develop priorities?

Gap list on Users SIG page.

• Are there dormant features that should be revisited?

• What barriers do you have in collecting priorities?

• What do you think would be a good time frame for collecting priorities?

• What can the PC do to help your SIG with this work?