Versions Compared

Version Old Version 82 New Version 83
Changes made by

MSU TechServices

Kay Granskog

Saved on

Key

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

...

TS Council 10-

...

9-19 (

...

AGENDA)

Present: Joshua, Don, Kay, AutumnRanti, DaoLucas, KayEmily, RantiNicole, Lisa S., Lee, Lisa R., Brooke, Don T.Ed

Regrets: Autumn, Tim, Dao, Brooke

Agenda

  • Approve TS Council minutes from 79-1018-19
  • Discuss "what a system "must" do"

    Look at the MCLS RFP for a system, section E.  We are considering using this as a model for content.  What is missing or is different for us when we know our instance will include three separate libraries as opposed to the waffling this RFP was trying to do?

Action items

  •  Action 1
  •  Action 2
  •  Action 3

...

  • Decision 1
  • Decision 2
  • Decision 3

09-18-19

Present: Joshua, Don, Autumn, Dao, Kay, Ranti, Lisa S., Ed, Lisa R., Brooke

Regrets: Don T.

Agenda

  • Approve TS Council minutes from 7-10-19
  • Discuss what a system should do (dealbreakers in bold)
    • web-based, not Java-based
    • post-MARC capabilities
    • quality training and documentation 
    • data management and manipulation capabilities
      • powerful queries
      • record list storage & editing
      • global changes
      • reports & statistics
      • easier MARC record extraction/loading
        • ability to extract entire database in the case of system change
    • catalog management
      • local fields and local coding
        • both in bib records and attached records
        • more fields for back-end codes
      • customize indexing
      • version history for records
    • public facing interface 
      • highly customizable display
      • faceting on numerous record data points
      • API for bento box search
      • mobile capabilities
    • acquisitions functions
      • audit trail
      • multi fund codes
      • receive electronic invoices
    • electronic resources management
      • generate local fields, notes fields, etc.
      • place to store accessibility info
      • indicating LOCKSS/preservation status
    • interface with campus systems
      • student info system?
      • EBS
    • system administration functions
      • more granularity in permissions and access levels
      • secured/restricted access fields to include sensitive information
        • licensing, financial info, etc.
    • authority functions
      • local authority records
    • workflow management
      • methods of routing, tracking, etc., which would help us cut down on paper
      • bibliographer view of budget/fund info
      • patron tracking of statuses, requests, etc.
        • related to Get It function
      • staff notifications related to records, resources, workflows
    • robust ergonomic & usability functions
      • keystrokes for frequent commands
      • ease of selection, editing, deleting, copy/pasting, etc.
      • change font size
    • ability to share records with or provide access to external sites
      • Internet Archive, etc.


07-10-19 TS Council

Present: Joshua, Tim, Dao, Don, Autumn, Nicole, Lisa S., Ed, Ranti, Lisa R

...