Primo SP 4.8.2 Release Notes

1

Version No:4.8.2 - September 2014

Highlights:

General Documentation for Version:Located in the Version 4.x folder in the Ex Libris Documentation Center.

Primo version 4.8.2 includes a number of fixes that are primarily related to the Copy Citation feature. Another important fix relates to the display of the number of results, which—in some cases—is not consistent across pages of a blended result set.

2

4.8.2 Defect FixesItem Description Implementation Notes

3

4.8.2 Defect FixesModule Issue NumberRelated

Documentation

4

4.0.1 - 4.8 Defect FixesItem Description Implementation Notes Module

5

4.0.1 - 4.8 Defect FixesIssue NumberRelated

Documentation

6

4.5.1 Primo Central Defect FixesItem Description Implementation Notes Module

7

4.5.1 Primo Central Defect FixesIssue NumberRelated

Documentation

Item #17956The following changes were made to the Generic MARC template:

1. Field: browse/title Note: Recommended. This fix removes leading articles from the 440 tag based on the no-filing indicator. Description: An additional transformation was added to the rule for the 440 tag (#14): Drop non-filing text/ @@ind2@@

All of the following changes are due to the use of the new MARC 264 tag, which was added for RDA support. Basically, all of the rules for 260 were duplicated for 264. In addition, rules were added to make use of the 1st indicator in the 260 tag to give preference to the current publication information. All changes are recommended. The descriptions below just explain the change in general terms. Refer to the out-of-the-box template to see the current set of rules.

2. Field: display/publisher Description: All of the rules were re-worked. Priority is given to the following tags 502, 260-3 (current publisher). 264-31 (current publication information), 260 and 264 without indicators are used as catch-alls. There is an OR between all of the rules. The rules for 880 have been moved to the end, and they are added with a MERGE and a condition to prevent multiple entries.

3. Field: display/creationdate Description: Rules now use the following priority with an OR between them: 260-3, 26431, 260, 264, 008.

4. Field: search/creationdate Description: Duplicated the rules for 260 for 264. Since all dates are added (the action is “ADD”), there is no hierarchy in this set of rules.

5. Fields: search/startdate and search/enddate Description: Duplicated rules for 260-3 and 264-31 and added rules for 260 and 264 as catch-alls.

6. Field: search/general Description: Duplicated the rules for 260 for 264. Since all dates are added (the action is “ADD”), there is no hierarchy in this set of rules.

7. Field: facets/creationdate Description: added rules for 2603 and 264. Rules now use the following priority with an OR between them: 008, 260-3, 26431, 260, 264.

8. Field: dedup/c4 Description: added rules for 2603 and 264 for format=serials. Rules now use the following priority with an OR between them: 260-3, 26431, 260, 264.

9. Field: dedup/f6 Description: added rules for 2603 and 264. Rules now use the following priority with an OR between them: 008, 260-3, 26431, 260, 264.

10. Field: dedup/f10 Description: duplicated rules for both serial and non-serial formats. Rules now use the following priority with an OR between them: 260-3, 26431, 260, 264.

11. Field: addata/date: Description: Fixed rule to use an OR instead of an ADD (only 1st date is used) and added rules for 2603 and 264. Rules now use the following priority with an OR between them: 260-3, 26431, 260, 264.

12. Field: addata/risdate Description: Added rules for 260-3 and 264. Rules now use the following priority with an OR between them: 260-3, 26431, 260, 264.

13. Field: sort/creationdate Description: Added rules for 260-3 and 264. Rules now use the following priority with an OR between them: 008, 260-3, 26431, 260, 264.

Item #17957The following changes were made to the ALEPH MARC template:


All of the following changes are due to the use of the new MARC 264 tag, which was added for RDA support. Basically, all of the rules for 260 were duplicated for 264. In addition, rules were added to make use of the 1st indicator in the 260 tag to give preference to the current publication information. All changes are recommended. The descriptions below just explain the changes in general terms. Refer to the out-of-the-box template to see the current set of rules.

2. Field: display/publisher Description: All of the rules were re-worked. Priority is given to following tags 502, 260-3 (current publisher). 264-31 (current publication information), 260 and 264 without indicators are used as catch-alls. There is an OR between all rules. The rules for 880 have been moved to the end, and they are added with a MERGE and a condition to prevent multiple entries.


4. Field: search/creationdate Description: Duplicated the rules for 260 and 264. Since all dates are added (the action is “ADD”), there is no hierarchy in this set of rules.


6. Field: search/general Description: Duplicated the rule for 260 for 264. Since all dates are added (the action is “ADD”), there is no hierarchy in this set of rules.








Item #17958The following changes were made to the Alma MARC template:


All of the following changes are due to the use of the new MARC 264 tag, which was added for RDA support. Basically, all of the rules for 260 were duplicated for 264. In addition, rules were added to make use of the 1st indicator in the 260 tag to give preference to the current publication information. All changes are recommended. The descriptions below just explain the changes in general terms. Refer to the out-of-the-box template to see the current set of rules.

2. Field: display/publisher Description: All of the rules were re-worked. Priority is given to following tags 502, 260-3 (current publisher). 264-31 (current publication information), 260 and 264 without indicators are used as catch-alls. There is an “OR” between all rules. The rules for 880 have been moved to the end, and they are added with a MERGE and a condition to prevent multiple entries.


4. Field: search/creationdate Description: Duplicated the rules for 260 for 264. Since all dates are added (the action is “ADD”), there is no hierarchy in this set of rules.


6. Field: search/general Description: Duplicated the rules for 260 for 264. Since all dates are added (the action is “ADD”), there is no hierarchy in this set of rules.








Item #17959The following changes were made to the DigiTool MARC template:


All of the following changes are due to the use of the new MARC 264 tag added, which was added for RDA support. Basically, all of the rules for 260 were duplicated for 264. In addition, rules were added to make use of the 1st indicator in the 260 tag to give preference to the current publication information. All changes are recommended. The descriptions below just explain the change in general terms. Refer to the out-of-the-box template to see the current set of rules.

2. Field: display/publisher Description: All of the rules were re-worked. Priority is given to the following tags 502, 260-3 (current publisher). 264-31 (current publication information), 260 and 264 without indicators are used as catch-alls. There is an “OR” between all rules. The rules for 880 have been moved to the end, and they are added with a MERGE and a condition to prevent multiple entries.


4. Field: search/creationdate Description: Duplicated the rule for 260 for 264. Since all dates are added (the action is “ADD”), there is no hierarchy in this set of rules.







11. Field: addata/date: Description: Fixed rule to use “OR” instead of “ADD” (only 1st date is used) and added rules for 2603 and 264. Rules now use the following priority with an OR between them: 260-3, 26431, 260, 264.



Item #17960The following changes were made to the SFX template:


All of the following changes are due to the use of the new MARC 264 tag added for RDA support. Basically, all of the rules for 260 were duplicated for 264. In addition, rules were added to make use of the 1st indicator in the 260 tag to give preference to the current publication information. All changes are recommended. The descriptions below just explain the change in general terms. Refer to the out-of-the-box template to see the current set of rules.

2. Field: display/publisher Description: All the rules were re-worked. Priority is given to the following tags 502, 260-3 (current publisher). 264-31 (current publication information), 260 and 264 without indicators are used as catch-alls. There is an “OR” between all rules. The rules for 880 have been moved to the end. They are added with a MERGE and a condition to prevent multiple entries.

3. Field: display/creationdate Description: Rules now use the following priority with OR between them: 260-3, 26431, 260, 264, 008.

4. Field: search/creationdate Description: Duplicated the rule for 260 for 264. Since all dates are added (the action is “ADD”) there is no hierarchy in this set of rules.







11. Field: addata/date: Description: Fixed rule to use “OR” instead of “ADD” (only 1st date is used) and added rules for 2603 and 264. Rules now use the following priority with an OR between them: 260-3, 26431, 260, 264.



Item #17961The following changes were made to the Unicorn template:

1. Field: browse/title Note: Recommended. This fix removes leading articles from the 440 tag based on no-filing indicator. Description: An additional transformation was added to the rule for the 440 tag (#14): Drop non-filing text/ @@ind2@@

All the following changes are due to the use of the new MARC 264 tag, which was added for RDA support. Basically, all the rules for 260 were duplicated for 264. In addition, rules were added to make use of the 1st indicator in the 260 tag to give preference to the current publication information. All changes are recommended. The descriptions below just explain the change in general terms. Refer to the out-of-the-box template to see the current set of rules.

2. Field: display/publisher Description: All the rules were re-worked. Priority is given to following tags 502, 260-3 (current publisher). 264-31 (current publication information), 260 and 264 without indicators are used as catch-alls. There is an “OR” between all rules. The rules for 880 have been moved to the end, and they are added with a MERGE and a condition to prevent multiple entries.

3. Field: display/creationdate Description: Rules now use following priority with OR between them: 260-3, 26431, 260, 264, 008.




7. Field: facets/creationdate Description: added rules for 2603 and 264. Rules now use the following priority with OR between them: 008, 260-3, 26431, 260, 264.

8. Field: dedup/c4 Description: added rules for 2603 and 264 for format=serials. Rules now use the following priority with OR between them: 260-3, 26431, 260, 264.

9. Field: dedup/f6 Description: added rules for 2603 and 264. Rules now use the following priority with OR between them: 008, 260-3, 26431, 260, 264.

10. Field: dedup/f10 Description: duplicated rules for both serial and non-serial formats. Rules now use the following priority with OR between them: 260-3, 26431, 260, 264.

11. Field: addata/date: Description: Fixed rule to use “OR” instead of “ADD” (only 1st date is used) and added rules for 2603 and 264. Rules now use following priority with OR between them: 260-3, 26431, 260, 264.

12. Field: addata/risdate Description: Added rules for 260-3 and 264. Rules now use following priority with OR between them: 260-3, 26431, 260, 264.

13. Field: sort/creationdate Description: Added rules for 260-3 and 264. Rules now use the following priority with OR between them: 008, 260-3, 26431, 260, 264.

Item #17962The following changes were made to the Voyager template:

1. Field: browse/title Note: Recommended. This fix will remove leading articles from the 440 tag based on no-filing indicator. Description: An additional transformation was added to the rule for the 440 tag (#14): Drop non-filing text/ @@ind2@@

All the following changes are due to the use of the new MARC 264 tag, which was added for RDA support. Basically, all the rules for 260 were duplicated for 264. In addition, rules were added to make use of the first indicator in the 260 tag to give preference to the current publication information. All changes are recommended. The descriptions below just explain the change in general terms. Refer to the out-of-the-box template to see the current set of rules.

2. Field: display/publisher Description: All of the rules were re-worked. Priority is given to following tags 502, 260-3 (current publisher). 264-31 (current publication information), 260 and 264 without indicators are used as catch-all’s. There is an “OR” between all rules. The rules for 880 have been moved to the end. They are added with a MERGE and with a condition to prevent multiple entries.

3. Field: display/creationdate Description: Rules now use following priority with an OR between them: 260-3, 26431, 260, 264, 008.


5. Fields: search/startdate and search/enddate Description: Duplicated rules for 260-3 and 264-31 and added rules for 260 and 264 as catch-all’s.


7. Field: facets/creationdate Description: added rules for 2603 and 264. Rules now use following priority with OR between them: 008, 260-3, 26431, 260, 264.


9. Field: dedup/f6 Description: added rules for 2603 and 264. Rules now use following priority with an OR between them: 008, 260-3, 26431, 260, 264.

10. Field: dedup/f10 Description: duplicated rules for both serial and non-serial formats. Rules now use following priority with an OR between them: 260-3, 26431, 260, 264.

11. Field: addata/date: Description: Fixed rule to use “OR” and not “ADD” (only 1st date is used) and added rules for 2603 and 264. Rules now use the following priority with an OR between them: 260-3, 26431, 260, 264.



Item #18245The following changes were made to the Alma MARC normalization rules template:

1.Field: dedup/c5Note: Mandatory to ensure that Primo always dedups based on the MMS ID. It is necessary to re-pipe your Alma data source. For more details refer to item #17349.Description:The following rule was added: Source: MARC 001 Transformation: Copy as is Action: OR

2. Field: addata/au Note: Recommended. This fix remove data that should not be included in the RIS format. Description: The input of the rule for the 100 tag was changed from 100 a,b,c,d,e,j,q,u to 100 a,b,q

3. Field: addata/addau Note: Recommended. This fix remove data that should not be included in the RIS format. Description: The input of the rule for the 700 tag was changed from 700 a,b,c,d,e,j,q,u to 700 a,b,q

4. Fields: dedup/f4 & dedup/f5 Note: Recommended. This fix normalizes incorrect ISSN and ISBN by removing hyphens. A re-pipe of all data is recommended to ensure consistency in dedup. Description: Added an additional transformation (as the last one) to the rules for 020 and 022: Delete characters/-

Item #18466The following changes were made to the Voyager normalization rules template:

A. Changes for enhanced support of Browse. Voyager 8.2.1 (which will be released in March) supports the publishing of additional information that Primo needs to be able to display cross-references in the authors and subjects browse lists, subject type in the subjects browse list, and separate call number browse lists. After you have installed the necessary upgrade, you should modify the setup for the Primo extract in the PprimoExp-*.ini so that the parameter 'InsertPrimoBrowseTags' is set to 'Y' and then re-harvest all of the data. For more information, refer to the Voyager - Primo Integration guide. In parallel, you should update the Primo normalization rules as described below.

1. Field: browse/author Note: Mandatory if you want to display cross-references in the authors browse list Description: Added to all the browse/author fields rules to create $$I with the ID of the linked authority record (source subfield - $$0) and $$P with the Preferred heading indicator (source subfield - $$9).

2. Field: browse/subject Note: Mandatory if you want to display cross-references in the subjects browse list Description: Added to all the browse/subject fields rules to create $$I with the ID of the linked authority record (source subfield - $$0), $$P with the Preferred heading indicator (source subfield - $$9) and $$T with the subject type (source subfield - $$2).

3. Field: browse/callnumber Note: Mandatory if you want to have separate call number lists per call number type - LC, Dewey, Sudoc. Note that you also need to activate the lists in the Browse Lists mapping table so they display in the Front End. Description: Added a rule to create $$T with the type from the source subfield k.

4. Fields: display/creator & display/contributor & display/subject Note: Mandatory to prevent display of non-preferred authors and subjects in the "Details" tab. Description: A condition to check if the author is the preferred term has been added to all of the rules (except those with the source tag 880). The condition checks the content of the source subfield $$9 for the current MARC field. The condition is structured as follows: Conditions logic: True Condition -1 Logic: False Source: MARC <MARC tag> subfield 9 Success if: Match Current Routine : Check string equals string/N

5. Field: facets/Creatorcontrib Note: Mandatory to prevent display of non-preferred authors and subjects in facets. Description: A condition to check whether the subject is the preferred term has been added to all of the rules. The condition checks the content of the source subfield $$9 for the current MARC field. The condition is structured as follows: Conditions logic: True Condition -1 Logic: False Source: MARC <MARC tag> subfield 9 Success if: Match Current Routine : Check string equals string/N

B. Additional updates:

1. Field: addata/au Note: Recommended. This fix remove data that should not be included in the RIS format. Description: The input of the rule for the 100 tag was changed from 100 a,b,c,d,e,j,q,u to 100 a,b,q

2. Field: addata/addau Note: Recommended. This fix remove data that should not be included in the RIS format. Description: The input of the rule for the 700 tag was changed from 700 a,b,c,d,e,j,q,u to 700 a,b,q


25

Item #18541The following changes were made to the Aleph MARC normalization rules template:

A. Aleph - v.21.1 (rep_change 002112) and v.20 (rep_change 003801) - now supports the publishing of additional information that Primo needs to display cross-references in the authors and subjects browse lists, subject type in the subjects browse list, and separate call number browse lists. Once you have installed the necessary upgrade, you will need to change the setup in Aleph Publishing for Primo to use the 'expand_doc_bib_accref' expand routine (instead of expand_doc_bib_accref_1) with the new ADDITIONAL-INFO parameter and re-harvest all of the records. For more information, refer to the How to Configure Aleph - Primo Interoperability document in the Documentation Center. In parallel, you should update the Primo normalization rules as described below.

1. Field: browse/author Note: Mandatory if you want to display cross-references in the authors browse list. Description: Added to all the browse/author fields rules to create $$I with the ID of the linked authority record (source subfield - $$0) and $$P with the Preferred heading indicator (source subfield - $$P).

2. Field: browse/subject Note: Mandatory if you want to display cross-references in the subjects browse list.

Description: Added to all of the browse/subject fields rules to create $$I with the ID of the linked authority record (source subfield - $$0), $$P with the Preferred heading indicator (source subfield - $$P) and $$T with the subject type (source subfield - $$2).

3. Field: browse/callnumber Note: Mandatory if you want to have separate call number lists per call number type - LC, Dewey, Sudoc. Note that you also need to activate the lists in the Browse Lists mapping table so they display in the Front End. Description: Added a rule to create $$T with the type from the source subfield k.

4. Fields: display/creator & display/contributor & display/subject Note: Mandatory to prevent display of non-preferred authors and subjects in the "Details" tab. Description: A condition to check if the author is the preferred term has been added to all the rules (except those with the source tag 880). The condition checks the content of the source subfield $$P for the current MARC field. The condition is structured like this: Conditions logic: True Condition -1 Logic: False Source: MARC <MARC tag> subfield P Success if: Match Current Routine : Check string equals string/N

26

Item #18541

5. Field: facets/Creatorcontrib Note: Mandatory to prevent display of non-preferred authors and subjects in facets. Description: A condition to check whether the subject is the preferred term has been added to all of the rules. The condition checks the content of the source subfield $$P for the current MARC field. The condition is structured like this: Conditions logic: True Condition -1 Logic: False Source: MARC <MARC tag> subfield P Success if: Match Current Routine : Check string equals string/N

B. Additional updates:

1. Field: addata/au Note: Recommended. This fix removes data that should not be included in the RIS format. Description: The input of the rule for the 100 tag was changed from 100 a,b,c,d,e,j,q,u to 100 a,b,q

2. Field: addata/addau Note: Recommended. This fix removes data that should not be included in the RIS format. Description: The input for the 700 tag rule was changed from 700 a,b,c,d,e,j,q,u to 700 a,b,q


27

Item #19585Until now, all records retrieved via the Ebsco API were automatically assigned the article resource type. Now, Primo maps the Ebsco resource types to the out-of-the-box Primo resource types in the following PNX fields: display/type, addata/ristype, addata/genre, addata/format. In addition, Primo will map the resource type pre-filter and resource type facets to the Ebsco resource types when the query is sent to Ebsco. For more information on the mapping, see the EBSCO API section in the Primo Back Office Guide.

It is possible to override the out-of-the-box mapping by including the following parameters in the EbscoLocal section of the thirdnode configuration in the /exlibris/primo/p4_X/ng/primo/home/system/search/conf/thirdnode-config.xml file.

* rtype_to_ebsco - Maps the Primo resource type facet to Ebsco types. Every Primo type should be mapped to a single Ebsco type. Note the different Primo types can be mapped to the same Ebsco type. The structure should be <Primo type>, <EBSCO type> with additional mappings separated by a semicolon. If this parameter does not exist in the configuration file, the default mappings will be used. Example:

• rtype_to_ebsco = other,Abstract;articles,Article;other,Bibliography;....

* ebsco_to_display_type - Maps the EBSCO resource type to the Primo display/type field. Every EBSCO type should be mapped to a single Primo type. The structure should be <EBSCO type, Primo Type> with additional mappings separated by a semicolon. If this parameter does not exist in the configuration file, the default mappings will be used. Example:

• ebsco_to_display_type = Abstract,other;Article,article;Bibliography,other;....

* ebsco_to_ris_type - Maps the Ebsco resource type to the Primo addata/ristype field. Every Ebsco type should be mapped to a single Primo type. The structure should be <Ebsco type, Primo Type> with the different mappings separated with semicolon. If this parameter does not exist in the configuration file the default mappings will be taken. Example:

• ebsco_to_ris_type = Abstract,GEN;Article,JOUR;Bibliography,GEN;Biography,BOOK;....

* DEFAULT_EBSCO_TO_PRIMO_FORMAT_TYPE - Maps the Ebsco resource type to the Primo addata/format field.This is a one-to-one relation meaning that every Ebsco type must be mapped to a single Primo type. Mappings should be structured as (EBSCO_TYPE,PRIMO_TYPE) and different mappings should be separated with semicolon. If this parameter does not exist on the configuration file, default mappings will be taken. \For example:

• ebsco_to_format_type = Abstract,book;Article,journal;Bibliography,book;Biography,book;...

* ebsco_to_genere_type - Maps the Ebsco resource type to the Primo addata/genre field. Every Ebsco type should be mapped to a single Primo type. The structure should be <Ebsco type, Primo Type> with the different mappings separated with semicolon. If this parameter does not exist in the configuration file the default mappings will be taken. Example:

• ebsco_to_genere_type = Abstract,unknown;Article,article;Bibliography,unknown;Biography,book;...


1. Several changes were made to the template related to Browse support. For complete details, refer to the Primo Version 4 Highlights document.

2. Several changes were made to make use of the "Available For settings for E-Resources" which are added as AVE fields in the records published to Primo. The "Available For" feature was added in the Alma August release. Two changes were made:

Field: delivery/institution Note: adding this field will ensure that if an institution's subscriptions are handled by another institution or the network zone, this institution will be added to the PNX as one of the institutions that own the record. Description: The action was changed from "OR" to "ADD" A new rule was added as the 2nd rule: Source: MARC AVE i Transformation: Use mapping table/Alma Institution Codes

Field: search/searchscope Note: adding these fields will enable you to create search scopes for a specific campus or library in terms of E records. You will still need to define the scope values as well as add the scopes to the View.

Description: Two rules were added to the end Rule 1: Source: MARC AVE i,c Conditions logic: true Condition 1: Condition 1 logic: true Source: MARC AVE c Success if: Match current Validation routine: Input exists Transformations: Copy as is Delete spaces Action: ADD

Rule 2: Source: MARC AVE i,l Conditions logic: true Condition 1: Condition 1 logic: true Source: MARC AVE l Success if: Match current Validation routine: Input exists Transformations: Copy as is Delete spaces Action: ADD

3. Field: search/title Note: Recommended. It is now possible to index up to three fields for an exact title match. Refer also to #20508. This will improve ranking of journal title searches. In addition for other records, it is recommended to index only 245 subfields: a,b,f,g,n,p. Description: * The source of the rule for 245 was changed from a,b,f,g,k,n,p to a,b,f,g,n,p. In addition, the following condition was added:

Conditions logic: True Condition 1 logic: False Condition 1 Source: PNX display/type Success if: Match last Validation routine: Check string equals string/journal

The Action should be "OR"

* The rule for 130 tag was deleted.

* In addition the following rules were added:

Source: MARC 245 a Conditions logic: True Condition 1 logic: True Condition 1 Source: PNX display/type Success if: Match last Validation routine: Check string equals string/journal Transformation: Copy as is Action: ADD

Source: MARC 245 a,b,f,g,n,p Conditions logic: True Condition 1 logic: True Condition 1 Source: PNX display/type Success if: Match last Validation routine: Check string equals string/journal Transformation: Copy as is Action: ADD


4. Field: addata/date Note: Recommended Description: The source of the fourth rule was changed from 266 to 260.

Item #20121The following changes were made to the Aleph MARC normalization rules template:






* In addition, the following rules were added:



Source: MARC 130 a Conditions logic: True Condition 1 logic: True Condition 1 Source: PNX display/type Success if: Match last Validation routine: Check string equals string/journal Transformation: Copy as is Action: ADD 3. Field: addata/date Note: Recommended Description: The source of the fourth rule was changed from 266 to 260.












Item #20123The following changes were made to the Generic MARC normalization rules template:






Source: MARC 245 a Conditions logic: True Condition 1 logic: True Condition 1 Source: PNX display/type Success if: Match last

Validation routine: Check string equals string/journal Transformation: Copy as is Action: ADD



2. Field: addata/date Note: Recommended Description: The source of the 4th rule was changed from 266 to 260.

Item #20124The following changes were made to the DigiTool MARC normalization rules template:











Item #20125The following changes were made to the SFX normalization rules template:











Item #20126The following changes were made to the Unicorn normalization rules template:

1. Field: search/title Note: Recommended. It is now possible to index up to three fields for an exact title match. Refer also to #20508. This will improve ranking of journal title searches. In addition for other records, it is recommended to index only 245 subfields: a,b,f,g,n,p. Description: * The source of the rule for 245 was changed from a,b,f,g,k,n,p to a,b,f,g,n,p. In addition the following condition was added:










Item #21946The following changes were made to the Alma MARC Template.

A. Support for Alma Centralized Publishing (see also #21341).

These changes are relevant only to Alma consortia using the Centralized Publishing Mode. The template continues to support the standard publishing mode.

The rules for the following fields have been modified:

Control/almaid - the almaid combines the Alma institution and the IE-ID. Until now, the almaid was created from INST $$a and the control/sourcerecordid ID. Now it is also be created from INST $$a and INST $$b. INST $$b will be published only in the Centralized Publishing mode.

Search/Additional Source Record Id - this field will also be created from the MSS field, which includes the institutional MSS field. The MSS field is published only in the Centralized Publishing mode.

Search/Search Scope - the rules for the creation of the AZ<institution> scope for the A-Z eJournal list have been modified. There are now four rules - two that will create AZ<institution> scope for regular publishing and two that creates the AZ<institution> scope for Centralizing Publishing records. The following rules have been added instead of the existing single rule:

Rule 5 Source: PNX delivery/institution Conditions logic: True Conditions relation : And Condition 1 Source: PNX delivery/delcategory Match if: Match last Routine: Check string equals string/Alma-E Conditon 2 Source: PNX display/type Match if: Match last Routine: Check string equals string/journal Transformations: Copy as is Add to beginning of string/AZ Action: ADD

Rule 6 - same as rule 5 except that the first condition checks for Online Resource and this is also the text that is removed by the transformation.

Rule 7 Source: PNX delivery/delcategory Conditions logic: True Conditions relation : And Condition 1 Source: PNX delivery/delcategory Match if: Match current Routine: Check string equals string/Alma-E$$I Conditon 2 Source: PNX display/type Match if: Match last Routine: Check string equals string/journal Transformations: Copy as is Remove Leading String/Alma-E$$I Add to beginning of string/AZ Action: ADD

Rule 8 - same as rule 7 except that the first condition checks for Online Resource$$I and this is also the text that is removed by the transformation.

Delivery/Institution. The action was changed to "ADD" to ensure that multiple INST fields are processed.

Delivery/Delivery Category. Rules 1 and 2 were added. The delivery category for Centralized Publishing is stored in INST $$b. Rules were added to take this into account. In addition, in order to ensure that the delivery category can be assigned per institution, $$I is now appended to the delivery category. Refer to #15305 for more information about having a delivery category per institution in the PNX.

B. Support for AVE field

These changes are only relevant to customers using the "Available For (E-Resource)" functionality. The changes are intended to make sure that an institution field and delivery category per institution are created based on the AVE field. Note that the Alma multicampus scenario in which every Alma campus is defined as a Primo institution is not supported in the out-of-the-box rules. Refer to Primo Version 4 Highlights document for more information on support for Alma multicampus.

The rules for the following fields has been changed:

delivery/institution - Rule 2 was added to ensure that an institution is created per AVE $$i. delivery/delivery category - Rule 3 was added to ensure that a delivery category is created per AVE $$i with the institution in $$I.

C. Additional changes

1. Field: sort/creationdate Note: Recommended. These changes ensure that the sort creation date is the same as the display creation date. Previously, the sort/creation date was first created from 008 while the display/creation date was created based on 260 $$c. In some cases, the data was not consistent, causing a mismatch between the sort and display. Note that the database needs to be re-indexed from scratch to benefit from this fix. For information on re-indexing, see the Performing System Cleanup – Re-Indexing the Database section in the Primo System Administration Guide.

Description: The order of the rules was changed to ensure that it is in the same order as the rules of display/creationdate.

2. Field: facets/creationdate Note: Recommended. These changes ensure that the facets creation date is the same as the display creation date. Previously, the facets/creation date was first created from 008 while the display/creation date was created based on 260 $$c. In some cases, the data was not consistent, causing a mismatch. Note that the database needs to be re-indexed from scratch to benefit from this fix. For information on re-indexing, see the Performing System Cleanup – Re-Indexing the Database section in the Primo System Administration Guide.


3. Field: dedup/c10 Note: Recommended. This field is not in use by dedup. Keeping it will not create problems, but it serves no purpose. The c5 field is used for dedup and is based on Alma MSS.

Description: The rules for dedup/c10 were deleted. The rules created c10 from the 001 tag. It was a duplicate of the rules for c5.

Item #21996Previously, only the "Upper case every first letter" was available for use in the normalization rules editor. Now there are three additional transformations that can be used to change text to uppercase:

1. "Upper case every first letter (lower case others)" --> this is the original transformation, which will be automatically updated during the upgrade. 2. "Upper case every first letter" 3. "Upper case every first letter - whitespace only (lower case others)" 4. "Upper case every first letter - whitespace only"

The following rules apply to the transformations: - Transformations 1 and 3 capitalize the first letter of each word and make sure that all others characters are lowercase. - Transformations 2 and 4 capitalize the first letter of each word, leaving the other input characters in their original case. - Transformations 1 and 2 define a word as any string separated by a space or punctuation. - Transformations 3 and 4 define a word as any string separated by white space only.

In addition, all of these transformations accept a normalization mapping table name as a parameter. This mapping table can be used to define words that should be ignored by the transformation. The source column contains the word that you want to exclude, and the target column contains the transformation. The same word can be added to both source and target to ensure that they are not transformed at all. For example:

Source: and Target: and

For example, if the normalization uses the 'Upper case every first letter (lower case others)' transformation and the input is "barnes and noble," the output will be "Barnes and Noble."

Item #22015The 'Extract and arrange XML elements' normalization rule transformation has been added to extract child nodes from an XML element in a specific order when there are multiple occurrences of the XML element. The transformation handles every element separately. The transformation was added because it was difficult to get this level of control with multiple elements.

The input to the transformation should be a simple XML structure, such as the following: <parent> <child1>data1</child1> <child2>data2</child2> <child3>data3</child3> </parent>

The transformation has the following parameters (separated with @@). At least one parameter must be added. 1. Output order - the order of the elements constructing the output (element name separated with ;). 2. Delimiter string - a string delimiter to place between each element. 3. Delete others - an indication that says whether to delete fields not specified on the output order. 4. Delete tag names - an indication that says whether to delete tag names from the output.

Parameters Notes: * At least one parameter is mandatory. * The order of the parameters must be retained; if any parameter is not used, the '@@" delimiter still should be used. For example, if the output order and delete tag names are the only ones needed, enter – param1@@@@@@param4. * To add space as a delimiter, use '\s' as the delimiter string parameter. * Default values for Delete others and Delete tag names parameters are false. If you want to use one of them, use 'D' (Delete) as the parameter value (for example, param1@@param2@@D@@D). * If the output order parameter is not specified and the Delete others parameter is not set to true, all data elements will be used in a random order and the XML order will not be preserved.

Examples (for the XML on top): * chid2;child1@@\s will result in: <child2>data2</child2> <child1>data1</child1> <child3>data3</data3> * chid2;child1@@\s@@D will result in: <child2>data2</child2> <child1>data1</child1> * chid2;child1@@\s@@D@@D will result in data2 data1 * chid2;child1@@@@D@@D will result in data2data1

Item #22191


The following changes were made to the Generic MARC Template.

1. Field: sort/creationdate Note: Recommended. The changes ensure that the sort creation date is the same as the display creation date. Previously, the sort/creation date was first created from 008 while the display/creation date was created based on 260 $$c. In some cases, the data was not consistent, causing a mismatch. Note that the database needs to be re-indexed from scratch to benefit from this fix. Instructions can be located in the Performing System Cleanup – Re-Indexing the Database section in the Primo System Administration Guide. Description: The order of the rules was changed to ensure that it is in the same order as the rules of display/creationdate.

2. Field: facets/creationdate Note: Recommended. The changes ensure that the facets creation date is the same as the display creation date. Previously, the facets/creation date was first created from 008 while the display/creation date was created based on 260 $$c. In some cases, the data was not consistent, causing a mismatch. Note that the database needs to be re-indexed from scratch to benefit from this fix. Instructions can be located in the Performing System Cleanup – Re-Indexing the Database section in the Primo System Administration Guide.

Item #22192The following changes were made to the SFX Template.




Item #22193The following changes were made to the DigiTool MARC Template.


2. Field: facets/creationdate Note: Recommended. The changes ensure that the facets creation date is the same as the display creation date. Previously, the facets/creation date was first created from 008 while the display/creation date was created based on 260 $$c.In some cases, the data was not consistent, causing a mismatch. Note that the database needs to be re-indexed from scratch to benefit from this fix. Instructions can be located in the Performing System Cleanup – Re-Indexing the Database section in the Primo System Administration Guide.


46

Item #22194The following changes were made to the Voyager Template.




47

Item #22195The following changes were made to the Unicorn Template.

1. Field: sort/creationdate Note: Recommended. The changes ensure that the sort creation date is the same as the display creation date. Previously, the sort/creation date was first created from 008 while the display/creation date was created based on 260 $$c. In some cases, the data was not consistent, causing a mismatch between the sort and display. Note that the database needs to be re-indexed from scratch to benefit from this fix. Instructions can be located in the Performing System Cleanup – Re-Indexing the Database section in the Primo System Administration Guide. Description: The order of the rules was changed to ensure that it is in the same order as the rules of display/creationdate.

2. Field: facets/creationdate Note: Recommended. The changes ensure that the facets creation date is the same as the display creation date. Previously, the facets/creation date was first created from 008 while the display/creation date was created based on 260 $$c. In some cases, the data was not consistent, causing a mismatch. Note that the database needs to be re-indexed from scratch to benefit from this fix. Instructions can be located in the Performing System Cleanup – Re-Indexing the Database section in the Primo System Administration Guide. Description: The order of the rules was changed to ensure that it is in the same order as the rules of display/creationdate.

48

Item #22196The following changes were made to the Aleph MARC Template.

1. Field: sort/creationdate Note: Recommended. The changes ensure that the sort creation date is the same as the display creation date. Previously, the sort/creation date was first created from 008 while the display/creation date was created based on 260 $$c. In some cases, the data was not consistent, causing a mismatch between the sort and display. Note that the database needs to be re-indexed from scratch to benefit from this fix. Instructions can be located in the Performing System Cleanup – Re-Indexing the Database section in the Primo System Administration Guide. Description: The order of the rules was changed to ensure that it is in the same order as the rules of display/creationdate.

2. Field: facets/creationdate Note: Recommended. The changes ensure that the facets creation date is the same as the display creation date. Previously, the facets/creation date was first created from 008 while the display/creation date was created based on 260 $$c. In some cases, the data was not consistent, causing a mismatch. Note that the database needs to be re-indexed from scratch to benefit from this fix. Instructions can be located in the Performing System Cleanup – Re-Indexing the Database section in the Primo System Administration Guide. Description: The order of the rules was changed to ensure that it is in the same order as the rules of display/creationdate.

IN #22524Customers using the Talis RTA program as a locally-installed plugin should enable the out-of-the-box plugin:

1. Disable the existing RTA plugin from the Plugins mapping table. 2. Disable all the parameters defined for the plugin in the Plugin parameters mapping table. 3. Make sure that the TalisRTAPlugin RTA Plugin program is enabled in the Plugins mapping table. 4. Add all necessary parameters to the TalisRTAPlugin in the Plugins parameters mapping table. Note that the out-of-the-box value for the SourceSystem' parameter is Talis. Change the value to the source system you have in the control/sourcesystem field in the PNX records harvested from Talis (It may be Other.). 5. Deploy the RTA Configuration option on the Deploy All page.

The Talis RTA Plugin has the following parameters:

* IdentifierXPath – the out-of-the-box value is 'record/control/sourcerecordid' * SourceSystem – the out-of-the-box value is 'Talis'

The following parameters have not been added to the mapping table out of the box, but they can be added locally:

* Debug (true/false). This parameter adds additional details to the library_server log. The default is 'false'. * Location (text) – this is a default location required by the Talis RTA API. The default is 'Main%20Catalogue' * LibraryCodes (Primo mapping table) - The mapping table for used to map Talis source library codes to Primo Library codes. The default is 'ILS Library Codes'. * Timeout (in milliseconds) - Connection time out for Talis RTA requests. The default is 1000. * KillNonWords (true/false) – This parameter can be used to normalize the location in the Talis response. It replaces spaces with an underscore and strips all characters except for digits, letters, and underscores. The default is 'false'. * ToUpper (true/false) - This parameter can be used to normalize the location in the Talis response. It convert the location to uppercase. The default is false. * ToLower (true/false) - This parameter can be used to normalize the location in the Talis response. It converts the location to lowercase. The default is false.

Item #22810The following changes were made to the Aleph danMARC2 normalization rules template:

1. Field:display/availlibrary Note: It is required to be able to use Aleph priorities defined for locations. For more information, see the Location Priority for Aleph and Voyager (V4.8) section in the Primo Version 4.x Highlights document.Description: Added a rule at end to create $$P from $$p AVA/949, which contains the priority of the location. 2. Field: addata/metadata Note: Optional. An additional rule was added to create Metadata Type = 'journal' if the resource type is 'conference_proceeding' and the record has an ISSN. Otherwise, it will default to a book. See also #22807, which includes changes in the Metadata Type mapping table. This is relevant if your local data includes this resource type. Description: The following rule was added as the second rule: Source: PNX display/type Conditions logic: true Conditions relation: And Condition1 Logic: true Source: PNX display/type Success if: Match last Validation: Check if string equals string/conference_proceeding Condition2: Logic: true Source: search/issn Success if: Match last Validation: Input exists Transformation Write constant/journal Action: OR

Item #22811The following changes were made to the Aleph KORMARC normalization rules template: 1. Field: display/availlibrary Note: This is required if you want to control the order of the Primo locations based on the priority defined in Aleph. For more information, see the Location Priority for Aleph and Voyager (V4.8) section in the Primo Version 4.x Highlights document. Description: A rule was added at the end to create $$P from AVA $$p, which contains the priority of the location.

2. Field: addata/metadata Note: Optional. An additional rule was added to create Metadata Type = 'journal' if the resource type is 'conference_proceeding' and the record has an ISSN. Otherwise, it will default to a book. See also #22807, which includes changes in the Metadata Type mapping table. This is relevant if your local data includes this resource type. Description: The following rule was added as the second rule: Source: PNX display/type Conditions logic: true Conditions relation: And Condition1 Logic: true Source: PNX display/type Success if: Match last Validation: Check if string equals string/conference_proceeding Condition2: Logic: true Source: search/issn Success if: Match last Validation: Input exists Transformation Write constant/journal Action: OR

Item #22812The following changes were made to the Aleph MARC normalization mapping table:

1. Field: display/availlibrary Note: This is required if you want to control the order of the Primo locations based on the priority defined in Aleph. For more information, see the Location Priority for Aleph and Voyager (V4.8) section in the Primo Version 4.x Highlights document. Description: A rule was added at the end to create $$P from AVA $$p, which contains the priority of the location.

2. Field: addata/metadata Note: Optional. An additional rule was added to create Metadata Type = 'journal' if the resource type is 'conference_proceeding' and the record has an ISSN. Otherwise, it will default to a book. See also #22807, which includes changes in the Metadata Type mapping table. This is relevant if your local data includes this resource type. Description: The following rule was added as the second rule: Source: PNX display/type Conditions logic: true Conditions relation: And Condition1 Logic: true Source: PNX display/type Success if: Match last Validation: Check if string equals string/conference_proceeding Condition2: Logic: true Source: search/issn Success if: Match last Validation: Input exists Transformation Write constant/journal Action: OR

3. Field: browse/title Note: This is recommended if the relevant fields contain subfield 0 with the authority record ID. Description: Subfield 0 has been excluded from the source of the rules for the tags 130, 240, 440, 730, and 830.

Item #22813The following changes were made to the Aleph UNIMARC normalization rules template:


2. Many fields were updated to improve support for Browse, including the display of cross-references. For more details, refer to the Support Browse in Normalization Rules section in the Primo Version 4.x Highlights document.

3. Field display/creator Note: Recommended Description: The rule for field 710 1_ (first indicator=1) – corporate body name – Meeting - has been added. The field was missing in the original template.

4. Field display/contributor Note: Recommended Description: The rule for field 701 – personal Name Alternative intellectual responsibility has been added. The field was missing in the original template.

5. Field display/contributor Note: Recommended Description: The rule for field 711 1_(first indicator=1) – corporate body name- Meeting – Alternative intellectual responsibility - has been added. The field was missing in the original template

6. Field display/contributor Note: Recommended Description: The rule for field 712 1_(first indicator=1) – corporate body name- Meeting –Secondary intellectual responsibility - has been added. The field was missing in the original template

7. Field search/creator/contributor Note: recommended Description: Rules for searching fields based on 701 and 711 have been added. In addition, a rule that copies the content of display/creator and display/contributor has been added.

8. Field facets/toplevel Note: recommended Description: A rule for the creation of the ‘Available in the library’ top-level facet has been created. This rule is based on the AVA subfield e. If its content is available or check_holdings, the ‘available’ constant is written.

9. Field facets/creator/contributor Note: Recommended Description: The rule for field 710 1_(first indicator=1) – corporate body name- Meeting –Primary intellectual responsibility - has been added. This field was missing in the original template

10. Field facets/creator/contributor Note: Recommended Description: The rule for field 711 1_(first indicator=1) – corporate body name - Meeting – Alternative intellectual responsibility - has been added. This field was missing in the original template

11. Field Field facets/creator/contributor Note: Recommended Description: The rule for field 712 1_(first indicator=1) – corporate body name- Meeting –Secondary intellectual responsibility - has been added. This field was missing in the original template

12. Field Additional data / Corporate Author Note: recommended Description: Fields 710 1_ and 711 1 have been added.

13. Field Additional data / Additional Author Note: recommended Description: Moreover field 712 1_ has been added.

14. Field Search / Additional title Note:recommended Description: Add rule to search into source unimarc field 410 $a, $e, $i (series) Add rule to search into source unimarc field 421 $a, $e (supplement) Add rule to search into source unimarc field 422 $a, $e (parent of supplement) Add rule to search into source unimarc field 423 $a, $e (Issued with Preceding entries) Add rule to search into source unimarc field 430 $a, $e (Continues) Add rule to search into source unimarc field 431 $a, $e (continues in part) Add rule to search into source unimarc field 432 $a, $e (Supersedes) Add rule to search into source unimarc field 433 $a, $e (Supersedes in part) Add rule to search into source unimarc field 434 $a, $e (Absorbed) Add rule to search into source unimarc field 435 $a, $e (Absorbed in part) Add rule to search into source unimarc field 436 $a, $e (Formed by merger of) Add rule to search into source unimarc field 437 $a, $e (Separated from) Add rule to search into source unimarc field 440 $a, $e (Continued by) Add rule to search into source unimarc field 441 $a, $e (Continued in part by) Add rule to search into source unimarc field 442 $a, $e (Superseded by) Add rule to search into source unimarc field 443 $a, $e (Superseded in part by) Add rule to search into source unimarc field 444 $a, $e (Absorbed by) Add rule to search into source unimarc field 445 $a, $e (Absorbed in part by) Add rule to search into source unimarc field 446 $a, $e (Split into) Add rule to search into source unimarc field 447 $a, $e (Merged with xxx to form)

Add rule to search into source unimarc field 448 $a, $e (Changed back to) Add rule to search into source unimarc field 451 $a, $e (Other edition in same medium) Add rule to search into source unimarc field 452 $a, $e (Other edition in a different medium) Add rule to search into source unimarc field 453 $a, $e (Translated as) Add rule to search into source unimarc field 454 $a, $e (Translated of) Add rule to search into source unimarc field 455 $a, $e (Reproduction of) Add rule to search into source unimarc field 456 $a, $e (Reproduced as) Add rule to search into source unimarc field 470 $a, $e (Item reviewed) Add rule to search into source unimarc field 481 $a, $e (Also bound with this volume) Add rule to search into source unimarc field 482 $a, $e (Bound with) Add rule to search into source unimarc field 488 $a, $e (Other related works) Add rule to search into source unimarc field 501 $a (Collective uniform title) Add rule to search into source unimarc field 510 $a $e (Parallel title proper) Add rule to search into source unimarc field 512 $a $e (Cover title) Add rule to search into source unimarc field 517 $a $e (Other variant titles) Add rule to search into source unimarc field 518 $a $e (Title in Standard modern spelling) Add rule to search into source unimarc field 531 $a $e (Abbreviated title) Add rule to search into source unimarc field 532 $a $e (Expanded title) Add rule to search into source unimarc field 545 $a $e (Section title)

15. Field: addata/metadata Note: Optional. An additional rule was added to create Metadata Type = 'journal' if the resource type is 'conference_proceeding' and the record has an ISSN. Otherwise, it will default to a book. See also #22807, which includes changes in the Metadata Type mapping table. This is relevant if your local data includes this resource type. Description: The following rule was added as the second rule: Source: PNX display/type Conditions logic: true Conditions relation: And Condition1 Logic: true

Source: search/issn Success if: Match last Validation: Input exists Transformation Write constant/journal Action: OR

16. Fields display/lds30, lds31, lds32 & search/lsr30, lsr31, lsr32 Note: Optional. These fields can be used if you have linked records from Aleph with PLK data in which subfields m and n are used. Note that the "Use local fields 30-39 as lateral links' parameter in General Configuration - Installation must be defined as Y. This is the default value. In hosted environments the parameter is enabled. Description: Rules for the display lateral links based on use of UP/DOWN/PAR type links in the PLK field have been added. The rules are disabled out of the box.


1. Field: display/type Note: Recommended. This rule creates the 'database' resource type based on the ECT field. Description: The following rules was added as the first first rule: Source: MARC/ECT a Conditions logic: true Condition1: Logic: true Source: MARC/ECT a Success if: Match last Validation: Lower case Check string equals string/database Transformation; Write constant/database Action: OR

2. Field: addata/metadata Note: Optional. An additional rule was added to create Metadata Type = 'journal' if the resource type is 'conference_proceeding' and the record has an ISSN. Otherwise, it will default to a book. This is relevant if your local data includes this resource type. See also #22807, which includes changes in the Metadata Type mapping table. Description: The following rule was added as the second rule: Source: PNX display/type Conditions logic: true Conditions relation: And Condition1 Logic: true Source: PNX display/type

Success if: Match last Validation: Check if string equals string/conference_proceeding Condition2: Logic: true Source: search/issn Success if: Match last Validation: Input exists Transformation Write constant/journal Action: OR


Item #22816The following changes were made to the DigiTool DC normalization rules template:

1. Field: search/enddate Note: Recommended. The rules for this field were missing from the template. They are required for proper date interval searching. Description: The following rules were added: Action: OR Rule 1: Source: XML/dc:date Transformations: Format year/9 Complete end date

Rule 2: Source: XML/dcterms:created Transformations: Format year/9 Complete end date

Rule 3: Source: XML/dcterms:dateCopyrighted Transformations: Format year/9 Complete end date

2. Field: addata/metadata Note: Optional. An additional rule was added to create the Metadata Type = 'journal' if the resource type is 'conference_proceeding' and the record has an ISSN. Otherwise,it will default to a book. See also #22807, which includes changes in the Metadata Type mapping table. This is relevant if your local data includes this resource type.

Description: The following rule was added as the first rule: Source: PNX display/type Conditions logic: true Conditions relation: And Condition1 Logic: true Source: PNX display/type Success if: Match last Validation: Check if string equals string/conference_proceeding Condition2: Logic: true Source: search/issn Success if: Match last Validation: Input exists Transformation Write constant/journal Action: OR

Item #22817The following changes were made to the DigiTool MARC normalization rules template:

1. Field: addata/metadata Note: Optional. An additional rule was added to create the Metadata Type = 'journal' if the resource type is 'conference_proceeding' and the record has an ISSN. Otherwise, it will default to a book. This is relevant if your local data includes this resource type. See also #22807, which includes changes in the Metadata Type mapping table. Description: The following rule was added as the second rule: Source: PNX display/type Conditions logic: true Conditions relation: And Condition1 Logic: true Source: PNX display/type Success if: Match last Validation: Check if string equals string/conference_proceeding Condition2: Logic: true Source: search/issn Success if: Match last Validation: Input exists Transformation Write constant/journal Action: OR


Item #22820The following changes were made to the Generic UNIMARC normalization rules template: 1. Field display/creator Note: Recommended. Description: The rule for field 710 1_ (first indicator=1) – corporate body name – Meeting - has been added. This field was missing in the original template.

2. Field display/contributor Note: Recommended. Description: The rule for field 701 – personal Name Alternative intellectual responsibility has been added. This field was missing in the original template

3. Field display/contributor Note: Recommended. Description: The rule for field 711 1_(first indicator=1) – corporate body name- Meeting – Alternative intellectual responsibility - has been added. This field was missing in the original template

4. Field display/contributor Note: Recommended. Description: The rule for field 712 1_(first indicator=1) – corporate body name- Meeting –Secondary intellectual responsibility - has been added. This field was missing in the original template

5. Field search/creator/contributor

Note: recommended. Description: Rules for searching fields based on 701 and 711 have been added. Moreover, a rule that copies the content of display/creator and display/contributor has been added

6. Field browse/author Note: recommended. Description: Some of the rules have been adjusted in order to create the elements required for the browse functionality. Added the $$E element. This rule was missing.

7. Field browse/subject Note: recommended Description: Some of the rules have been adjusted in order to create the elements required for the browse functionality. Added the $$E element This rule was missing.

8. Field: addata/metadata Note: Optional. An additional rule was added to create the Metadata Type ='journal' if the resource type is 'conference_proceeding' and the record has an ISSN. Otherwise, it will default to 'book'. This is relevant if your local data includes this resource type. See also #22807, which includes changes in the Metadata Type mapping table. Description: The following rule was added as the second rule: Source: PNX display/type Conditions logic: true Conditions relation: And Condition1 Logic: true Source: PNX display/type

Success if: Match last Validation: Check if string equals string/conference_proceeding Condition2: Logic: true Source: search/issn Success if: Match last Validation: Input exists Transformation Write constant/journal Action: OR

9. Field: links/linkstotoc Note: This is recommended if your institution subscribes to Table of Contents from Syndetics. Description: The source of the second rule was changed from 327 to 010 because the link to Syndetics is based on the ISBN.

10. Field: links/linkstoabsract Note: This is recommended if your institution subscribes to Abstracts from Syndetics. Description: The source of the rule was changed from 020 to 010 because the link to Syndetics is based on the ISBN.

11. Field: links/linkstoexcerpt Note: This is recommended if your institution subscribes to Excerpts from Syndetics. Description: The source of the rule was changed from 020 to 010 because the link to Syndetics is based on the ISBN.

Item #22821The following changes were made to the SFX normalization rules template:

1. Field: addata/metadata Note: Optional. An additional rule was added to create the Metadata Type ='journal' if the resource type is 'conference_proceeding' and the record has an ISSN. Otherwise, it will default to 'book'. This is relevant if your local data includes this resource type. See also #22807, which includes changes in the Metadata Type mapping table. Description: The following rule was added as the second rule: Source: PNX display/type Conditions logic: true Conditions relation: And Condition1 Logic: true Source: PNX display/type Success if: Match last Validation: Check if string equals string/conference_proceeding Condition2: Logic: true Source: search/issn Success if: Match last Validation: Input exists Transformation Write constant/journal Action: OR


Item #22822The following changes were made to the Unicorn normalization rules template:

1. Field: addata/metadata Note: Optional. An additional rule was added to create the Metadata Type ='journal' if the resource type is 'conference_proceeding' and the record has an ISSN. Otherwise, it will default to 'book'. This is relevant if your local data includes this resource type. See also #22807, which includes changes in the Metadata Type mapping table. Description: The following rule was added as the second rule: Source: PNX display/type Conditions logic: true Conditions relation: And Condition1 Logic: true Source: PNX display/type Success if: Match last Validation: Check if string equals string/conference_proceeding Condition2: Logic: true Source: search/issn Success if: Match last Validation: Input exists Transformation Write constant/journal Action: OR



1. Field: display/availlibrary Note: This is required if you want to control the order of the Primo locations based on the priority defined in Voyager. For more information, see the Location Priority for Aleph and Voyager (V4.8) section in the Primo Version 4.x Highlights document. Description: A rule was added at the end to create $$P from 949 $$p, which contains the priority of the location.

2. Field: addata/metadata Note: Optional. An additional rule was added to create the Metadata Type ='journal' if the resource type is 'conference_proceeding' and the record has an ISSN. Otherwise, it will default to 'book'. See also #22807, which includes changes in the Metadata Type mapping table. This is relevant if your local data includes this resource type. Description: The following rule was added as the second rule: Source: PNX display/type Conditions logic: true Conditions relation: And Condition1 Logic: true Source: PNX display/type Success if: Match last Validation: Check if string equals string/conference_proceeding Condition2: Logic: true Source: search/issn Success if: Match last Validation: Input exists Transformation Write constant/journal Action: OR


Item #22824The following changes were made to the Generic MARC normalization rules template:

1. Field: addata/metadata Note: Optional. An additional rule was added to create the Metadata Type ='journal' if the resource type is 'conference_proceeding' and the record has an ISSN. Otherwise, it will default to 'book'. This is relevant if your local data includes this resource type. See also #22807, which includes changes to the Metadata Type mapping table. Description: The following rule was added as the second rule: Source: PNX display/type Conditions logic: true Conditions relation: And Condition1 Logic: true Source: PNX display/type Success if: Match last Validation: Check if string equals string/conference_proceeding Condition2: Logic: true Source: search/issn Success if: Match last Validation: Input exists Transformation Write constant/journal Action: OR

2. Field: browse/title Note: This is recommended if the relevant fields contain subfield 0 with the authority record ID Description: Subfield 0 has been excluded from the source of the rules for the tags 130, 240, 440, 730, and 830.

Item #22825The following changes were made to the Aleph MAB normalization rules template:


2. Field: addata/metadata Note: Optional. An additional rule was added to create the Metadata Type ='journal' if the resource type is 'conference_proceeding' and the record has an ISSN. Otherwise, it will default to 'book'. See also #22807, which includes changes in the Metadata Type mapping table. This is relevant if your local data includes this resource type. Description: The following rule was added as the second rule: Source: PNX display/type Conditions logic: true Conditions relation: And Condition1 Logic: true Source: PNX display/type Success if: Match last Validation: Check if string equals string/conference_proceeding Condition2: Logic: true Source: search/issn Success if: Match last Validation: Input exists Transformation Write constant/journal Action: OR

Item #23345Added several data elements from the item records that are displayed by Primo in the Locations tab, which are returned by the ILS when OPAC via Primo is in use.

The following hidden elements have been added under the <div> element with the "EXLLocationTableActions" class:

<div class="EXLLocationTableActions"> <span class="EXLLocationTableActionsLabel">Select Request Option: </span> <input class="EXLLocationItemId" type="hidden" value=""> <input class="EXLLocationItemCategoryCode" type="hidden" value=""> <input class="EXLLocationMainLocationCode" type="hidden" value=""> <input class="EXLLocationSecondaryLocationCode" type="hidden" value=""> <input class="EXLLocationItemLoanStatus" type="hidden" value="f"> <input class="EXLLocationItemStatusCode" type="hidden" value=""> <input class="EXLLocationProcessingStatus" type="hidden" value=""> <input class="EXLLocationItemMaterial" type="hidden" value=""> <input class="EXLLocationItemBarcode" type="hidden" value=""> <input class="EXLLocationCallNumber" type="hidden" value=""> <div class="EXLLocationTableActionsMenu"> </div>

A description for each element and their mapping from the Aleph and Voyager DLF response is as follows: EXLLocationItemId - The ID of the item record. - Aleph: Aleph ADM library code + ADM record ID + item sequence. For example: PRM50001855894000010. - Voyager- The item record ID. For example: 695. EXLLocationItemCategoryCode - The code of the item category. - Aleph: Item status code (z30-item-status-code) Voyager: Item type code (typeCode) EXLLocationMainLocationCode – The code of the main location - Aleph: Sublibrary code (z30-sublibrary-code) - Voyager: Location code (locationCode)

EXLLocationSecondaryLocationCode – The code of the secondary location. - Aleph: Collection code (z30-collection-code) - Voyager: N/A EXLLocationItemLoanStatus – The loan status of the item. - Aleph: loan status (status) - Voyager: loan status (itemStatus) EXLLocationItemStatusCode – The item category name. - Aleph: item status name (z30-item-status) - Voyager: item typename (typeDesc) EXLLocationProcessingStatus – The item processing status code. - Aleph: item processing status (z30-item-process-status-code) - Voyager: N/A EXLLocationItemMaterial – The item material type. - Aleph: item material type (z30-material) - Voyager: item media type (mediaType) EXLLocationItemBarcode – The item barcode. - Aleph: (z30-barcode) - Voyager: (itemBarcode) EXLLocationCallNumber – The item call number. - Aleph: (z30-call-no) - Voyager: (callNumber)

Date post:	09-Feb-2016
Category:	Documents
Upload:	mariolgui68
View:	277 times
Download:	0 times

Primo SP 4.8.2 Release Notes

Documents