186 results found

1. Decouple the bib-level material type of Music into Scores and Sound Recordings

   The bibliographic material type of Music inexplicably combines scores (Leader/06 c or d) and sound recordings (Leader/06 i or j) into a single facet. This makes no sense and makes standard statistics reporting extremely difficult as scores are usually reported with books (they are, after all, pieces of paper bound between covers) whereas sound recordings are usually reported with other media. Scores should be separated out as its own bib-level material type.

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

   “Music” is one of the seven different distinct bibliographic material types used by the MARC standard: https://www.loc.gov/marc/bibliographic/bdintro.html

   This is defined as: “Music (MU) - used for printed, electronic, manuscript, and microform music, as well as musical sound recordings, and non-musical sound recordings. Material may be monographic or serial in nature”.

   As adherence to the MARC standard is important to many of our customers (as also reflected in the comments to this idea), we will keep these distinct seven formats, and not add or subtract from them.

   Alma also provides a “Resource Type” category, which is more granular and is based on a combination of fields – this includes the following non-musical types:

   Audio nonmusical – Physical: LDR pos. 06 = i AND LDR pos. 7 = m AND 008 pos. 23 != a,b,c,o,f,q,s (MARC 21), LDR pos. 6 = i (UNIMARC) or LDR pos. 06 = i AND LDR pos. 7 = m AND has 125 (CNMARC)

   Audio nonmusical – Electronic: LDR pos. 06 = i AND LDR pos. 7 = m AND 008 pos. 23 = o,q,s (MARC 21), LDR pos. 6 = i and 106 $a/0 = s (UNIMARC) or LDR pos. 06 = i AND LDR pos. 7 = m AND has 135 (CNMARC)

   Audio nonmusical – Component Part: LDR pos. 06 = i AND LDR pos. 7 = a (MARC 21)

   For more information, see: https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/010Getting_Started/050Alma_User_Interface_%E2%80%93_General_Information/Searching_in_Alma#The_Resource_Type_Field

   Without dissociating the material type field from the MARC standard, if there is a need for an update to the more flexible Resource Type field - we would like to hear more and better understand this need so that we can provide a solution.

   “Music” is one of the seven different distinct bibliographic material types used by the MARC standard: https://www.loc.gov/marc/bibliographic/bdintro.html

   This is defined as: “Music (MU) - used for printed, electronic, manuscript, and microform music, as well as musical sound recordings, and non-musical sound recordings. Material may be monographic or serial in nature”.

   As adherence to the MARC standard is important to many of our customers (as also reflected in the comments to this idea), we will keep these distinct seven formats, and not add or subtract from them.

   Alma also provides a “Resource Type” category, which is more granular and is based on a combination of fields – this includes the following non-musical types:

   Audio nonmusical – Physical: LDR pos. 06 = i AND LDR pos. 7 = m AND 008 pos. 23 != a,b,c,o,f,q,s (MARC 21), LDR pos. 6 = i (UNIMARC) or LDR pos. 06 = i AND LDR pos.… more

2. Want to view more of a bibliographic record when editing without having to scroll

   There is currently quite a lot of unused space above and below a bibliographic record. It would be great if I could drag the bottom of the bibliographic record down further when I am editing so that I can view as much of the record as possible at once.

   54 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 →
   Closed  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

   This idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.

3. Improved functionality for Authority contribution (Copy to community)

   This copy option was introduced in the November 2019 release: Authority Contribution – Copy Option:

   For institutions that are authorized to contribute authority records to the Community Zone, there is a new Record View page action (Copy to Community) that enables you to easily copy an authority record to the MD Editor, edit and save it, and contribute the saved record to the Community Zone and an external authority system such as GND, BARE, or NLI. The Copy to Community action appears when you select a title to view from your Authorities search results on the Community tab. See Copy to Community for more information.

   We very much welcome this feature. The current functionality, totally detached from the cataloging process, makes it however a lot less useful than expected. We suggest ExLibris redesign the functionality to better make it support our daily cataloging workflow:

   • When authorizing a heading during cataloging in the MDE (F3), an option to search for external authorities, much like the "Search Resources"-functionality, should appear.

   • There is a need for matching, merging, normalizing and filtering the authority records in the same way as for the bib.records we import by use of "Search Resources". It should be possible to have different import profiles for the different sources.

   This copy option was introduced in the November 2019 release: Authority Contribution – Copy Option:

   For institutions that are authorized to contribute authority records to the Community Zone, there is a new Record View page action (Copy to Community) that enables you to easily copy an authority record to the MD Editor, edit and save it, and contribute the saved record to the Community Zone and an external authority system such as GND, BARE, or NLI. The Copy to Community action appears when you select a title to view from your Authorities search results on the Community tab. See Copy… more

   52 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 →
   Closed  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

   This idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.

4. Diacritics and special characters

   When importing records from vendors diacritics and special characters should also import. Currently they come in as random characters or unicode and it takes up staff time to manually correct them.

   47 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 →
   Closed  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

   This idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.

5. Add a drool normalization process option, to Publish to Primo job

   This will enable libraries to export to Primo their activated CZ bibliographic records, under the same conditions applied on their local bibliographic records.

   46 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 →
   Closed  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

   This idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.

6. Metadata Editor: Add More Keyboard Shortcuts and Make Existing Ones Intuitive

   The ME needs a keyboard shortcut for every function. 'Search External Resources', 'Release Record', and many other actions do not have keyboard shortcuts, so I still essentially have to use the menu for everything. This is simply inaccessible.

   Secondly, the shortcuts that do exist don't make sense. A new field is F8, but deleting a field is CTRL + F6? Why not just make it CTRL + F8? Or F9? These shortcuts are poorly thought out and confusing.

   41 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 →
   Closed  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

   This idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.

7. In Metadata Editor, open records by MMS id directly

   It's common to have a list of MMS ids that need to be worked on in Metadata Editor. The current workflow is to do a repository search, be taken out of MDE, click "Edit Record" and wait to be slowly taken back into MDE.

   It would speed things up tremendously if there was a way for users in MDE to input an MMS id and just have the record open up straight away.

   30 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 →
   Closed  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

   This idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.

8. Create a Separate Search Index for Specific OCLC Number

   Currently, the OCLC Number for a record is indexed in the search index "Other System Number." This is not ideal, since the Other System Number indexes other numbers related to vendor record, CONSER, related item, etc.
   We request that Ex Libris provide a separate search index for OCLC number based on the presence of the '(OCoLC)' prefix in the 035 $a and/or $z, or (without prefix) in the 019 $a if there is a number in the 035 with an (OCoLC) prefix. Currently these specific (OCoLC) numbers are mixed in with other numbers occurring in the 019, 035, 773, 774, 775 777, 786, 800, 810, 811, 830 $w tags and subfields. Disambiguating these specific (OCoLC) numbers from the "other system numbers" would allow us to use them as unique identifiers. We see the potential for: Improved search Improved matching upon record import Cleaner Excel exports from Alma (we currently have to clean this field every time we export) Creation of a new Analytics field for OCLC number in Alma Analytics Establishment of a model for non-OCLC systems to create other unique search indexes 

   Currently, the OCLC Number for a record is indexed in the search index "Other System Number." This is not ideal, since the Other System Number indexes other numbers related to vendor record, CONSER, related item, etc.
   We request that Ex Libris provide a separate search index for OCLC number based on the presence of the '(OCoLC)' prefix in the 035 $a and/or $z, or (without prefix) in the 019 $a if there is a number in the 035 with an (OCoLC) prefix. Currently these specific (OCoLC) numbers are mixed in with other numbers occurring in the 019, 035, 773, 774,… more

   30 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 →
   Closed  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

   This idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.

9. reorder tags / fields in metadata editor mde using drag and drop

   Sometimes repeatable field must be sorted/reordered.
   For example, we have records with many 505 tags that are added overtime and we have to arrange their order so that they are properly displayed in Primo.
   Right now one must copy the content of the tag to move; add a tag in the proper position with indicators etc.; paste the content; delete the source tag. Quite a long and error prone procedure.
   Having the chance to simply drag and drop the fields in the mde to reorder them would be therefore a great enhancement.

   29 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 →
   Closed  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

   This idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.

10. Lists of Name Authorities similar Subject Authorities

    Lists of Name Authorities similar Subject Authorities
    When cataloging a bibliographic record, Alma allows selecting different lists of Subject Authorities (LC, UC or UANDES, etc.). In the case of the Name Authorities, it currently only allows the use of a list of Name Authorities. We propose that the authorities of name are handled in the same way as the Matter Authorities.

    // Al momento de catalogar un registro bibliográfico, Alma
    permite seleccionar distintos listados de Autoridades de Materia (LC, UC o UANDES, etc.). En el caso de las Autoridades de Nombre, actualmente sólo permite usar un listado de Autoridades de Nombre. Proponemos que las autoridades de nombre se manejen igual que las Autoridades de Materia.

    Lists of Name Authorities similar Subject Authorities
    When cataloging a bibliographic record, Alma allows selecting different lists of Subject Authorities (LC, UC or UANDES, etc.). In the case of the Name Authorities, it currently only allows the use of a list of Name Authorities. We propose that the authorities of name are handled in the same way as the Matter Authorities.

    // Al momento de catalogar un registro bibliográfico, Alma
    permite seleccionar distintos listados de Autoridades de Materia (LC, UC o UANDES, etc.). En el caso de las Autoridades de Nombre, actualmente sólo permite usar un listado de Autoridades de… more

    27 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 →
    Closed  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

    This idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.

11. Version control/history of normalization, merge, and indication rules

    Alma should store the version history of normalization, merge, and indication rules - just like bibliographic metadata - in case someone makes an inadvertent edit. This would allow users to restore the rule to a previous, working state.

    24 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 →
    Closed  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

    This idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.

12. it is very important to be able to browse the indexes by author, subject, series, classification, etc. in Alma.
    24 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 →
    Closed  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

    This idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.

13. Enable authority control on subdivisions

    Currently, Alma creates a link between a full bib heading with an authority that has exactly the same subfields.
    For instance:

    650 7 $$a Sports $$x Gestion. $$2 ram
    Will fully link with authority:
    150 _ $$a Sports $$x Gestion (ID: FRBNF11965041)

    If Alma cannot match an authority with the full heading, then it attempts to link the first subfield of the heading with an authority:

    650 7 $$a Sports $$x Gestion $$z France $$y 1990-2020. $$2 ram
    Will (partially) link with authority
    150 _ $$a Sports(ID: FRBNF13318890)
    The other subfields will remain unlinked and therefore not under authority control.

    This behavior is problematic for subject vocabularies that allow constructing headings from various authorities (precoordinated subject indexing). LCSH and Rameau work this way. Headings that do not match exactly with an authority are only partially linked and subfields following the linked subfields (i.e. subdivision headings) do not benefit from authority control. This is especially problematic when a subdivision authority is changed, for all subdivisions in the subject heading will remain the same.

    A recent example with Rameau is the chronological subdivision ""1990-..."" that changed to ""1990-2020""." When the authority was changed, no subject headings in the bib records were updated, because subfield “$$y 1990-...” is not under authority control.

    Heading “650 _7 $$a Sports $$x Gestion $$z France $$y 1990-..... $$2 ram” should have been updated into:
    650 _7 $$a Sports $$x Gestion $$z France $$y 1990-2020. $$2 ram
    But Alma didn’t do it. Librarians had to do it themselves using normalization rules.

    Alma should have the ability to link not only the first subfield of a subject heading but each part of the heading that has a corresponding authority. More specifically, Alma should be able to search for authorities at least for subfields x,y and z.

    For heading “650 7 $$a Sports $$x Gestion $$z France $$y 1990-2020. $$2 ram”, Alma should search for corresponding authorities for each subfields:
    $$a Sports -> 150 _ $$a Sports
    $$x Gestion -> 180 __ $$x Gestion
    $$z France -> 181 __ $$z France
    $$y 1990-2020 -> 182 __ $$y 1990-2020

    There will be cases where some parts of the heading will not match with any authorities (for instance, subfields $$d or subfields $$x when the term is not used alone, but always in a composed heading), but this behavior would be much more satisfying than the current one.

    Currently, Alma creates a link between a full bib heading with an authority that has exactly the same subfields.
    For instance:

    650 7 $$a Sports $$x Gestion. $$2 ram
    Will fully link with authority:
    150 _ $$a Sports $$x Gestion (ID: FRBNF11965041)

    If Alma cannot match an authority with the full heading, then it attempts to link the first subfield of the heading with an authority:

    650 7 $$a Sports $$x Gestion $$z France $$y 1990-2020. $$2 ram
    Will (partially) link with authority
    150 _ $$a Sports(ID: FRBNF13318890)
    The other subfields will remain unlinked and therefore not under authority control.

    … more

    23 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 →
    Closed  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

    This idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.

14. View actually linked bib records in 'Browse bibliographic headings'

    When using the Browse bibliographic headings feature, it is not possible to diplay the list of bib records that are ACTUALLY linked to one authority. We can only see the bib records that match with the authority.
    On the contrary, when using the F3 index, Alma provides an extra menu in the 'View' option of a bibliographic heading where one can choose between records that match the authority or records that are linked to the authority.
    This Idea requests that the same feature be added in the Browse bib heading tool.

    22 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 →
    Closed  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

    This idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.

15. Enable case-insensitivity for indication and other rules

    Indication (and other) rules in Alma are case sensitive by design. Case sensitivity of course is often desirable, to ensure most exact matching and prevent inadvertent data problems. However, in some instances, especially with indication rules, it would be very helpful and time-saving to be able to use case insensitivity, as is possible with regular expressions (ex: /i). An example of a scenario in which this would be helpful is when using an indication rule to identify records which contain a particular textual note, when that note may have been entered with varying cases: sometime all uppercase, sometimes sentence case, sometimes title case, and so on. Currently, one must try to imagine and include all possible text case variants and add them to the indication rule; being able to toggle case sensitivity/insensitivity would make it possible to more easily search for and find all variants.

    Indication (and other) rules in Alma are case sensitive by design. Case sensitivity of course is often desirable, to ensure most exact matching and prevent inadvertent data problems. However, in some instances, especially with indication rules, it would be very helpful and time-saving to be able to use case insensitivity, as is possible with regular expressions (ex: /i). An example of a scenario in which this would be helpful is when using an indication rule to identify records which contain a particular textual note, when that note may have been entered with varying cases: sometime all uppercase, sometimes sentence case,… more

    22 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 →
    Closed  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

    This idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.

16. Authority creation - Populate 670 Source Data Found from open bib

    When creating an authority by F3 searching from a bib record and clicking "Create authority record", no data is linked from the bib. Voyager populated bib information in new authorities to track and differentiate headings.

    Please populate the 670 field (Source Data Found) in the new authority record with Title, date in $a and MMS ID in $w.

    This would look like: 670 ##$a [245$a], [260/264$c] $w [001]

    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…)
    0 comments  ·  Metadata Management  ·  Delete…  ·  Admin →
    Closed  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

    This idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.

17. ACTL needs to be refined: Ending ISBD punctuation issue

    There are many entries in ACTL that the only difference between BIB Heading Before and BIB Heading After is that the full stop is removed at the end of BIB Heading After. For example:

    BIB Heading Before
    
    Hong Kong (China). Census and Statistics Department.

    BIB Heading After
    Hong Kong (China). Census and Statistics Department

    This kind of entries should be excluded from ACTL since this is not heading update at all.

    18 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 →
    Closed  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

    This idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.

18. Provide authority control for terms in 3XX fields.

    Terms in fields 380, 382, 385 and 386 should be matched to authority records based on the $2 code and an icon placed next to the field when the terms have been verified.

    17 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 →
    Closed  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

    Hello All,

    This idea has been closed as part of a cleanup process for ideas older than two years with fewer than 20 votes.

    This cleanup process is necessary to streamline our idea management process and ensure that the most relevant and impactful ideas receive the attention they deserve. If you still feel strongly about this idea, you may submit it via the NERS process.

    We value your feedback and encourage you to continue submitting and voting for ideas that you believe will enhance Alma.

    Alma Product Team

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

    16 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 →
    Closed  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

    Hello All,

    This idea has been closed as part of a cleanup process for ideas older than two years with fewer than 20 votes.

    This cleanup process is necessary to streamline our idea management process and ensure that the most relevant and impactful ideas receive the attention they deserve. If you still feel strongly about this idea, you may submit it via the NERS process.

    We value your feedback and encourage you to continue submitting and voting for ideas that you believe will enhance Alma.

    Alma Product Team

20. Notes on bibliographic records should open as a pop-up message when a user starts editing the record.

    We have the option to add notes to bibliographic records in Alma which are only visible in the metadata editor. This is found under record actions – add note. The option to add notes here is very practical, but it is easy for the cataloger to ignore the note. To make the note harder to ignore it should open as a pop-up message when you first start to edit the bibliographic record in the metadata editor. This could be added as a feature that each library could turn on or off in their configuration menu.

    16 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 →
    Closed  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

    This idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.