Hanoch Roniger
My feedback
10 results found
-
221 votes
Dear all, since this idea combines various very different enhancement requests for Alma's normalization rules infrastructure, we are unable to add these to our roadmap at this time. This may change as we get more information on prioritization and needs. In the meantime, we suggest opening dedicated ideas for specific enhancements you would like to promote.
An error occurred while saving the comment An error occurred while saving the comment Hanoch Roniger
commented
The site did not allow us to post the suggestions directly, only via attachment.
This is a list of the requested functions (the file also contains explanations & examples)
1. Position sensitive functions
2. Popup function
3. Identify & remove duplicate fields
4. Position sensitive removeSubField function
5. Functionality for Booleans in if conditions
6. Let the changeField also control indicators
7. Add the possibility to delete specific repeatable subfields based on contents
8. Possibility to check "when" conditionals after manipulation of the fields
9. Possibility to add several subfields with one function
10. Add functionality to copyField based on position
11. Add functionality to copyControlField based on position
12. Add the possibility to check if contents are the same
13. Check string length
14. Let functions run on several fields
15. Add mathematical functions / variables
16. Function for merging all subfields to a single subfield
17. Use metadata from within the NR
(See also: https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/18865093-normalization-rules-adding-dates)
18. Possibility to exchange data between holdings and bibliographical records
19. Add possibility to add/remove characters based on hex/Unicode to bypass problems with problematic characters
20. Add "View versions" to NRHanoch Roniger
shared this idea
·
-
78 votesHanoch Roniger
shared this idea
·
-
101 votesHanoch Roniger
supported this idea
·
-
126 votesHanoch Roniger
supported this idea
·
-
172 votesHanoch Roniger
supported this idea
·
-
249 votes
We will add this improvement to our roadmap
Hanoch Roniger
supported this idea
·
-
544 votes
Dear all,
I believe we now understand the requirement better: To be able to paste a block of text in MARC 21 format, and have Alma parse it and populate the MARC tags, indicators and subfields accordingly.
This is a larger development, but we hope to be able to add a solution for it to our future roadmap.
Hanoch Roniger
supported this idea
·
-
63 votes
Hi. 1. Are you stating that you want a new “Resource Type”?
2. The definitions of the resource types are explained in the table titled “Rules Used to Create the Resource Type Field – MARC 21/KORMARC and UNIMARC” at 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
3. Do you want a new row in this table which would be as follows?
Archival materials. LDR pos. 8 = a
4. The table is read top to bottom and as soon as match is found it stops. Where in the table would you like this new row to appear?
5. How come the title of this suggestion states “LDR pos. 8 = a” but the comment from Feb. 2 also has “LDR pos. 6 = p”? We do not think “LDR pos. 6 = p” is a good idea. That is used for “mixed materials”. On the other hand “LDR pos. 8…Hanoch Roniger
supported this idea
·
-
66 votes
Dear all, we would like to update that in addition to what was done in the May 2020 Release, we are looking at ways to allow libraries to select if diacritics should be taken into account in the linking process. We are exploring adding diacritics matching as a condition in the authority control rules to support flexibility, setting this for specific authority vocabularies only.
An error occurred while saving the comment Hanoch Roniger
commented
I agree with a caveat.
The combining diacritics are interchangeable with the legacy characters - I personally use combining characters where I can.
On the other hand, some of the LC romanization schemes use more than one kind of apostrophe to signify separate things.
An example from the LC romanization of Semitic languages:
ʻ (U+02BB) ʻayn
ʼ (U+02BC) alef
′ (U+2032) prime - "placed between two letters representing two distinct consonantal sounds when the combination might otherwise be read as a digraph" (this is also used in Armenian for the same purpose) -
396 votesHanoch Roniger
supported this idea
·
Please check (and support) the following suggestion:
https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/44068353-position-sensitive-nrs-normalization-rules-isb
It contains only #1, which is the most problematic to circumvent, especially when the field is repeatable
Since it only contains a single request, it might have a higher chance of being developed