I support the inclusion of usage information (MARC 680) for display in association with a browse heading in Primo, but See Also references are problematic. The transfer of authority data from Alma to Primo is currently managed by having Alma bundle data from authorities into each PNX record that the authority is linked to. This would have the effect of making broader and related terms which may not be relevant to the bib item access points in Primo for that bib item. The intent of See Also references is that they should be represented as relationships between the topical terms themselves. Primo has to be able to harvest See Also references as something other than an extension for every PNX record's access data, and that requirement needs to be specified in the proposal. I'm very supportive of including See Also references in Primo--I just see perils in the easy path to implementing them.
Anonymous
I support the inclusion of usage information (MARC 680) for display in association with a browse heading in Primo, but See Also references are problematic. The transfer of authority data from Alma to Primo is currently managed by having Alma bundle data from authorities into each PNX record that the authority is linked to. This would have the effect of making broader and related terms which may not be relevant to the bib item access points in Primo for that bib item. The intent of See Also references is that they should be represented as relationships between the topical terms themselves. Primo has to be able to harvest See Also references as something other than an extension for every PNX record's access data, and that requirement needs to be specified in the proposal. I'm very supportive of including See Also references in Primo--I just see perils in the easy path to implementing them.