Versions Compared

Key

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

Proposed in the Aug. 20, 2020 MM SIG meeting

Goals: document use cases for productivity tracking statistics; investigate & develop short-term solutions for productivity tracking in FOLIO; define a long-term solution for productivity tracking in FOLIO

Membership

Name / contactFOLIO area(s)Institution / role
Metadata ManagementCornell / Assistant Director, Metadata Production

Jacquie Samples Jacquie Samples

Metadata ManagementDuke / Head, Metadata & Discovery Strategy Department
Felicia Piscitelli
TAMU
Metadata Management, some work with Resource Management locallyUChicago / Metadata & Digital Resources Librarian
Julia Corrice
Cornell
Natalie Sommerville Natalie Sommerville
Duke / Interim Head, Resource Description Department

Slack channel: #folio-productivity-stats

Some examples and discussion (slides)

Google drive documents

Common understanding of what productivity statistics are and what we need, make sure not to exclude needs outside metadata/cataloging

Which apps are involved?

Notes (20 November 2020):

  • Element suggestions
  • Demo of Duke's cataloging using aleph and the data warehouse
  • assuming ISO date format in FOLIO
  • how will be attach an ID for batch loads such as from GOBI or OCLC?
  • can the proposed element get stamped automatically with the date-time-stamp as well as an API or batch process that would probably need a permission or token to work anyway
  • no meeting in december, work on vision statement and use cases, and talk about contingencies in January

Notes (6 November 2020):

  • Looking at the Element Codes document here.
  • ref: CAT field in ALEPH (tracking historical changes)
  • How to deal with 'change tracker'
  • want to see which line was changed (say, a note was added or edited)
  • tracking MARC updates generally with a code that something was changed, not necessarily needing to know what, but is tracked in the same way a new cataloging was done
  • ref: tags as a helper app
  • Do we need a statistics app?
    • is this related to a need for a reporting app?
    • Could we use the action menu for this?
    • we hope to propose an ideal product for all conceivable permutations for what we really want
    • how might we use macro-express?
    • How to use keyboard shortcuts?
      • ideally: we would be able to use macros, use manual entry, and some obvious places when literals are needed
    • We need a VISION document! (Laura Daniels (Wright) 

Notes (5 Oct 2020)

  • next meeting (oct 23, 2020)
  • Cornell (LW) on the use of the 948 (indicators and subfields) for stats
  • Do we not have a 'item created' date in the item record?  Yes, in Admin data accordion of the item.
  • Supposed to have 'date created'
  • There are notes in the item that can be checked for 'staff only'
  • need to better understand the Library Data Platform from reporting SIG (uses SQL)
  • We need data like 'who' and maybe in what department or unit
  • action: need to understand acquisitions workflows to better understand receiving (with orders already made and perhaps when receiving might involve when an order had NOT previously been added)
  • Receiving admin metadata does not have notes either as well as no viewable admin info
  • How to count RUSH cataloging?
  • We need FOLIO to accommodate our need for local productivity data
  • How to distinguish for batch processes
  • keep in mind the API integrations for MARCEdit

Notes (23 October 2020):

  • How to use macros in OCLC to make records get to FOLIO, getting statistics from OCLC to FOLIO via export adnd then import (but no gateway is currently in development) / generating a daily file in OCLC and then load in data import...?
  • While in the instance record, there is not a place to edit and put cataloging codes
  • Can item notes for cataloging (for physical holdings)
  • But we need instance or holdings for serials or eHoldings
  • We are PROBABLY moving toward proposing a new element that should include all the things we might need (universally and locally)
    • we need a place to enter a place for the userID or a batch ID
    • See the 'Elements needed' section below
    • mapping some MARC tag to Instance and then making the instance records editable <the same element being proposed below> (but this mapping could be locally determined)
    • What about how to use ARL stats, etc?
    • LW will create a google doc for us to put together some needs for the element mentioned below

Notes (18 Sept 2020):

  • For receiving, make sure to tick the box left of caption to receive it.
  • Will need to know the number of items received in a period
  • Receiving is pulling title information from inventory
  • 'Note' is required in fast-add in Inventory