45 results found

1. Linked Data Enrichment Moves $e Relator Subfields to Incorrect Positions When Saving Authorities with F3

   When saving a name authority record in Alma using the F3 function, the Linked Data Enrichment process is causing the $e relator subfield to move to an incorrect position within the field. Instead of maintaining the expected order (e.g., $a, $e, $1), the $e subfield is often placed at the end or in another unexpected location after $0/$1 subfields are added. This disrupts the intended structure of the authority field and creates extra manual work for cataloguers.

   Attempts to correct the placement by copying and pasting the $e subfield do not work as expected—Alma consistently pastes it at the end of the field, regardless of cursor position. This issue only occurs after Linked Data Enrichment and does not affect other fields or occur before enrichment.

   Ex Libris support has indicated that this is currently by design, as part of the Preferred Term Correction (PTC) process.

   Impact:
   • Authority records are not formatted as cataloguers expect, leading to confusion and extra manual editing.
   • The copy-paste function does not work reliably for $e subfields after enrichment.
   • The current behaviour reduces efficiency and increases the risk of errors in authority data.

   Request:
   Please review and enhance the Linked Data Enrichment and F3 saving process so that $e relator subfields retain their correct position (immediately after $a) when new $0/$1 subfields are added. Additionally, ensure that copy-pasting subfields works as expected in all scenarios. This change would improve cataloguing accuracy and workflow efficiency.

   When saving a name authority record in Alma using the F3 function, the Linked Data Enrichment process is causing the $e relator subfield to move to an incorrect position within the field. Instead of maintaining the expected order (e.g., $a, $e, $1), the $e subfield is often placed at the end or in another unexpected location after $0/$1 subfields are added. This disrupts the intended structure of the authority field and creates extra manual work for cataloguers.

   Attempts to correct the placement by copying and pasting the $e subfield do not work as expected—Alma consistently pastes it at the end… more

   48 votes

   Vote 0 votes 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 a NR to run with the PTC job

   TL;DR:
   We would like to have the ability to run a normalization rule whenever the PTC modifies a record.

   Background:
   In November 2024 Ex-Libris added a new functionality to the PTC job:
   MARC 21 Preferred Term Correction Can Flip Headings with Cross-Reference in Different Field
   https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2024/Alma_2024_Release_Notes?mon=202411

   Problem:
   The PTC job only changes the first indicator correctly when the PTC job changes a field into 630.
   in all other cases, the existing indicators remain.
   We opened a case and spoke directly with Ex-Libris, but were told that the PTC job runs as intended, and that not handling the indicators is not a bug.
   I understand that other institutions have different reasons for having a NR run whenever the PTC changes a record.

   Request:
   We would like to have the option to add a normalization task to the PTC in the configuration menu, that way we will be able to fix problems that arise from this job.

   TL;DR:
   We would like to have the ability to run a normalization rule whenever the PTC modifies a record.

   Background:
   In November 2024 Ex-Libris added a new functionality to the PTC job:
   MARC 21 Preferred Term Correction Can Flip Headings with Cross-Reference in Different Field
   https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2024/Alma_2024_Release_Notes?mon=202411

   Problem:
   The PTC job only changes the first indicator correctly when the PTC job changes a field into 630.
   in all other cases, the existing indicators remain.
   We opened a case and spoke directly with Ex-Libris, but were told that the PTC job runs as intended, and that not handling the indicators is not… more

   45 votes

   Vote 0 votes 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

3. Add an API endpoint to rerun an import profile job that failed

   We are monthly running an automated import profile to import electronic resources. Almost every time the import profile job finishes with status Completed with Errors and needs to be manually "rerun". This is a documented behavior: https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/040Resource_Management/060Record_Import/080Monitor_and_View_Import_Jobs#Rerun.

   We would like to have an API endpoint through which we can simply rerun the import profile job that have failed due to the error "Failed in Commit after calling NZ" in some of it's files. This would allow to have the whole import process truly automated and without the need to manually intervene every time it runs.

   30 votes

   Vote 0 votes 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

4. 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 0 votes 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

5. MDE Virtual Keyboard – Add Welsh as a separate language option.

   The new Virtual Keyboard for Inserting Special Characters and Diacritics in the Metadata Editor has many different language options. However Welsh is not amongst them.

   Can Welsh be added as a separate language.

   22 votes

   Vote 0 votes 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

6. 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 0 votes 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

7. Expanding Unicode Tool range in Metadata Editor

   The new Insert Unicode Characters tool in the Metadata Editor should be expanded to include the 0300-036F range of characters. This range includes several diacritics that are commonly used by catalogers, including the ligature (0361), candrabindu (0310), and combining diaeresis below (0324).

   21 votes

   Vote 0 votes 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

8. 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 0 votes 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. Reloading several records from the union catalog at once

   I would like to update several records from the union catalog at once, for example all the records within an itemized set. So far, this is only possible for individual records in the MDE ("Reload record from central catalog"), which is rather exhausting. It would be much easier if there was a button saying "reload records" by which you can push all checked items to the MDE and simultaneously reload the records from central catalog.

   In this way, we could easily and quickly update bibliographic records from the "Failed to update delete" event in Analytics. Another use case would be changes to periodical records that would otherwise not appear in the records of the related volumes.

   I would like to update several records from the union catalog at once, for example all the records within an itemized set. So far, this is only possible for individual records in the MDE ("Reload record from central catalog"), which is rather exhausting. It would be much easier if there was a button saying "reload records" by which you can push all checked items to the MDE and simultaneously reload the records from central catalog.

   In this way, we could easily and quickly update bibliographic records from the "Failed to update delete" event in Analytics. Another use case would be… more

   15 votes

   Vote 0 votes 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

10. ensure that when 'po_line_description_update_upon_bib_change' enabled, subfield A does not get overwritten by subfield L in 022

    Sharing description from our Cataloger, CH:

    We believe the following describes a defect.

    Support indicates it is an enhancement request and suggests we propose on Idea Exchange.

    Background:
    1) We turned on the ‘polinedescriptionupdateuponbibchange’ enhancement in the sandbox.
    2) The enhancement overwrote the $$l instead of pulling in the $$a from 022 – this behavior describes a defect
    None of the following 3 options allow us to properly use the ‘polinedescriptionupdateuponbibchange’ enhancement:
    1. Ideally, we want to enable the ‘polinedescriptionupdateuponbibchange’ function to auto-sync changes in the bib record to the POL bib description. This saves our Cataloging team from an additional step to manually edit the POL record.
    However, we are unable to use this Alma function at all because when we do, it auto-reverts the POL bib desc ISSN from $$a to $$l.

    1. Less ideal, we use the Reload Bib Data button to sync changes in the POL bib desc to match the bib record (a more manual approach—it means our Cataloging team needs to click the ‘Reload Bib Data’ button).
       However, again, we are unable to use this function because this option also changes the ISSN from $$a to $$l. Another Alma feature we are not able to use.

    2. Least ideal – Cataloging team manually updates every field in POL bib desc to match bib record updates. This is the most work for the Cataloging team, as it does not allow them to use the 2 previous enhancements in Alma to make their jobs easier. With this feature enabled, if the Cataloging team manually types anything into the ISSN field in the POL bib description, the system will auto-revert to $$l and override manual changes. Once the Cataloging team makes any change to the ISSN field in the POL bib description, they CANNOT revert it back to $$a. It's as though they lost control of that field entirely. This feels to our organization to be a major glitch - why doesn't the system allow the user to make and save a MANUAL change to a field?

    Sharing description from our Cataloger, CH:

    We believe the following describes a defect.

    Support indicates it is an enhancement request and suggests we propose on Idea Exchange.

    Background:
    1) We turned on the ‘polinedescriptionupdateuponbibchange’ enhancement in the sandbox.
    2) The enhancement overwrote the $$l instead of pulling in the $$a from 022 – this behavior describes a defect
    None of the following 3 options allow us to properly use the ‘polinedescriptionupdateuponbibchange’ enhancement:
    1. Ideally, we want to enable the ‘polinedescriptionupdateuponbibchange’ function to… more

    10 votes

    Vote 0 votes 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

11. 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 0 votes 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. Display personal metadata editor history of opened/edited records

    Currently in Alma's All Titles search you can see a list of records you have previous looked at, but it would be helpful in the metadata editor if you had a list of records that you have opened recently. Even a list of 5-10 would helpful.

    8 votes

    Vote 0 votes 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

13. NACSIS-CAT Could App: Enable English output in NOTE field when converting 336/337/338 fields for records with 040 $$b eng

    Currently, when converting 336/337/338 fields to a NOTE field in Alma --> NACSIS-CAT mappings, the output uses Japanese vocabulary regardless of the cataloging language. For records with 040 $$b eng, we request that the NOTE field be generated using English vocabulary to match the cataloging language.

    Example:

    Expected output for 040 $$b eng:
    336 $$a text $$2 ncrcontent
    337 $$a unmediated $$2 ncrmedia
    338 $$a volume $$2 ncrcarrier
    → NOTE: Content Type: text (ncrcontent), Media Type: unmediated (ncrmedia), Carrier Type: volume (ncrcarrier)

    Current output:
    → NOTE: 表現種別: text (ncrcontent), 機器種別: unmediated (ncrmedia), キャリア種別: volume (ncrcarrier)

    This enhancement would ensure consistency between cataloging language and output vocabulary, improving metadata quality and usability for English-language records.

    Currently, when converting 336/337/338 fields to a NOTE field in Alma --> NACSIS-CAT mappings, the output uses Japanese vocabulary regardless of the cataloging language. For records with 040 $$b eng, we request that the NOTE field be generated using English vocabulary to match the cataloging language.

    Example:

    Expected output for 040 $$b eng:
    336 $$a text $$2 ncrcontent
    337 $$a unmediated $$2 ncrmedia
    338 $$a volume $$2 ncrcarrier
    → NOTE: Content Type: text (ncrcontent), Media Type: unmediated (ncrmedia), Carrier Type: volume (ncrcarrier)

    Current output:
    → NOTE: 表現種別: text (ncrcontent), 機器種別: unmediated (ncrmedia), キャリア種別: volume (ncrcarrier)

    This enhancement would ensure consistency… more

    7 votes

    Vote 0 votes 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

14. Quick Links and Keyboard Shortcuts in the Metadata Editor for Enhance the Record Normalization Processes

    As a cataloger, I want to create quick links and keyboard shortcuts for normalization processes in the metadata editor, instead of selecting them via "Enhance the record", so that I can work more efficiently.

    4 votes

    Vote 0 votes 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

15. Intelex Past Masters collection needs better metadata

    The Intelex Past Masters

    In Alma in the electronic collections I can find the metadata have a structure that follows the structure of the database and not a normal catalogue standard.

    A title looks like this: 'Collected works of Ludwig Wittgenstein. On certainty' and there are very few other information, eg. the field for ISBN and the writer has not been filled out.

    When I search in Primo, I have to do a very specific search to find the title, since the title is not simply 'On certainty' and Wittgenstein in the writers field. Therefore the ranking gives a very poor priority to these titles.
    They are main primary titles within philosophy and other fields and therefore is much used, when findable.

    We just moved to Alma from Intota, and in Intota there were more metadata (see photo) and the title would simply be 'On Certainty'

    The Intelex Past Masters

    In Alma in the electronic collections I can find the metadata have a structure that follows the structure of the database and not a normal catalogue standard.

    A title looks like this: 'Collected works of Ludwig Wittgenstein. On certainty' and there are very few other information, eg. the field for ISBN and the writer has not been filled out.

    When I search in Primo, I have to do a very specific search to find the title, since the title is not simply 'On certainty' and Wittgenstein in the writers field. Therefore the ranking gives a very… more

    •  

    4 votes

    Vote 0 votes 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

16. List of possible CZ electronic collection types are inadequate

    According to Alma documentation and the answer from ticket 08300011 CZ electronic collection types can be characterised as:

    Abstract & Index
    Book
    Journal
    Mixed
    OPAC
    Web Service

    Our library has linked to CZ collections which only have streaming video, or streaming audio portolios. We think it would be better if there were more content types available to CZ collections to better reflect their contents

    4 votes

    Vote 0 votes 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

17. 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

    3 votes

    Vote 0 votes 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

18. 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 0 votes 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

19. Create an All Open Access CZ Collection for Elsevier ScienceDirect Journals

    Could a CZ collection be created for Elsevier ScienceDirect journals that are completely open access leaving out hybrid journals (or what Elsevier terms as "contains open access" or "subscribed & complimentary"). That information can be found on their web site: https://www-sciencedirect-com.proxy.binghamton.edu/browse/journals-and-books?contentType=JL&accessType=openAccess

    If a title becomes open access after a specific date, that information can be found on the journals "All issues" page (see attached showing that Advances in Nutrition became OA "31st December 2022").

    • 

    2 votes

    Vote 0 votes 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

20. Información del campo-Editor de metadatos

    En los diferentes campos de un registro en el editor de metadatos la información del campo podría estar en castellano.

    1 vote

    Vote 0 votes 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  ·  Edit…  ·  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