Skip to content
Innovative Idea Exchange

Settings and activity

4 results found

  1. 99 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)
    Mist Alvaro supported this idea  · 
  2. 29 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)
    Mist Alvaro supported this idea  · 
  3. 52 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)
    Mist Alvaro supported this idea  · 
  4. 57 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)
    An error occurred while saving the comment
    Mist Alvaro commented  · 

    Thank you for submitting this idea! This is the number one issue preventing my catalogers from using Leap for regular cataloging. We frequently copy and paste full MARC fields from other Polaris records or from .txt documents we maintain with frequently-added fields or groups of fields (especially for cataloging AV, notes required only in local standards, or adding notes preferred by our consortial partners). The additional time and effort required to hand-key each field is a serious hardship for the team. Hand-keying the fields also increases the likelihood of natural human error.

    Mist Alvaro supported this idea  ·