6 results found

1. Metadata editor: Enable moving up and down within a field using arrow keys

   It would be nice to be able to move up and down within a field using arrow keys in MDE. For example, when a lengthy 505 or 520 MARC field has many lines, the cataloger must now move to the desired line using either mouse or left/right arrow keys, since pressing up/down arrow causes the pointer to move to the previous/next field.

   My suggestion is that the pointer should be able to move within the field using up/down arrows and move only to the previous/next field when the pointer is on the first/last line of the field.

   Using up/down arrow keys when moving within a field would streamline cataloger’s work and help making the MDE more user-friendly.

   It would be nice to be able to move up and down within a field using arrow keys in MDE. For example, when a lengthy 505 or 520 MARC field has many lines, the cataloger must now move to the desired line using either mouse or left/right arrow keys, since pressing up/down arrow causes the pointer to move to the previous/next field.

   My suggestion is that the pointer should be able to move within the field using up/down arrows and move only to the previous/next field when the pointer is on the first/last line of the field.

   Using up/down arrow… more

   332 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 →
   Accepted  ·  AdminLili Daie (Product Manager, Ex Libris) responded

   Dear all, we are currently working on a design concept for a new form interface option for cataloging, which will make it easier to navigate long fields and subfields - we will take this request into account as part of this design. See our "Form Editing for MARC 21 Bibliographic Records" roadmap plans for more information: https://knowledge.exlibrisgroup.com/Alma/Product_Materials/010Roadmap/Alma_Roadmap_Highlights_(2024-2025)/Metadata_Management#Form_Editing_for_MARC_21_Bibliographic_Records

2. Subdivided LCSH headings should be flipped by Preferred Term Correction

   Preferred Term Correction is not flipping all LCSH headings when the authority record changes. If there is an authority record that has a subdivision, it is only flipped by PTC if the heading in the bib has no additional subdivisions. This means there is a significant gap in the PTC process that requires manual attention and handling, which is unsustainable. The PTC process needs to be more thorough.

   For example, this LCSH:

   $a Germany $x Politics and government $y 19th century

   was updated by LC to be:

   $a Germany $x Politics and government $y 1789-1900

   When the authority record changed, bib headings that had the original $a $x $y (only) were flipped by PTC to have the new $y. But any headings that had additional subdivisions were not flipped.

   For example, this bib heading was flipped to the new form:
   BEFORE: $a Germany $x Politics and government $y 19th century
   AFTER: $a Germany $x Politics and government $y 1789-1900

   But this bib heading was NOT flipped:
   $a Germany $x Politics and government $y 19th century $v Congresses.

   More example of headings that were not flipped but should have been flipped:
   651 0 $a Germany $x Politics and government $y 19th century $v Caricatures and cartoons.
   651 0 $a Germany $x Politics and government $y 19th century $v Congresses.
   651 0 $a Germany $x Politics and government $y 19th century $v Exhibitions.
   651 0 $a Germany $x Politics and government $y 19th century $x In literature.
   651 0 $a Germany $x Politics and government $y 19th century $v Periodicals.
   651 0 $a Germany $x Politics and government $y 19th century $v Poetry.

   Impact of Problem: The fact that PTC does not flip these headings means that staff have to manually correct hundreds or thousands of headings. The PTC process is lacking and is not performing its function of managing authority control automatically.

   Preferred Term Correction is not flipping all LCSH headings when the authority record changes. If there is an authority record that has a subdivision, it is only flipped by PTC if the heading in the bib has no additional subdivisions. This means there is a significant gap in the PTC process that requires manual attention and handling, which is unsustainable. The PTC process needs to be more thorough.

   For example, this LCSH:

   $a Germany $x Politics and government $y 19th century

   was updated by LC to be:

   $a Germany $x Politics and government $y 1789-1900

   When the authority record changed,… more

   307 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…)
   Accepted  ·  3 comments  ·  Metadata Management  ·  Delete…  ·  Admin →

3. Copy and paste multiple MARC fields into the metadata editor

   We would like to be able to copy multiple lines from MARC records and paste them into the metadata editor so that multiple MARC fields are pasted into the record in one action. This would help us enormously with our workflow of importing MARC authority records from LibrariesAustralia into Alma.

   For us, this is necessary because the LibrariesAustralia headings are not in the community zone and are unlikely to ever be included there and Alma does not allow for Z39.50 import of authority headings.

   We have this functionality of copying and pasting multiple fields in the LibrariesAustralia Cataloguing Client and other library systems allow it. At the moment we need to paste each line one by one into Alma and it is slow and repetitive. This process is a step backward from previous functionality.

   We would like to be able to copy multiple lines from MARC records and paste them into the metadata editor so that multiple MARC fields are pasted into the record in one action. This would help us enormously with our workflow of importing MARC authority records from LibrariesAustralia into Alma.

   For us, this is necessary because the LibrariesAustralia headings are not in the community zone and are unlikely to ever be included there and Alma does not allow for Z39.50 import of authority headings.

   We have this functionality of copying and pasting multiple fields in the LibrariesAustralia Cataloguing Client and… more

   550 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…)
   8 comments  ·  Metadata Management  ·  Delete…  ·  Admin →
   Accepted  ·  AdminLili Daie (Product Manager, Ex Libris) responded

   Dear all,

   I believe we now understand the requirement better: To be able to paste a block of text in MARC 21 format, and have Alma parse it and populate the MARC tags, indicators and subfields accordingly.

   This is a larger development, but we hope to be able to add a solution for it to our future roadmap.

4. Add notifications to Alma reminders

   I appreciate the addition of the Reminders in Alma, but I think it would be even more useful if reminders could trigger email notifications when the reminder date has arrived.

   215 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…)
   17 comments  ·  Metadata Management  ·  Delete…  ·  Admin →
   Accepted  ·  AdminLili Daie (Product Manager, Ex Libris) responded

   A new task will be added to the tasks widget, alerting catalogers when reminders' date arrives.

5. It would be helpful if there were an option to "print MARC record" within the MD editor and from the Repository Search.

   We sometimes have need of a hard copy of the MARC record for tracking certain workflows. One such example is for making notes about title changes and tracking them across several records. It would be nice if there was a "print full record" option, both in the MD editor and in the repository hit list. Right now, we need to either do print screens or do a screen capture and print from that. Thank you!

   158 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…)
   Accepted  ·  9 comments  ·  Metadata Management  ·  Delete…  ·  Admin →

6. Ctrl-z/Undo in the Metadata Editor

   Currently, there is no Ctrl-z/Undo function in the Metadata Editor.
   Please add this function.
   Use case:
   A record is in draft mode and the cataloger deletes a field accidentaly, there is no way of bringing it back.
   Or a cataloger works on an exisiting record, makes a lot of changes and only wants to undo the last actions, but not go back to the previous version.

   350 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…)
   14 comments  ·  Metadata Management  ·  Delete…  ·  Admin →
   Accepted  ·  AdminLili Daie (Product Manager, Ex Libris) responded

   Dear Alma Community,

   As part of our ongoing commitment to align our internal development processes and increase roadmap transparency with our community, to provide a more realistic and transparent view of Alma development, this idea that was previously marked as “Planned” had been reassigned a status of “Accepted”.

   The “Accepted” status signifies that the Alma Product Management team recognizes the value of the remaining part of this idea, and is committed to its development. However - as we are still looking into possible solutions, it is not expected to make it onto the roadmap this year. We appreciate your understanding and patience as we implement this change.

   We understand that this change may lead to disappointment or frustration, and we sincerely apologize for any inconvenience it may cause. Please know that your ideas and suggestions are extremely important to us, and we are committed to continually enhancing Alma based on your valuable input. Thank you for your continued effort in enhancing Alma - we look forward to continuing to work together to make Alma the best it can be.

   Most sincerely,

   Alma Team

   Dear Alma Community,

   As part of our ongoing commitment to align our internal development processes and increase roadmap transparency with our community, to provide a more realistic and transparent view of Alma development, this idea that was previously marked as “Planned” had been reassigned a status of “Accepted”.

   The “Accepted” status signifies that the Alma Product Management team recognizes the value of the remaining part of this idea, and is committed to its development. However - as we are still looking into possible solutions, it is not expected to make it onto the roadmap this year. We appreciate your understanding and patience as we implement this change.

   We understand that this change may lead to disappointment or frustration, and we sincerely apologize for any inconvenience it may cause. Please know that your ideas and suggestions are extremely important to us, and we are committed to continually enhancing Alma based on… more