Hanoch Roniger
My feedback
8 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
·
-
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
·
-
2 votes
An error occurred while saving the comment Hanoch Roniger
commented
As of June 2018 the solution I suggested is no longer valid as "$$" is not allowed and will break the NR (I found two inelegant solutions as a workaround).
In addition, I see no point in preventing a save because of a technical change required from the cataloger, it i seems that a better solution will be to autocorrect "‡" & "ǂ" into "$$" (when the are adjacent to a character) on save instead of getting an error message prompting you to make this exact change manually.
An error occurred while saving the comment Hanoch Roniger
commented
Dear mcorby,
We at the Hebrew University of Jerusalem have circumvented this problem by creating a NR that runs upon saving which changes the double daggers to $$please note that we used the character 'Latin letter alveolar click' (U+01C2) and not the double dagger ‡ (U+02021) because this is the one that is used in OCLC Connexion
I have pasted our NR below
Hope it could be of use to you,
Hanoch
----
rule "change double-dagger to $$"
when
(TRUE)
then
replaceContents "0**.*.ǂ" with "$$"
replaceContents "1**.*.ǂ" with "$$"
replaceContents "2**.*.ǂ" with "$$"
replaceContents "3**.*.ǂ" with "$$"
replaceContents "4**.*.ǂ" with "$$"
replaceContents "5**.*.ǂ" with "$$"
replaceContents "6**.*.ǂ" with "$$"
replaceContents "7**.*.ǂ" with "$$"
replaceContents "8**.*.ǂ" with "$$"
end -
2 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