Document status

Area coveredCataloging, Systems
Lead Author
Co-authors

Marcus Jun (Unlicensed), Moon Kim (Unlicensed), Elizabeth Rallos, Jeremy Hobbs


Background

See Also: Brief Record Level Configuration (Acquisitions Task Force)

Policy Justification: Interim Policy on use of the “Do not override/merge a non-brief record with a brief version” flag in Alma import profiles


In the December 2014 release Ex Libris has added a flag to the import profile (found in the Match Profile tab) which when checked, will prevent a “brief” record from overlaying a “full” record. However, it has been determined that the existing algorithms for determining what is a brief record is not adequate for Alliance purposes. Therefore, it is Alliance policy for the time being that you should not check this flag.

With the Alma August 2016 release Ex Libris updated the algorithms used for determining the brief level record utilizing the brief level rules established. (see: Alma Brief Level Record Configuration) While testing did show that some of the functionality works as expected, it can be confusing to figure out when to use the setting and when using the setting could cause problems.

TSWG continues to recommend that you should not check this flag until Ex Libris can resolve the issues.

Our testing results have been shared with Ex Libris and the Alliance will work with Ex Libris through the COE Initiative.

Testing results are shared below, including when using the setting may work as expected.


Testing results:

Scenarios where functionality works as expected post August 2016 release:


Problems:


How this setting works (see Alliance documentation for more information):


History:

The 3-month implementation of Brief level rule in Alma has completed with the August release. You can read more about the history and settings of the Brief level rule in the NZ in the Alliance documentation. The brief level rule has been set in the NZ as detailed in the documentation. Brief levels were assigned to existing NZ records and all incoming records from Connexion or imports are assigned brief levels.


Further configuration and testing may result in changes to this policy.

Policy Statement

TSWG continues to recommend that you should not check this flag until Ex Libris can resolve the issues.

Best practice recommendations

Procedures in Alma

Detailed procedures are only necessary when other documentation is unavailable. Link to existing procedural documentation if it adequately demonstrates practice. If there is a need to indicate specific data input in order to obtain the desired result list as a procedure?  

Action log


SectionPoint Person

Expected Completion Date

Last action takenNext action required

Articulate the need for the policy (background)

person's name

 

9/15/16 - Met with the working group. Discussed that this is a policy being considered by the leads group?


Mallory will draft the need for the policy and send to the leads on 9/26/16. After review it will be sent to the working group listserv for approval/additions by 10/10/16.


Create a Policy Statement

person's name

 



Identify and create best practice recommendations

person's name


 



Where applicable, identify and write up procedures in Alma

person's name


 




Tasks to be completed