150 results found

1. Add fields to record historical valuation data

   When rare books and other special collections are valued for insurance / exhibition / audit, it would be useful to add this into dedicated fields in the item record for physical inventory or other areas for digital titles. This way, a history of the value of the item can be recorded over time.

   2 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Resource Management - General  ·  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. 490's accompanying 830 field display

   When you search titles, Alma currently displays 830 in the Series field when traced (490 with a 1 indicator).
   However, 830 depending on 490 means that 490 takes precedence.

   It must be said that the trace which 830 is, is supposed to be used to be able to view 490 by the cataloguers and librarians.
   But currently, when using the trace, 490 is not displayed.

   When you have a 490 field with several $a, you write several 830s.
   For example ISBN: 9784043675043.
   245 00 $$a Tō enmei.
   490 1# $$a Kadokawa bunko ; $$v 13617. $$a Kadokawa sofia bunko ; $$v 123. $$a Bigināzu kurashikkusu. $$a Chūgoku no koten
   830 #0 $$a Kadokawa bunko. $$p Kadokawa sofia bunko ; $$v 123
   830 #0 $$a Kadokawa bunko. $$p Bigināzu kurashikkusu
   830 #0 $$a Kadokawa bunko. $$p Chūgoku no koten
   →Short records
   Series: Kadokawa bunko. Kadokawa sofia bunko ; 123 ; Kadokawa bunko. Bigināzu kurashikkusu ; Kadokawa bunko. Chūgoku no koten
   (If you display the main 490 as a series, then
   Kadokawa bunko ; 13617. Kadokawa sofia bunko ; 123. Bigināzu kurashikkusu. Chūgoku no koten)

   490's second $a is the series statement, and 830 is the "Name of part of a work" as an added entry.
   Since 490 takes precedence, it should be displayed instead or at least along with field 830.

   Thank you.

   When you search titles, Alma currently displays 830 in the Series field when traced (490 with a 1 indicator).
   However, 830 depending on 490 means that 490 takes precedence.

   It must be said that the trace which 830 is, is supposed to be used to be able to view 490 by the cataloguers and librarians.
   But currently, when using the trace, 490 is not displayed.

   When you have a 490 field with several $a, you write several 830s.
   For example ISBN: 9784043675043.
   245 00 $$a Tō enmei.
   490 1# $$a Kadokawa bunko ; $$v 13617. $$a Kadokawa sofia bunko ;… more

   3 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  ·  Resource Management - General  ·  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. Import Profiles - Match Profile - Adding a Title only match method

   The customer would like to add a Title only match method for CNMARC when loading new records via import profiles.
   The title field can be set to 200$a.

   Because when the ISBNs are matched, the book title may be different for some Chinese books. It would be great to be able to match on the 200$a - main title.

   13 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  ·  Resource Management - General  ·  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. Additional Input Parameter Options for Item Description Templates

   When creating an Item Description Template it would be very helpful to include additional Input Parameter options such as Permanent Physical Location. We utilize different description orders on our labels dependent upon the different locations items are shelved and there doesn't seem to be a way to distinguish the differing order with the current parameter options. More input parameter options would allow for greater individual institutional nuances and their unique practices.

   For example, I could have an unclassed serial shelved in "serials" with material type issue and I want the description to display as:
   v.{EnumA} no.{EnumB} {ChronI} {ChronJ}
   I could also have a classed serial shelved in "stacks" with a material type issue and I want the description to display as:
   {ChronI} v.{EnumA} no.{EnumB} {ChronJ}

   I want them different in order to be consistent with the cataloging practices of the two different shelving locations. Currently it doesn't seem there is a way to create this distinction.

   When creating an Item Description Template it would be very helpful to include additional Input Parameter options such as Permanent Physical Location. We utilize different description orders on our labels dependent upon the different locations items are shelved and there doesn't seem to be a way to distinguish the differing order with the current parameter options. More input parameter options would allow for greater individual institutional nuances and their unique practices.

   For example, I could have an unclassed serial shelved in "serials" with material type issue and I want the description to display as:
   v.{EnumA} no.{EnumB} {ChronI} {ChronJ}
   I could… more

   3 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  ·  Resource Management - General  ·  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. Search results sorted by record creation date

   For the purpose of having an overview of the progress in cataloguing a sorting option for bibliographic records by their creation date in chronological order is necessary.

   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  ·  Resource Management - General  ·  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. Having the ability to configure the presence of all available Licensing terms in the Repository Search in Alma

   There are a number of License terms that appear in the Advanced Repository search that are not configurable, that is there is no option to stop them appearing as options to search under in a simple or advanced search.

   We want to delete some of these terms from Advanced Search. We want to get rid of the terms that we're not using in our current Licensing workflows (they clog up the search). The terms we want to delete from the Advanced Search are not available to configure in the Alma Configuration Menu > Resources > Search Configuration > Search Indexes.

   We would like to be able to do this.

   There are a number of License terms that appear in the Advanced Repository search that are not configurable, that is there is no option to stop them appearing as options to search under in a simple or advanced search.

   We want to delete some of these terms from Advanced Search. We want to get rid of the terms that we're not using in our current Licensing workflows (they clog up the search). The terms we want to delete from the Advanced Search are not available to configure in the Alma Configuration Menu > Resources > Search Configuration > Search Indexes.

   … more

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Resource Management - General  ·  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. error message

   when you want to add a title into a collection, if this title already exists in the collection, an error message should appear "title already in the collection". It would be very useful.

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Resource Management - General  ·  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. Ability to know which set/s a specific record belong to

   It would be very useful to have the ability in Alma to know which set or sets a specific record is in. It would be nice to search for an item id (for itemized sets), an mms id (for titles sets) and so on, and get the sets' names those items or mmsids belong to.

   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  ·  Resource Management - General  ·  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. Publishing profiles should be able to produce valid MARCXML

   The ability to produce valid MARCXML exports from publishing profiles, with the namespace included, would be useful.

   Currently the "MARCXML" option produces a file that is not valid MARCXML. It doesn't include a namespace.

   The rationale given by ExL Support for not including a namespace was that it would be possible for the user to use norm rules to change the data on export, in which case the data might not be valid, so they didn't want to include a namespace. In some cases it may be necessary for libraries to produce data exports that are not valid, but even in those cases it may be helpful to have the namespace included.

   This enhancement would change the publishing profile configuration page (and the machinery behind it). When publishing using "Physical format" = XML, there should be two additional choices that appear:

   Include XML Namespace: yes/no
   Validate before publishing: yes/no

   For most use cases, I would think libraries would want to choose 'yes' to both of those. In that case, the profile should build the export file (with namespace included) and then validate it.

   If the validation is request and fails, the next step should be one of these options (listed in order of preference):
   1. Don't publish the file, and send a job report to the appropriate user saying why it didn't validate.
   2. Publish the file (with namespace), and send a job report to the appropriate user saying why it didn't validate.
   3. Publish the file (without namespace), and send a job report to the appropriate user saying why it didn't validate.

   The ability to produce valid MARCXML exports from publishing profiles, with the namespace included, would be useful.

   Currently the "MARCXML" option produces a file that is not valid MARCXML. It doesn't include a namespace.

   The rationale given by ExL Support for not including a namespace was that it would be possible for the user to use norm rules to change the data on export, in which case the data might not be valid, so they didn't want to include a namespace. In some cases it may be necessary for libraries to produce data exports that are not valid, but even… more

   0 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  ·  Resource Management - General  ·  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. Raise the exporting capacity from Alma to Excel

    It's recently found that there is a limit of 100,000 records when exporting from Alma to Excel. Please consider raising the exporting capacity.

    Background information: please refer to Salesforce case # 944923, and this documentation in the knowledge centre:
    https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/010Getting_Started/050Alma_User_Interface_%E2%80%93_General_Information/The_Alma_User_Interface#Export_to_Excel

    Thank you!

    4 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  ·  Resource Management - General  ·  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. Block Deleted Records from Merge Records and Combine Inventory Process

    Currently, when a CSV file is loaded into the "Merge Records and Combine Inventory" process in Alma Resource Management, if the preferred bibliographic record is already deleted from the repository, the merged record attaches to a deleted bib, and is deleted, which is not ideal. We would like to have those merges bounce or error and not merge, or at least be noted in the results file when this occurs, so that staff may manually review or fix that error.

    11 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  ·  Resource Management - General  ·  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. Add 385,386,655 to Alma export list

    Please add columns to Alma Export to List (Excel) from these fields: Creator/ contributor term (386/a), Audience (385/a), and Genre/form (655/a,2). These fields are important to include to the list.

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Resource Management - General  ·  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. Add the 019 field as a match profile in import profiles

    In managing import profiles, adding an option under Match Profile to match records on the 019 field would be very helpful. Some libraries use the 019 as the OCLC number and some use it for LibrariesAustralia numbers.

    Matching on the 035 and 020/022 doesn't cover all situations for importing records.

    4 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  ·  Resource Management - General  ·  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. CDI labels in Alma to be more clear and user friendly

    User Story - Our staff are confused when using CDI and would like clearer label, so they understand where to enabled something or not.
    We would prefer the labels to be changed to more ‘symptom based diagnosis’ wording. So it would be clear for CDI operators. We have left 'CDI-only full text activation' blank, because he is still not sure what this option is for. In our example we have only given suggested wording. We are happy for this to be different, as long as the labels are more clear and user friendly about what the functions do.

    •  

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Resource Management - General  ·  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. function "back"

    Metadata Editor: We miss the simple function of being able to undo the last steps when cataloging or editing records. In Aleph there was the function
    CTRL + Z. This would be extremely helpful. The ability to restore an earlier version is not suitable for this.

    0 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  ·  Resource Management - General  ·  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. Allow compression to export/publish files containing records in format binary MARC21

    This option, to compress the file before send is available only if publishin MARCXML.
    Spain University Colective Catalogue REBIUN, requieres files in that format, so publishing takes a long time.

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Resource Management - General  ·  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. rerun Overlap and Collection Analysis

    There are certain reports that I would like to run in Overlap and Collection Analysis periodically. It would be helpful if I could rerun a past report instead of having to enter all the criteria every time.

    3 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  ·  Resource Management - General  ·  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. Automatically deactivate any scheduling of repository import profiles when import method changed to Upload Files/s

    When the import method of a repository import profile is changed to Upload File/s, any scheduling previously set for another import method should be automatically switched off.

    Currently the scheduling status for FTP/OAI has to be manually changed to inactive, in addition to changing the import method.

    This could easily be forgotten by staff making changes to import profiles and results in the scheduled metadata import jobs continuing to run and subsequently failing.

    The process would be streamlined and more efficient if scheduling could be automatically removed when an import profile is changed to an import method which does not allow any scheduling.

    When the import method of a repository import profile is changed to Upload File/s, any scheduling previously set for another import method should be automatically switched off.

    Currently the scheduling status for FTP/OAI has to be manually changed to inactive, in addition to changing the import method.

    This could easily be forgotten by staff making changes to import profiles and results in the scheduled metadata import jobs continuing to run and subsequently failing.

    The process would be streamlined and more efficient if scheduling could be automatically removed when an import profile is changed to an import method which does not… more

    0 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  ·  Resource Management - General  ·  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. Add 017 field (subfields a, b) in the search index.

    Currently this field (Copyright or Legal Deposit Number) is not indexed in MARC 21 Bibliographic Tag to Search Index Mapping. Would you please add it so that it?

    13 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  ·  Resource Management - General  ·  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. Preferred Term Correction job needs option to turn off the reordering of subfield URIs $$0

    We have implemented URIs into our bib records, but found that the Preferred Term Correction job is reordering the subfield $$0, where URIs are automatically clumped together at the end of the subject string and are no longer associated with the term. Even though the current best practice is for only one URI to be associated with the subject string and for it to be last in order, most subject headings with multiple subfields do not yet have a single identifier (URI) assigned to the entire subject string. There should be an option for the reordering to be turned off with this Authority Task, which would prevent overwhelming the Authority Task List notifications and allow for flexibility with managing 6xx, 65x, subfields in the future. The only solution to prevent Preferred Term Correction job from doing this is to disable the Authority Jobs in its entirety.

    Examples of results from job: 650 _0 |a Technological innovations |x Political aspects. |0 http://id.loc.gov/authorities/subjects/sh85133143 |0 http://id.loc.gov/authorities/subjects/sh00005651

    650 _0 |a Children of immigrants |z Germany |x Attitudes. |0 http://id.loc.gov/authorities/subjects/sh85023552 |0 http://id.loc.gov/authorities/names/n80125931 |0 http://id.loc.gov/authorities/subjects/sh2002006216

    We have implemented URIs into our bib records, but found that the Preferred Term Correction job is reordering the subfield $$0, where URIs are automatically clumped together at the end of the subject string and are no longer associated with the term. Even though the current best practice is for only one URI to be associated with the subject string and for it to be last in order, most subject headings with multiple subfields do not yet have a single identifier (URI) assigned to the entire subject string. There should be an option for the reordering to be turned off… more

    3 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  ·  Resource Management - General  ·  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