Skip to content

Anna Ransmayr

My feedback

8 results found

  1. 129 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    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
    Anna Ransmayr commented  · 

    it would be helpful to have a custom set of frequently used characters

    Anna Ransmayr supported this idea  · 
  2. 145 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Anna Ransmayr supported this idea  · 
  3. 259 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Hello everyone, for those who raised comments about the correction of 830 $v, could you please provide a detailed, step-by-step explanation of the scenario in which this subfield gets overwritten?

    Anna Ransmayr supported this idea  · 
  4. 195 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Anna Ransmayr supported this idea  · 
  5. 107 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    As you all know, the Community Zone content is shared among all Alma customers, each with different requirements. Therefore, I’m not sure this request would be acceptable to the wider Alma community. That said, if there were a consensus on a closed list of fields that CZ bibliographic records should be restricted from deleting per MARC profile, this capability already exists and is managed by the Ex Libris Content Operations team. Unfortunately, this is not available for authorities. Do you think such a consensus could be reached?

    Anna Ransmayr supported this idea  · 
  6. 118 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Anna Ransmayr supported this idea  · 
  7. 151 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    I wonder if this request takes into account that certain fields in the 1XX/6XX/7XX have different first indicator definitions in the MARC21 standard for Bibliographic fields compared to their corresponding Authority fields. In such cases, copying the first indicator from the Authority to the Bibliographic heading would result in incorrect data. Is the reqeust is about Names only? Hans, I would recommend consulting with AAFG group for a detailed spec where this requested behavior is valid to which fields.

    Anna Ransmayr supported this idea  · 
  8. 273 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Dear colleagues,

    Thank you for raising this idea.

    This was part of the CERV cycle in 2025, but did not make it to the final list.

    During the analysis, 3 possible approaches were discussed, each has a different estimation and effort:

    Option 1: New dedicated process type

    • It will be possible to mark specific items as "unavailable", similarly to the way it is possible to mark them as "missing"
    • Items marked as "unavailable" will be considered as "not in place"
    • The new "unavailable" option will appear as a possible process type in all the places where there is a list of process types, including configuration options such as Fulfillment Unit Rules

    Option 2: Mark a location as "unavailable"

    • It will be possible to mark a location as "unavailable"
    • All items in this location will be considered as "not in place"
    • The difference from option 1 is that when an item…
    Anna Ransmayr supported this idea  · 

Feedback and Knowledge Base