...
Item | Desired Outcome | Time | Who | Notes | Decisions | Actions | |||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | STANDING ITEM: review Task Report | any blockers on tasks? | 5 | all | |||||||
| 2 | STANDING ITEM: Any AskSILS / SILS News or other tool requests? | Are there blockers for anything that’s come in? Are there any we need to talk about? | 5 | CN | |||||||
| 3 | Clean up batch process | Inform people? hash out specifics with ticket contact (Mallory) consult/approve (ask if objections) with RS OST inform: ILL CKG + any other UC ILL lists | JF | batch process that cleans up brokered requests; BUT it skipped the non-supply requests! consideration: make confl. page for doc & release notes |
| ||||||
| 4 | SILS & HathiTrust Discovery | Paul would like to know “information about the representation and discovery of HT materials in the SILS”. It doesn’t look like this has been discussed much yet within the SILS structure? | GSL | Davis might be using an API to pull in data (https://developers.exlibrisgroup.com/appcenter/hathitrust-availability/ ???) Bring it up again on Monday to talk with Caitlin. Probably needs to be discussed at all chairs. | 4 | tools review (from the parking lot) | how’s the meeting notes/agenda format going? | team | it’s fine
| ||
| 5 | GitHub | Discuss initial proposal and next steps | GSL | Organization name: ucsils Contact email: asksils or sils-sysops? Belongs to: California Digital Library Everyone in SILS Op gets added as admin? Yes: CN, AMR, JF, GSL Add to Access Instructions Anywhere else? Access rule: non-sils - tickets comes from SILS rep. Use Discovery as a pilot then distribute more widely. Team naming convention: Do we need to call out when OST? Can we get by with simplified naming (i.e. “Discovery”)? We will use name but not include OST, etc. Do we need tutorial, if so, what level? Point to GitHub tutorials. | |||||||
| 6 | tools review (sils ops space opening?) (team) | Decide whether we want to open or not | Team | keep this item for | |||||||
| 7 | Wrap up | Review actions and decisions | 5 | ||||||||
| 78 | Parking Lot | Capture important topics for future discussion | update for NZ approved users; What’s the status on this? Do we need an action item? (caitlin?) Collections process automation; Let’s wait until the needs assessment of CDL Shared Collections re:SILS has been started. (Joe/Gem)tools review (sils ops space opening?) (team) should silsops sign up for https://status.crossref.org/ updates? (alison) enable public (anonymous) view of user profiles in confluence? (Alison) add ‘term’ (years member will serve in sils gov; eg “Alison Ray, 2022-2026”) to https://libraries.universityofcalifornia.edu/sils/rosters page | 8update for NZ approved users; What’s the status on this? Do we need an action item? (caitlin?) | |||||||
| 9 | Total | x/x |