Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Attendees

 

Discussion items

ItemWhoNotes
Minute TakerEric Hartnett 
Selection Task Group draft charge: https://docs.google.com/document/d/1QJ_ysHijoQESdvD6eyzTpihm8aSW0CBayIykmfdFP6U/editKristin MartinKristin discussed it with the Product Council and they said it was up to the RM SIG to proceed as it sees fit. The Selection Task Group will proceed as a small, separate group reporting to the RM SIG. The Group will meet with Filip to provide assistance in the development of the selection support app. A list of members is needed by the end of next week (Friday, March 17). Kim will talk with the Collection Strategist at MIT to see if they're interested in participating. Kristin will check with Dan Wang at Lehigh. It was suggested that it would be good to get someone who works somewhere where selection is purely based on educational needs for curriculum rather than research. A convener for the group is needed.
Review outstanding tasks/smaller sub groupsall
  • Order/Material Types - Virginia created a document (https://docs.google.com/document/d/18nnVgPOZgOoQCn3XdHG5aQdbWN3oh-wap9uQMzW13G0/edit) detailing differences between order and material types which led to a discussion on the topic.
      • Question: Do we build a way of tagging materials so that libraries can create their own categories?
      • Order type can dictate functionality vs. material type which is used more for reporting purposes
      • One-time - The basics are: Did we pay for it? (What this means varies by library - Ex. paid=processed or paid=payment sent) Did we get (all of) it? (this can also vary) If yes to both, automatically close the order.
          • There may be cases where it's good to not require a receipt.
          • Order status = open/closed/cancelled by library/cancelled by vendor/received (all/part/access available)
      • Question: Would it be good to have a stripped down version of acquisitions for smaller libraries who don't need complicated functionality?
      • Subscription order - The basics: Did we pay for it? Did we receive it? At the end of the cycle, start the process over (it doesn't automatically close).
      • Current systems don't handle packages well.
      • Encumbrance rules should differ between one-time and subscriptions.
      • Question: How should the system handle an order where their may not be a payment for a number of years? Ex. Hosting fee is waived for X years but eventually, we will have to pay an annual fee.
      • The group will revise the document.
  • Customer Relation Management (CRM) - Kristin, Mike, Peter, and Eric had a call to discuss this. Mike will be writing up the notes.
  • Email Integration - Peter and Kristen met and Kristen added a document to the workflows folder which they're continuing to work on and should be able to discuss next week.
  • DDA - Ann Marie has created a document that is in workflows; Kristin will write up U. of Chicago's DDA process
  • Ann Marie reported that she recently attended an EBSCO meeting and was asked about the ERM functionality within FOLIO. Will it track license negotiations/conversations? Will there be management of the workflow - where it's at in the process?

 

Continue discussion of Filip's sketchesFilip Jakobsen Review outstanding tasks/smaller sub groupsallFilip is aiming to have a high level digital prototypes of the RM concepts by April 1.
   

Action items

  •