Thomas Trutt, member of the Prioritization Process Working Group, presented on the new proposed prioritization model → Presentation | Flow Chart:
Community ranking + PO ranking + SIG ranking, each rankings in one of the groups would be added, so that we end up with:
Institutional ranking: One of R1-R4
PO ranking: Will continue to do the PO ranking using a number value, e.g. 150 - 0. Charlotte explained that above 100 is highly ranked feature (when it comes to Inventory. The POs do use these number ranks a little differently.
SIG ranking: One of R1-R4
Qs:
Does each individual get a vote, or each institution? → still in discussion
What about consortia? → Jacquie Samples could you please add your answer here?
what is the definition of "new request” what does that cover? → Gap in the list of features identified – covers new features and updates to existing features, e.g. change to existing functionality
The focus is on epic and feature level
Felix suggest to circle back to this proposal in a couple of weeks
MM SIG liaison to PC. Call for a volunteer.
MM SIG membership. SIG charge document:
Talk about minimal criteria for MM SIG membership. Confluence Wiki account, regular meeting attendance
Configuration is detailed explained in the README.md file
Qs:
The instance status of "set" is applied by staff
Does it work with only 1 OCLC account
uChicago has a query to do this update
Do you have a check that the OCLC number is not on another record that is not withdrawn
issues with multiple OCLLs in the records. After single record import there will be multiple OCLC numbers in the record with and without the prefix. Lehigh is only taking the first one into account
Lehigh is stripping the leading part of the OCLC number, and only search on the digits
Search on OCLC number is a known issue, and in Inventory it will be improved with Morning Glory
Instance status ...
Could you have the tool to pull records changed in the last 3 days? So there's an overlap so if it fails on day it would catch that record the next two days. Lisa answered: I'm pretty sure the answer is "yes". And Maccabee Levine agreed: You would just manually run the script for each day, passing in the date. See more in the paragraph Instructions in the READme file.
The OCLC API will tell if you are giving it an old OCLC number. Do you report that out or doing anything else with it?
When you set your holdings, what does that mean? This is OCLC Connexion language, and means: Lehigh has send into OCLC, and OCLC has recorded that Lehigh has this instance.
Felix added that the German libraries do the same for international ILL via WorldCat but don't have to send holding by ourselfs as this is taken care by the Union Catalog provider
Idea of community created video documentation brought to App Interaction from Acquisitions SIG
Specifically focused on cross-app workflows
Current documentation group is a working group and focused on written documentation
This sort of work is outside their scope
Is a Documentation SIG needed? (a broader discussion point, but feedback welcomed) - yes, it's a permanent task, and all agreed in that a new Documentation SIG would be great
Short, targeted videos would be preferable to longer ones:
easier to create
easier to update if functionality changes
multiple shorter videos can be grouped together to represent more complex workflows
These are more appropriate for the wiki than as formal documentation (lower barrier to contribution)
There is value to sharing existing local documentation, no matter the language or local configuration
Jacquie like the idea of having metadata to describe the flower release better than an expiration date, since something might still flow the same way through releases.
Could there be some type of training on how to make a video? A couple of times I have thought about making a video, but I don't know how.