52 results found

1. Support Storage Location ID in SRU and Barcode API Queries

   Hi,

   Currently, Alma's BIB SRU interface does not support querying by Storage Location ID. This limits our ability to perform targeted searches for items based on their physical storage location, which is a critical need for institutions managing remote or offsite collections.

   We propose the following enhancements to improve Alma's interoperability and search capabilities:

   1. Extend the BIB SRU “q” parameter to support querying by Storage Location ID.

   2. Introduce an ITEM-level SRU endpoint, similar to the existing BIB SRU, that would support more granular item-level searches including by Storage Location ID.

   3. Alternatively or additionally, add Storage Location ID as a searchable field in the existing Alma API that supports querying by barcode.

   Example Usage:

   Libraries with multiple storage locations, including remote or automated facilities, need an efficient and standardized way to locate and manage items based on their storage location. Having Storage Location ID available in SRU and APIs would allow seamless integration with external inventory systems and automation workflows.

   Impact:

   • Streamlines item management in large and complex storage environments.

   • Enables better automation of inventory and retrieval tasks.

   • Facilitates integration with third-party systems through standards-compliant interfaces.

   We appreciate your consideration and look forward to seeing this functionality included in a future Alma release.

   Thank you,
   Shaul Greenstein
   NLI-Library

   Hi,

   Currently, Alma's BIB SRU interface does not support querying by Storage Location ID. This limits our ability to perform targeted searches for items based on their physical storage location, which is a critical need for institutions managing remote or offsite collections.

   We propose the following enhancements to improve Alma's interoperability and search capabilities:

   1. Extend the BIB SRU “q” parameter to support querying by Storage Location ID.

   2. Introduce an ITEM-level SRU endpoint, similar to the existing BIB SRU, that would support more granular item-level searches including by Storage Location ID.

   3. Alternatively or additionally, add Storage Location ID as a searchable… more

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Metadata Management  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Allow for an authority file to be addressed by different codes in $2 of various BIB fields

   In Alma the authority file, a subject or term stems from, is defined by the content of $2 in various 6XX fields. This code controls the F3 functionality, as well as the linking process and the various jobs like PTC. Each and every authority file is addressed by one specific code.

   In the German speaking countries we use an integrated authority file (GND), which amongst names and subjects, also includes genre/form terms. For historical reasons the genre/form terms in BIB field 655 are marked with the official LoC /MARC Genre/Form Code and Term Source Codes “gnd-content” and “gnd-carrier” in $2, while the terms are, as the code suggests, actually a subset of our integrated authority file “gnd”. The same goes for notated music terms in BIB field 348. These too are a subset of our integrated authority file and are marked by the official LoC /MARC code “gnd-music” in $2.

   Alma currently does not allow to link the above mentioned terms to said authority file, because the content of $2 does not exactly match the code for the authority file, which is “gnd”. This problem could be solved by allowing for different codes in $2 to address one and the same authority file.

   In Alma the authority file, a subject or term stems from, is defined by the content of $2 in various 6XX fields. This code controls the F3 functionality, as well as the linking process and the various jobs like PTC. Each and every authority file is addressed by one specific code.

   In the German speaking countries we use an integrated authority file (GND), which amongst names and subjects, also includes genre/form terms. For historical reasons the genre/form terms in BIB field 655 are marked with the official LoC /MARC Genre/Form Code and Term Source Codes “gnd-content” and “gnd-carrier” in $2,… more

   142 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Metadata Management  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Save certain subfields from being overwritten via F3 and PTC

   When linking names, subjects etc. from authority files in various BIB fields, some cataloguing conventions require giving additional information in certain cases.

   One example for such a requirement, stemming from the German speaking countries, is to add the time and place of an auction when linking to the genre/form term “auction catalogs” in BIB field 655 (see attached screenshot). This additional information is, of course, specific for each BIB record and must not be overwritten or deleted, if at a later point in time either PTC processes said BIB record or a colleague invokes the F3 functionality.

   Since different subfields might be used for various types of additional information, based on the field number and the cataloguing tradition and/or authority file linked to, it would be sensible to allow to define specific subfields to be exempt based on the field number, but also the authority file in use ($2).

   When linking names, subjects etc. from authority files in various BIB fields, some cataloguing conventions require giving additional information in certain cases.

   One example for such a requirement, stemming from the German speaking countries, is to add the time and place of an auction when linking to the genre/form term “auction catalogs” in BIB field 655 (see attached screenshot). This additional information is, of course, specific for each BIB record and must not be overwritten or deleted, if at a later point in time either PTC processes said BIB record or a colleague invokes the F3 functionality.

   Since different subfields… more

   •  

   258 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   9 comments  ·  Metadata Management  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   AdminErez Shabo (Senior Product Owner, Ex Libris) responded

   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?

4. Implement Checks on the Authority Heading Type for Institutions Using ID-based Authority Control

   Currently, when authority linking in Alma is based on ID rather than text, Alma does not check whether the authority heading type in the bibliographic record matches the heading type in the authority record. For example, Alma will link a 600 tag in the bib record for personal names with an authority record whose heading is in tag 110 for corporate names if their ID matches, even though Alma would not offer that option if F3 were pressed.

   We would like Alma to (1) avoid linking in such cases and (2) flag these instances in the authority control task list.

   We ran into this issue in the context of a migration from a non-MARC21 system, from where we still receive authority records that are mapped to MARC21. Initially, a certain sort of authority record was converted into personal name authority records (X00), which was changed later into corporate name authority records (X10). Consequently, we had to clean up instances where the authority heading type in the bib records does not match the heading type of the authority record.

   We had hoped to use the authority control task list to identify those instances where linking would fail due to a mismatch of authority types. However, according to Ex Libris, case 07775618, checking the authority heading type is only available for institutions using text-based authority linking.

   Ex Libris wrote: "The product manager thoroughly reviewed this case as a part of the issue handling and advised the designed behavior. The linking of direct ID authority is not dependent on specific heading types but is instead based on matching the 035 value of the authority with the $0 subfield of the bibliographic field. This means that direct ID authority linking does not involve additional checks for heading types. For example, it will correctly link a 650 field in the bibliography with a 110 field in the authority, as only the match in subfield $0 is considered. Similarly, any changes to the field tag in the linked authority record would not affect the field tag in the linked bibliographic record."

   We believe that adding checks on the authority heading type will benefit also other libraries that use ID-based authority linking.

   Currently, when authority linking in Alma is based on ID rather than text, Alma does not check whether the authority heading type in the bibliographic record matches the heading type in the authority record. For example, Alma will link a 600 tag in the bib record for personal names with an authority record whose heading is in tag 110 for corporate names if their ID matches, even though Alma would not offer that option if F3 were pressed.

   We would like Alma to (1) avoid linking in such cases and (2) flag these instances in the authority control task list.

   … more

   2 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Metadata Management  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Arrow keys now 'stick' in fields in MDE

   When navigating through records in MDE, if you've previously typed anything in a field, you now cannot move out of that field using the arrow keys. It's not entirely consistent and sometimes does let you move out the field, while other times it 'sticks' randomly in fields you haven't edited at all, but in general it is extraordinarily inconvenient.

   I see using the arrow keys to move within a field was previously suggested as a feature, but even within that suggestion, the idea included the stipulation that if the cursor was already at the start/end of a line hitting up/down should then move to the previous/next field.

   When navigating through records in MDE, if you've previously typed anything in a field, you now cannot move out of that field using the arrow keys. It's not entirely consistent and sometimes does let you move out the field, while other times it 'sticks' randomly in fields you haven't edited at all, but in general it is extraordinarily inconvenient.

   I see using the arrow keys to move within a field was previously suggested as a feature, but even within that suggestion, the idea included the stipulation that if the cursor was already at the start/end of a line hitting up/down… more

   2 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Metadata Management  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Add Release Displayed Records in List to Record Actions menu and a keystroke combination

   In the metadata editor, the option to release all displayed records in the record list has only one button which is not accessible by a keystroke. This makes the action less accessible to different users, and is also challenging to document for library staff without including visuals.

   This button, with tooltext "Release displayed records in list," should also appear in the Record Actions menu in the section with other release records options. At minimum, the function should continue the current behavior of releasing the records in the selected records tab. Though it would be useful to have an option to release all records in all records tabs (e.g., MARC21 Bib, Holdings, DC, etc.)

   For accessibility purposes, this function should also have a keystroke shortcut, similar to the split editor having "F6."

   In the metadata editor, the option to release all displayed records in the record list has only one button which is not accessible by a keystroke. This makes the action less accessible to different users, and is also challenging to document for library staff without including visuals.

   This button, with tooltext "Release displayed records in list," should also appear in the Record Actions menu in the section with other release records options. At minimum, the function should continue the current behavior of releasing the records in the selected records tab. Though it would be useful to have an option to… more

   •  

   8 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Metadata Management  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Improvements for the MDEs left pane

   The left pane in the MDE is a very helpful tool for navigation in daily business. With the following improvements it could be even more helpful:
   - Customization of the display of the different databases in all the tabs (records/templates/rules): it would be very helpful if one could select only the databases that are necessary for the daily work for display (example: I have in the record tab 14 different databases of which I only need 4, and one that I need is only accessible through the drop down menu); if a selection is not possible it would be helpful to be able to customize the sorting of the databases (which would help me in the above example to sort up the one in in the drop down)
   - Possibility to select records for release: it would be very helpful if one could select specific records in the list for releasing, because that is how most of us work with the list. Now we have to release the records one by one or all at once, which is not very helpful in daily business.

   The left pane in the MDE is a very helpful tool for navigation in daily business. With the following improvements it could be even more helpful:
   - Customization of the display of the different databases in all the tabs (records/templates/rules): it would be very helpful if one could select only the databases that are necessary for the daily work for display (example: I have in the record tab 14 different databases of which I only need 4, and one that I need is only accessible through the drop down menu); if a selection is not possible it would be helpful… more

   •  

   80 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Metadata Management  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Create a set from records held in the Metadata Editor

   It would be useful to be able to save all of the records that you are working on in the metadata editor as a set to come back to later.

   For example, this would be helpful when working on a bound with where you need to work on several records at the same time and need to add links across the records. At the moment, if this work is not completed and we need to return to it later, we would then need to create an itemised set by searching for and adding each record individually. Instead, it would be useful to have a way of pushing all the records in the MDE into a set at once.

   It would be useful to be able to save all of the records that you are working on in the metadata editor as a set to come back to later.

   For example, this would be helpful when working on a bound with where you need to work on several records at the same time and need to add links across the records. At the moment, if this work is not completed and we need to return to it later, we would then need to create an itemised set by searching for and adding each record individually. Instead, it would be… more

   76 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Metadata Management  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Abilty to edit the authorities from CZ

   In bibliographic records and in Browse Bibliographic Records you can check the information of the linked authority - also CZ authorities. The possibility to take the authority directly in edit mode, as you have the right to edit authorities of the CZ

   118 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  Metadata Management  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Prevent deletion in Community Zone based on field or value in specific field.

    Blocking deletion in Community Zone based on field or value in specific field. Possibility to be definded as a parameter for each CZ vocabulary.

    107 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Metadata Management  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    AdminErez Shabo (Senior Product Owner, Ex Libris) responded

    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?

11. MDE Search Resources mask should be empty

    When opening the Search Resources mask in MDE, the previous search is still in the data mask. For us there is no benefit for this behavior and we would like to have an empty mask and not to clear the mask every time before starting a new search.
    (If other libraries need this opportunity, we would suggest to make the default settings for this mask customizable)

    72 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Metadata Management  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Add option to Quick Cataloging Template for Publish/Don't Publish to OCLC.

    Add a checkbox option to the Quick Cataloging Template for Publish/Don't Publish to OCLC. This would prevent brief records for items created by circulation staff for professor's personal copies from being sent to OCLC and added as new records.

    20 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Metadata Management  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Authority data: first indicator in the bibliographic record

    Now we have many mistakes in our bibliographic records in the settings of the first indicator by connecting with authority data (GND, IdRef, ..). It would be great to have an automatic process, which takes over the first indicator of the authority data to the bibliographic record when you select the authority heading.

    What you have then is the following: First indicator, preferred term and authority identifier are taken over from the authority record to the bibliographic record by using “select” in the index view of the authority record.
    It would be great, if this is implemented for 1XX/6XX/7XX in the bibliographic record.

    Now we have many mistakes in our bibliographic records in the settings of the first indicator by connecting with authority data (GND, IdRef, ..). It would be great to have an automatic process, which takes over the first indicator of the authority data to the bibliographic record when you select the authority heading.

    What you have then is the following: First indicator, preferred term and authority identifier are taken over from the authority record to the bibliographic record by using “select” in the index view of the authority record.
    It would be great, if this is implemented for 1XX/6XX/7XX in… more

    148 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    4 comments  ·  Metadata Management  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    AdminErez Shabo (Senior Product Owner, Ex Libris) responded

    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.

14. Contribute to CZ records : GND Authority File for 1XX/7XX Fields

    A library wants to enhance CZ Bibliographic Records, one is asked by ExLibris to comply to their cataloguing standards (Alma Community Catalog: Cataloging Standards, Policies, Rights, and Responsibilities (exlibrisgroup.com)). On page 7 of those standards it is stated:

    "Since we have a one record policy in the CZ, the issue of languages has been the most challenging part of the solution. The current decision is that the language of the item dictates the language for cataloging. (…) Similarly, the forms of name used as authorized access points in the record should be consistent with the language of cataloging--– LCNAF if 040 $b eng, GND if 040 $b ger, etc."

    Now, if the librarian try to edit a field 100 in a CZ record and press F3, she/he gets only the LCNAMES displayed. She/he cannot access GND, IdRef or any other authority file provided by the CZ.

    Bibliographic data in CZ is becoming increasingly important. For normalization in Primo of bibliographic data in NZ with those in CZ to work, normalization of bibliographic data in CZ with authority data is essential.

    The idea: For bibliographic data in the CZ, F3 can be used to link the fields 1XX/7XX with authority data by using $$2 for the vocabulary

    A library wants to enhance CZ Bibliographic Records, one is asked by ExLibris to comply to their cataloguing standards (Alma Community Catalog: Cataloging Standards, Policies, Rights, and Responsibilities (exlibrisgroup.com)). On page 7 of those standards it is stated:

    "Since we have a one record policy in the CZ, the issue of languages has been the most challenging part of the solution. The current decision is that the language of the item dictates the language for cataloging. (…) Similarly, the forms of name used as authorized access points in the record should be consistent with the language of cataloging--– LCNAF if… more

    21 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Metadata Management  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Duplicate Title Analysis should include match option for Unique OCLC number match method

    The Duplicate Title Analysis job and report currently include matching on only one attribute at a time, rather than on all of the attributes that might be covered by a given match rule. For instance, matching on system number provides only matches between 035$a in different records, while the Unique OCLC number match method covers both 035$a and 035$z. As a result the duplicate title analysis report is missing records that would otherwise be found by an import profile or the match method in the network zone.

    26 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Metadata Management  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Indication rule that checks if subfields are in the same field

    Currently it is not possible to write an indication rule which checks the subfield a and b of a field only when both subfields are in the same field and not in repeated fields of the same record. Both of the following records are treated the same when looking for a subfield a "mercury" and subfield b "venus" in the 690 field:

    Record 1:
    690 $$a mercury $$b venus

    Record 2:
    690 $$a mercury $$b mars
    690 $$a earth $$b venus

    I'd appreciate an option to distinguish if I'm looking for subfields in different fields or in the same field. We need this quite often for our local fields, as our data reflects different classifications via subfield 2.

    Currently it is not possible to write an indication rule which checks the subfield a and b of a field only when both subfields are in the same field and not in repeated fields of the same record. Both of the following records are treated the same when looking for a subfield a "mercury" and subfield b "venus" in the 690 field:

    Record 1:
    690 $$a mercury $$b venus

    Record 2:
    690 $$a mercury $$b mars
    690 $$a earth $$b venus

    I'd appreciate an option to distinguish if I'm looking for subfields in different fields or in the same field.… more

    61 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Metadata Management  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    AdminErez Shabo (Senior Product Owner, Ex Libris) responded

    I recommend applying XSL normalization rules with the required logic and integrating them into the Upon Save normalization process.

17. Alma MDE: Filter by Marc21 field and subfield

    As a cataloger I would like to have the possibility in MDE to filter the Marc21 data by field and subfield
    value to have a better overview over the current part of the data which is to be checked/edited.
    Further I would like to have the possibility to quick access filters which i use often.

    Proposal:
    Add a possibility to filter by field and subfield, e.g. by having an input form for the Marc21
    field (rows filtered by "Begins with {value}") and for the Marc21 subfield (rows filtered by
    "Contains {value}"). The filtering should by done by "AND" condition. (See attached screenshot for an example of how it could look).

    Add a possibility to quick access filters. e.g. by having a list of the latest used filters from
    which the user can choose or by letting the user save the current filter to a list.

    As a cataloger I would like to have the possibility in MDE to filter the Marc21 data by field and subfield
    value to have a better overview over the current part of the data which is to be checked/edited.
    Further I would like to have the possibility to quick access filters which i use often.

    Proposal:
    Add a possibility to filter by field and subfield, e.g. by having an input form for the Marc21
    field (rows filtered by "Begins with {value}") and for the Marc21 subfield (rows filtered by
    "Contains {value}"). The filtering should by done by "AND" condition. (See… more

    •  

    76 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Metadata Management  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. New Metadata Editor templates: editing template v. creating new record

    Previously, when opening a template in the classic Metadata Editor (MDE), a click on the template name from the list of templates would give a list of options, including creating a new record: there was no doubt as to whether you were creating a new record from the template, or editing the template itself.

    However, with the new MDE, clicking on the template name takes you straight into editing the template itself. Creating a new record from the template now requires a right click first to get to the options menu, but this is not at all obvious. It is very easy to think you are creating a new record, when in fact you have just destroyed the template.

    Please can we go back to the options menu appearing from a standard click of the mouse on the template name, and not a right-click. This will prevent much heartache in losing templates.

    A message on the blue banner at the top of the template to make it clearer when you are editing the template itself would also be helpful.

    Previously, when opening a template in the classic Metadata Editor (MDE), a click on the template name from the list of templates would give a list of options, including creating a new record: there was no doubt as to whether you were creating a new record from the template, or editing the template itself.

    However, with the new MDE, clicking on the template name takes you straight into editing the template itself. Creating a new record from the template now requires a right click first to get to the options menu, but this is not at all obvious. It is… more

    66 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    6 comments  ·  Metadata Management  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. The text font ,font size and color of Metadata Editor

    1.When using Metadata Editor, the font size and color of the editing area are not friendly to the editor.

    2.The text in the editing area needs to be enlarged by 150% in the browser to make it convenient for users to work for a long time

    3.The text color or font in the editing area causes the black text to look like gray, which makes it inconvenient to check the bibliography

    4.Can workers modify the Metadata Editor environment to make them comfortable working environment, such as the font size, font type, and font color in the editing area?

    This can help the cataloging librarian to work for a long time without causing the eyes to be worn out too quickly

    1.When using Metadata Editor, the font size and color of the editing area are not friendly to the editor.

    2.The text in the editing area needs to be enlarged by 150% in the browser to make it convenient for users to work for a long time

    3.The text color or font in the editing area causes the black text to look like gray, which makes it inconvenient to check the bibliography

    4.Can workers modify the Metadata Editor environment to make them comfortable working environment, such as the font size, font type, and font color in the editing area?

    This can… more

    • 

    65 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    3 comments  ·  Metadata Management  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Visibility of extension packs and possibility of selecting them one by one for editing and/or deleting

    Extension packs once added to a local MARC-based profile are not visible and cannot be retrieved in any way. It would be much better if each extension pack loaded to a bibliographic profile could be visible to system admnistrators in order to be downloaded from bibliographic profile for purposes of editing and reloading, should the need arise. This feature was part of the tentative future developments proposed by Ex libris back in 2017 (see: internal: 2017 Q1 URM-45100)

    67 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Metadata Management  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating