Skip to content
Idea Exchange

Settings and activity

2 results found

  1. 36 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Paul Lightcap supported this idea  · 
  2. 80 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Paul Lightcap supported this idea  · 
    An error occurred while saving the comment
    Paul Lightcap commented  · 

    +1 for a MARC-based method which allows custom mapping that includes a local field/non-standard field which we can protect to prevent change/overlay, esp. for those using any record updates service to continually enhance their catalog records. A bit skeptical of a TOM override non-MARC field (essentially similar to what Sierra uses) since this requires a means to export into MARC as well as import in a way that can map through. Same worry for an item material type approach as this could fail if a library has slightly odd itemization practices, (e.g., let's say a book club kit with items for every book in the kit coded as books as well as an item with a kit type for the bag/kit proper). And, finally, a plug for ensuring however this is done can be successfully surfaced to any discovery product.