Norm Rule and Search Engine Configuration Procedures

Policy Statement

This policy describes the make-up and practices of the working group for norm rule changes (both MARC and non-MARC data sources) and search engine (SE) configuration. It addresses how changes to norm rules and SE configuration at the installation level are submitted, determined, implemented and communicated.

Best practice recommendations

1. The CSU Consortium Primo Norm Rules/Search Engine Team will be made up of four members selected by the ULMS Program Management Team. These members should represent four different CSU campuses. The membership of this Team should rotate at some regular interval.

2. This Working Group will be responsible for reviewing, testing, and implementing requests from CSU campuses for new Norm Rules for both MARC and non-MARC schemas and for Search Engine configuration changes. The Working Group will also maintain a current  list of all Primo NR and SE logic available online to all CSU campuses.

3. Norm rule and search engine configuration requests should be submitted to this group by all campuses using a google form. This form may be modeled on the norm rule request form currently used by the Orbis Cascade Alliance available at https://docs.google.com/a/sjsu.edu/forms/d/e/1FAIpQLSfY5SxV_afWGHdOu1AcOnftTcg1aLmd5CO5w0VnQn-7AOFhaw/viewform

4. The development cycle of the Working Group should be no less than 1 month and no more than 6 months so that requests are reviewed in a timely manner that is manageable to members.

5. The Working Group considers all requests within each cycle and sets priorities among requests, if necessary. Priorities should be set in discussion with COLD and the CSU Discovery Team.

6. The Working Group shares priorities with all CSU stakeholders through a system-wide communication tools. The Working Group may consider public posting of requests on a platform such as Trello, as used by the Orbis Cascade Alliance at https://trello.com/b/0xLGF2UT/nrwg-requests

7. The Working Group uses system-wide communication tools to collect feedback and discussion regarding requests within each cycle. This feedback, in combination with established priorities, is used to determine which requested changes to accept during the cycle.

8. For each accepted change the Working Group determines NR or SE logic and builds the change in the CSU Primo sandbox. Testing in the sandbox will be conducted by the Working Group with rebuilds performed as needed.

9. For each request that is not accepted, the Working Group provides communication and rationale to the requestor and/or system-wide stakeholders.

10. Once NR and SE changes have been successfully tested by the Working Group, the group announces an open round of sandbox testing to CSU stakeholders through system-wide communication tools. The announcement includes:

1. A list of changes being tested

2. A link to a testing guide

3. A link to a testing feedback form

11. CSU testing should be open for at least 2 weeks, during which feedback is collected using the feedback form provided.

12. Using the feedback, the Working Group provides a go/no go recommendation for each change to the Discovery Team.

13. The Discovery Team gives final approval for each change and determined the date of implementation in discussion with the Working Group.

14. The Working Group announces implementation using a system-wide communication tool. The announcement includes:

1. A list of changes being implemented

2. The date of the implementation

3. A link to documentation showing any Primo Back Office changes related to implementation

15. The Working Group implements the change in Primo production environment with the help of CO and EL staff as needed.

16. The change is logged on a public list of normalization and SE rules maintained by the Discovery Team.

Action log