Primo VE provide a job forcing a reindex recalculating also FRBR / View all versions grouping for a set of records or the whole catalogue
Sometimes wrong FRBR grouping are created and stay in the system until the scheduled six months indexing is performed.
There is a tool for fixing single records ( Dedup and FRBR Test Utility ) but a) it works for one record at time b) one needs to know exactly and in advance what records are wrong (and usually this is not the case).
We need therefore a job forcing a reindex and recalculating Dedup + FRBR / View all versions grouping for a set of records or the whole catalogue.
Luigi Siciliano
shared this idea
-
Stacey van Groll
commented
I suggest to test out the job to see if it works for the desired scenario, such as records in an existing FRBR group with rule change so that they will regroup and still be in FRBR groups but different ones, such as by choosing to run job with Prevent FRBR of No. I haven't tested that exact scenario, but you may find outcome with testing that it is a single job instance.
I have used it with scenarios like this though: Records are in a FRBR group and not in a DEDUP group. Rules are changed so that records will be in a DEDUP group. Test utility for an example tested shows message for DEDUP test of “Keys Match. Records are not connected in DB”. Run job with Prevent DEDUP No and FRBR blank. Outcome is that the records are now in a DEDUP group instead of a FRBR group. -
Luigi Siciliano
commented
Dear Stacey, thank you for pointing this out.
I am unsure If this 'Prevent FRBR and/or Dedup in Discovery' addresses our needs. I talking here about a scenario where records are already set to be FRBRized, but where the process was wrong and needs therefore to be done again.
Perhaps using 'Prevent FRBR and/or Dedup in Discovery' one may sets to No the records in the catalogue, and then to Yes later on, to force the process to be performed again. But I don't know if this could work and it's doubling the process of indexing...Luigi
-
Stacey van Groll
commented
There is the "Prevent FRBR and/or Dedup in Discovery" job.
The name is counterintuitive, but it offers both Yes and No options, with description: "Enables/disables the FRBR and/or Dedup processes on a set of bibliographic records."
Ex Libris might get upset if trying to run across all of your records at once, as perhaps might cause performance issues, but it states it's intended purpose of a set of records, so you could target to specific areas and work through them.