Versions Compared

Old Version 5

changes.mady.by.user Doreen Herold

Saved on

compared with

New Version Current

changes.mady.by.user Doreen Herold

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
  1. Record type
    1. Moving beyond bib-hldg-item
  2. Item statuses
    1. Formerly known as item status: what should it be called?
      1. May correspond to more than one kind of thing (see NCSU list).
  3. Workflows
    1. Role of workflows vs. item status
      1. Consider creating workflow charts showing item statuses as they move through the workflow.
      2. Curious to hear more about recording history of items, whether it is for changes of item statuses or when an item moves through a workflow.
        1. Do we need the system to retain history?  What system resources will it labor?
  4. Miscellaneous
    1. History of changes
      1. When spec'ing OLE, there seemed to be difficulty recording history of changes to the point that the difficulty outweighed the potential uses.  But I'd like to try and capture use cases for history of changes (not sure what else to call it) to note the usefulness of this feature and whether it is truly something we need.  My vision of it is something similar to Wikipedia, in that you can see the history of changes of a page, what the changes were, who made the changes and when, etc.
      2. Use case: update holdings in an external database (e.g. OCLC)
        1. Output OCLC nos. so we can send them to OCLC to add our holdings symbol on those records so that we and other libraries know what titles we own.  
        2. Query the FOLIO database for what items were cataloged in the most recent week and output OCLC nos. to a file we can send to OCLC.
      3. Use case: output cataloging statistics (to replace manual hashtags, external recordkeeping)
        1. Query the FOLIO database for what items were cataloged in a given timeframe
        2. Breakdown results by location, call number, staff ID, item type