111 results found

1. Bibliographic creation date should be original load date

   Currently, when you reload a bibliographic record, it updates the creation date, so you have no way of knowing when the record was loaded for the first time. This makes statistics gathering difficult. It would make more sense to have some sort of original creation date (at least in analytics), so you can see when that bibliographic record/MMSID was created in the system for the first time.

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

2. Ability to publish data from different tags in the holdings record into a single tag per holdings record

   When publishing data for external parties, we would like to be able to combine data from different tags in the holdings record into a single tag in the published record. E.g. we want to export library, location and call number details from tag 852$b$c$h as well as details of volumes held from the 866$a:

   852 8_ $b J $c BJ $h PPPP007189-007195
   866 41 $a v.31:no.1(1970)-v.34:no.11/12(1973)

   as 949 $a J $b BJ $c PPPP007189-007195 $d v.31:no.1(1970)-v.34:no.11/12(1973)

   What we end up with is (in OAI) 2 separate published tags:

   <datafield tag="949" ind1="8" ind2=" ">
   <subfield code="a">J</subfield>
   <subfield code="b">BJ</subfield>
   <subfield code="c">PPPP007189-007195</subfield>
   <subfield code="8">22185971280001811</subfield>
   </datafield>

   <datafield tag="949" ind1="4" ind2="1">
   <subfield code="s">v.31:no.1(1970)-v.34:no.11/12(1973)</subfield>
   <subfield code="8"<22185971280001811</subfield>
   </datafield>

   For titles with multiple runs at different locations in storage, this can get quite messy.

   We know this can be done because the Publish holdings to Libraries Australia job does it when building a 984 tag in the published records:
   984 $a SUA $c PPPP007189-007195 $d v.31:no.1(1970)-v.34:no.11/12(1973)

   When publishing data for external parties, we would like to be able to combine data from different tags in the holdings record into a single tag in the published record. E.g. we want to export library, location and call number details from tag 852$b$c$h as well as details of volumes held from the 866$a:

   852 8_ $b J $c BJ $h PPPP007189-007195
   866 41 $a v.31:no.1(1970)-v.34:no.11/12(1973)

   as 949 $a J $b BJ $c PPPP007189-007195 $d v.31:no.1(1970)-v.34:no.11/12(1973)

   What we end up with is (in OAI) 2 separate published tags:

   <datafield tag="949" ind1="8" ind2=" ">
   <subfield code="a">J</subfield>
   <subfield code="b">BJ</subfield>
   <subfield code="c">PPPP007189-007195</subfield>
   <subfield… 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…)
   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
   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

3. Show Brief Record Levels in Search External Resources

   It would be really useful if we could see the brief record level when searching for catalogue records via "Search External Resources".

   Currently the only way to perform a brief level analysis on a record is to import and save it. It would be really useful to see this when searching external resources, without having to save and import the record first.

   This will be useful to ensure a good level of metadata is maintained across our catalogue.

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

4. Release All function to release Bibs and Holdings simultaneously
   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
   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

5. Visually accessible display of MMS IDs etc.

   The MMS IDs and other IDs (e.g. holdings IDs, PIDs, item IDs, etc.) are very long. It's very difficult to distinguish one MMS ID from another.

   In the case of MMS IDs in our IZ and our associated NZ, the last 4 digits are fixed and have specific meaning, e.g.:
   MMS IDs ending with -3409 refer to our institution's MMS IDs
   MMS IDs ending with -3406 refer to the associated NZ's MMS IDs

   We'd like Alma to provide an option to display the 5 digits before the 4 ending digits in a different colour in order to make it easier to read the MMS IDs when we need to distinguish one MMS ID from another.

   For example:
   MMS ID 991000145579703409 -- Please make 57970 appear in a different colour
   MMS ID 9910283394903406 -- Please make 39490 appear in a different colour

   Thank you for your consideration!

   The MMS IDs and other IDs (e.g. holdings IDs, PIDs, item IDs, etc.) are very long. It's very difficult to distinguish one MMS ID from another.

   In the case of MMS IDs in our IZ and our associated NZ, the last 4 digits are fixed and have specific meaning, e.g.:
   MMS IDs ending with -3409 refer to our institution's MMS IDs
   MMS IDs ending with -3406 refer to the associated NZ's MMS IDs

   We'd like Alma to provide an option to display the 5 digits before the 4 ending digits in a different colour in order to make it easier… more

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

6. (Metadata editor) Make the "yes" and "no" Release All Records buttons keyboard actionable

   It would be great to be able just to type Y or N in the Release All Records dialogue window, rather than having to mouseclick on "Yes" or "No."

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

7. Remove Automatically Created Extra Space Before Subfields in the Metadata Editor

   In the Metdadata Editor, an extra space is automatically created before the first full word after a subfield. This space shows up only when you begin to type the word.

   Not only is this annoying, but it also affects the functionality of the authority record search, as that extra space has to be edited out for the authority to be found either with the automatic dropdown, or with the F3 command.

   I have attached an image that shows this phenomenon. Note the margin difference between all of the other fields and the 090.

   Please remove the automatic space.

   •  

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

8. Active/inactive indicator for electronic collections

   We propose an indicator - e.g. a yes/no radio button set - to indicate whether or not an electronic collection is active. This will make it easier to exclude inactive electronic collections from searches and Analytics reports. Current methods of indicating this status aren't comprehensive. The bib can be suppressed, and/or the URL removed, but there are other reasons to suppress bib records and remove URLs (such as when we want only portfolios to display in our discovery layer). In aggregator and selective packages, we can delete the service or mark it inactive, but this doesn't apply to database-type electronic collections.

   We propose an indicator - e.g. a yes/no radio button set - to indicate whether or not an electronic collection is active. This will make it easier to exclude inactive electronic collections from searches and Analytics reports. Current methods of indicating this status aren't comprehensive. The bib can be suppressed, and/or the URL removed, but there are other reasons to suppress bib records and remove URLs (such as when we want only portfolios to display in our discovery layer). In aggregator and selective packages, we can delete the service or mark it inactive, but this doesn't apply to database-type electronic… more

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

9. Allow the contents of MARC subfield 041 $$h to be considered for Search Index Mapping

   The MARC 21 Bibliographic Tag to Search Index Mapping table (https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/040Resource_Management/040Metadata_Management/180Search_Indexes/050MARC_21_Search_Indexes) confirms that the contents of 041 subfields $$a, $$b, $$d, $$e, $$f, $$g, $$j, plus those of the 008 field positions 35-37, map to an advanced search of the Language (Title) index in Alma.

   The contents of 041 subfield $$h ("language code of original"), however, do not. This discriminates against those works which are translated from an original language into the one stipulated in 041 $$a subfield.

   There are plenty of titles in our stock where information regarding the language of the original material is no less important than the information regarding the language into which it has been translated (I'm thinking especially about texts in ancient language and/or non-Roman scripts); and experience of handling supplier and publisher MARC records confirms that 041 $$h subfields (which aren't mapped) are applied far more frequently and assiduously to records than 240 $$l subfields (which are mapped, albeit to Title and Uniform Title).

   It is appreciated that adding $$h to the Language (Title) index may not be what every customer wants, as that would lose the distinction between, say, titles in Swedish and titles that were translated to English from original Swedish.

   That being the case, could it at least be possible for ExLibris to introduce an additional advanced search index option - called "Language of Translation" or similar - whose contents are drawn solely from 041 $$h subfields wheresover they exist?

   The MARC 21 Bibliographic Tag to Search Index Mapping table (https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/040Resource_Management/040Metadata_Management/180Search_Indexes/050MARC_21_Search_Indexes) confirms that the contents of 041 subfields $$a, $$b, $$d, $$e, $$f, $$g, $$j, plus those of the 008 field positions 35-37, map to an advanced search of the Language (Title) index in Alma.

   The contents of 041 subfield $$h ("language code of original"), however, do not. This discriminates against those works which are translated from an original language into the one stipulated in 041 $$a subfield.

   There are plenty of titles in our stock where information regarding the language of the original material is no less… more

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

10. Make merge rule actions fully interchangeable with all merge conditions

    Currently, merge actions (add, remove, replace) only operate with specific conditional statements. For example, ADD when CONTAINS or REPLACE when DOES NOT CONTAIN. This enhancement should add the ability to use all action words with any valid conditional statement, permitting uses such as ADD when DOES NOT CONTAIN or REPLACE when CONTAINS.

    6 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
    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

11. Authority control: ability to exclude certain fields and subfields from authority control. Prsence of 700 $i fails the link to auth file.

    Presence of 700 $i in the bib record causes the heading not to link to the authority record and it reports as an unlinked heading, when in fact the rest of the 700 field does have an existing authority record.

    6 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
    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

12. Assigning Authority Control Tasks to Specific Staff Members

    At the end of each month, I go into the Authority Control Task List, dismiss headings I don’t want my staff to work on, and export the other headings to an Excel spreadsheet, which we work off directly.

    It would be helpful if there was a way to assign tasks to my staff directly and have it appear in the general task menu on the Alma homepage. For example, if there were 200 headings to update, and I wanted to split them between two staff members, I could select the first 100 in the Authority Control Task List and assign them to someone and then assign the other 100 to someone else.

    Thank you.

    At the end of each month, I go into the Authority Control Task List, dismiss headings I don’t want my staff to work on, and export the other headings to an Excel spreadsheet, which we work off directly.

    It would be helpful if there was a way to assign tasks to my staff directly and have it appear in the general task menu on the Alma homepage. For example, if there were 200 headings to update, and I wanted to split them between two staff members, I could select the first 100 in the Authority Control Task List and assign… more

    6 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
    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

13. Show more information about how and where normalization rules are being used

    • A flag that indicates if a rule has been turned into a norm process.
    • At the bottom of the current Metadata Editor, with the tabs, add a tab that shows import profiles the process is used in if the rule has been turned into a process.
    6 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
    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

14. DB-category-job on all bibliographic records

    In Alma there is a job that based on a specified marc-field builds up a hierarchy of categories for the A-Z Database search in Primo.

    This works fine, but the job is limited to a certian subset of records only.

    From Ex Libris:
    "The Database Categories File job runs for the benefit of Primo database search, and is therefore relevant only for bib records linked to databases." https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/040Resource_Management/050Inventory/020Managing_Electronic_Resources#Working_with_Database_Type_Electronic_Collections

    I can understand why it was designed like this, but in our consortia we see that the institutions would like to include other records in the A-Z-list as well. Records that are not databases in a pure sense, but has similarities and characteristics that makes it meaningful to include them in the A-Z-list. We can do this in the normalization in Primo, but the categories the record represents will not be included in the hierarchy of categories because the bibliographic record is not included in the job that runs in Alma.

    We would suggest that the job are changed so that it includes all bibliotegraphic records that use the specified marc-field for categories, regardless of type.

    In Alma there is a job that based on a specified marc-field builds up a hierarchy of categories for the A-Z Database search in Primo.

    This works fine, but the job is limited to a certian subset of records only.

    From Ex Libris:
    "The Database Categories File job runs for the benefit of Primo database search, and is therefore relevant only for bib records linked to databases." https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/040Resource_Management/050Inventory/020Managing_Electronic_Resources#Working_with_Database_Type_Electronic_Collections

    I can understand why it was designed like this, but in our consortia we see that the institutions would like to include other records in the A-Z-list as well. Records that are… more

    6 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
    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

15. Don't Close My Bib

    Hello,
    
    when I add a Holdings Record to a bibliographic record I click "save and release" when I'm done working with the new holdings record. This then takes me back to a blank search screen, so then I have to search again for the bibliographic record I was working on. It would be helpful if there was a way to go back to bibliographic record I was working on.

    6 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
    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

16. Role for adding normalizations processes

    Cataloging staff often need to create normalization or indication rules to edit groups of records. They can create these in the Medatdata Editor but they cannot use them on sets of records until they are added as a process/task in the resources metadata configuration area.

    The ability to add processes is limited to the highest role of cataloger administrator which also allows configuration permissions.

    Include the ability to add normalization and indication rule processes to the cataloger manager role to allow more flexibility to do global changes on Marc records.

    Catalog managers need to add their own rules without giving them the ability to alter other configurations.

    Cataloging staff often need to create normalization or indication rules to edit groups of records. They can create these in the Medatdata Editor but they cannot use them on sets of records until they are added as a process/task in the resources metadata configuration area.

    The ability to add processes is limited to the highest role of cataloger administrator which also allows configuration permissions.

    Include the ability to add normalization and indication rule processes to the cataloger manager role to allow more flexibility to do global changes on Marc records.

    Catalog managers need to add their own rules without giving… more

    6 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
    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

17. Validation exception based on conditions in linked authority records

    There are certain types of authority records, such as facets, that should not be utilized in bibliographic records. MARC 21 Authority offers some options for supporting that, such as 008/15="b" ("Headings are not appropriate for use as a subject access entry in bibliographic records") and 008/09="b" ("100-15X field contains an unestablished heading that is not authorized for use as the element in an access point in a bibliographic record").

    However, when authorizing authority fields in the Alma Metadata Editor, there does not seem to be a way to prevent such records to be authorized.

    One way to prevent this would be if it was possible to create validation exceptions based on conditions in the linked authority records. Then we could create a validation exception for e.g. the case when a bibliographic record links to an authority record that has 008/15="b".

    There are certain types of authority records, such as facets, that should not be utilized in bibliographic records. MARC 21 Authority offers some options for supporting that, such as 008/15="b" ("Headings are not appropriate for use as a subject access entry in bibliographic records") and 008/09="b" ("100-15X field contains an unestablished heading that is not authorized for use as the element in an access point in a bibliographic record").

    However, when authorizing authority fields in the Alma Metadata Editor, there does not seem to be a way to prevent such records to be authorized.

    One way to prevent this would… more

    6 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
    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

18. Restrict the ability to edit local templates

    On several occasions, people have edited our local templates to catalogue a book instead of copying the template and using it as a template. It would be great if we could restrict the ability to edit local templates (to Catalog Administrator, perhaps?).

    If this is not possible, could we have the ability to roll a template back to a previous version, like we can with bibliographic records?

    6 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
    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. External Authority Record Search

    Please add a way to search externally for authority records. At present if there are no institutional or community records that can be used, we have to go outside of Alma to find a record, and then find a way to get it into Alma. Then go back into Alma to edit or work with it.

    5 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
    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. Missing subfields in authority records

    Some of the subfields are missing from the authorities in Alma - in particular subfields for 100 and 700 MARC tags are f, k, l, m, n, o, p, r, s, t
    Please include all subfields that can be used in authorities

    •  

    5 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
    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